Detailed ASP.Net info not displaying in browser

[Tim Reynolds]

Team,
I am developing a web service. In testing in on my enw PC, I am expecting to
see exceptions thrown appear on my browser. Instead I am getting an HTTP 500
Internal Server Error page and I am not seeing my exception details. The
web.config file being used has the setting <customErrors mode="Off"/>. This
should allow me to see the detailed exception info. On a different computer
- same code - same web config - the exception details display. Not sure what
else on my new computer needs set in order to see this info.

Please advise.
Much thanks,
Tim Reynolds

[Martin Honnen]

Tim Reynolds wrote:

I am developing a web service. In testing in on my enw PC, I am expecting to
see exceptions thrown appear on my browser. Instead I am getting an HTTP 500
Internal Server Error page and I am not seeing my exception details. The
web.config file being used has the setting <customErrors mode="Off"/>. This
should allow me to see the detailed exception info. On a different computer
- same code - same web config - the exception details display. Not sure what
else on my new computer needs set in order to see this info.

It might be that you are using IE as the browser and that IE is
configured to show short HTTP error messages instead of the complete
error document the server sends. Thus if you are using IE check your IE
settings to disable "short HTTP error messages" (note: I am using a
German IE version here so the exact English wording of the setting might
be different, the wording above is my attempt to translate the German
description of the setting I see here).

--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/

[Tim Reynolds]

Thanks Martin.

The closest thing I have to that setting is 'Show Friendly HTTP error
messages'. I have tried this option and although I do get some of the
exception info (inner exception message)- I do not get all of the exception
details. I have identical project & web.config on another PC (we'll call it
my old PC) and when I run on my old PC, I see ALL the exception info - not
just the inner exception message. So, yes, I see some difference when Show
Friendly HTTP Error messages is unchecked, I do not see ALL the detailed
information such as the stack trace - the outer exception, the outer
exception strack trace... etc...

Of note, on my old PC that DOES show all the exception info, this item 'Show
Friendly HTTP error messages' is CHECKED.

Therefore, I am guessing that there are other settings somewhere else on
this PC in order to get it set up so my new PC will display exceptions just
like my old one did (and just like other teammates PC's do).

Thanks,
Tim
"Martin Honnen" wrote:

>

Tim Reynolds wrote:

I am developing a web service. In testing in on my enw PC, I am expecting to
see exceptions thrown appear on my browser. Instead I am getting an HTTP 500
Internal Server Error page and I am not seeing my exception details. The
web.config file being used has the setting <customErrors mode="Off"/>. This
should allow me to see the detailed exception info. On a different computer
- same code - same web config - the exception details display. Not sure what
else on my new computer needs set in order to see this info.

It might be that you are using IE as the browser and that IE is
configured to show short HTTP error messages instead of the complete
error document the server sends. Thus if you are using IE check your IE
settings to disable "short HTTP error messages" (note: I am using a
German IE version here so the exact English wording of the setting might
be different, the wording above is my attempt to translate the German
description of the setting I see here).

--

Martin Honnen --- MVP XML
http://JavaScript.FAQTs.com/

[Walter Wang [MSFT]]

Hi Tim,

After reviewing your post, I'm not sure whether you're developing a "web
service" or a "web site". If you're developing a "web service" using
ASP.NET, how are you testing it? If you're using IE to test the web
service, as far as I know, you can only test it from localhost except
you're using another web site to test the web service.

On your "new" pc, does it report HTTP 500 error on every page? or only
report when an expected exception is thrown?

The ¡°HTTP 500 internal server error¡± is the general error message. To get
more details information, please:
1. Open the menu Tools -- Internet Options in IE.
2. Click Advanced tab.
3. Clear the checkbox ¡°Show friendly HTTP error messages¡±.
4. Click OK to close the dialogbox.
5. Try to visit the page again.
6. Create a screen shot of the error message you received.
7. Send me the screen shot as well as the event logs on the server
(application and system).

Sincerely,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Tim Reynolds]

Walter,
I am developing a web service which I am using locally on IE browser to test
(http://localhost/..). Problem only occuring on my new PC and I only get the
HTTP 500 page when an exception is thrown from the web service. Otherwise I
see the correct result. On this PC (new PC), when I do clear the check box
'Show Friendly HTTP error messages', I do no longer get the HTTP 500 page -
but instead get a page with the exception & inner exception messages. This is
good, but I am still expecting to see the entire exception details including
the exception names and stack traces like I do on my old PC. Furthermore, on
my old PC, regardless of whether 'Show Friendly HTTP error messages' is
checked or unchecked, I do see ALL exception details.I want my new PC to
behave similarly where it gives me the ENTIRE exception details (including
exception names and stack traces).

Here is what I see in IE browser when running locally (http://localhost/..).
on my NEW (problem) PC:
**** Begin screen shot ***
Exception encountered in dr_DB2Process.SetCommit --ERROR [08007] [IBM][CLI
Driver][DB2] SQL30073N &quot;0x2113" Parameter value "0x0000" is not
supported. SQLSTATE=58017
**** End screen shot ***

Here is what I see in IE browser when running locally (http://localhost/..).
on my OLD (good) PC:
(note - Old PC has the same code and same web.config being used as NEW PC -
code is from clear case repository)

**** Begin screen shot ***
VOSE.Common.Util.VOSEBaseApplicationException: Exception encountered in
dr_DB2Process.SetCommit ---IBM.Data.DB2.Db2Exception: ERROR [08007]
[IBM][CLI Driver][DB2] SQL30073N "0x2113" Parameter value "0x0000" is not
supported. SQLSTATE=58017

at IBM.Data.DB2.DB2Connection.HandleError(IntPtr hHandle, SQL_Handle hType,
RETCODE retcode)
at IBM.Data.DB2.DB2Command.ExecuteReaderObject(Comman dBehavior behavior,
String method)
at IBM.Data.DB2.DB2Command.ExecuteNonQuery()
at VOSE.Data.DataRequest.dr_DB2Process.SetCommit(DB2C onnection conn) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Data\VOSE.Data. DataRequest\DB2Request\dr_DB2Process.cs:line 6105
--- End of inner exception stack trace ---
at VOSE.Data.DataRequest.dr_DB2Process.SetCommit(DB2C onnection conn) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Data\VOSE.Data. DataRequest\DB2Request\dr_DB2Process.cs:line 6116
at VOSE.Data.DataRequest.dr_DB2Process.DeleteCommRows (String company, String
orderumber, String AttentionCode, String MatchingText, String ActionCode) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Data\VOSE.Data. DataRequest\DB2Request\dr_DB2Process.cs:line 9259
at
VOSE.Business.OrderManagement.OMBuildIVAPPNotifica tion.GetAddOrderMessage(tQueue
objQueue, tOrderManagementIndicator omindicator, Int32 intTriggerId) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Business\VOSE.B usiness.OrderManagement\OMBuildIVAPPNotification.c s:line 1045
at
VOSE.Business.OrderManagement.OMBuildIVAPPNotifica tion.GetAddOrderMessage(tQueue
objQueue, tOrderManagementIndicator omindicator) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Business\VOSE.B usiness.OrderManagement\OMBuildIVAPPNotification.c s:line 561
at VOSE.WebServices.WebServices.GetAddOrderXMLNoQueue Object(String
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersino) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\WebServices\VOS E.WebServices\WebServices.asmx.cs:line 6258
**** End screen shot ***

Please note all the additional info being shown by IE here.

The only thing in my application log is a log written by the application
logging the exception before it throws it. In includes all the exception
details put in a particular format along with an error message number and
name. This would be similar between new & old PC other than actual file
names in the stack trace. This is one I copied from my new PC and I have no
issues with it- only issue is with IE browser.
*** From event viewer ***
<Log Message="0004 DB2 System Error or Exception ; Additional
Info: Exception Type: VOSE.Common.Util.VOSEBaseApplicationException
;Exception Message: Exception encountered in dr_DB2Process.SetCommit
;Exception Stack Trace: at
VOSE.Data.DataRequest.dr_DB2Process.SetCommit(DB2C onnection conn) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Data\VOSE.Data.DataRequest\DB2Request\dr_DB2Pro cess.cs:line 6116
at VOSE.Data.DataRequest.dr_DB2Process.DeleteCommRows (String company,
String orderNumber, String AttentionCode, String MatchingText, String
ActionCode) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Data\VOSE.Data.DataRequest\DB2Request\dr_DB2Pro cess.cs:line 9259
at
VOSE.Business.OrderManagement.OMBuildIVAPPNotifica tion.GetAddOrderMessage(tQueue
objQueue, tOrderManagementIndicator omIndicator, Int32 intTriggerId) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Business\VOSE.Business.OrderManagement\OMBuildI VAPPNotification.cs:line 1056
at
VOSE.Business.OrderManagement.OMBuildIVAPPNotifica tion.GetAddOrderMessage(tQueue
objQueue, tOrderManagementIndicator omIndicator) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Business\VOSE.Business.OrderManagement\OMBuildI VAPPNotification.cs:line 561
at VOSE.WebServices.WebServices.GetAddOrderXMLNoQueue Object(String
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersion) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\WebServices\VOSE.WebServices\WebServices.asmx.c s:line
6248 ;Inner Exception Type: IBM.Data.DB2.DB2Exception ;Inner Exception
Message: ERROR [08007] [IBM][CLI Driver][DB2] SQL30073N "0x2113" Parameter
value "0x0000" is not supported. SQLSTATE=58017
;Inner Exception Stack Trace at
IBM.Data.DB2.DB2Connection.HandleError(IntPtr hHandle, SQL_HANDLE hType,
RETCODE retcode)
at IBM.Data.DB2.DB2Command.ExecuteReaderObject(Comman dBehavior behavior,
String method)
at IBM.Data.DB2.DB2Command.ExecuteNonQuery()
at VOSE.Data.DataRequest.dr_DB2Process.SetCommit(DB2C onnection conn) in
C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Data\VOSE.Data.DataRequest\DB2Request\dr_DB2Pro cess.cs:line
6105" Company="C" Severity="8" StackTrace=" at
VOSE.Common.Util.ut_Logging.PublishEvent(BaseEvent messageEvent,
CustomEventSource customEventSource) in c:\my
documents\vose\views\treynolds_september06view\vos e1\common\vose.common.util\logevents\ut_logging.cs : line 433
at VOSE.Common.Util.ut_Logging.PublishErrorEvent(Stri ng message,
CustomEventSource customEventSource, ErrorSeverity errorSeverity, String
company) in c:\my
documents\vose\views\treynolds_september06view\vos e1\common\vose.common.util\logevents\ut_logging.cs : line 277
at VOSE.Common.Util.ut_Logging.PublishErrorEvent(Int3 2 intMessageNo, String
messageDescription, ErrorSeverity errorSeverity, Int32 intOrderNo, String
strOrderTypeCodeQueue, Int32 intVersion, String additionalMessageText,
CustomEventSource eventSource, String company) in c:\my
documents\vose\views\treynolds_september06view\vos e1\common\vose.common.util\logevents\ut_logging.cs : line 358
at VOSE.Business.bu_Logging.PublishErrorEvent(String strCompany, Int32
intMessageNo, Int32 intOrderNo, String strOrderTypeCodeQueue, Int32
intVersion, String additionalMessageText, CustomEventSource eventSource) in
C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Business\VOSE.Business\bu_Logging.cs: line 117
at VOSE.Business.bu_Logging.LogException(VOSEBaseAppl icationException e,
CustomEventSource customEventSource, String strCompany) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Business\VOSE.Business\bu_Logging.cs: line 55
at VOSE.WebServices.WebServices.GetAddOrderXMLNoQueue Object(String
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersion) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\WebServices\VOSE.WebServices\WebServices.asmx.c s: line 6258
at System.Reflection.RuntimeMethodInfo.InternalInvoke (Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.InternalInvoke (Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodInfo.Invoke(Object obj, Object[] parameters)
at System.Web.Services.Protocols.LogicalMethodInfo.In voke(Object target,
Object[] values)
at System.Web.Services.Protocols.WebServiceHandler.In voke()
at System.Web.Services.Protocols.WebServiceHandler.Co reProcessRequest()
at
System.Web.Services.Protocols.SyncSessionlessHandl er.ProcessRequest(HttpContext context)
at
System.Web.CallHandlerExecutionStep.System.Web.Htt pApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously)
at System.Web.HttpApplication.ResumeSteps(Exception error)
at
System.Web.HttpApplication.System.Web.IHttpAsyncHa ndler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
at System.Web.HttpRuntime.ProcessRequestInternal(Http WorkerRequest wr)
at System.Web.HttpRuntime.ProcessRequest(HttpWorkerRe quest wr)
at System.Web.Hosting.ISAPIRuntime.ProcessRequest(Int Ptr ecb, Int32
iWRType)" EventSourceName="VOSE Web Services Incoming"
MachineName="TREYNOLDS"></Log>

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Thanks for your assistance in resolving this...Please advise me if you need
any more info. I am guessing that some setting on my new PC is not allowing
the exception info to display but don't know why.
"Walter Wang [MSFT]" wrote:

Hi Tim,

After reviewing your post, I'm not sure whether you're developing a "web
service" or a "web site". If you're developing a "web service" using
ASP.NET, how are you testing it? If you're using IE to test the web
service, as far as I know, you can only test it from localhost except
you're using another web site to test the web service.

On your "new" pc, does it report HTTP 500 error on every page? or only
report when an expected exception is thrown?

The ¡°HTTP 500 internal server error¡± is the general error message. To get
more details information, please:
1. Open the menu Tools -- Internet Options in IE.
2. Click Advanced tab.
3. Clear the checkbox ¡°Show friendly HTTP error messages¡±.
4. Click OK to close the dialogbox.
5. Try to visit the page again.
6. Create a screen shot of the error message you received.
7. Send me the screen shot as well as the event logs on the server
(application and system).

Sincerely,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Tim Reynolds]

Walter,
Thanks for your response.

I am developing a web service which I am using locally on IE browser to test
(http://localhost/..). Problem only occuring on my new PC and I only get the
HTTP 500 page when an exception is thrown from the web service. Otherwise I
see the correct result. On this PC (new PC), when I do clear the check box
'Show Friendly HTTP error messages', I do no longer get the HTTP 500 page -
but instead get a page with the exception & inner exception messages. This is
good, but I am still expecting to see the entire exception details including
the exception names and stack traces like I do on my old PC. Furthermore, on
my old PC, regardless of whether 'Show Friendly HTTP error messages' is
checked or unchecked, I do see ALL exception details.I want my new PC to
behave similarly where it gives me the ENTIRE exception details (including
exception names and stack traces).

Here is what I see in IE browser when running locally (http://localhost/..).
on my NEW (problem) PC:
**** Begin screen shot ***
Exception encountered in dr_DB2Process.SetCommit --ERROR [08007] [IBM][CLI
Driver][DB2] SQL30073N &quot;0x2113" Parameter value "0x0000" is not
supported. SQLSTATE=58017
**** End screen shot ***

Here is what I see in IE browser when running locally (http://localhost/..).
on my OLD (good) PC:
(note - Old PC has the same code and same web.config being used as NEW PC -
code is from clear case repository)

**** Begin screen shot ***
VOSE.Common.Util.VOSEBaseApplicationException: Exception encountered in
dr_DB2Process.SetCommit ---IBM.Data.DB2.Db2Exception: ERROR [08007]
[IBM][CLI Driver][DB2] SQL30073N "0x2113" Parameter value "0x0000" is not
supported. SQLSTATE=58017

at IBM.Data.DB2.DB2Connection.HandleError(IntPtr hHandle, SQL_Handle hType,
RETCODE retcode)
at IBM.Data.DB2.DB2Command.ExecuteReaderObject(Comman dBehavior behavior,
String method)
at IBM.Data.DB2.DB2Command.ExecuteNonQuery()
at VOSE.Data.DataRequest.dr_DB2Process.SetCommit(DB2C onnection conn) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Data\VOSE.Data. DataRequest\DB2Request\dr_DB2Process.cs:line 6105
--- End of inner exception stack trace ---
at VOSE.Data.DataRequest.dr_DB2Process.SetCommit(DB2C onnection conn) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Data\VOSE.Data. DataRequest\DB2Request\dr_DB2Process.cs:line 6116
at VOSE.Data.DataRequest.dr_DB2Process.DeleteCommRows (String company, String
orderumber, String AttentionCode, String MatchingText, String ActionCode) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Data\VOSE.Data. DataRequest\DB2Request\dr_DB2Process.cs:line 9259
at
VOSE.Business.OrderManagement.OMBuildIVAPPNotifica tion.GetAddOrderMessage(tQueue
objQueue, tOrderManagementIndicator omindicator, Int32 intTriggerId) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Business\VOSE.B usiness.OrderManagement\OMBuildIVAPPNotification.c s:line 1045
at
VOSE.Business.OrderManagement.OMBuildIVAPPNotifica tion.GetAddOrderMessage(tQueue
objQueue, tOrderManagementIndicator omindicator) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\Business\VOSE.B usiness.OrderManagement\OMBuildIVAPPNotification.c s:line 561
at VOSE.WebServices.WebServices.GetAddOrderXMLNoQueue Object(String
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersino) in
C:\VIEWS\TReynolds_SeptOldPC\VOSE1\WebServices\VOS E.WebServices\WebServices.asmx.cs:line 6258
**** End screen shot ***

Please note all the additional info being shown by IE here.

The only thing in my application log is a log written by the application
logging the exception before it throws it. In includes all the exception
details put in a particular format along with an error message number and
name. This would be similar between new & old PC other than actual file
names in the stack trace. This is one I copied from my new PC and I have no
issues with it- only issue is with IE browser.
*** From event viewer ***
<Log Message="0004 DB2 System Error or Exception ; Additional
Info: Exception Type: VOSE.Common.Util.VOSEBaseApplicationException
;Exception Message: Exception encountered in dr_DB2Process.SetCommit
;Exception Stack Trace: at
VOSE.Data.DataRequest.dr_DB2Process.SetCommit(DB2C onnection conn) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Data\VOSE.Data.DataRequest\DB2Request\dr_DB2Pro cess.cs:line 6116
at VOSE.Data.DataRequest.dr_DB2Process.DeleteCommRows (String company,
String orderNumber, String AttentionCode, String MatchingText, String
ActionCode) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Data\VOSE.Data.DataRequest\DB2Request\dr_DB2Pro cess.cs:line 9259
at
VOSE.Business.OrderManagement.OMBuildIVAPPNotifica tion.GetAddOrderMessage(tQueue
objQueue, tOrderManagementIndicator omIndicator, Int32 intTriggerId) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Business\VOSE.Business.OrderManagement\OMBuildI VAPPNotification.cs:line 1056
at
VOSE.Business.OrderManagement.OMBuildIVAPPNotifica tion.GetAddOrderMessage(tQueue
objQueue, tOrderManagementIndicator omIndicator) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Business\VOSE.Business.OrderManagement\OMBuildI VAPPNotification.cs:line 561
at VOSE.WebServices.WebServices.GetAddOrderXMLNoQueue Object(String
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersion) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\WebServices\VOSE.WebServices\WebServices.asmx.c s:line
6248 ;Inner Exception Type: IBM.Data.DB2.DB2Exception ;Inner Exception
Message: ERROR [08007] [IBM][CLI Driver][DB2] SQL30073N "0x2113" Parameter
value "0x0000" is not supported. SQLSTATE=58017
;Inner Exception Stack Trace at
IBM.Data.DB2.DB2Connection.HandleError(IntPtr hHandle, SQL_HANDLE hType,
RETCODE retcode)
at IBM.Data.DB2.DB2Command.ExecuteReaderObject(Comman dBehavior behavior,
String method)
at IBM.Data.DB2.DB2Command.ExecuteNonQuery()
at VOSE.Data.DataRequest.dr_DB2Process.SetCommit(DB2C onnection conn) in
C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Data\VOSE.Data.DataRequest\DB2Request\dr_DB2Pro cess.cs:line
6105" Company="C" Severity="8" StackTrace=" at
VOSE.Common.Util.ut_Logging.PublishEvent(BaseEvent messageEvent,
CustomEventSource customEventSource) in c:\my
documents\vose\views\treynolds_september06view\vos e1\common\vose.common.util\logevents\ut_logging.cs : line 433
at VOSE.Common.Util.ut_Logging.PublishErrorEvent(Stri ng message,
CustomEventSource customEventSource, ErrorSeverity errorSeverity, String
company) in c:\my
documents\vose\views\treynolds_september06view\vos e1\common\vose.common.util\logevents\ut_logging.cs : line 277
at VOSE.Common.Util.ut_Logging.PublishErrorEvent(Int3 2 intMessageNo, String
messageDescription, ErrorSeverity errorSeverity, Int32 intOrderNo, String
strOrderTypeCodeQueue, Int32 intVersion, String additionalMessageText,
CustomEventSource eventSource, String company) in c:\my
documents\vose\views\treynolds_september06view\vos e1\common\vose.common.util\logevents\ut_logging.cs : line 358
at VOSE.Business.bu_Logging.PublishErrorEvent(String strCompany, Int32
intMessageNo, Int32 intOrderNo, String strOrderTypeCodeQueue, Int32
intVersion, String additionalMessageText, CustomEventSource eventSource) in
C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Business\VOSE.Business\bu_Logging.cs: line 117
at VOSE.Business.bu_Logging.LogException(VOSEBaseAppl icationException e,
CustomEventSource customEventSource, String strCompany) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\Business\VOSE.Business\bu_Logging.cs: line 55
at VOSE.WebServices.WebServices.GetAddOrderXMLNoQueue Object(String
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersion) in C:\My
Documents\VOSE\VIEWS\TReynolds_September06view\VOS E1\WebServices\VOSE.WebServices\WebServices.asmx.c s: line 6258
at System.Reflection.RuntimeMethodInfo.InternalInvoke (Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.InternalInvoke (Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean verifyAccess)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflection.MethodInfo.Invoke(Object obj, Object[] parameters)
at System.Web.Services.Protocols.LogicalMethodInfo.In voke(Object target,
Object[] values)
at System.Web.Services.Protocols.WebServiceHandler.In voke()
at System.Web.Services.Protocols.WebServiceHandler.Co reProcessRequest()
at
System.Web.Services.Protocols.SyncSessionlessHandl er.ProcessRequest(HttpContext context)
at
System.Web.CallHandlerExecutionStep.System.Web.Htt pApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously)
at System.Web.HttpApplication.ResumeSteps(Exception error)
at
System.Web.HttpApplication.System.Web.IHttpAsyncHa ndler.BeginProcessRequest(HttpContext context, AsyncCallback cb, Object extraData)
at System.Web.HttpRuntime.ProcessRequestInternal(Http WorkerRequest wr)
at System.Web.HttpRuntime.ProcessRequest(HttpWorkerRe quest wr)
at System.Web.Hosting.ISAPIRuntime.ProcessRequest(Int Ptr ecb, Int32
iWRType)" EventSourceName="VOSE Web Services Incoming"
MachineName="TREYNOLDS"></Log>

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Thanks for your assistance in resolving this...Please advise me if you need
any more info. I am guessing that some setting on my new PC is not allowing
the exception info to display but don't know why.

Thanks,
Tim

"Walter Wang [MSFT]" wrote:

Hi Tim,

After reviewing your post, I'm not sure whether you're developing a "web
service" or a "web site". If you're developing a "web service" using
ASP.NET, how are you testing it? If you're using IE to test the web
service, as far as I know, you can only test it from localhost except
you're using another web site to test the web service.

On your "new" pc, does it report HTTP 500 error on every page? or only
report when an expected exception is thrown?

The ¡°HTTP 500 internal server error¡± is the general error message. To get
more details information, please:
1. Open the menu Tools -- Internet Options in IE.
2. Click Advanced tab.
3. Clear the checkbox ¡°Show friendly HTTP error messages¡±.
4. Click OK to close the dialogbox.
5. Try to visit the page again.
6. Create a screen shot of the error message you received.
7. Send me the screen shot as well as the event logs on the server
(application and system).

Sincerely,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Walter Wang [MSFT]]

Hi Tim,

From your description of the two pc's behavior, it seems the first one is
only showing the exception's message.

I recommend you use the simplest web service to diagnose this issue:

public string HelloWorld() {
throw new Exception("hello");
}

If my guess is right, the first pc should only report

=========================
hello
=========================

while the second pc will report something like:

=========================
System.Exception: hello
at Service.HelloWorld() in
c:\Inetpub\wwwroot\webserviceException2\App_Code\S ervice.cs:line 18
=========================

Please create a console application, add web reference to the simplest web
service, then call the HelloWorld() method, on 2nd pc, it should report
something like:

=========================
An unhandled exception of type
'System.Web.Services.Protocols.SoapException' occurred in
System.Web.Services.dll

Additional information: System.Web.Services.Protocols.SoapException: Server
was unable to process request. ---System.Exception: hello
at Service.HelloWorld() in
c:\Inetpub\wwwroot\webserviceException2\App_Code\S ervice.cs:line 18
--- End of inner exception stack trace ---
=========================

What I want to know is the exception reported by the 1st pc. If it's still
only a message, then this issue is not related to IE, it should be related
to the web service handler. If it's correct, then this issue is related to
IE (or the built-in test page to test the web service).

Please let me know the result. Thanks.

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Tim Reynolds]

Walter,
Yes, the new web method gave results exactly as you predicted on new pc and
on the old pc. Then, per your suggsetion, on the old PC, I put in a console
app to refer to this web method on new PC. When I ran this console app in
debug mode, the exception came back in a Microsoft Development Environment
window with text "An unhandled exception of type
'System.Web.Services.Protocols.SoapException' occurred in
System.Web.Services.dll

Additional information: Server was unable to process request. ---hello"

As you can see here, this is different than your exepcted result in that the
exception type (System.Exception) and stack trace ('at Service.HelloWorld()
in
c:\Inetpub\wwwroot\webserviceException2\App_Code\S ervice.cs:line 18
--- End of inner exception stack trace ---') are NOT returned.

Please advise....

Much thanks,
Tim Reynolds

"Walter Wang [MSFT]" wrote:

Hi Tim,

From your description of the two pc's behavior, it seems the first one is
only showing the exception's message.

I recommend you use the simplest web service to diagnose this issue:

public string HelloWorld() {
throw new Exception("hello");
}

If my guess is right, the first pc should only report

=========================
hello
=========================

while the second pc will report something like:

=========================
System.Exception: hello
at Service.HelloWorld() in
c:\Inetpub\wwwroot\webserviceException2\App_Code\S ervice.cs:line 18
=========================

Please create a console application, add web reference to the simplest web
service, then call the HelloWorld() method, on 2nd pc, it should report
something like:

=========================
An unhandled exception of type
'System.Web.Services.Protocols.SoapException' occurred in
System.Web.Services.dll

Additional information: System.Web.Services.Protocols.SoapException: Server
was unable to process request. ---System.Exception: hello
at Service.HelloWorld() in
c:\Inetpub\wwwroot\webserviceException2\App_Code\S ervice.cs:line 18
--- End of inner exception stack trace ---
=========================

What I want to know is the exception reported by the 1st pc. If it's still
only a message, then this issue is not related to IE, it should be related
to the web service handler. If it's correct, then this issue is related to
IE (or the built-in test page to test the web service).

Please let me know the result. Thanks.

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Tim Reynolds]

Walter,
One more test I did was to create a console app on my NEW pc and call to the
web service on my OLD pc. The result was that the exception comign back DID
contain the stack trace and exception type - "An unhandled exception of type
'System.Web.Services.Protocols.SoapException' occurred in
system.web.services.dll

Additional information: System.Web.Services.Protocols.SoapException: Server
was unable to process request. ---System.Exception: hello
at VOSE.WebServices.WebServices.HelloWorld() in
c:\views\treynolds_septoldpc\vose1\webservices\vos e.webservices\webservices.asmx.cs:line 90
--- End of inner exception stack trace ---"

So looks like IE has nothing to do with it. The info is returned from oldPC
but not from newPC for some reason....

Please advise what settings I can change on my newPC to mirror the old in
this regard.

Thank you,
Tim Reynolds
"Walter Wang [MSFT]" wrote:

Hi Tim,

From your description of the two pc's behavior, it seems the first one is
only showing the exception's message.

I recommend you use the simplest web service to diagnose this issue:

public string HelloWorld() {
throw new Exception("hello");
}

If my guess is right, the first pc should only report

=========================
hello
=========================

while the second pc will report something like:

=========================
System.Exception: hello
at Service.HelloWorld() in
c:\Inetpub\wwwroot\webserviceException2\App_Code\S ervice.cs:line 18
=========================

Please create a console application, add web reference to the simplest web
service, then call the HelloWorld() method, on 2nd pc, it should report
something like:

=========================
An unhandled exception of type
'System.Web.Services.Protocols.SoapException' occurred in
System.Web.Services.dll

Additional information: System.Web.Services.Protocols.SoapException: Server
was unable to process request. ---System.Exception: hello
at Service.HelloWorld() in
c:\Inetpub\wwwroot\webserviceException2\App_Code\S ervice.cs:line 18
--- End of inner exception stack trace ---
=========================

What I want to know is the exception reported by the 1st pc. If it's still
only a message, then this issue is not related to IE, it should be related
to the web service handler. If it's correct, then this issue is related to
IE (or the built-in test page to test the web service).

Please let me know the result. Thanks.

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Kevin Yu [MSFT]]

Hi Tim,

It's better to compare the returned soap message from both web services to
see the difference. You can use any network trace tools you're familiar
with. If you don't have one, I suggest Microsoft SOAP Toolkit 3.0. It can
be downloaded from the following link:

http://www.microsoft.com/downloads/d...0dd-ceec-4088-
9753-86f052ec8450&DisplayLang=en

Please let me know the results, so that we can make further troubleshooting.

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Tim Reynolds]

Thanks Kevin,
I did use SOAP Toolkit to review the soap messages returned. The SOAP
message being returned from web service on new PC does not include the
exception type and stack trace. That is the difference. New PC not
returning the info - and that makes sense while testing locally why IE
browser only gets the exception message - and not the exception type and
stack trace. Question is, what settings on this new PC are surpressing this
information? I need to get back this data.

Please advise...

Thanks
Tim Reynolds
"Kevin Yu [MSFT]" wrote:

Hi Tim,

It's better to compare the returned soap message from both web services to
see the difference. You can use any network trace tools you're familiar
with. If you don't have one, I suggest Microsoft SOAP Toolkit 3.0. It can
be downloaded from the following link:

http://www.microsoft.com/downloads/d...0dd-ceec-4088-
9753-86f052ec8450&DisplayLang=en

Please let me know the results, so that we can make further troubleshooting.

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Kevin Yu [MSFT]]

Hi Tim,

Yes, we're trying to analyze what is causing the difference in response.
Now we have compared the response from server, but have you checked the
difference for requests? Also, please make sure that the two clients are
independent machines from the server. So that we might know what are the
differences between two requests besides IP address.

Thank you for your cooperation.

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Tim Reynolds]

Kevin,
The clients are not two independent machines from the server. Here is the
scenario: I have a PC I've used to develop a while. When an exception is
thrown from a web service hosted on that machine, that machine returns the
stack trace and the exception type along with the exception message. This is
true regardless of whether I call the web service from an IE browser or a
console app - and whether I call it locally or remotely. On the new PC I
have, when an exception is thrown from a web service hosted on that machine,
the machine returns ONLY the exception message. This is also true regardless
of whether I call the web service from an IE browswer or a console app - and
again whether I call it locally or remotely.

Based on Walter Yang's post on this previously, he is indicating then that
the problem may be related to the the web service handler.

I do not know how this 'web service handler' works - but only that one my
new PC it seems to handle the exception and not pass on the exception type
and stack trace.

Is there anything that can be done to expedite the resolution on this? I
really apprecaite it.

Thanks,
Tim Reynolds

"Kevin Yu [MSFT]" wrote:

Hi Tim,

Yes, we're trying to analyze what is causing the difference in response.
Now we have compared the response from server, but have you checked the
difference for requests? Also, please make sure that the two clients are
independent machines from the server. So that we might know what are the
differences between two requests besides IP address.

Thank you for your cooperation.

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[John Saunders]

"Tim Reynolds" <ti**********@online.nospamwrote in message
news:C4**********************************@microsof t.com...

Kevin,
The clients are not two independent machines from the server. Here is the
scenario: I have a PC I've used to develop a while. When an exception is
thrown from a web service hosted on that machine, that machine returns the
stack trace and the exception type along with the exception message. This
is
true regardless of whether I call the web service from an IE browser or a
console app - and whether I call it locally or remotely. On the new PC I
have, when an exception is thrown from a web service hosted on that
machine,
the machine returns ONLY the exception message. This is also true
regardless
of whether I call the web service from an IE browswer or a console app -
and
again whether I call it locally or remotely.

Based on Walter Yang's post on this previously, he is indicating then that
the problem may be related to the the web service handler.

I do not know how this 'web service handler' works - but only that one my
new PC it seems to handle the exception and not pass on the exception type
and stack trace.

Is there anything that can be done to expedite the resolution on this? I
really apprecaite it.

Tim, if it helps to know that you're not alone in this, then this should
help: I've got the same problem. On Windows Server 2003 systems, I get the
entire stack trace. On Windows XP systems, I do not.

John

[Kevin Yu [MSFT]]

Hi Tim

Thank your for your explanation. I tried to reproduce it on my machine. But
as far as I can see, I only got the stack trace from a local IE access. The
remote IE access and Console app accesses all returned without the server
side stack trace.

I assume there are some differences between our web.config file. Could you
please post your web.config file here?

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Tim Reynolds]

Sure Kevin.
Both PC's are using the same web config...

<?xml version="1.0" encoding="utf-8"?>
<!-- Note 1 - This file will need to be availalbe to operation staff,
support staff, & VOSE team for modification in all environments
Note 2 - Formatters must exists in %windir%\system32 folder -->
<configuration>
<configSections>
<section name="eventFormatterSettings"
type="Microsoft.ApplicationBlocks.Logging.EventSin ks.FormatterConfigHandler,
Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"/>
</configSections>

<eventFormatterSettings>
<!-- Formatters referred to by EnterpriseInstrumentation are listed here
They must exists in %windir%\system32 folder -->
<formatterInfo name="logSinkXslt"
type="Microsoft.ApplicationBlocks.Logging.EventSin ks.XsltEventFormatter,
Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"
fullyQualifiedDefaultXsltPath="eventlogtransform.x slt"/>
<formatterInfo name="basiclogSinkXslt"
type="Microsoft.ApplicationBlocks.Logging.EventSin ks.XsltEventFormatter,
Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"
fullyQualifiedDefaultXsltPath="eventlogtransform.x slt"/>
<formatterInfo name="sqlSinkXslt"
type="Microsoft.ApplicationBlocks.Logging.EventSin ks.XsltEventFormatter,
Microsoft.ApplicationBlocks.Logging.EventSinks, Version=1.0.0.0,
Culture=neutral, PublicKeyToken=da59d79eb5fd8f1a"
fullyQualifiedDefaultXsltPath="eventsqltransform.x slt"/>
</eventFormatterSettings>

<appSettings>
<!-- applicationLogLevel is used to determine if event is logged
The event sink in question (ie, event log, or sqlsink) compares the
eventPublishLogLevel
with the applicationLogLevel. If eventPublishLogLevel is less than or
equal to
applicationLogLevel, the event is logged. Otherwise it is not. To turn
off all logging
for the application, the applicationLogLevel must be set to none. To
turn on all logging,
the applicationLogLevel must be set to debug.
Typically, for production the applicationLogLevel will be set to error.
In development, it will be set to debug.
For GUI & WebServices projects, when the web.config is changed, the change
takes place immediately. For all the rest, the windows service needs
refreshed
in order for the change to be picked up-->
<add key="applicationLogLevel" value="5"/<!--(possible values are
none,always,error,warning,informational,debug)-->
<add key="instrumentationConfigFile"
value="..\..\EnterpriseInstrumentation.config"/>
<add key="Defaultconnstring" value="data source=113.130.192.177;
database=VOSE_H;user id=voseapp;password=voseapp"/>
<add key="SACCompaniesToProcess" value="S C A N M H "/>
<add key="TPACompaniesToProcess" value="F K I L G"/>
<add key="VOSE.WebServices.RemoteWebServices.WebService s"
value="http://localhost/appl02/WebServices.asmx"/>
<add key="VOSE.WebServices.RemoteEsales.ESales"
value="http://localhost/appl02/Esales.asmx"/>
<add key="VOSE.WebServices.RemoteServiceOrders.ServiceO rders"
value="http://localhost/appl02/ServiceOrders.asmx"/>
<add key="VOSE.WebServices.RemoteSPIDER.SPIDER"
value="http://localhost/appl02/SPIDER.asmx"/>
<add key="VOSE.WebServices.RemoteTPV.TPV"
value="http://localhost/appl02/TPV.asmx"/>
<add key="VOSE.WebServices.RemoteCreditStatus.CreditSta tus"
value="http://localhost/appl02/CreditStatus.asmx"/>
<add key="VOSE.WebServices.RemoteRedLightOrderStatus.Re dLightOrderStatus"
value="http://localhost/appl02/RedLightOrderStatus.asmx"/>
</appSettings>

<system.net>
<defaultProxy>
<proxy usesystemdefault="false"/>
</defaultProxy>
<connectionManagement>
<add address="*" maxconnection="1000"/>
</connectionManagement>
</system.net>

<system.web>

<!-- DYNAMIC DEBUG COMPILATION
Set compilation debug="true" to enable ASPX debugging. Otherwise,
setting this value to
false will improve runtime performance of this application.
Set compilation debug="true" to insert debugging symbols (.pdb
information)
into the compiled page. Because this creates a larger file that
executes
more slowly, you should set this value to true only when debugging
and to
false at all other times. For more information, refer to the
documentation about
debugging ASP.NET files.
-->
<compilation defaultLanguage="c#" debug="true"/>
<!-- CUSTOM ERROR MESSAGES
Set customErrors mode="On" or "RemoteOnly" to enable custom error
messages, "Off" to disable.
Add <errortags for each of the errors you want to handle.

"On" Always display custom (friendly) messages.
"Off" Always display detailed ASP.NET error information.
"RemoteOnly" Display custom (friendly) messages only to users not
running
on the local Web server. This setting is recommended for security
purposes, so
that you do not display application detail information to remote
clients.
-->
<customErrors mode="Off"/>

<!-- AUTHENTICATION
This section sets the authentication policies of the application.
Possible modes are "Windows",
"Forms", "Passport" and "None"

"None" No authentication is performed.
"Windows" IIS performs authentication (Basic, Digest, or
Integrated Windows) according to
its settings for the application. Anonymous access must be
disabled in IIS.
"Forms" You provide a custom form (Web page) for users to enter
their credentials, and then
you authenticate them in your application. A user credential
token is stored in a cookie.
"Passport" Authentication is performed via a centralized
authentication service provided
by Microsoft that offers a single logon and core profile services
for member sites.
-->
<authentication mode="Windows"/>

<!-- AUTHORIZATION
This section sets the authorization policies of the application.
You can allow or deny access
to application resources by user or role. Wildcards: "*" mean
everyone, "?" means anonymous
(unauthenticated) users.
-->

<authorization>
<allow users="*"/<!-- Allow all users -->
<!-- <allow users="[comma separated list of users]"
roles="[comma separated list of roles]"/>
<deny users="[comma separated list of users]"
roles="[comma separated list of roles]"/>
-->
</authorization>

<!-- APPLICATION-LEVEL TRACE LOGGING
Application-level tracing enables trace log output for every page
within an application.
Set trace enabled="true" to enable application trace logging. If
pageOutput="true", the
trace information will be displayed at the bottom of each page.
Otherwise, you can view the
application trace log by browsing the "trace.axd" page from your
web application
root.
-->
<trace enabled="false" requestLimit="10" pageOutput="false"
traceMode="SortByTime" localOnly="true"/>

<!-- SESSION STATE SETTINGS
By default ASP.NET uses cookies to identify which requests belong
to a particular session.
If cookies are not available, a session can be tracked by adding a
session identifier to the URL.
To disable cookies, set sessionState cookieless="true".
-->
<!--<sessionState mode="InProc"
stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data
source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="20"/>
-->
<sessionState mode="SQLServer"
stateConnectionString="tcpip=113.130.192.177" sqlConnectionString="data
source=113.130.192.177;user id=voseapp;password=voseapp" cookieless="false"
timeout="15"/>
<!-- GLOBALIZATION
This section sets the globalization settings of the application.
-->
<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
<webServices>
<protocols>
<add name="HttpGet"/>
<add name="HttpPost"/>
</protocols>
</webServices>

</system.web>
</configuration>

"Kevin Yu [MSFT]" wrote:

Hi Tim

Thank your for your explanation. I tried to reproduce it on my machine. But
as far as I can see, I only got the stack trace from a local IE access. The
remote IE access and Console app accesses all returned without the server
side stack trace.

I assume there are some differences between our web.config file. Could you
please post your web.config file here?

Kevin Yu
Microsoft Online Community Support
==================================================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)

[Walter Wang [MSFT]]

Hi Tim,

I was out of office last week so my colleague Kevin helped me on this case.

Would you please give me following information:

1. The OS version of your "old pc" and "new pc".
2. The configured ASP.NET version of your web service in IIS (you can
verify this by open IIS manager and check the properties dialog of the web
service, there's a Combox named "ASP.NET version" on the tab named
"ASP.NET")

Per John's information on the difference behavior of Windows Server 2003
and XP, I didn't reproduce the issue with the minimum HelloWorld service.

Since the "new pc" didn't produce the exception stack trace even tested
locally, I think the "customErrors" setting in web.config is not related.
And the setting:

<webServices>
<protocols>
<add name="HttpGet"/>
<add name="HttpPost"/>
</protocols>
</webServices>

is also related to remote invoking the webservice, which I also think is
irrelevant. So I assume removing web.config for the HelloWorld service will
also reproduce the issue on your "new pc". Then it may be related to the
installed .NET runtime, I recommend you to reinstall .NET runtime to see
whether this will fix the problem.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Tim Reynolds]

Thank you, Walter.

Old PC - XP Pro Version 2002 Service Pack 2
New PC - XP Pro Version 2002 Service Pack 1

(Note here - by memory- -when my old PC was service Pack 1 - which it was
for a long time - it always would return stack trace and exception type -
Therefore I do not believe the difference in Service Pack answers this issue).

As for the ASP.Net version, I cannot find the 'ASP.NET' tab on properties of
the web service in IIS. The only tabs I see are Virtual Directory,
Documents, Directory Security, HTTP Headers, and Custom Errors. However, on
both PC's, in Windows Explorer I find
C:\Inetpub\wwwroot\aspnet_client\system_web\1_1_43 22. So I'm guessing it
would be version 1.1.4322....for both..

As for reinstalling .Net Framework, I belive this was the Visual Studio .Net
2003 Prerequisites (disk 2072 from MDSN media kit) that I originally
installed on this PC.

Is this what you are recommending me to reinstall?

Thanks,
Tim Reynolds

"Walter Wang [MSFT]" wrote:

Hi Tim,

I was out of office last week so my colleague Kevin helped me on this case.

Would you please give me following information:

1. The OS version of your "old pc" and "new pc".
2. The configured ASP.NET version of your web service in IIS (you can
verify this by open IIS manager and check the properties dialog of the web
service, there's a Combox named "ASP.NET version" on the tab named
"ASP.NET")

Per John's information on the difference behavior of Windows Server 2003
and XP, I didn't reproduce the issue with the minimum HelloWorld service.

Since the "new pc" didn't produce the exception stack trace even tested
locally, I think the "customErrors" setting in web.config is not related.
And the setting:

<webServices>
<protocols>
<add name="HttpGet"/>
<add name="HttpPost"/>
</protocols>
</webServices>

is also related to remote invoking the webservice, which I also think is
irrelevant. So I assume removing web.config for the HelloWorld service will
also reproduce the issue on your "new pc". Then it may be related to the
installed .NET runtime, I recommend you to reinstall .NET runtime to see
whether this will fix the problem.
Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Walter Wang [MSFT]]

Hi Tim,

First, I suggest you use following steps to compare the .NET Framework
version on your "old pc" and "new pc":

#How to determine which versions of the .NET Framework are installed and
whether service packs have been applied
http://support.microsoft.com/kb/318785/

Then I suggest you reinstall .NET Framework 1.1 SP1 on "new pc":

http://www.microsoft.com/downloads/d...&FamilyID=A8F5
654F-088E-40B2-BBDB-A83353618B38

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Tim Reynolds]

Hi Walter,
Old PC - 1.1.4322.573 - Original RTM
New PC - 1.1.4322.2032 - Service Pack 1

Please advise what to do since new PC DOES have Service Pack 1.

Thanks,
Tim

"Walter Wang [MSFT]" wrote:

Hi Tim,

First, I suggest you use following steps to compare the .NET Framework
version on your "old pc" and "new pc":

#How to determine which versions of the .NET Framework are installed and
whether service packs have been applied
http://support.microsoft.com/kb/318785/

Then I suggest you reinstall .NET Framework 1.1 SP1 on "new pc":

http://www.microsoft.com/downloads/d...&FamilyID=A8F5
654F-088E-40B2-BBDB-A83353618B38

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Walter Wang [MSFT]]

Hi Tim,

Thank you for your quick update.

What I can suggest now is to remove the .NET Framework on "new pc" and
reinstall it to see if it works.

Since this issue is environment specific and non-reproducible, what we can
do in newsgroup support is to suggest some steps to track down the problem.
For complete and efficient diagnosing, I suggest you contact PSS for
further assistance which will provide some thorough throubleshooting like
dump analyze or live debugging.

For PSS support or a local on site, you can also try contacting the global
support center through the following link:

http://support.microsoft.com/gp/assistsupport

They will provide you the detailed info on how to contact the local
developer support center.

That said, if you wish, we can still continue this discussion here.

Regards,
Walter Wang (wa****@online.microsoft.com, remove 'online.')
Microsoft Online Community Support

==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.