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.S etCommit --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.Uti l.VOSEBaseAppli cationException : Exception encountered in
dr_DB2Process.S etCommit ---IBM.Data.DB2.Db 2Exception: ERROR [08007]
[IBM][CLI Driver][DB2] SQL30073N "0x2113" Parameter value "0x0000" is not
supported. SQLSTATE=58017

at IBM.Data.DB2.DB 2Connection.Han dleError(IntPtr hHandle, SQL_Handle hType,
RETCODE retcode)
at IBM.Data.DB2.DB 2Command.Execut eReaderObject(C ommandBehavior behavior,
String method)
at IBM.Data.DB2.DB 2Command.Execut eNonQuery()
at VOSE.Data.DataR equest.dr_DB2Pr ocess.SetCommit (DB2Connection conn) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Data\VOSE. Data.DataReques t\DB2Request\dr _DB2Process.cs: line 6105
--- End of inner exception stack trace ---
at VOSE.Data.DataR equest.dr_DB2Pr ocess.SetCommit (DB2Connection conn) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Data\VOSE. Data.DataReques t\DB2Request\dr _DB2Process.cs: line 6116
at VOSE.Data.DataR equest.dr_DB2Pr ocess.DeleteCom mRows(String company, String
orderumber, String AttentionCode, String MatchingText, String ActionCode) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Data\VOSE. Data.DataReques t\DB2Request\dr _DB2Process.cs: line 9259
at
VOSE.Business.O rderManagement. OMBuildIVAPPNot ification.GetAd dOrderMessage(t Queue
objQueue, tOrderManagemen tIndicator omindicator, Int32 intTriggerId) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Business\V OSE.Business.Or derManagement\O MBuildIVAPPNoti fication.cs:lin e 1045
at
VOSE.Business.O rderManagement. OMBuildIVAPPNot ification.GetAd dOrderMessage(t Queue
objQueue, tOrderManagemen tIndicator omindicator) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Business\V OSE.Business.Or derManagement\O MBuildIVAPPNoti fication.cs:lin e 561
at VOSE.WebService s.WebServices.G etAddOrderXMLNo QueueObject(Str ing
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersino) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\WebService s\VOSE.WebServi ces\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.Uti l.VOSEBaseAppli cationException
;Exception Message: Exception encountered in dr_DB2Process.S etCommit
;Exception Stack Trace: at
VOSE.Data.DataR equest.dr_DB2Pr ocess.SetCommit (DB2Connection conn) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Data\VO SE.Data.DataReq uest\DB2Request \dr_DB2Process. cs:line 6116
at VOSE.Data.DataR equest.dr_DB2Pr ocess.DeleteCom mRows(String company,
String orderNumber, String AttentionCode, String MatchingText, String
ActionCode) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Data\VO SE.Data.DataReq uest\DB2Request \dr_DB2Process. cs:line 9259
at
VOSE.Business.O rderManagement. OMBuildIVAPPNot ification.GetAd dOrderMessage(t Queue
objQueue, tOrderManagemen tIndicator omIndicator, Int32 intTriggerId) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Busines s\VOSE.Business .OrderManagemen t\OMBuildIVAPPN otification.cs: line 1056
at
VOSE.Business.O rderManagement. OMBuildIVAPPNot ification.GetAd dOrderMessage(t Queue
objQueue, tOrderManagemen tIndicator omIndicator) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Busines s\VOSE.Business .OrderManagemen t\OMBuildIVAPPN otification.cs: line 561
at VOSE.WebService s.WebServices.G etAddOrderXMLNo QueueObject(Str ing
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersion) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\WebServ ices\VOSE.WebSe rvices\WebServi ces.asmx.cs:lin e
6248 ;Inner Exception Type: IBM.Data.DB2.DB 2Exception ;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.DB 2Connection.Han dleError(IntPtr hHandle, SQL_HANDLE hType,
RETCODE retcode)
at IBM.Data.DB2.DB 2Command.Execut eReaderObject(C ommandBehavior behavior,
String method)
at IBM.Data.DB2.DB 2Command.Execut eNonQuery()
at VOSE.Data.DataR equest.dr_DB2Pr ocess.SetCommit (DB2Connection conn) in
C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Data\VO SE.Data.DataReq uest\DB2Request \dr_DB2Process. cs:line
6105" Company="C" Severity="8" StackTrace=" at
VOSE.Common.Uti l.ut_Logging.Pu blishEvent(Base Event messageEvent,
CustomEventSour ce customEventSour ce) in c:\my
documents\vose\ views\treynolds _september06vie w\vose1\common\ vose.common.uti l\logevents\ut_ logging.cs: line 433
at VOSE.Common.Uti l.ut_Logging.Pu blishErrorEvent (String message,
CustomEventSour ce customEventSour ce, ErrorSeverity errorSeverity, String
company) in c:\my
documents\vose\ views\treynolds _september06vie w\vose1\common\ vose.common.uti l\logevents\ut_ logging.cs: line 277
at VOSE.Common.Uti l.ut_Logging.Pu blishErrorEvent (Int32 intMessageNo, String
messageDescript ion, ErrorSeverity errorSeverity, Int32 intOrderNo, String
strOrderTypeCod eQueue, Int32 intVersion, String additionalMessa geText,
CustomEventSour ce eventSource, String company) in c:\my
documents\vose\ views\treynolds _september06vie w\vose1\common\ vose.common.uti l\logevents\ut_ logging.cs: line 358
at VOSE.Business.b u_Logging.Publi shErrorEvent(St ring strCompany, Int32
intMessageNo, Int32 intOrderNo, String strOrderTypeCod eQueue, Int32
intVersion, String additionalMessa geText, CustomEventSour ce eventSource) in
C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Busines s\VOSE.Business \bu_Logging.cs: line 117
at VOSE.Business.b u_Logging.LogEx ception(VOSEBas eApplicationExc eption e,
CustomEventSour ce customEventSour ce, String strCompany) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Busines s\VOSE.Business \bu_Logging.cs: line 55
at VOSE.WebService s.WebServices.G etAddOrderXMLNo QueueObject(Str ing
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersion) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\WebServ ices\VOSE.WebSe rvices\WebServi ces.asmx.cs: line 6258
at System.Reflecti on.RuntimeMetho dInfo.InternalI nvoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean isBinderDefault , Assembly caller, Boolean verifyAccess)
at System.Reflecti on.RuntimeMetho dInfo.InternalI nvoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean verifyAccess)
at System.Reflecti on.RuntimeMetho dInfo.Invoke(Ob ject obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflecti on.MethodInfo.I nvoke(Object obj, Object[] parameters)
at System.Web.Serv ices.Protocols. LogicalMethodIn fo.Invoke(Objec t target,
Object[] values)
at System.Web.Serv ices.Protocols. WebServiceHandl er.Invoke()
at System.Web.Serv ices.Protocols. WebServiceHandl er.CoreProcessR equest()
at
System.Web.Serv ices.Protocols. SyncSessionless Handler.Process Request(HttpCon text context)
at
System.Web.Call HandlerExecutio nStep.System.We b.HttpApplicati on+IExecutionSt ep.Execute()
at System.Web.Http Application.Exe cuteStep(IExecu tionStep step, Boolean&
completedSynchr onously)
at System.Web.Http Application.Res umeSteps(Except ion error)
at
System.Web.Http Application.Sys tem.Web.IHttpAs yncHandler.Begi nProcessRequest (HttpContext context, AsyncCallback cb, Object extraData)
at System.Web.Http Runtime.Process RequestInternal (HttpWorkerRequ est wr)
at System.Web.Http Runtime.Process Request(HttpWor kerRequest wr)
at System.Web.Host ing.ISAPIRuntim e.ProcessReques t(IntPtr ecb, Int32
iWRType)" EventSourceName ="VOSE Web Services Incoming"
MachineName="TR EYNOLDS"></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.S etCommit --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.Uti l.VOSEBaseAppli cationException : Exception encountered in
dr_DB2Process.S etCommit ---IBM.Data.DB2.Db 2Exception: ERROR [08007]
[IBM][CLI Driver][DB2] SQL30073N "0x2113" Parameter value "0x0000" is not
supported. SQLSTATE=58017

at IBM.Data.DB2.DB 2Connection.Han dleError(IntPtr hHandle, SQL_Handle hType,
RETCODE retcode)
at IBM.Data.DB2.DB 2Command.Execut eReaderObject(C ommandBehavior behavior,
String method)
at IBM.Data.DB2.DB 2Command.Execut eNonQuery()
at VOSE.Data.DataR equest.dr_DB2Pr ocess.SetCommit (DB2Connection conn) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Data\VOSE. Data.DataReques t\DB2Request\dr _DB2Process.cs: line 6105
--- End of inner exception stack trace ---
at VOSE.Data.DataR equest.dr_DB2Pr ocess.SetCommit (DB2Connection conn) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Data\VOSE. Data.DataReques t\DB2Request\dr _DB2Process.cs: line 6116
at VOSE.Data.DataR equest.dr_DB2Pr ocess.DeleteCom mRows(String company, String
orderumber, String AttentionCode, String MatchingText, String ActionCode) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Data\VOSE. Data.DataReques t\DB2Request\dr _DB2Process.cs: line 9259
at
VOSE.Business.O rderManagement. OMBuildIVAPPNot ification.GetAd dOrderMessage(t Queue
objQueue, tOrderManagemen tIndicator omindicator, Int32 intTriggerId) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Business\V OSE.Business.Or derManagement\O MBuildIVAPPNoti fication.cs:lin e 1045
at
VOSE.Business.O rderManagement. OMBuildIVAPPNot ification.GetAd dOrderMessage(t Queue
objQueue, tOrderManagemen tIndicator omindicator) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\Business\V OSE.Business.Or derManagement\O MBuildIVAPPNoti fication.cs:lin e 561
at VOSE.WebService s.WebServices.G etAddOrderXMLNo QueueObject(Str ing
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersino) in
C:\VIEWS\TReyno lds_SeptOldPC\V OSE1\WebService s\VOSE.WebServi ces\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.Uti l.VOSEBaseAppli cationException
;Exception Message: Exception encountered in dr_DB2Process.S etCommit
;Exception Stack Trace: at
VOSE.Data.DataR equest.dr_DB2Pr ocess.SetCommit (DB2Connection conn) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Data\VO SE.Data.DataReq uest\DB2Request \dr_DB2Process. cs:line 6116
at VOSE.Data.DataR equest.dr_DB2Pr ocess.DeleteCom mRows(String company,
String orderNumber, String AttentionCode, String MatchingText, String
ActionCode) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Data\VO SE.Data.DataReq uest\DB2Request \dr_DB2Process. cs:line 9259
at
VOSE.Business.O rderManagement. OMBuildIVAPPNot ification.GetAd dOrderMessage(t Queue
objQueue, tOrderManagemen tIndicator omIndicator, Int32 intTriggerId) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Busines s\VOSE.Business .OrderManagemen t\OMBuildIVAPPN otification.cs: line 1056
at
VOSE.Business.O rderManagement. OMBuildIVAPPNot ification.GetAd dOrderMessage(t Queue
objQueue, tOrderManagemen tIndicator omIndicator) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Busines s\VOSE.Business .OrderManagemen t\OMBuildIVAPPN otification.cs: line 561
at VOSE.WebService s.WebServices.G etAddOrderXMLNo QueueObject(Str ing
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersion) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\WebServ ices\VOSE.WebSe rvices\WebServi ces.asmx.cs:lin e
6248 ;Inner Exception Type: IBM.Data.DB2.DB 2Exception ;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.DB 2Connection.Han dleError(IntPtr hHandle, SQL_HANDLE hType,
RETCODE retcode)
at IBM.Data.DB2.DB 2Command.Execut eReaderObject(C ommandBehavior behavior,
String method)
at IBM.Data.DB2.DB 2Command.Execut eNonQuery()
at VOSE.Data.DataR equest.dr_DB2Pr ocess.SetCommit (DB2Connection conn) in
C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Data\VO SE.Data.DataReq uest\DB2Request \dr_DB2Process. cs:line
6105" Company="C" Severity="8" StackTrace=" at
VOSE.Common.Uti l.ut_Logging.Pu blishEvent(Base Event messageEvent,
CustomEventSour ce customEventSour ce) in c:\my
documents\vose\ views\treynolds _september06vie w\vose1\common\ vose.common.uti l\logevents\ut_ logging.cs: line 433
at VOSE.Common.Uti l.ut_Logging.Pu blishErrorEvent (String message,
CustomEventSour ce customEventSour ce, ErrorSeverity errorSeverity, String
company) in c:\my
documents\vose\ views\treynolds _september06vie w\vose1\common\ vose.common.uti l\logevents\ut_ logging.cs: line 277
at VOSE.Common.Uti l.ut_Logging.Pu blishErrorEvent (Int32 intMessageNo, String
messageDescript ion, ErrorSeverity errorSeverity, Int32 intOrderNo, String
strOrderTypeCod eQueue, Int32 intVersion, String additionalMessa geText,
CustomEventSour ce eventSource, String company) in c:\my
documents\vose\ views\treynolds _september06vie w\vose1\common\ vose.common.uti l\logevents\ut_ logging.cs: line 358
at VOSE.Business.b u_Logging.Publi shErrorEvent(St ring strCompany, Int32
intMessageNo, Int32 intOrderNo, String strOrderTypeCod eQueue, Int32
intVersion, String additionalMessa geText, CustomEventSour ce eventSource) in
C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Busines s\VOSE.Business \bu_Logging.cs: line 117
at VOSE.Business.b u_Logging.LogEx ception(VOSEBas eApplicationExc eption e,
CustomEventSour ce customEventSour ce, String strCompany) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\Busines s\VOSE.Business \bu_Logging.cs: line 55
at VOSE.WebService s.WebServices.G etAddOrderXMLNo QueueObject(Str ing
strCompany, Int32 intOrderNo, String strOrderType, Int32 intVersion) in C:\My
Documents\VOSE\ VIEWS\TReynolds _September06vie w\VOSE1\WebServ ices\VOSE.WebSe rvices\WebServi ces.asmx.cs: line 6258
at System.Reflecti on.RuntimeMetho dInfo.InternalI nvoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean isBinderDefault , Assembly caller, Boolean verifyAccess)
at System.Reflecti on.RuntimeMetho dInfo.InternalI nvoke(Object obj,
BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
culture, Boolean verifyAccess)
at System.Reflecti on.RuntimeMetho dInfo.Invoke(Ob ject obj, BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Reflecti on.MethodInfo.I nvoke(Object obj, Object[] parameters)
at System.Web.Serv ices.Protocols. LogicalMethodIn fo.Invoke(Objec t target,
Object[] values)
at System.Web.Serv ices.Protocols. WebServiceHandl er.Invoke()
at System.Web.Serv ices.Protocols. WebServiceHandl er.CoreProcessR equest()
at
System.Web.Serv ices.Protocols. SyncSessionless Handler.Process Request(HttpCon text context)
at
System.Web.Call HandlerExecutio nStep.System.We b.HttpApplicati on+IExecutionSt ep.Execute()
at System.Web.Http Application.Exe cuteStep(IExecu tionStep step, Boolean&
completedSynchr onously)
at System.Web.Http Application.Res umeSteps(Except ion error)
at
System.Web.Http Application.Sys tem.Web.IHttpAs yncHandler.Begi nProcessRequest (HttpContext context, AsyncCallback cb, Object extraData)
at System.Web.Http Runtime.Process RequestInternal (HttpWorkerRequ est wr)
at System.Web.Http Runtime.Process Request(HttpWor kerRequest wr)
at System.Web.Host ing.ISAPIRuntim e.ProcessReques t(IntPtr ecb, Int32
iWRType)" EventSourceName ="VOSE Web Services Incoming"
MachineName="TR EYNOLDS"></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("hell o");
}

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

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

while the second pc will report something like:

=============== ==========
System.Exceptio n: hello
at Service.HelloWo rld() in
c:\Inetpub\wwwr oot\webserviceE xception2\App_C ode\Service.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.Ser vices.Protocols .SoapException' occurred in
System.Web.Serv ices.dll

Additional information: System.Web.Serv ices.Protocols. SoapException: Server
was unable to process request. ---System.Exceptio n: hello
at Service.HelloWo rld() in
c:\Inetpub\wwwr oot\webserviceE xception2\App_C ode\Service.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.Ser vices.Protocols .SoapException' occurred in
System.Web.Serv ices.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.Excepti on) and stack trace ('at Service.HelloWo rld()
in
c:\Inetpub\wwwr oot\webserviceE xception2\App_C ode\Service.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("hell o");
}

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

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

while the second pc will report something like:

=============== ==========
System.Exceptio n: hello
at Service.HelloWo rld() in
c:\Inetpub\wwwr oot\webserviceE xception2\App_C ode\Service.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.Ser vices.Protocols .SoapException' occurred in
System.Web.Serv ices.dll

Additional information: System.Web.Serv ices.Protocols. SoapException: Server
was unable to process request. ---System.Exceptio n: hello
at Service.HelloWo rld() in
c:\Inetpub\wwwr oot\webserviceE xception2\App_C ode\Service.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.Ser vices.Protocols .SoapException' occurred in
system.web.serv ices.dll

Additional information: System.Web.Serv ices.Protocols. SoapException: Server
was unable to process request. ---System.Exceptio n: hello
at VOSE.WebService s.WebServices.H elloWorld() in
c:\views\treyno lds_septoldpc\v ose1\webservice s\vose.webservi ces\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("hell o");
}

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

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

while the second pc will report something like:

=============== ==========
System.Exceptio n: hello
at Service.HelloWo rld() in
c:\Inetpub\wwwr oot\webserviceE xception2\App_C ode\Service.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.Ser vices.Protocols .SoapException' occurred in
System.Web.Serv ices.dll

Additional information: System.Web.Serv ices.Protocols. SoapException: Server
was unable to process request. ---System.Exceptio n: hello
at Service.HelloWo rld() in
c:\Inetpub\wwwr oot\webserviceE xception2\App_C ode\Service.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&Di splayLang=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.)