J
JDeats
I'm in a situation where it's difficult to get on-site and
troubleshoot, so I'm looking for scenarios from those experienced on
what might be causing this problem.
I have a .NET 2.0 WinForms based application that that has a few web
references. The application makes the first web service/SOAP call when
the user first launches the app to submit product registration
information. The user is getting an generic "network error message"
that I've created to display when a general Exception is thrown, the
only thing I can confirm is the exception is being thrown when the web
service call is being made.
This application has been tested on many different systems with varied
configurations with no problems, so I assume it's something blocking
the application from port 80.
If you had to troubleshoot this issue without being able to "remote
in" or go on site and you could only use very little of the end users
time to troubleshoot the problem what would your approach be?
troubleshoot, so I'm looking for scenarios from those experienced on
what might be causing this problem.
I have a .NET 2.0 WinForms based application that that has a few web
references. The application makes the first web service/SOAP call when
the user first launches the app to submit product registration
information. The user is getting an generic "network error message"
that I've created to display when a general Exception is thrown, the
only thing I can confirm is the exception is being thrown when the web
service call is being made.
This application has been tested on many different systems with varied
configurations with no problems, so I assume it's something blocking
the application from port 80.
If you had to troubleshoot this issue without being able to "remote
in" or go on site and you could only use very little of the end users
time to troubleshoot the problem what would your approach be?