Rank: Member
Groups: Member
Joined: 4/25/2013
Posts: 17
|
Greetings, we have a client who is using the Ajax Uploader and it is timing out and giving a 500 (INKApi Error) in the javascript console. Interestingly, when they pick the file to upload (ex: test.pdf) the location doesn't show the actual location on their computer but instead says "C:\fakepath\test.pdf"
I suspect that it has something to do with the clients firewall or security settings b/c we have many people using the ajax uploader with no problem (and we're not able to duplicate the problem). However, it would probably help if we could tell them which restriction they need to loosen. Any ideas?
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
The 500 error is an error given by your IIS and you will need to start troubleshooting from there. I would recommend you using a traffic monitor such as Fiddler to monitor the traffic between the server and the client. The normal response for an AJAXUploader should be in XML format. When something is wrong on your server side, typically the server would return an error page. You won't see the content of the error page from the browser directly (because it's an AJAX request), however you should be able to see the full contents with a traffic monitor. The content of the error page should help you find out the root of the problem.
"c:\fakepath\test.pdf" is normal. Modern browser does not allow your page (both client side JavaScript code and server side code) to see the actual physical path of the file you are trying to upload. So instead of displaying the actual path, it displays "fakepath".
Thanks!
|
Rank: Member
Groups: Member
Joined: 4/25/2013
Posts: 17
|
Here is what I found in IIS logs. Doesn't look familiar to me:
Exception information:
Exception type: KeyNotFoundException
Exception message: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at EO.Internal.dz.a(String A_0)
at EO.Internal.am0.a(String A_0)
at EO.Internal.amh.a(Char A_0)
at EO.Internal.amh.b(Char A_0)
at EO.Internal.amh.b()
at EO.Internal.a8x.a(a1t A_0, HttpResponse A_1, Object A_2)
at EO.Internal.a0d.a(dt A_0, Boolean A_1, AsyncCallback A_2, a1t A_3, HttpResponse A_4, Object A_5)
at EO.Internal.a0d.a(a1t A_0, Boolean A_1, AsyncCallback A_2)
at EO.Internal.a0d.a(HttpApplication A_0, Boolean A_1)
at EO.Internal.ys.a(Object A_0, Boolean A_1)
at EO.Internal.awa.b(Object A_0, EventArgs A_1)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
Request information:
Request URL: https://----------:443/eo_web.ashx?id=1C62BC22-BE43-4a46-BB13-E8A5AC6650E5&i=bee075ea-43c0-4006-82f9-f44ff4088842&s=1&a=1
Request path: /eo_web.ashx
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,221
|
Hi,
You will need to match up the log with the request first. This particular error can be fine ---- you will get this error if you have updated the server to a newer version, but a cached client page is trying to request the server page with old cached arguments. This does not indicate a problem and the client page needs to be refreshed. So you can try to refresh the page then make sure the error you see comes from the page you are working with. This is why you need to use a traffic monitor instead of just looking into IIS log.
Thanks!
|