Archive Page 2


SharePoint 2013: The server was unable to save the form at this time. Please try again.

I got this message, “The server was unable to save the form at this time. Please try again.” when trying to create a folder on a document library.  A quick search found this article where I found that restarting the "Sharepoint Search Hosting Controller" service fixed the problem.  That was weird!



Oops! I Accidentally Uploaded a Document to My Winshuttle Query Scripts Library

In my new job and new role, I’ve entered the world of Winshuttle, a suite of apps that allow you to easily and non-technically integrate SharePoint Workflows (created with Winshuttle Studio) with SAP transactions, to effectively eliminate the “swivel-chair” integration that often occurs between two systems.  However, like any application, there are things that occur that are unplanned…and this is one of them!

If you find you “accidentally” uploaded a document to the Query Scripts library (a system library on Winshuttle Central), you’ll find that trying to delete it will throw the error: 

“An internal error occurred while doing this action. Object reference not set to an instance of an object.”

How can you delete it?



Edit the properties of the offending file and change the Content Type from eShuttleBase to one of the others (I believe I chose BaseQueryDoc, but I believe QueryFileDoc or MetaInfoQueryFileDoc will also work).  You should then be able to delete the file and happily send it on its way to the SharePoint recycle bin!



Remove-SPUser PowerShell Command: How to Use it in SharePoint 2013

I was trying to use the Remove-SPUser cmdlet and kept getting this error:

Remove-SPUser : You must specify a valid user object or user identity.


With claims based authentication the cmdlet Get-SPUser returns all users like this:


So, you can see the format of the –Identity (UserLogin) is something like this:


This thread referred to the Get-SPUser cmdlet and using New-SPClaimsPrincipal, but what I found was pretty simple.

Use this format for the cmdlet:

Remove-SPUser -identity "i:0#.w|cfgmgt\rwright" -web http://cmsp2013:5555

The trick for me was to put double quotes around the encoded user name.

Now, if the Microsoft documentation would be more accurate…


Create MS Access View Missing after Installing Hotfix KB2553170

Windows 7 SP1, Office 2010, accessing SharePoint 2013 on both Office 365 and on-premises.

You might find you have an issue when attempting to create an Access view from SharePoint 2013.  In this case I was getting an error when I clicked on Access View, "Export to database failed. To export a list, you must have a Microsoft SharePoint Foundation-compatible application."


I found an article where this error was being discussed.  There was a hotfix issued in December 2013 that addressed the issue.  However, after installing the hotfix, I found the Access View link on the create view page was missing.  This required performing an Office 2010 repair (from Programs and Features) by selecting Change on Office 2010.


After doing this and rebooting, the link was back…and it worked!  This is the 2nd time in the last week I’ve had to perform an Office 2010 repair.  I think it all started when I installed SharePoint Designer 2013 on this machine (it already has SPD2007 and SPD2010).

Hey Microsoft, stop breaking your software!


Opening Office Document Information Panel with Managed Metadata Causes Application to Crash

Every time I opened a Word document (or tried to create one) using a content type in SharePoint 2013 that had a managed metadata column and the document information panel was displayed, Word would crash.

This was happening on both my Windows 8.1 Lenovo Yoga that has Office 2010 and Office 2013 and My Windows 7 Dell D830 that has Office 2010.  Both of these machine had SharePoint Designer 2013 installed on them, in addition to SPD 2007 and SPD 2010.

I found this post from L.L that seemed to address my problem.  It appears that running an office repair fixes the issue.  Yay!

I guess the last one you repair (Office 2013 or Office 2010) is the one that gets registered as the default application.  Which is okay by me, because I am constantly annoyed by the ditching of skeuomorphism and replacement of flat design found within Office 2013.

Keywords:  Office 2010, Office 2013, SharePoint 2013, Managed metadata, Content types, Crash, MS Word 2010, MS Word 2013.


Changing Host Header for the MySite Host in SharePoint 2013

Update for SharePoint 2013:

I recently set up a SharePoint 2013 site and provisioned the MySite host as "" when I should’ve used something like ""

In order to fix this, it’s very similar to fixing it in 2007. 

Change the alternate access mapping.


Edit the default zone URL.


Edit the Site Binding in IIS to reflect the new host header.


Manage Service Applications


Click on your User Profile Service Application to manage it.


Go to Setup My Sites.


Change the My Site Host location.


IISReset and you should be good to go.


Hey, and if you want to change the name of the web application so it matches (I know, I know…it’s a bit anal, but I’m kinda’ OCD), here’s some PowerShell.

$WebApp = SPWebApplication | where {$_.Name -match "OldWebAppNameGoesHere"}
$WebApp.Name ="NewWebAppNameGoesHere"




Original post for SharePoint 2007:

I was playing around with SharePoint on my virtual machine and had set up a new installation of MOSS when I noticed I had entered a host header incorrectly (at least incorrectly from the standpoint of being consistent with my previous installations). I entered "MySite" instead of "MySites" as the first part of the host header. I know, I know, it’s probably more correct to use the singular, but I was trying to be consistent with what others had done.
All I wanted to do was to change the host header and have SharePoint recognize the change. I performed the standard internet search and didn’t get instant gratification, so I started playing around. I found that making the changes in three places and an IISRESET seemed to take care of my problem.
First, in Central Administration under Operations, Global Configuration, Alternate access mappings, edit the internal URL.

Next, open up IIS Manager and select the properties of the MySites web app. Change the host header by clicking on the Advanced… button.

Again in Central Administration, navigate to the Shared Services provider and click on My Site settings in the User Profiles and My Sites section. Change the personal site provider URL.

Perform an IISRESET. All should be well.


Deleting List or Library Fields Breaks Data View Web Part in SharePoint 2007

Okay, I know this is OLD 2007, but some folks are still running it!

This is actually a two-part fix. 

  1. Fix the data source so it isn’t referencing the deleted fields
  2. Fix the web part so it isn’t referencing deleted fields from the data source

Here’s the web part that is showing an error because field(s) were deleted from the underlying list (library).


The data source will not return any data because it is also messed up due to the deleted list fields.


You can find the datasource in the _fpdatasources folder.


Then you can edit it in XML or Text mode.  You probably need to check it out first, or you won’t be able to save it!


Fix the data source.  This involves finding the field in the data source XML that has been deleted.  In this example, we have found <FieldRef Name="Scorecard"> that has been encoded (e.g. &lt;).  Delete it, and be sure you get all the correct text deleted. 


Now you can see the data in the data source once again!


You need to fix the web part by finding the extra field(s) that are being referenced and remove them from the data source reference.


In the code view, find the <DataSources> tag and you can then locate the <datafields> section where the deleted list fields are still present.  You need to remove them as shown above.





The server returned a non-specific error when trying to get data from the data source.  Check the format and content of your query and try again.  If the problem persists, contact the server administrator.

Asif Rehmani’s SharePoint Videos


Click to access a wealth of SharePoint videos

SharePoint Rx

SharePoint Rx Home


Posts by Date

November 2015
« Oct    
Support Wikipedia


Get every new post delivered to your Inbox.