01 June, 2013

SharePoint site are slow intermittently: SharePoint 2010.

Issue: We have been experiencing intermittent slowness on the SharePoint Farm.

Background: We are getting intermittent partial outage on the SharePoint Farm. We have assigned dedicated set of WFE’s for different set of web applications and all of sudden without any alert or alarming, user started reporting that SharePoint is taking long time to load or its keep on clocking. Lead time for the sites is min 3-5 min.


We have checked if this issue is occurring for an individual user. It was happening for the large number of groups and people and not region specific.

We have checked on the specific server and sites are slow on the web servers as well.

We have checked on the SAAS, SCOM Alerts and Site Scope system from HP, however, no alert was triggered.

No blocking reported on the SQL server.

From server Event logs we only see an error message that “Cannot connect to SQL Server .”

Temporary Resolution: As a temporary resolution we had recycled the app pool on the webserver running that applications and it worked fine. However, I was not sure that there would be a huge service destruction coming in the next coming day.

You know what; this issue started occurring three to four times a day. And recycling app pool was not the correct choice always.

Permanent Resolution: So one day we have decided to involve the SQL Team as we see from the Event Logs that we get an Error message “Cannot connect to SQL ”.

Based on the MS analysis, we saw there were so many page latches on the TEMP DB by running the sys.dm_os_latch_stats and see what type of latches have increased contention and wait types, compared to previous base-line.

MS recommended splitting the 20 GB of Temp DB in smaller chunks. We divided Temp DB in 5 GB in size with 4 Databases on each SQL Server we have in the farm.

KB Article which support this resolution: http://support.microsoft.com/kb/307487.


Diagnosing and Resolving Latch Contention on SQL Server: http://www.microsoft.com/en-in/download/details.aspx?id=26665

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.

Applies to:  SharePoint Foundation Server 2010, SharePoint 2010, SQL Server 2005 and SQL Server 2008.

30 May, 2013

Invalid field name {} _layouts/changesitemasterpage.aspx: SharePoint 2007.

Issue:  User reported that one of the sub-site on his site is not using the same layouts as of on the Parent site.

Background: We have a branding feature activated on all the site collection we create in the environment. However, when browsing the sub-site it was opening with the default look and feel of the SharePoint 2007 site.


Tried to open the master page gallery, but only default.master page was showing.

Checked to open the Changesitematerpage.apsx page, however, got the above error message.

Checked feature Office SharePoint Server Publishing on the sub-site level and it was deactivated.

Checked feature Office SharePoint Server Publishing Infrastructure on the site collection level and it was also deactivated.


Activate the Office SharePoint Server Publishing Infrastructure feature from the site collection level features list and Office SharePoint Server Publishing feature from the sub-site level features list.

Select the appropriate master or branding page from the list.

Click ok, and try to browse the site. It should be having the same template as of the parent site.

You would also have the option to deactivate the both of the features from the site collection and site levels.

Applies To: SharePoint Server 2007, WSS 3.0 

27 May, 2013

Issues with SharePoint Audit Logs Reports after migration from SharePoint 2007 to SharePoint 2010.

Problem Description: While saving an audit logs to a library user is getting “An Unexpected error has occurred” following a correlation.

Error Message: An unexpected Error has occurred.


We have checked this Audit logs settings and it was enabled.

We have run all the reports one by one and all of them were having problem.

There is only site which was having issue.

Based on the correlation ID in the error message, Checked the ULS logs from the server and found the below logs.


Tried Goggling on the same issue with the keyword: System.InvalidCastException: Specified cast is not valid. at Microsoft.Office.RecordsManagement.Reporting.ReportData.GenerateNextReport().

Found only one reference which talks about the resolution: 

Resolution Steps:

Go to Site Actions.

Choose to select Site Settings.

Under Site collection administration tab.

Choose to select Site collections features.

Look for Reporting feature. (It should be activated by default).

Click Deactivate and a warning message would appear, Select Deactivate this feature.

You will be taken to the site collection administration Feature list. Choose to click Activate. 

And now try to run the Audit Logs Report and now you should be able to save the reports to desired library.

Note: You should have the site collection rights to perform the above given steps.

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.

Applies to: SharePoint Foundation Server 2010, SharePoint 2010.

Unable to view items in the document library and list after migration: SharePoint 2010

Issue: One of my clients was having a very strange behavior where he was not able to view few of the items in his SharePoint list or Library.  


Checked the permissions on the library and list level. 

User was having full control permissions.

Tried removing and re-adding them to list and site, no success.

This issue was not happening at my end as I have FARM admin rights.

Tried login on client machine in SharePoint site with my credentials and issue still exist.

Tried login on my machine in SharePoint site with client credentials and issue was not there. 

Based on the above steps performed this is clear that this is machine specific issue.

Tried various things on the client machine such as clear IE cache, Resetting to default settings, Adding the site to trusted zone. But no success.


Go to Start.
Open Run command type CMD.
This will open command prompt for you.  
Type ipconfig /flushdns and it will flush domain name server cache from you system.  

Reboot your machine and try to access SharePoint list or document library items.
It should work for you now.

I am not sure, how this resolution had resolved the problem and what it has to do with the issue. But it finally worked and we have a happy customer.

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.

Applies to: SharePoint Foundation Server 2010, SharePoint 2010.