SharePoint designer hangs and eventually times out with an error.

SharePoint designer hangs and eventually times out with an error.

In SharePoint Designer there is an option to disable the preloading of site data…

File > Options > (General Tab) > Application Options:

By disabling the “Preload site data during the site open process” and restarting SharePoint Designer… everything now works.

Please test like everything.

Please let me know if this is helpful or you have any questions.

Thank you !

Abhi

SOAP message cannot be parsed

SharePoint list has 209 columns and there are 9 lookup columns and 19 calculated fields. With this list structure when you re-publish the InfoPath, SharePoint trying to update each item's property behind the scene and this operations times-out is logical with “SOAP message cannot be parsed” error.

To support more execution time override the executionTimeout <httpRuntime maxRequestLength="51200" executionTimeout="3000" /> in related web.config file. I tried with 3000 seconds and the update went through successfully.

Again this can be due to many reason - large list/calculated fields/number of views/applied master page and CSS- so please check your ULS log and Fiddler to get the exact situation.

Thank you !

ProcDump v7.01

ProcDump is a command-line utility whose primary purpose is monitoring an application for CPU spikes and generating crash dumps during a spike that an administrator or developer can use to determine the cause of the spike. ProcDump also includes hung window monitoring (using the same definition of a window hang that Windows and Task Manager use), unhandled exception monitoring and can generate dumps based on the values of system performance counters. It also can serve as a general process dump utility that you can embed in other scripts.

Download URL- https://technet.microsoft.com/en-us/sysinternals/dd996900.aspx

Tiny tool and you can run at client side - I was trying to test the this for SPD with the below syntax

1. Put the binary to c:\
2. Open DOS shell 
3. Use this command for SPD - procdump.exe -f "" -e 1 -w spdesign.exe > proc.txt
4. Open SharePoint Designer and open the site
5. Once done - Ctr+C to terminate the dump collection process
6. Open proc.txt and see the result for further analysis

Unable to parse page for field values: The 'mso:CustomDocumentProperties' start tag on line 2 does not match the end tag of

When you have upgraded from SP 2007 to SP 2010 and trying to access customized any .aspx pages you might receive the the below errors - 

1. List does not exist.  The page you selected contains a list that does not exist.  It may have been deleted by another user.

2.w3wp.exe (0x5C30) 0x62A8 SharePoint Foundation Performance btw0 Medium Unable to parse page for field values: The 'mso:CustomDocumentProperties' start tag on line 2 does not match the end tag of 'mso:PSD_x0020_Product_x0020_Mgr'. Line 354, position 7., pageContent = 

3. System.ArgumentException: Value does not fall within the expected range.

Unexpected       System.ArgumentException: Value does not fall within the expected range.    at Microsoft.SharePoint.Library.SPRequestInternalClass.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback pPagingCallback, ISPDataCallback pPagingPrevCallback, ISPDataCallback pFilterLinkCallback, ISPDataCallback pSchemaCallback, ISPDataCallback pRowCountCallback, Boolean& pbMaximalView)     at Microsoft.SharePoint.Library.SPRequest.GetListItemDataWithCallback2(IListItemSqlClient pSqlClient, String bstrUrl, String bstrListName, String bstrViewName, String bstrViewXml, SAFEARRAYFLAGS fSafeArrayFlags, ISP2DSafeArrayWriter pSACallback, ISPDataCallback ...   b38ad70a-09d7-420e-b3fc-d91ebbff39d9

You can try the below steps - 

1) Deactivate the features - publishing

2) delete the "Relationships List"

3) Activate the features using PowerShell. It creates the  "Relationships List" again

Or 

you can also try to copy the problematic .aspx page from explorer view and paste at the same location with different name and then browse it.

seems the below tag is automatically updated in copied page and it works -

<mso:_dlc_DocIdItemGuid msdt:dt="string">620c31d7-5d91-40d2-9c60-d08101fcc0d8</mso:_dlc_DocIdItemGuid>

Note - this is in my case so please first check the situation and error and then try these above options.

Thank you !

An SPRequest object was not disposed before the end of this thread.

An SPRequest object was not disposed before the end of this thread.  To avoid wasting system resources, dispose of this object or its parent (such as an SPSite or SPWeb) as soon as you are done using it.  Due to flags specified at object creation, this will not be freed until processed by garbage collection.  Allocation Id: {D7B164AB-A421-46AC-80C6-D119DBE511BB}  To determine where this object was allocated, set Microsoft.SharePoint.Administration.SPWebService.ContentService.CollectSPRequestAllocationCallStacks = true.


Solution - Related web application pool stop and start again and it works fine for me :)

Dissecting the Office Web Apps cache in SharePoint 2010

http://www.wictorwilen.se/Post/Dissecting-the-Office-Web-Apps-cache-in-SharePoint-2010.aspx

http://blogs.catapultsystems.com/IT/archive/2010/08/26/co-authoring-in-sharepoint-2010-explained.aspx

Feature upgrade incomplete for Feature 'PublishingWeb' (Id: '94c94ca6-b32f-4da9-a9e3-1f3d343d7ecb') in Web. Exception: A duplicate content type name "Resource" was found.

When the SharePoint Server Publishing Infrastructure is activated it creates this hidden list automatically. 

This list is hidden and can be accessed by going to this URL: http://portalsite/relationships%20list/allitems.aspx. What happens here since the SharePoint Server Publishing Infrastructure feature is already activated in the SP2007 environment and then moved over to SP2010 via DB attachment there is a conflict with a column in that list called GroupGuid.

In SharePoint 2007 the column name is GroupId and is type text, and is changed in SharePoint 2010 to GroupGuid with the same type text. For whatever reason this column type is not updated when migrated over. This column type needs to be set at GUID not text. Since there is no way within SharePoint to create a column with a GUID type the best way to fix the problem is to delete this list and have it automatically re-created. 

To successfully delete this list follow these steps.

1. Go to Site Actions, Site Settings and Site Collection features under Site Collection Administration.
2. Deactivate the SharePoint Server Publishing Infrastructure feature
3. Go back to http://portalsite/relationships%20list/allitems.aspx
4. Go to List, List Settings and Delete this list (If the SharePoint Server Publishing Infrastructure feature is not deactivated this option will not be visible)
5. After deleting the list go back to Site Actions, Site Settings, and Site Collection features
6. Activate SharePoint Server Publishing Infrastructure feature

Column Limit Exceeded

There are too many columns of the specified data type. Please delete some other columns first. Note that some column types like numbers and currency use the same data type.

when trying to reactivate this feature read this blog posting -

http://jshidell.com/2013/01/28/fixing-cannot-activate-sharepoint-2010-publishing-infrastructure-feature-column-limit-exceeded/ )

7. The SharePoint Server Publishing Infrastructure feature will automatically recreate the list.

Go back to http://portalsite/relationship%20list/allitems.aspx and verify that the column GroupGuid now has a column of type GUID instead of text.

            Now go back to the site you were trying to access and you should no longer get that error message                   “One or more field types are not installed properly. Go to List settings page to delete these                   fields”

SharePoint - Various way to get the size at the site collection and its various level

We have many times the requirement to get the size at various level in SharePoint – Hope the below information will help you !!

SharePoint Designer –

Specific feature of it – the ability to view the storage used for an entire site collection!

If you open up SharePoint Designer to the root site of your site collection, in the main window, once the site is opened under Site Information, that it will conveniently display the Total Storage Used of your entire site collection!

StorMan.aspx –

SharePoint 2010
Go to Site Actions -> Site Settings -> Site Collection Administration -> Storage Metrics, this will give you details on the usage – such as what sites, lists, libraries, and items are taking up the most space, however, it will not give you a total like our trusty SharePoint Swiss Army Knife – SharePoint Designer does, but, it will allow you to drill down into the usage.

PowerShell
$site = Get-SPSite http://my.sitecollection.com
$site.Usage;
$site.Dispose();

$site = Get-SPSite http://my.sitecollection.com
$site.Usage.Storage;
$site.Dispose();

Web Analytics
Go to Site Actions -> Site Settings -> Site Actions -> Site Collection Web Analytics reports

Once there, in the main screen, you can view a summary of the Total Storage Used under Inventory

And if you click on Storage Usage under Inventory within the quick launch navigation on the left, you can then view reports on storage utilization for your site collection, with a graph of the values so you can easily visualize the trend in storage usage.

You can also run reports for any date range since Web Analytics have been enabled, as well as run workflows against this data for alerting and reporting.

How to Restore from Unattached Content Database - Step by Step

1.Restore content database to a temporary location. Backup file is not enough, to use the unattached content database recovery you need the database mounted on a SQL server. This can be the same SQL instance used by SharePoint, or a different SQL box. If you restore into the same SQL instance make sure you (or your SQL DBA’s) use a different name for the restored database and don’t override the production content! Note the name of the SQL Server instance and the name of the database copy.

2.Go to SharePoint Central Administration, navigate to Backup and Restore and click the “Recover data from an unattached content database” link under Granular Backup.

3.Type the SQL Instance and temporary database names and specify what you want to do. Note that none of the available options actually allows you to restore a document, you can either create a backup of site collection or export a site or list. If you only need a single document, you’ll need to export the library in order to get it.

4.Select site collection, site and list to export. In this step you also specify the name for the export file and the export options, such as whether security and versions should be included in the export. You are ready to start the export.

5.Thank you ! you have completed the Unattached Content Database Recovery now! Wait, did you actually need that document? All you have is the export.cmp file, where to look next? There is no import available in the Central Administration UI. So what do you do next?

6.Start the SharePoint Management Shell, which is PowerShell with Microsoft.SharePoint.PowerShell snap-in already loaded. Then use the Import-SPWeb cmdlet to import the library. It is important to understand you cannot restore list or library under a different name. If a document library with the same name already exists in the destination site, import will merge contents and by default create new document versions where possible.

7.Finally, browse to the imported library and get the document you just restored. Once this is done, you can safely delete the imported document library from SharePoint, and delete the temporary database from SQL server.

Debugging/Troubleshooting Office Web Apps

Debugging

Use WireShark to capture traffic on the SharePoint server.
Use a Text Differencing tool to compare if web.config files on WFEs are identical.
Use Fiddler to monitor web traffic using the People Picker. This will provide insight in how to use the people picker for custom development. Please note: the client People Picker web service interface is located in SP.UI.ApplicationPages.ClientPeoplePickerWebServiceInterface.

Troubleshooting Office Web Apps
http://social.technet.microsoft.com/wiki/contents/articles/16640.sharepoint-2013-tips-for-troubleshooting-search-suggestions.aspx , troubleshooting search suggestions.
http://technet.microsoft.com/en-us/library/jj906556.aspx This link is external to TechNet Wiki. It will open in a new window.  , troubleshooting claims authentication.
http://technet.microsoft.com/en-us/library/dn169566.aspx This link is external to TechNet Wiki. It will open in a new window.  , troubleshooting fine grained permissions.
http://social.technet.microsoft.com/Forums/sharepoint/en-US/02b78299-bc7f-448b-b233-f9cae0da8466/sharepoint-2013-alerts-are-not-firing-any-mails-for-the-normal-alerts-and-search-alerts-can-someone , troubleshooting email alerts.