Rank: Advanced Member
Groups: Member
Joined: 11/16/2010
Posts: 48
|
The EO.web DLL version is 20.1.88
I have now had two incidents where an upload failed with this error...
Error in page :https://XXX.net/eo_web.ashx?id=4EF2A06E-5171-4166-82A6-242BD1985E8A&uploader_data=ByF1cGxvYWQCgImAh2N0bDAwX2NwTWFpbkNvbnRlbnRfVXBsb2FkZXJfMDpBSGl5QUd3Sm11d1VtUDJSN2d5U0RxbnJBSk1EcE93VGhncWk2QW1SRDZmaENaYkpvOTBZZndPcDdCU0hDcGpyQUpNRHBPd1RoZ3FpNkFtUkQ2ZmhDWmIzZXNjRGR3Q2k2QUNmeXc9PScmczozNDZlMjQwOC0xYWZkLTQ3NjYtYjkyYy05ODUyMzMwYjA0OTc=
Message
The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters.
StackTrace
at EO.Internal.gswx.nfgk(gsyi fjr, HttpResponse fjs, Object fjt) at EO.Internal.gsyk.ecdb(gsyj das, Boolean dat, AsyncCallback dau, gsyi dav, HttpResponse daw, Object dax) at EO.Internal.gsyk.nfgk(gsyi dap, Boolean daq, AsyncCallback dar) at EO.Internal.gsyk.eccz(HttpApplication dal, AsyncCallback dam) at EO.Web.Runtime.System.Web.IHttpAsyncHandler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Query String
id=4EF2A06E-5171-4166-82A6-242BD1985E8A&uploader_data=ByF1cGxvYWQCgImAh2N0bDAwX2NwTWFpbkNvbnRlbnRfVXBsb2FkZXJfMDpBSGl5QUd3Sm11d1VtUDJSN2d5U0RxbnJBSk1EcE93VGhncWk2QW1SRDZmaENaYkpvOTBZZndPcDdCU0hDcGpyQUpNRHBPd1RoZ3FpNkFtUkQ2ZmhDWmIzZXNjRGR3Q2k2QUNmeXc9PScmczozNDZlMjQwOC0xYWZkLTQ3NjYtYjkyYy05ODUyMzMwYjA0OTc%3d
Can you help?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,217
|
Hi,
Does this problem occurs consistently on some pages or only randomly? There are two possibilities: network issue or code issues. If the problem is due to a network issue, it could be the Url string was truncated that caused this error. In that case the issue should resolve as long as the network issue is resolved. If it is a code issue, then we need to be able to reproduce it first. In that case please try to update to the latest build first, then see if you can reproduce it. If you can reproduce it, please send us a small test project with instructions. If it only occurs on your site, then you can send us the site Url and we will try to access it from here to see if we can see the problem and then go from there.
Thanks!
|