How to: Get ASP.NET Errors in the Speech Server Logs
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
By default, ASP.NET errors are only logged and viewable on the local Web server. Some of this detailed information can be helpful in troubleshooting problems with voice response applications running on the Web server. However, if the Web server running the application is not the same computer running Speech Server, those errors are not available in the context of other application errors.
To get ASP.NET errors in the Speech Server logs, modify the application Web.config file so that it provides the error details to its client applications (namely Speech Server). When this change is implemented, Speech Server receives ASP.NET error information and logs it in the Speech Server Event trace log (ETL) files. You can view these logs after converting the files to text with the MSSLogToText tool.
Note
Performing this procedure can expose more information about an application than preferred. If the Web server is accessible from clients other than Speech Server, you should weigh this procedure's potential risk against its benefits.
Procedure
To get ASP.NET errors into the Speech Server logs
On the Web server, locate the Web.config file in the root directory of the application, and then open the file in Notepad.
Locate the customErrors mode attribute in the file.
<configuration> ??????<system.web> ????????????<customErrors mode="RemoteOnly"/> ??????</system.web> </configuration>Change the customErrors mode attribute from RemoteOnly to Off, and then save the file.
ASP.NET errors are sent to Speech Server where they are recorded in the Speech Server ETL files.
To view ASP.NET error details, use the MSSLogToText tool to convert the ETL files to text. For more information, see Log File Conversion to Text.