The SPListItem provided is not compatible with a Publishing Page

Problem description:

I was facing this error while submitting information via list view webpart, additionally problems with the check-in – checkout functionality.

Note:

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Error message:

The SPListItem provided is not compatible with a Publishing Page

ULS Logs Findings:

System.ArgumentException: Invalid SPListItem. The SPListItem provided is not compatible with a Publishing Page.    at Microsoft.SharePoint.Publishing.PublishingPage.GetPublishingPage(SPListItem sourceListItem)     at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageStateControl.RaisePostBackEventForPageRouting(String eventArgument, SPRibbonCommandHandler control, RaisePostBackEventDelegate raisePostBackEventDelegate)     at Microsoft.SharePoint.Publishing.Internal.WebControls.PublishingPageCheckinHandler.RaisePostBackEvent(String eventArgument)     at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)     at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)b3c1032c-e249-4879-82f6-02e4b3db028c

Troubleshooting done:

o   Checked the ULS logs

o   Tried changing the master page but didn’t resolves the issue

o   Checked with different templates but that also showed the same error message

o   Tried replicating on different web application but same results i.e. same error!

As you can see the error message itself saying that there is some relation with the publishing functionality so what you can do to resolve this issue? Here are the details.

Resolution#1:

1.   Open your SharePoint site

2.   Site actions

3.   Site Settings

4.   Manage site features

5.   Deactivate “Publishing Infrastructure” feature – scope is WEB

Once that done, we need to repeat the same steps at the site level (scope is different)

1.   Site ->Site actions->Site settings

2.   Site collection administration

3.   Site collection features

4.   Deactivate “Publishing Infrastructure” feature

Bottom line: we have deactivated “Publishing Infrastructure” feature at the web as well as site level.

Now, let’s re-activate the same feature one by one (order will be different this time) i.e. site scope first and then web scope.

If the above steps don't resolves the issues then please use the following script to resolve it.

Resolution#2:

$web = get-spweb "http://site-collection/URL-of-the-problem-site"

$correctId = $web.Lists["Pages"].ID

$web.AllProperties["__PagesListId"] = $correctId.ToString()

$web.Update()

$web.AllProperties["__PublishingFeatureActivated"] = "True"

$web.Update()

That’s it – done! –

Product Applies To:

v  SharePoint 2010

v  SharePoint 2013

InfoPath form library forms cannot be filled out in a Web browser

Today I was monitoring the SP servers along with some regular sanity checks that need to be carried out on daily basis. While doing that, I noticed one error based on this InfoPath rendering in the Health check analyzer!  But let me tell guys InfoPath is perfectly working in our environment without any issues and nobody has reported any incident also then why this error is showing in the health analyzer? – you must be thinking the same but no need to worry about as this is not a big one which will take lot of your time, some minor checks and you are done.

Error message:

InfoPath Forms Services forms cannot be filled out in a Web browser because no State Service connection is configured.

If this is your new configuration then you need to follow this existing official documentation from Microsoft which is pretty awesome!

http://technet.microsoft.com/library/ff805082.aspx

In our case, we have already done this configuration long time back and as I said, it’s working fine. The error message is little bit misleading one as its asking you to check the “state service” service application to be online or not but that’s not the case. We have already configured this service application long time back so where exactly the issue is and why it’s throwing the error?

Let me tell you the trick which we sometimes ignored – Look out the error in the HAL rule – see the below:

You will notice that it’s also giving you the URL of the web application for whom its failing and name of the servers also.

In our case, we have recently created a new web application in the farm and its been reflected in that! What it means? Pretty simple – the ‘state service’ service application is not configured for the same.

So what we need to do now for this re-association? Here are the details:

Resolution:

1.   Open the central Administration

2.   Application management

3.   Service applications

4.   Configure service application associations

5.   Select the web application for whim it’s failing

6.   Click on custom

7.   It will open the service application options

8.   Select the state service check box and click OK

Once you are done with the above steps then come back to health analyzer list, click on the same rule and hit “Reanalyze now” – that’s it, you are done.

Product Applies To:

o   SharePoint 2010

o   SharePoint 2013

o   SharePoint Foundation 2013

o   SharePoint Foundation 2010

Cannot uninstall Language Pack 0 because it is not deployed

SharePoint 2013 is really a good product w.r.t. functionality and awesome GUI to work with! But today’s article is based on the error that I faced while updating the solution.

IMP NOTE:

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Here is the error message:

Cannot uninstall Language Pack 0 because it is not deployed when attempting to uninstall-spsolution

One thing we always need to understand is the logic would be same for the functionality irrespective of which SharePoint version you are working!

What’s that funda? – Here we go:

If you are facing this error message then I would suggest checking the status of your solution in central administration. How to check this? Here are the details:

o   Central Administration

o   System Settings

o   Manage Farm Solutions

o   It will open the solution management

o   Here you can check the status of your solution

If your solution is showing updating, deploying or retracting status then first and top most check that you need to verify the status of your TIMER JOB across all WFE’s.  How to check this? – Here are the details:

o   Login to your web front end (WFE)

o   Start

o   Run

o   Type “services.msc” and hit enter

o   It will open the services console

o   Click on any service and press S

o   It will directly show you the SharePoint Services

o   Second service will be SharePoint Timer Service

o   Check the status across all your servers

Two outcomes will be there:

1.   Timer service will be stopped one of the server:

If this is the case then start the timer job on that specific server and check the results by executing the commands that you are using.

2.   Timer service is started on all the servers:

If this is the case then restart all the SharePoint Timer Services across all servers. Once this done then execute the commands that you are doing and check the results

Details notes:

Add-SPSolution

Add-SPSolution -LiteralPath c:\nameofyoursolution.wsp

Install-SPSolution

Install-SPSolution -Identity nameofyoursolution.wsp –GACDeployment

Uninstall-SPSolution

Uninstall-SPSolution -Identity nameofyoursolution.wsp

Remove-SPSolution

Remove-SPSolution -Identity nameofyoursolution.wsp

Update-SPSolution

Update-SPSolution -Identity nameofyoursolution.wsp -LiteralPath c:\nameofyoursolution.wsp -GACDeployment

If you have any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Product Applies To:

o   SharePoint 2013

o   SharePoint 2010

o   SharePoint 2007

Wow, that's a big workbook. Unfortunately, we can't open a workbook larger than 10 MB. You'll need to open this in Excel.

Problem description:

One user has reported an issue where he was getting an error while accessing the excel files from SharePoint site.

Before contacting the user, I tried uploading one dummy excel file to check the behavior and it works fine so I thought it might user who is doing some mistake. Further probing on the issue, I got the following details.

Entities:

1.   SharePoint 2013

2.   Excel 2013 / Office 2013

3.   Internet explorer 8.0

How to reproduce this error?

a)   Upload your excel document in the document library

b)   Try to open this document by directly clicking on it or excel dropdown ->view in browser.

c)   You will get the following error:

Error Message#1:

Wow, that's a big workbook. Unfortunately, we can't open a workbook larger than 10 MB. You'll need to open this in Excel.

Error message#2:

Couldn't Open the Workbook. Wow, that’s a big workbook. Unfortunately, we can't open a workbook larger than 10MB. You'll need to open this in Excel.

Error message#3:

The form submission cannot be processed because it exceeded the maximum length allowed by the web administrator. Please resubmit the form with less data.

Resolution:

a)   Central administration

b)   Application management

c)   Service applications

d)   Manage service applications

e)   Excel Services Application

f)    Trusted File locations

g)   Select the document library where your web part is failing

h)   Refer the section named as “workbook properties”

i)     Change the maximum workbook size

j)    By default its 10MB

k)   Change it to 50MB / 100MB as per your requirement

l)     Click OK.

Product applies to:

1.   SharePoint 2013

2.   SharePoint Foundation 2013

3.   SharePoint 2010

4.   SharePoint Foundation 2010

Access denied by Business Data Connectivity - BCS - Resolved

Create an External Content type based on backend SQL Server Database and create an External list based on it.

Open the Site in SharePoint Designer 2010: http://portal.contoso.com

Provide username and password in the promotion for open the site

Opening the site http://portal.contoso.com by communicating with the Web service

Retrieving External Content type Report

Create new external content type: Define General Properties for External Content type

Content type name: Contact; Name Space: http://portal.contoso.com; Office Item Type: Contact; Enable offline Sync to External list 

External System: Click here to discover external data sources and define operations 

Add Connection 

Managing Connections to external data sources and the operations for this external content type

External Data Source Type Selection: SQL Server -> Open the SQL Server Connection

SQL Server Connection: Populate the Database Server and Database name in the box

 Navigate to the appropriate database (AdventureWorks) and scroll through the required table (Contact)  

Table: Verify the available operations for that table

Operations for External content type means action that can be performed on the data associated with the external system -> Click on Create all Operations

Specify the parameters for the Operation

Example: Get the “Last Name” parameter-> Office property: Last Name; Check the Show in Picker box.

Filter Parameter Configuration

Add Filter Parameter: Add a Limit filter to the Query Item List Operation

Add Filter Type: Limit (Strongly Recommended to add a filter of type ‘Limit’ for this operation type)  

Filter Filed: None; Default value given as “100” for the limit filter type

Save the Content type to the Business Data Connectivity Metadata Store

Create an External List for the External Content type

External List : Business Contacts ; System Instance : AdventureWorks

External List: Business Contacts Created

Set Business Connectivity Store Permissions

List and Libraries -> External List-> Business Contacts -> Open Preview in Browser

Access is being denied by Business Data Connectivity Service (Reason: There is no permission for viewing this list)

Set the permission: Open CA->App mgmt. ->Manage Service Applications-> Business Data Connectivity Service->Manage->Set Metadata Store Permissions 

 Add Contoso\Administrator and feed all the (Edit, Execute, Selectable in Clients, Set Permissions) permission to the user.

Propagate permissions to all BDC Models, External Systems and External Content types in the BDC Metadata Store.

Work with External Content type in the Browser: Navigate to the http://portal.contoso.com

List will display with the no permission error now

Edit Item: Edit any of the lists and include any data in the list.

Example: Data Included in one of the List

Product Applies To:
- SharePoint 2010
- SharePoint 2013