This is from the CF pages in e-Communities with 15.1.1 Public Views.
When a document is uploaded the form errors with first this message then a viewstate error page.
A msg box with:"Document.form1.TDescription is null or not an object." is the first error response.
To see screenshots see attached
This is truncated from the Event Viewer on the application server.
Event Type: Information
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1316
User: N/A
Description:
Event code: 4009
Event message: Viewstate verification failed. Reason: The viewstate supplied failed integrity check.
Event ID: 9d4d56261c8e44cab8507ecfbafc08b8
Event sequence: 42
Event occurrence: 2
Event detail code: 50203
Application information:
Application domain: /LM/W3SVC/1/Root/iMISpublic-1-129067291068872500
Trust level: Full
Application Virtual Path: /iMISpublic
Application Path: C:\Program Files\ASI\iMIS15\iMIS_public\
Process information:
Process ID: 4172
Process name: w3wp.exe
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1316
User: N/A
Description:
Event code: 4009
Event message: Viewstate verification failed. Reason: The viewstate supplied failed integrity check.
Event ID: 9d4d56261c8e44cab8507ecfbafc08b8
Event sequence: 42
Event occurrence: 2
Event detail code: 50203
Application information:
Application domain: /LM/W3SVC/1/Root/iMISpublic-1-129067291068872500
Trust level: Full
Application Virtual Path: /iMISpublic
Application Path: C:\Program Files\ASI\iMIS15\iMIS_public\
Process information:
Process ID: 4172
Process name: w3wp.exe
How does e-Communities perpetuate or terminate Viewstate?
Why would a post redirect cause a viewstae issue unless a form field data point was deprecated in the last build or lost in translation?
There is also the iMIS error
at System.Web.Configuration.MachineKeySection.GetDecodedData(Byte[] buf, Byte[] modifier, Int32 start, Int32 length, Int32& dataLength)
at System.Web.UI.ObjectStateFormatter.Deserialize(String inputString)<br><br>
Unable to validate data.<br><br>
System.Web.HttpException<br><br>
at System.Web.UI.ObjectStateFormatter.Deserialize(String inputString)<br><br>
Unable to validate data.<br><br>
System.Web.HttpException<br><br>
These are the files loaded after the document uploads in 15.0.3
\ASI\iMIS15\iMIS_public\Source\Communities\documentArchive.cfm
iMIS_public\Source\Communities\addToDocumentPost.cfm
ASI\iMIS15\iMIS_public\ScriptContent\header.cfm
ASI\iMIS15\iMIS_public\AM\Templates\TemplateHeader\DefaultHeader.cfm
ASI\iMIS15\iMIS_public\Source\Communities\Application.cfm
ASI\iMIS15\iMIS_public\Source\Communities\module.cfm
ASI\iMIS15\iMIS_public\AM\DetermineHeader.cfm
ASI\iMIS15\iMIS_public\AM\AMeseries\eSeriesKeepLogin.cfm
ASI\iMIS15\iMIS_public\AM\TemplateSection.cfm
ASI\iMIS15\iMIS_public\AM\Templates\FooterInclude.cfm
ASI\iMIS15\iMIS_public\AM\Templates\HeaderInclude.cfm
ASI\iMIS15\iMIS_public\AM\Templates\TemplateFooter\DefaultFooter.cfm
ASI\iMIS15\iMIS_public\ScriptContent\StyleSheet.cfm
ASI\iMIS15\iMIS_public\ScriptContent\eSeriesHeader.cfm
ASI\iMIS15\iMIS_public\ScriptContent\footer.cfm
ASI\iMIS15\iMIS_public\ScriptContent\head.cfm
ASI\iMIS15\iMIS_public\Source\Body.txt
ASI\iMIS15\iMIS_public\Source\Communities\breadcrumb.cfm
ASI\iMIS15\iMIS_public\Source\Communities\cmtySecurityCheck.cfm
ASI\iMIS15\iMIS_public\Source\Find\util_find.cfm
ASI\iMIS15\iMIS_public\Source\Library\appSetSessionDisplay.cfm
ASI\iMIS15\iMIS_public\Source\Library\setModuleSSL.cfm
iMIS_public\Source\Communities\addToDocumentPost.cfm
ASI\iMIS15\iMIS_public\ScriptContent\header.cfm
ASI\iMIS15\iMIS_public\AM\Templates\TemplateHeader\DefaultHeader.cfm
ASI\iMIS15\iMIS_public\Source\Communities\Application.cfm
ASI\iMIS15\iMIS_public\Source\Communities\module.cfm
ASI\iMIS15\iMIS_public\AM\DetermineHeader.cfm
ASI\iMIS15\iMIS_public\AM\AMeseries\eSeriesKeepLogin.cfm
ASI\iMIS15\iMIS_public\AM\TemplateSection.cfm
ASI\iMIS15\iMIS_public\AM\Templates\FooterInclude.cfm
ASI\iMIS15\iMIS_public\AM\Templates\HeaderInclude.cfm
ASI\iMIS15\iMIS_public\AM\Templates\TemplateFooter\DefaultFooter.cfm
ASI\iMIS15\iMIS_public\ScriptContent\StyleSheet.cfm
ASI\iMIS15\iMIS_public\ScriptContent\eSeriesHeader.cfm
ASI\iMIS15\iMIS_public\ScriptContent\footer.cfm
ASI\iMIS15\iMIS_public\ScriptContent\head.cfm
ASI\iMIS15\iMIS_public\Source\Body.txt
ASI\iMIS15\iMIS_public\Source\Communities\breadcrumb.cfm
ASI\iMIS15\iMIS_public\Source\Communities\cmtySecurityCheck.cfm
ASI\iMIS15\iMIS_public\Source\Find\util_find.cfm
ASI\iMIS15\iMIS_public\Source\Library\appSetSessionDisplay.cfm
ASI\iMIS15\iMIS_public\Source\Library\setModuleSSL.cfm
| Attachment | Size |
|---|---|
| uploaderror.doc | 192.5 KB |
Would there be away to remove the custom header from just those
This is a blended viewstate issue that fails cf submit and upload methods.
The stock e-Communities page defaultHeader.cfm had been customized.
Once the defaultHeader.cfm was replaced with the stock header all functionality returned. Formatting was gone and somewhat abstract.
Now this is a formatting issue.
The viewstate validation will always fail because of the templategen.aspx lack of persistance within a CF session.
There seems to be a re-post caused by the CF upload method addToDocumentPost.cfm.
That re-post to the customized defaultHeader.cfm calls the iMIS master page twice and likely why viewstate does not authenticate in this instance.
There have been form tag manipulations and viewstate comparisons from 15.0.3 and 15.1.1.
I am going to try a simple HTML page to see if that can wrap the header and footer.
Bruce M Walker
BSCI
Chicago IL