I was working on Sharepoint 13 standalone server and suddenly found this error
"The Server was unable to save the form at this time. Please try again."
I was working on a simple list to add the data into it . The error was not allowing me to add the data into the simple share point list .Searching on internet I came to know that restarting the "Search Host Controller Service" would solve the issue .The ideology was it was eating lot of RAM and so it has to be restarted .But since I knew this issue, in our server "Search Host Controller Service" was already disabled long back ,since we were not working on search .
But some how i had to solve this issue since my share point 13 server was taking in any items.
So I decided to give a try and started "Search Host Controller Service" luckily it worked and I was able to add items to any list in the web application .
Worked for me, thanks !
ReplyDeleteyou are welcome Remy :)
ReplyDeleteThanks a lot it really works for me , highly appreciated .
ReplyDeleteRegards,
Waseem Khan
Worked for me too.
ReplyDeleteThx!
Thanks a lot :) Worked !
ReplyDeleteThis did not work for me. Still seeing a "The server was unable to save the form at this time. Please try again." error when attempting to create a folder in a library.
ReplyDeleteMichael ,
ReplyDeleteWhat is your system configuration ?Did to try stopping all those search services ?
@Michael: if you are using any event receiver code to redirect to a different page, you need to propably edit the corresponding web part in either new or edit form and change its CSR Render mode to ServerRender. iot worked for me.
ReplyDeleteGracias por la solución, me funciono bastante bien
ReplyDeleteRicardo Rosales ,you are welcome :)
ReplyDeleteSharePoint online 2013 - a member with add/edit permission got the same problem, however administrator doesn't. Please help. What can be done?
ReplyDeleteTambién debéis tener identificado a que nivel da el error, con esto me refiero a que esta solución se aplica si el error es a nivel global del site, si es a nivel individual (solo a un usuario le da el error) debéis comprobar que este usuario tiene al menos permisos de lectura sobre el sitio ya que aunque tenga acceso a las bibliotecas, carpetas, listas etc...al realizar un cambio o al agregar un nuevo ítem o incluso al crear una carpeta le saltará este error. Aseguraros a que nivel os afecta este error (Global o Individual) ya actuar dependiendo del nivel al que este el error, no siempre reiniciar servicios o hacer un IISReset es la solución.
DeleteDude :-) It worked for me too :-)
ReplyDeletehaha u tried now :P
DeleteWorked for me thanks
ReplyDeleteTambién debéis tener identificado a que nivel da el error, con esto me refiero a que esta solución se aplica si el error es a nivel global del site, si es a nivel individual (solo a un usuario le da el error) debéis comprobar que este usuario tiene al menos permisos de lectura sobre el sitio ya que aunque tenga acceso a las bibliotecas, carpetas, listas etc...al realizar un cambio o al agregar un nuevo ítem o incluso al crear una carpeta le saltará este error. Aseguraros a que nivel os afecta este error (Global o Individual) ya actuar dependiendo del nivel al que este el error, no siempre reiniciar servicios o hacer un IISReset es la solución.
ReplyDeleteYou must also have identified at what level gives the error, with this I mean that this solution is applied if the error is global level of the site, if it is at an individual level (only a user gives the error) you should check that this user has at least read permissions on the site because even if you have access to libraries, folders, lists etc ... when making a change or adding a new item or even creating a folder you will miss this error. Make sure to what level this error affects you (Global or Individual) and to act depending on the level to which the error is, not always restarting services or making an IISReset is the solution.
Delete