The information provided is to precisely identify the troubleshooting issues that arise with ArcIMS 4.0 ActiveX Connector.
- Download the command line ActiveX Diagnostic Scripts and extract them to their own directory. The location is not important.
- Open a command prompt and change into the directory where the scripts are located.
- Run the first script--diag1.js--by typing
cscript //nologo diag1.js
- Run the diag2.js script by typing
cscript //nologo diag2.js
If 'Worked' displays, proceed to Step 5. If not, then the ActiveX Connector was not installed on this machine or the installation failed.
- Run the diag3.js script by typing
cscript //nologo diag3.js
If the following response displays, proceed to Step 6:
Node operations worked
If not, the Microsoft XML Parser needs to be installed. It can be installed from the ArcIMS 4.0 CD by double-clicking the file: \Support\System\aimsmsxml.msi
- Run the diag4.js script by typing
cscript //nologo diag4.js
If 'Worked' displays, proceed to Step 7. If not, Microsoft Transaction Server 2.0 (MTS) is not installed. MTS is installed automatically with Windows 2000 and XP. However, Windows NT 4.0 users need to install it from the Windows NT 4.0 Option Pack.
- Run the last script--diag5.js--by typing
cscript diag5.js <APPSERVER_NAME> <APPSERVER_PORT>
If a "Subscript out of range" error is returned, you failed to specify the ArcIMS Application Server's name or port. Make sure you substitute <APPSERVER_NAME> and <APPSERVER_PORT> in the command with the your site information.
The default port used by the Application Server is 5300.
If the response is:
Description:XML document must have a top level element.
then the ActiveX Connector failed to connect to the ArcIMS Application Server. You may have specified the machine name or port incorrectly or the ArcIMS Application Server may not be running. If you determine that these are not the cause, then you may have a networking issue. This type of issue is beyond the scope of this article.