Failed to create the Pages library – SharePoint 2010

When try to create a new site ( Publishing Site ) under your site collection Event log message was: ‘Failed to create the ‘Pages’ library.’.
Exception was: ‘Microsoft.SharePoint.SPException: User cannot be found.
at Microsoft.SharePoint.SPUserCollection.get_Item(String loginName)
at Microsoft.SharePoint.Workflow.SPWorkflowNoCodeSupport.LoadWorkflowBytesElevated(SPFile file, Int32 fileVer, Int32& userid, DateTime& lastModified)

the error caused by the user who created the latest revision of the workflow no longer exists in the site collection.

1) Download and install Sharepoint Designer 2010 if you already do not have it on your system.

2)In Sharepoint Designer, please open the root web

3)Go to All files > _Catalogs> wfpub

4)Check out and then Check in all Publishing Workflow configuration files:

5)De-activate and re-activate the publishing Feature from Site Settings

Important: Please proceed with a full farm backup before proceeding with this . It would also be beneficial for your users if you could implement the action plan outside of your regular business hours.


The settings for this list have been recently changed. Refresh your browser before editing this list

Hello Everyone,

In this article,i am going to talk about one of SharePoint development issue with object model if you faced this annoying error :
“The settings for this list have been recently changed. Refresh your browser before editing this list”

Here a sample scenario:
* You have a C# application from which you are frequently uploading documents to a SharePoint Foundation 2010 Document Library while updating or deleting the list item getting this error.

You may encounter possible 3 issue:

1) Your event recievers is executing something wrong.
Check your event handlers code. for detect the problem you may try to remove the event reciever(s) and test that issue is happening again.
It may cause by some buggy code belongs to triggered eventreciever or this event reciever has activated more than one time or not an appropriate time.if you have this kind of issue
i suggest  that use SPEventReceiverBase.EventFiringEnabled property to prevent unnecessery code execution when your event recievers triggered.

2) You may changing some  property of a list which is not to done in item level operations.
somehow you change high level setting or property of this list object  like SPList.EnableThrottling property , by design you should get fallowing error “The settings for this list have been recently changed. Refresh your browser before editing this list.” This is same scenario as while UserA who already editing a document metadata , changing Versioning settings of the current list by an administrator, UserA will get the error when he/she try to save his/her changes.

Check your source code for to be dangerous changes of list settings.So there is not any way to escape from this error while changing this kind of settings .Main rule is simple do not change list settings while you are working on list items.

3) It caused by a bug. Consider the following scenario:

  • You click the Variation link to configure the variation setting in a Windows SharePoint Services 3.0 publishing site.
  • You click the Variation Labels link to create two variation labels.
  • You click the Create Hierarchies link to create hierarchies.
  • You create a new publishing page in the source variation site.
  • You publish the new publishing page, and then you wait until the page propagation ends.
  • You edit the page in the destination variation site, and then you try to save it.

In this scenario, you receive the following error is fixed by June CU 2011

If you have another one , please inform me .)

“The specified database is not a valid synchronization database” issue

Good Day Everyone,

Let me guess , if you are reading this article possible you may in the middle of a restore or migration issue and not able to restore User Profile Service Application .
This warning means you can not restore old sycronization database (default name is Sync DB) .This is a by design issue and you do not allowed to do it. that’s why you are getting fallowing warning.  For resolution just create a new Syncronization database. Don’t worry about the content in it because SharePoint will rebuild it once you configured User Profile Service Application correctly.


Sharepoint 2010 Restore problem with SqlException The restart-checkpoint

Object <Content Database> failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory. SqlException: The restart-checkpoint file ‘Drive:\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\xxxx.CKP’ could not be opened. Operating system error ‘3(The system cannot find the path specified.)’. Correct the problem, or reissue the command without RESTART. RESTORE DATABASE is terminating abnormally.

When SQL Server has been installing , it creates a default SQL Server Database backup folder like ‘Drive:\MSSQL10_50.MSSQLSERVER\MSSQL\Backup’

This error occurs that the BACKUP or RESTORE process needs to create a checkpoint file that will indicate at what point any failure occurs. This allows the WITH RESTART option to be used . The WITH RESTART option specifies that SQL Server should restart a restore operation that has been interrupted and continue restore operation where the interruption has occured . The information about how much data the BACKUP or RESTORE command had processed before the interruption occurred is stored in a checkpoint file in the BACKUP directory like ‘Drive:\<SQL INSTANCE>\MSSQL\Backup

The checkpoint file is a temporary file, deleted when the restore process is completed, and is normally placed in the default backup folder.

Some of the reasons the checkpoint file cannot be created :

– The “backup” directory does not exist under the directory where SQL Server is installed.
– The drive where the “backup” directory resides is full.
– The “backup” directory is not accessible to the SQL Server account.

For fixing the issue you may check fallowings.

– Verify that the BACKUP directory exists under the directory where SQL Server is installed. If it does not exist, create it.
– Verify that there is available space on the drive where the BACKUP directory resides.
– Verify that the SQL Server startup account has permission to read from and write to the BACKUP directory.

This error has a limited impact and does not prevent a restore operation from succeeding. This error message occurs when a restore is interrupted, and the checkpoint file that is used to restart a restore is not written, or the checkpoint file is not written correctly. If you receive this error, it means that, if for some reason the restore operation is interrupted in the middle of the process, you have to restart it from the beginning of the backup file rather than the checkpoint file.

Check fallowing KB articles for more information :






Problem about Reporting Service (SSRS) for SharePoint 2010 Integration

Recently i faced fallowing error and decided that write about an article about SSRS with Sharepoint Integration because of MSDN articles is very detailed but sometimes the people can miss the basic points.Lets see what we faced:

The configuration parameter SharePointIntegrated is set to True but Share Point Object Model cannot be loaded.

System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ or one of its dependencies. The system cannot find the file specified. File name: ‘Microsoft.SharePoint, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ at Microsoft.ReportingServices.SharePoint.Objects.RSSPImpSecurity.set_StaticCatchAccessDeniedException(Boolean value) at Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelper..ctor() at Microsoft.ReportingServices.SharePoint.Server.SharePointServiceHelperFactory.get_ServiceHelper() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. . (rsSharePointObjectModelNotInstalled) Get Online Help

The cause of the problem is the server which SSRS installed has not  sharepoint installation.SSRS server and the sharepoint technology instance are on separated machines.If you deep in MSDN articles you can find fallowing informations :

You plan to immediately install the Reporting Services Add-in and configure report server integration settings on the SharePoint site. If the report server provides report processing capability to a SharePoint farm, you must also install a SharePoint Web front end on the report server computer so that you can join it to the farm
“For deployments that include a SharePoint server farm, install a SharePoint Web front-end on the report server computer. The Web front-end joins the report server computer to a SharePoint farm. Installing the Web front-end on the report server computer is only necessary if you deploy the report server and the SharePoint technology instance on separate computers.”
Configuring Reporting Services for SharePoint 2010 Integration

So the SSRS server must be a member of the sharepoint farm. In order to join the farm, the farm must aware of the SSRS server. So we need to install the sharepoint web front-end on the SSRS server to make it able to communicate with other machines.

Please check for more info:
Requirements for Running Reporting Services in SharePoint Integrated Mode


Excel Service can not display workbooks in Sharepoint 2010

Hi Everybody,

I have recently faced for a strange issue about displaying excel workbooks on Sharepoint 2010 .
When i checked the uls logs we have multiple exceptions like.

Stack trace: onetutil.dll: (unresolved symbol, module offset=00000000000A1A7D)
at 0x000007FEEFD71A7D onetutil.dll: (unresolved symbol, module offset=00000000000A2C3D)
at 0x000007FEEFD72C3D owssvr.dll: (unresolved symbol, module offset=0000000000008FA2)
at 0x000007FEE9A58FA2 owssvr.dll: (unresolved symbol, module offset=0000000000048C74)
at 0x000007FEE9A98C74 mscorwks.dll: (unresolved symbol, module offset=00000000002BF6D7)
at 0x000007FEF365F6D7 (unresolved symbol, module offset=00000000000EC86B)
at 0x000007FEEB45C86B (unresolved symbol, module offset=0000000001AB6942)
at 0x000007FEED476942 (unresolved symbol, module offset=0000000001A7ADED)
at 0x000007FEED43ADED (unresolved symbol, module offset=0000000001A7CF66)
at 0x000007FEED43CF66 (unresolved symbol, module offset=0000000001A7FA31)
at 0x000007FEED43FA31

An internal error occurred.
at Microsoft.Office.Excel.WebUI.ExcelWebRendererControl.InternalPreRender()
at Microsoft.Office.Excel.WebUI.Utils.ExecuteWebEventHandler(CoreWebEventHandler coreWebEventHandler, CoreWebEventHandler baseClassHandler, Object param, IMainControl mainControl)

Utils.ExecuteWebEventHandler: unexpected exception System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Office.Excel.WebUI.ExcelWebRendererControl.InternalPreRender()
at Microsoft.Office.Excel.WebUI.Utils.ExecuteWebEventHandler(CoreWebEventHandler coreWebEventHandler, CoreWebEventHandler baseClassHandler, Object param, IMainControl mainControl)

Watson bucket parameters: SharePoint Server 2010, ULSException14, 5f9be61a “excel services application”, 0e00178d “14.0.6029.0”, 13ed43ce “”, 0e00178b “14.0.6027.0”, 4da5bd73 “wed apr 13 18:12:51 2011”, 000009ca “000009ca”, 000000e9 “000000e9”, 4a6d3421 “nullreferenceexception”, 62646b69 “bdki”
The file that i want to open have url like
But  the important one is in logs   in this correlation that unrelated information log not the exceptions. This info is about :
“There is no Web named “/SiteDirectory/BlogContent/Lists/Categories/AllCategories.aspx”. in first i ignored it quickly. Than i realized that article:

Excel Calculation Service cannot display workbooks if no root site collection is created for a web application.

The sharepoint version which i was working on it is before Oct 2011 CU . The Solution is simple install at least Oct 2011 CU for fixing these errors.