Applies To
Express Software Manager version 4.0 and higher

Summary
The Express client writes usage and inventory data to the application library. It uses a path in a local file called Hdc.ini to determine the library's location. If the library path is incorrect in the Hdc.ini file, the client machine will not appear in Express Administrative Console. The Express client can install successfully yet still have a bad path in the Hdc.ini file. This technical note describes how to verify that the Express client is using a valid path to the application library.

Verifying the Path to the Library
The library location (the path) is defined when you create the library in Express Administrative Console. During the library creation process, you are prompted for a path to the library location. This path is written into the Applib.ini file in the library. When the Express client is installed to a client machine, a local Hdc.ini is created on the client machine. This local Hdc.ini file includes the path from the Applib.ini file.

The paths in the Applib.ini and local Hdc.ini files must match in order for the Express client to function properly.

Some common reasons for the Applib.ini and Hdc.ini files to have incorrect paths:

• The application library was originally created in a location that was not a shared folder, and subsequently the folder was shared out.

  In this case, the Applib.ini and Hdc.ini files will contain the original path rather than the new share path.

• The library was created with a path that was not in UNC format.

  You should always use UNC format when creating a library unless your network protocol does not support UNC. If you do not use a UNC path, every client machine must have a drive mapping to the same drive that appears in the path statement.

• The library was created on an administrative share.

  An administrative share includes a drive letter (such as C$ or D$) and is not accessible to users who do not have administrative rights. You should never create an application library on an administrative share.

To verify the library path:

1. Check the path in the local Hdc.ini file.

The Hdc.ini file is a hidden file located on the client machine, in the \Windows folder. It contains a path to the application library. Check that path to confirm it points to the correct library location. To check the path, open the file in Notepad and look at the line that begins:

APPLIB.INI=

The path should be in UNC format and should reference the actual application library. (The path will be in 8.3 format so it may be difficult to decipher.)

Note: If you change this path you should also change it in the library copy of the Hdc.ini file, located in the \Clients folder. See number 3 below.

2. Check the path in the Applib.ini file.

The Applib.ini file is located in the application library folder. Use Notepad to open the file and check the path in the line that begins:

Library=

The path shown there should be in UNC format and match the Hdc.ini path exactly. (Note: It will be in 8.3 format so it may be difficult to decipher.)

If the library was originally created in a location that was not a shared folder, the path in the Applib.ini file may include a drive letter. You can edit this file to correct the problem. Enter a valid UNC path to the application library.

For example, if the application library was originally created locally on a machine called ESMServ, the path in the Applib.ini file may say something like:

Library=C:\esm\libs\sales

You should update this path to say:

Library=\\ESMServ\esm\libs\sales

3. Check the path in the library Hdc.ini file.

Each application library includes a folder called Clients. This folder contains client files, including client installation files. The Clients folder also includes a copy of the Hdc.ini file. This file is used by the Express inventory client, if the client is run directly from the library share. Like the local Hdc.ini file, the library Hdc.ini file contains a path to the application library. Check that path to confirm it points to the correct library location. To check the path, open the file in Notepad and look at the line that begins:

APPLIB.INI=

The path should be in UNC format and should reference the actual application library. (The path will be in 8.3 format so it may be difficult to decipher.)

Using the client troubleshooting tool
Each application library includes a tool for troubleshooting client problems. The client troubleshooting tool (also called the Express Client Information tool) is located in the \Clients folder of the application library. To use the tool:

1. On the client workstation, choose Run from the Start menu.

2. Browse to the \Clients folder of the application library.

3. Select Exinfo32.exe and click Open.

4. Click OK to run the client troubleshooting tool.

5. Click the Details button of the Application Library group to view information about the library. You can edit both the local Hdc.ini file and the library Applib.ini files from the Application Library details dialog box.

When you have confirmed that the Express client has a correct path to the application library, you can move on to the next troubleshooting step.

Related Technical Notes

1587	Troubleshooting Express Client Problems
1592	Express Client Troubleshooting Tools
9989	Express Software Manager 6.x Technical Notes
9991	Express Software Manager Technical Notes (5.x or lower)