|
|
Rank: Advanced Member
Groups: Member
Joined: 11/16/2010
Posts: 48
|
One user of my web upload program is consistently receiving the following on the upload (the Data element differs). Others users are uploading without error....
Error in page :http://www.photocompentries.net/eo_web.ashx?id=4EF2A06E-5171-4166-82A6-242BD1985E8A&uploader_data=DSFnZXRfcHJvZ3Jlc3MCgAAAAIyAAAAAh2N0bDAwX2NwTWFpbkNvbnRlbnRfVXBsb2FkZXJfMDpTWi9MZUxJQWpBbWE3QlNZL1pIdURKSU9xZXNBa3dPazdCT0dDcUxvQ1pFUHArRUpsc21qM1JoL0E2bnNGSWNLbU9zQWt3T2s3Qk9HQ3FMb0NaRVBwK0VKbHZkNnh3TjNBS0xvQUE9PQsKczozMDFlZDg4Nw==
Message
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
StackTrace
at EO.Web.Internal.u.a(a3 A_0, HttpResponse A_1, Object A_2)
at EO.Web.Internal.fa.a(jt A_0, Boolean A_1, AsyncCallback A_2, a3 A_3, HttpResponse A_4, Object A_5)
at EO.Web.Internal.fa.a(a3 A_0, Boolean A_1, AsyncCallback A_2)
at EO.Web.Internal.fa.a(HttpApplication A_0, AsyncCallback A_1)
at EO.Web.Internal.fe.a(HttpContext A_0, AsyncCallback A_1)
at EO.Web.Runtime.a(HttpContext A_0, AsyncCallback A_1, Object A_2)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Query String
id=4EF2A06E-5171-4166-82A6-242BD1985E8A&uploader_data=DSFnZXRfcHJvZ3Jlc3MCgAAAAIyAAAAAh2N0bDAwX2NwTWFpbkNvbnRlbnRfVXBsb2FkZXJfMDpTWi9MZUxJQWpBbWE3QlNZL1pIdURKSU9xZXNBa3dPazdCT0dDcUxvQ1pFUHArRUpsc21qM1JoL0E2bnNGSWNLbU9zQWt3T2s3Qk9HQ3FMb0NaRVBwK0VKbHZkNnh3TjNBS0xvQUE9PQsKczozMDFlZDg4Nw%3d%3d
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,225
|
Hi,
I can't think of anything that can cause this error since the GUID in the query string is in fact the correct format. If the user can duplicate this in a stripped down test site and set up a test server, we will be happy to connect to it to investigate further.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 5/11/2010
Posts: 10
|
Any resolution? I'm getting the same error today, but different users on two different websites (although other users are having no issue on both sites). What interesting is it's the same GUID as the original post above. Here's my error: https://www.mywebsiteobscured.com:443/MySiteObscured/eo_web.ashx?id=4EF2A06E-5171-4166-82A6-242BD1985E8A&uploader_data=ByF1cGxvYWQCTUxjdGwwMF9Db250ZW50UGxhY2VIb2xkZXIxX0FKQVhVcGxvYWRlcjE6QlpmY0JaZjhrYzBVandxVzNQaUlDS1c4RFpVWFpacXlBSm9BCwpzOmQyODAwMTk3
|
|
Rank: Member
Groups: Member
Joined: 5/11/2010
Posts: 10
|
Initial POST in the IIS log is getting a 200 return code, then 500's thereafter: 165.x.xxx.xxx, tuser@tcompany.com, 7/11/2017, 8:36:53, W3SVC3, WEBSERVER, 10.20.1.6, 109, 1298, 522, 200, 0, POST, /HIDINet/eo_web.ashx, id=4EF2A06E-5171-4166-82A6-242BD1985E8A&uploader_data=DCFuZXdfc2Vzc2lvbgJIR2N0bDAwX0NvbnRlbnRQbGFjZUhvbGRlcjFfVXBsb2FkZXI6QkFDWDNBV1gvSkhORkk4S2x0ejRpQWlsdkEyVkYyV2FzZ0NhBQRmYzox, 165.x.xxx.xxx, tuser@tcompany.com, 7/11/2017, 8:36:53, W3SVC3, WEBSERVER, 10.20.1.6, 109, 1310, 3765, 500, 0, POST, /HIDINet/eo_web.ashx, id=4EF2A06E-5171-4166-82A6-242BD1985E8A&uploader_data=DSFnZXRfcHJvZ3Jlc3MCSEdjdGwwMF9Db250ZW50UGxhY2VIb2xkZXIxX1VwbG9hZGVyOkJBQ1gzQVdYL0pITkZJOEtsdHo0aUFpbHZBMlZGMldhc2dDYQsKczo1MWFiNzYwMg==, 165.x.xxx.xxx, tuser@tcompany.com, 7/11/2017, 8:36:53, W3SVC3, WEBSERVER, 10.20.1.6, 468, 66626, 3765, 500, 0, POST, /HIDINet/eo_web.ashx, id=4EF2A06E-5171-4166-82A6-242BD1985E8A&uploader_data=ByF1cGxvYWQCSEdjdGwwMF9Db250ZW50UGxhY2VIb2xkZXIxX1VwbG9hZGVyOkJBQ1gzQVdYL0pITkZJOEtsdHo0aUFpbHZBMlZGMldhc2dDYQsKczo1MWFiNzYwMg==,
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,225
|
Hi,
We have looked into this issue again. The Guid portion in the Url is not the GUID that causes the problem.
When user starts an upload, the client side JavaScript will first send an AJAX request to the server to create an upload session. This session is represented by an internal GUID. When the session is successfully created, this GUID is sent to the client side. The client side then keeps this GUID and send it back for all further communications about this upload. Such communications are still processed through the same eo_web.ashx call. The communication arguments, including the session GUID and other information, are encoded in the uploader_data Url argument.
In your case, this session GUID encoded in uploader_data is apparently wrong (it only has a portion of the data). The encoding part does not seem to be the problem because all other arguments can be decoded fine. However we do not know which step the data were altered. We are still trying to find this and if we find anything we will post again.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 5/11/2010
Posts: 10
|
OK, Thanks. User is using IE11, not that I think that is an issue.
|
|
Rank: Member
Groups: Member
Joined: 5/11/2010
Posts: 10
|
Just FYI, same customer uploaded without issue this morning. Same PC, browser, everything.
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/16/2010
Posts: 48
|
I posted the original query - and I've had a couple since.... They were uploading from Australia to a server the UK and I just wondered if the GUID was getting corrupted somewhere along the way. I have a similar (occasional) problem with viewstates on some Australian entries.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,225
|
Yes that is possible. However we are also looking on our end as a precaution since everything else in the encoded data seems to be valid, so it would be quite strange that their network only alter the GUID part.
|
|