Browser Forms

Re: What is the error: SESSION_STATE_PASCAL_CASED is not configured properly indicating?

Larry W. Virden — Mon, 22 Apr 2013 14:40:03 GMT

Thank you, patrick, for the pointer to that thread. I have read that thread and others, but none seem to actually have a real solution to the problem. For instance, in most cases, when people refer to the stsadm command, subsequent followups are either that it did not help, or it made things worse. I am hesitant to go down that path. Also, in our case, the forms have been republished recently and the error still occurs.

If anyone else has had success resolving the error, please let me know.

Thank you all

Re: What is the error: SESSION_STATE_PASCAL_CASED is not configured properly indicating?

Patrick Halstead — Sun, 21 Apr 2013 16:44:54 GMT

http://social.msdn.microsoft.com/forums/en-US/sharepointcustomizationlegacy/thread/fac73ccc-1af5-4978-a650-e1f97d201052

What is the error: SESSION_STATE_PASCAL_CASED is not configured properly indicating?

Larry W. Virden — Fri, 19 Apr 2013 11:31:01 GMT

We have a single small MOSS SP 2007 (SP3) 32 bit farm.

We get numerous times a day an error of the effect:

Alert: InfoPath Forms Services event counter mismatch

Source: myserver

Path: myserver.net

Last modified by: System

Last modified time: 4/18/2013 3:49:32 PM

Alert description: Event ID 5760 from Source Office SharePoint Server on agent computer myserver.net has triggered this Alert Description : InfoPath Forms Services has detected a mismatch between the user's data in the browser and on the server. This may indicate the SESSION_STATE_PASCAL_CASED is not configured properly on a multiple front end farm or that a malicious user is trying to tamper with client data. (User: mydomain\user20, Form Name: Travel, IP: , Request: http://myserver.nett/_layouts/Postback.FormServer.aspx, Form ID: urn:schemas-microsoft-com:office:infopath:Travel:-myXSD-2012-07-01T18-57-06)

It occurs with random users - managers, employees, etc. I don't know what "tamper with client data" means.

One developer has indicated that he thought the problem arose when a user sat in a form "too long". I don't have any idea, myself.

What would cause this sort of thing, and how would a form need modified so things were configured properly?