Category Archives: General

SharePoint 2013–While updating a list or adding a new user, getting error “The server was unable to save the form at this time. Please try again”

Recently users and I started getting error when trying to update a list or adding a new user:

The server was unable to save the form at this time. Please try againimage

server error

As a Farm administrator and site collection administrator, I had full access to the site. Also, earlier I had no issues updating lists, so it was flabbergasting at first why this error was cropping up.

Then I remembered that the only change I made to environment was to add multiple bindings in the site.


I had added both server:8080 and to IIS bindings.

Further, a quick search on the net gave me multiple articles about WCF having issues with multiple bindings (, etc.)

So, as soon as I removed the additional binding e.g. server:8080, I was able to edit lists without the above error!


SharePoint 2013 – Error while creating a new site “New-SPSite : User cannot be found.”


I wanted to do a content deployment to a new farm and wanted to create a new blank site using powershell:

New-SPSite -Url http://<servername>:8080/sites/test –OwnerEmail  <email address> –OwnerAlias domain\<account>


. While trying to create a new site, I got the following error:

New-SPSite : User cannot be found.
At line:1 char:2
+  New-SPSite -Url http://<servername>:8080/sites/tes
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (Microsoft.Share…SPCmdletNewSite:SPCmdletNewSite) [New-SPSite], SPException
    + FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSite


I was initially stumped. Only the other day I had created a new site successfully, why would it fail now?

I tried creating a new site using Central Administration and it still failed with error “Sorry, something went wrong   User cannot be found”:



But, I was able to create a new site collection on another farm using the same account. Also I was able to create a new site collection on on a new test web application on the problem server with this user account.

Turns out the issue was due to enabling Trusted Identity Provider (STS) for Forms login for external users  on an extended site. For some reason, after enabling STS,  SharePoint was failing to identify Windows NT id .

Funny thing was this was not enabled on http://<servername>:8080/sites/test but on extended site http://<servername>:80/sites/test. I have not investigated on why this happens yet.




So, my best guess is, with STS enabled SharePoint wants to resolve users in the format  i:0#.w|domain\account and this creates problem. (btw, I had already tried creating a new site using

New-SPSite -Url http://<servername>:8080/sites/test –OwnerEmail <email address> –OwnerAlias  i:0#.w|domain\account

But that did not work either.

But what I did find was that if I disabled the Trusted Identity provider by unchecking the box, I could create a new site without error.