Troubleshooting for the IisProxy
Module
Symptoms
· When starting the Default Web Site in the Internet Services Manager, you get an error message stating that the service couldn’t start.
· The inetinfo.exe process dies.
· The System event log contains error messages from the Service Control Manager: with Event ID 7031: The World Wide Web Publishing Service service terminated unexpectedly. or The IIS Admin Service service terminated unexpectedly.
·
The
IisProxy_<yymmdd>.log file contains only the message:
<hh:mm:ss> Global F-Init
IisProxy Filter 1.3.0.0 initializing.
Causes and Solutions
Cause |
Solution |
|
The MSXML (Microsoft XML Parser) on the machine is outdated. |
Download and install the Microsoft XML Parser 3.0 Service Pack 2 from the Microsoft Download site at www.microsoft.com/downloads (search using the keyword MSXML). |
Symptoms
· The IisProxy module does not load.
- When checking the state in the Internet Services Manager, the module status is marked with a red arrow.
Causes and Solutions
Cause |
Solution |
|
The IisProxy.dll file or the IisProxy.xml file is missing. |
Copy the missing file to the <Inetpub>\scripts directory. |
|
The MSVCR71.dll file is missing. |
Copy the missing file to the %SysDir% (%WinDir%\system32) directory. |
|
The IisProxy module cannot determine its own path. |
Search for a file named IisProxy_<yymmdd>.log in the <SystemRoot>\system32 directory. If the file exists, read the error message therein and correct the error. |
|
The IisProxy.xml file cannot be parsed. |
Read the error message in the <Inetpub>\scripts\IisProxy_<yymmdd.log> file and correct the error. |
|
The version of the IisProxy.xml file is missing, or the value doesn’t match the version of the IisProxy.dll file. |
The IisProxy.dll contains a version check: The version of the configuration must match the first two numbers of the file version (right-click the IisProxy.dll file, choose Properties, change to the Version tab and note the File version: value.) Obtain the sample configuration file that was shipped with the IisProxy.dll file, and update it according to your configuration. |
Symptom
Requests that should be forwarded to the SAP J2EE Engine cause a 404 Not foundresponse containing the IIS message: Cannot find server.
Causes and Solutions
Cause |
Solution |
|
The URL does not map to any of the mapping source patterns. |
Check the URL and the <source> elements in the IisProxy.xml file. |
Symptom
Requests that should be forwarded to the J2EE Engine cause a 500 Server Errorresponse containing the message: The specified module could not be found.
Causes and Solutions
Cause |
Solution |
|
The value for the extension-url filter attribute does not point to the location of the IisProxy.dll file. |
Correct the extension-url filter attribute or copy the IisProxy.dll file to the specified location. |
Symptom
Requests that should be forwarded to the J2EE Engine cause a 500 Internal Server Error response containing the message: ProxyWorker(): IOException: SapConnection(): Cannot connect to <host>:<port> or ProxyWorker(): IOException: NiBufConnect() failed: -10 (NIECONN_REFUSED).
Causes and Solutions
Cause |
Solution |
|
The SAP J2EE Engine is not running. |
Start the SAP J2EE Engine. |
|
The network connection to the SAP J2EE Engine is not possible. |
Check that the <host> and <port> parameters match the network address of your SAP J2EE Engine. |