Problem with a web service

D

DLN

Hello all,

I'm running into a problem with one of our site's production web
applications that was written in VB.net. The web app is running on
W2K3/IIS6 and up until this afternoon, was working just fine. The
application calls a web service that exists as an application under the main
application's root directory, and it looks as though this is where the
application dies. The UI returns "The request failed with HTTP status 400:
Bad Request" plus the source file and line number where the unhandled
exception occurred and a stack trace. The IIS server log returns a 500
error (internal server error), which still isn't all that helpful. I have
the web app source code from the developers which I have built and
configured to hit the exact same web service on the production server, and
my sandbox web app appears to function properly. The difference though is
that in my sandbox, the web app is not running off the production server
(although the web service still is). With the production system, the web
service and web app are both are running off the same box.

I don't know what has changed to cause this behavior, I've just been tasked
to fix it. I've been pulled off another project to look at this problem and
it's the first time I've seen this code. There's also a time delay between
our site and where the developers are, so I'm on my own for the next few
hours. I could really use some advice on how I can troubleshoot this
problem further. Based on the fact that the app seems to run fine when
running off a separate server than the web service I'm wondering if
something is misconfigured on the server, but I've run out of places to
look.

Just some additional info (in hopes that it might be useful), both the app
and web service are using the same IIS application pool and the pool is
configured to run as "Network Service". Both the app and service are
configured to allow anonymous logons through IIS but the web.config file for
the application is set for forms based authentication and "identity
impersonate". The web service's web.config file is set to windows
authentication.

I certainly would appreciate any hints, tips or suggestions.

Regards,

dln
 
D

DLN

Figured it out - it was a problem with assigning an IP address to the web
site (as opposed to "All Unassigned") and configuring a host header value.
Once I changed the site to use all unassigned IP addresses and removed the
host header value, everything started working again.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top