Exceptions occurring on IIS but not on VS

Question

0.00/5 (No votes)

See more:

, +

Hello all,

I'm having this problem with an app I tried to deploy to IIS version 6.1. My code makes an asynchronous call (via a WebClient and delegate code) to retrieve XML data from a remote server, and this is working perfectly fine when I run the app from Visual Studio 2010. However, when I deploy the app to my IIS server, a TargetInvocationException is thrown by this code and the process is stopped as this call is the first step of a long flow of mixed processes, all of which seem to be working fine. I'm deploying the app to the .Net 4 application pool (this is the version in which the code is compiled) but the exception is still thrown. Has any of you had a similar experience where your code produces an exception of this type in IIS but not on your IDE? What could I be doing wrong with the configuration? Any suggestions and/or responses will be highly appreciated, thanks.

--Erick

Posted 8-Oct-12 7:04am

Erick Dee

Add a Solution

Comments

Erick Dee 8-Oct-12 13:42pm

Tried it but got the same result :(

Teenustar 8-Oct-12 15:00pm

This might help
http://netindonesia.net/blogs/zeddy/archive/2008/08/21/how-to-resolve-targetinvocationexception-error-catching-exception-in-asynchronous-calls.aspx

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Erick Dee · Accepted Answer · 2012-10-10T12:46:00

Found out what the problem was. The remote server was denying me access (401) because I was sending the DefaultCredentials in the WebClient object. It turns out that they're not the same when using the ASP Development server (your Windows account) than those sent by IIS when the app is deployed, since it sends a username like "IIS APPOOL\YourAppPoolName". Thanks anyway for your replies.