SharePoint 2013 is always full of mysteries as it’s a starting time and
most of the firms are doing the migration of their SharePoint 2010 environment
to SP2013 platform. So it’s quite obvious it will take some time to make your
farm stable!
Note:
If you find a different
solution, please report it as a comment to this post. Be sure to double-verify
it: undo your solution and verify that the problem comes back, then redo it and
verify that the problem goes away.
Problem
description:
We have recently done the
migration from SP2010 -> SP2013 in our development environment and given
access to limited number of high profile users and developers for the testing.
While doing the testing, one of the developers has reported an incident
mentioning he is facing some error while editing the list item. Further
exploration reveals that we can’t add a new item also.
So bottom line, this error comes up while: Adding a new item in
a list or at the time of editing the item
Error Message:
The server was unable to save the form at this time. Please try
again.
Troubleshooting
done:
1. Tried creating
different list with some different template / type but same issue.
2. Checked the list in
SharePoint Designer 2013 but didn’t find anything relevant.
3. Checked the site
settings for any customized content type but it was using default settings
4. Checked the event
viewer for any critical errors but didn’t not find anything
5. Checked the
services console, did some try & error funda but that did the trick. Later
I did some research on my “trial and error method” and understood the complete
process via Microsoft articles (reference article –bottom of this page)
Resolution:
1. Go to your
SharePoint Server
2. Start
3. Run
4. Type – services.msc
5. It will open the
services console
6. Search for this
service - SharePoint Search Host Controller
7. Restart it.
It
fixed the issue and I was able to create new items as well as edit the existing
items too.
Happy
SharePoint once again!
Few
suggestions if the above solution doesn’t work:-
1) IISRESET on
SharePoint Servers
2) Restart all the
SharePoint Servers
3) Enable anonymous
authentication for the website in IIS.
I
hope the above information works for you also! But in case of any
queries/questions then please let me know. I would be more than happy to help
you as well as resolves your issues, Thank you.
Product applies to:
a) SharePoint 2013
b) SharePoint
Foundation 2013
This can happen for a number of reasons but the one we hit most often is the fact that if your machines memory usage hits 95% allocated (so only 5% free memory on the server), SharePoint 2013 stops saving form data. Free up just 1% (so 94% allocated) and it starts working again.
ReplyDeleteNice Post, but I agree with the above comment.You can see how I am able to resolve this from
ReplyDeletehttp://asharepointsolutions.blogspot.in/2014/01/the-server-was-unable-to-save-form-at.html
Thanks Ajeet! This will be definitely useful for the entire SharePoint community.
DeleteThanks for the article, I have done all your steps except server restarting
ReplyDeleteI hope that the issue will be solved once I restart the servers
Mahmoud Algoul
please keep me posted about the result. Thanks.
DeleteBytheway, above issue will be cause because of below:
ReplyDelete1. Permission Level: make sure user dose have read access on site level --> worked with me.
2. re-create new NewForm.aspx --> this also worked with me.
Mahmoud Algoul
Great to have this info! Thanks for sharing...
DeleteAnother issue with Infopath regarding People Picker field.
ReplyDeleteit show below error:
json is undefined for ie11 only. any clue about it
Mahmoud Algoul
add your site in compatibility view (IE->Tools->compatibility view) and then check the results
DeleteI got the fix
Deleteyou need to update PickerDialog masterpage IE=8 to 9 and it will work.
Mahmoud Algoul
for "The server was unable to save the form at this time. Please try again" I found the solution:
ReplyDeleteThe problem is being caused because users who have permissions to a single library or list, but not permissions to the actual SharePoint site, are missing a key SharePoint permission set on the SharePoint site, the “Use Remote Interfaces” permission.
Without this permission set, users will not be able to “Use SOAP, Web DAV, the Client
Object Model or SharePoint Designer interfaces to access the Web site”.
This is key, because SharePoint 2013 uses the Client Object Model in the forms for a SharePoint list.
Agreed!!
DeleteAgreed too!!
DeleteHi
ReplyDeleteI have tried all possibilty but no working for me....
http://social.technet.microsoft.com/Forums/office/en-US/e68326a7-82a0-4a6f-8591-60db02ac2fe1/the-server-was-unable-to-save-the-form-at-this-time-please-try-again?forum=sharepointgeneral
help me!
Another cause for this we found was hidden, control characters (for instance 0x0B or VT) which are pasted into a text field.
ReplyDeleteNice post, it solved my issue. thanks
ReplyDeleteTried everything and ended up restarting the server works. Maybe it has to do with the workflow management service is installed on the same WFE
ReplyDelete