GWIA Admin could not locate file 'exepath.cfg'

(Last modified: 16Nov2004)

This document (10095505) is provided subject to the disclaimer at the end of this document.

fact

GroupWise 6.5 for Linux

SLES 8

Administration

ConsoleOne

GWIA

symptom

GWIA Admin could not locate file 'exepath.cfg'

Error is seen when going into properties of gwia object in ConsoleOne

cause

The GroupWise ConsoleOne snapins look for the exepath.cfg whenever you go into the properties of the GWIA object.  If the exepath.cfg is missing, corrupted, or administrator does not have necessary permissions to see the file the error may be seen.  The exepath.cfg is found under the domain's wpgate/gwia directory.  The snapins know how to find it by looking for the path to the domain and adding wpgate/gwia to that path.

fix

In this case the path to the domain had directory names containing  mixed case letters.  The problem was resolved by changing all the (GroupWise) directories to lowercase.  The path in the domain object had to be corrected, the paths in the GWIA object under Server Directories had to be corrected as well.  The startup files for the MTA and Gateways had to be corrected to match.

***Novell tested this on a SLES9 server and could not reproduce the problem*** this means the problem may be specific to certain Linux distributions.  Novell recommends to specify lowercas letters for any GroupWise directories which makes it easier navigating in a terminal window.

document

Document Title: GWIA Admin could not locate file 'exepath.cfg'
Document ID: 10095505
Solution ID: NOVL99845
Creation Date: 16Nov2004
Modified Date: 16Nov2004
Novell Product Class:GroupWise Client/Admin

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.