Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, September 25, 2013 10:42 PM | 1 vote
I have a simple infopath form. there is no workflow behind it. i have some dropdown fields and some selection fields. When i try to change the default value to something else , this give the error message with Correlation ID.
"A Microsoft SharePoint Server State Service error occurred while processing your request. For more information, contact your server farm administrator."
on ULS log, i found this
09/25/2013 18:27:28.70 w3wp.exe (0x2748) 0x27E0 SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://link.domain.local:80/sites/domain/it/bi/_layouts/Postback.FormServer.aspx) 2047c959-1e42-4721-a916-ec7e9d5b6e47
09/25/2013 18:27:28.71 w3wp.exe (0x2748) 0x27E0 SharePoint Server State Service bm0u Medium StateManager.GetState() No data (e0d600a3-63f5-4d38-ac89-8fc22d4d3df4) 2047c959-1e42-4721-a916-ec7e9d5b6e47
09/25/2013 18:27:28.71 w3wp.exe (0x2748) 0x27E0 InfoPath Forms Services Runtime - State Service b5st Medium MOSS StateService threw an exception: A Microsoft SharePoint Server State Service error occurred while processing your request. For more information, contact your server farm administrator. 2047c959-1e42-4721-a916-ec7e9d5b6e47
09/25/2013 18:27:28.71 w3wp.exe (0x2748) 0x27E0 SharePoint Server State Service 8kfs Medium The StateManager is disposing and calling ReleaseLockedStates() (Count=0) 2047c959-1e42-4721-a916-ec7e9d5b6e47
Please Help.
All replies (10)
Sunday, October 20, 2013 4:43 AM ✅Answered | 3 votes
check you SQL free space, probably related to it
Friday, March 21, 2014 7:33 PM ✅Answered | 1 vote
In my case issue was
Details: The transaction log for database 'StateService_0a9199c7ae644c9a9f29c44206c8f488' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases 0b763f0e-2380-443b-8712-89a3bfbe1224
I got this log from ULS 14 Hive log.
Clear SQL log resolved the issue.
Wednesday, September 25, 2013 11:19 PM
I'm assuming the State Service (Application) is in a healthy state?
Trevor Seward, MCC
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
Wednesday, September 25, 2013 11:28 PM
This error message doesn't come all the time. It happens 4 out of 10 times.
Also i created new State Service Application and associated that web application with this new state service application.
i also increased the max connection time out for infopath.
Thursday, September 26, 2013 12:27 AM | 1 vote
Can you increase the diagnostic logging on the State Service and try again?
Central Administration -> Monitoring -> Configure Diagnostic Logging -> SharePoint Server -> State Service.
Trevor Seward, MCC
Follow or contact me at...
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.
Thursday, September 26, 2013 1:19 AM
This is what i got from verbose logging.
09/25/2013 21:13:38.17 w3wp.exe (0x1F68) 0x10BC SharePoint Foundation Logging Correlation Data xmnv Medium Name=Request (POST:http://link.domain.local:80/sites/domain/it/bi/_layouts/Postback.FormServer.aspx) 9a3c7182-94a6-4647-bc2d-f9e309966161
09/25/2013 21:13:38.18 w3wp.exe (0x1F68) 0x10BC SharePoint Server State Service 0000 Verbose StateSqlSession.ScopedHash (00000000-0000-0000-0000-000000000000) 9a3c7182-94a6-4647-bc2d-f9e309966161
09/25/2013 21:13:38.18 w3wp.exe (0x1F68) 0x10BC SharePoint Server State Service 0000 Verbose StateSqlSession.GetItemBytesInternal: Executing proc_GetItemWithLock with ID e5c9c987aab14f09abd11684bf2d87ad_00000000-0000-0000-0000-000000000000 in database StateDatabase Name=StateService_4624a17beb0340b4a06e02205d4a7fbd 9a3c7182-94a6-4647-bc2d-f9e309966161
09/25/2013 21:13:38.18 w3wp.exe (0x1F68) 0x10BC SharePoint Server State Service 0000 Verbose StateSqlSession.GetItemBytesInternal: proc_GetItemWithLock completed with no data returned (locked: , lockDate: , lockCookie: ). 9a3c7182-94a6-4647-bc2d-f9e309966161
09/25/2013 21:13:38.18 w3wp.exe (0x1F68) 0x10BC SharePoint Server State Service bm0u Medium StateManager.GetState() No data (e5c9c987-aab1-4f09-abd1-1684bf2d87ad) 9a3c7182-94a6-4647-bc2d-f9e309966161
09/25/2013 21:13:38.18 w3wp.exe (0x1F68) 0x10BC InfoPath Forms Services Runtime - State Service b5st Medium MOSS StateService threw an exception: A Microsoft SharePoint Server State Service error occurred while processing your request. For more information, contact your server farm administrator. 9a3c7182-94a6-4647-bc2d-f9e309966161
09/25/2013 21:13:38.18 w3wp.exe (0x1F68) 0x10BC SharePoint Server State Service 8kfs Medium The StateManager is disposing and calling ReleaseLockedStates() (Count=0) 9a3c7182-94a6-4647-bc2d-f9e309966161
09/25/2013 21:13:38.18 w3wp.exe (0x1F68) 0x10BC SharePoint Foundation Monitoring b4ly Medium Leaving Monitored Scope (Request (POST:http://link.domain.local:80/sites/domain/it/bi/_layouts/Postback.FormServer.aspx)). Execution Time=18.3945206529446 9a3c7182-94a6-4647-bc2d-f9e309966161
Thursday, June 19, 2014 10:49 AM
It seems the login user is not having appropriate permission at form library or any list/library/service used in your form. Kindly verify that user has permission for each and every content.
In my case I was updating some custom list on form submit event. On these custom lists the login user was not having add/edit permissions. After granting the user Contribute permissions on the lists the error was resolved.
Wednesday, June 1, 2016 5:58 PM
What steps did you take to clear the SQL log?
Toni Marie
Tuesday, June 5, 2018 12:01 AM
Start 'Service Bus Message Broker' and 'service bus gateway' from your WFM Server.
Friday, January 24, 2020 8:32 PM
In our case transaction log drive was full only 9.9MB out of 500GB was there. As quick response, I took off Search Crawl DB offline and moved crawl log to another drive temporary to spare the disk. After this everything worked as expected.