BIS Troubleshooting Tips

This Appendix outlines the symptoms of some common abnormal conditions, and provides insight as to the possible cause(s) and corrective action(s).

Before troubleshooting, if you are using Internet Explorer, be sure that the Show Friendly HTTP error messages option is not checked. This option can be found in Tools > Internet Options > Advanced > Browsing in either Internet Explorer or Control Panel > Internet Options.

• Symptom:

  Server Error in Application "Default Web Site/acuxbis"
  
  HTTP Error 500.0 - Internal Server Error
  Description: Handler "AboMapperCustom-24582078" has a bad module
  	 "IsapiModule" in its module list 
  Error Code: 0x8007000d 
  Notification: ExecuteRequestHandler 
  Module: IIS Web Core 
  Requested URL: http://localhost:80/acuxbis/samples/default.srf?trace=page 
  Physical Path: C:\inetpub\wwwroot\acuxbis\samples\default.srf 
  
  Logon User: Anonymous 
  Logon Method: Anonymous 
  Handler: AboMapperCustom-24582078 
  

• Possible Cause: Indicates that IIS ISAPI extension support is not installed.
• Suggestion: In Windows Vista or Windows 2008 Server, start Programs and Features in the Windows control panel, and ensure that ISAPI Extensions are enabled (that is, the option is checked) under Internet Information Services > World Wide Web Services > Application Development Features.
• Symptom:

  Business Information Server Error
  An error occurred while BIS was processing your request. Additional 
  information is below.
  XMLExchange failed: the service program returned error
  "80004004", which is "Operation aborted". The session has ended.
  

• Possible Cause: Indicates that there was a problem starting the Service Engine.
• Suggestion: To narrow the problem, turn on tracing by adding this tag to your .srf file:

  {{ Trace(start, page) }}

  Then, refresh the page. You should now see a table headed Request Details at the end of the page. Scroll down to Trace Information and look for Service in the left-most column.

  The BIS samples are pre-configured for tracing and tracing may be turned on and off with a query parameter defined in the Trace tag. For example, if the problem occurred running the VERIFYBIS program, log into the server running BIS and use this URL:

  http://localhost/acuxbis/verify/default.srf?trace=page

  Trace output will appear at the bottom of the page, and this will include the BIS Service Engine startup messages that should reveal the problem.

• Symptom: An error 500 occurs.
• Possible Cause: A replacement tag precedes the Handler tag.
• Suggestion: The only tags allowed before the Handler tag are comment tags. Move all tags that precede the Handler tag to follow it.
• Symptom: One of the following error messages is reported:

  Cannot create the trace file for session "nH6shZykCtbZmdDZHo0LhJhiVSq5" (the last attempted filename is "D:\Documents and Settings\UserID\Local Settings\Temp\BIS-nH6s-trace.txt"). The last error code was 80070005
  
  Cannot reopen the trace file for session "nH6shZykCtbZmdDZHo0LhJhiVSq5" (the last attempted filename is "D:\ Documents and Settings\UserID\Local Settings\Temp\BIS-nH6s-trace.txt"). The last error code was 80070005
  
  Could not write the trace file to the directory "D:\ Documents and Settings\UserID\Local Settings \Temp\": the error code was 80004005. 

• Suggestion: To correct this error, give the IWAM_* account write access to this directory. See the Troubleshooting appendix in the User's Guide for more information.
• Symptom: The following error message appears in the web browser:

  Server Error
  LoadLibrary failed.

• Possible Cause: The Handler tag is missing, invalid, or refers to a missing or invalid library.
• Suggestion: Make sure that your .srf page has a {{ Handler * }} tag, and that this tag is the first non-comment/non-include tag in the file. For Windows, it must also appear in the first 4096 characters of the .srf file.