The CheckConfig Tool

• Introduction
• Command Line Options
• Interpreting the Output
• GUI Version

Introduction

J-Integra® has been used to access thousands of different COM object on multiple Windows platforms. To assist our support team in resolving configuration issues, the CheckConfig tool is used to print out information about your platform and configuration. The output produced by CheckConfig is used to check that your Windows system is setup correctly to access COM objects via DCOM.

Command Line Options

Type checkconfig /? to view the usage information. The different options are:

Option	Definition
/typelib [Typelib file]	Opens the specified type library and display information about the classes and interfaces inside it. It also displays the access permissions for these classes if they have been configured in the registry. If the /typelib option is not specified, CheckConfig will display registry information for the last type library used. e.g. CheckConfig /typelib "c:\Program Files\Microsoft Office\Office\EXCEL.EXE"
/rhost [hostname]	Tests the DCOM connection to the specified hostname or IP address. e.g. CheckConfig /rhost 192.168.0.18
/progid [progid]	Displays the configuration information associated with the specified progid such as the AppID, access permissions, launch permissions, etc. e.g. CheckConfig /progid Excel.Application
filename	If a file name is specified at the end of the command line, the output will be redirected to the given file. e.g. CheckConfig /progid Excel.Application config.log

Interpreting the Output

Most of the output is self explanatory. Items marked with three stars ( *** ) indicate errors or suspicious settings. CheckConfig displays the following system information:

• Operating system information (name, version, etc.)
• System time
• Type libraries (class names, CLSIDs, registry configuration, etc.).
• User information (user names, groups, etc.)
• DCOM settings (EnableDCOM, access permissions, etc.)
• Java to COM settings (is logging enabled, registered JVM IDs, registered CLSIDs, etc.)
• Verify that SCM is active (if not, DCOM will not work)
• IP Configuration (IP address, hostname, etc.)
• Winsock Information (version and description)
• Environment variables

Troubleshooting

First, make sure you have configured DCOM correctly.

If you are getting "access denied" errors, then pay close attention to the Access Permissions and Launch Permissions for the COM CLSID you are attempting to access. Also check what groups your user name is a member of in the Checking Username section of the output.

Also check that DCOM is enabled in the Checking DCOM settings section of the output, and that connecting to the SCM was successful in both the Connecting to SCM and IP Configuration sections.

GUI Version

A GUI version of CheckConfig is available and can be downloaded from our website.