[Incident]: Some users report they are unable to access the case portal. Please see this community notice for more information.

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Could not open configuration file C: Program Files (x86)\\<vendorName>lmadmin/conf/httpd.conf: The system cannot find the path specified.

Could not open configuration file C: Program Files (x86)\\<vendorName>lmadmin/conf/httpd.conf: The system cannot find the path specified.

Summary

This article will explain how to overcome the lmadmin startup error: "Could not open configuration file C: Program Files (x86)\\/lmadmin/conf/httpd.conf: The system cannot find the path specified." when placing files that are user customised in the ProgramData folder.

Symptoms

When creating an lmadmin installer that has to be compliant with Windows 7 Client Software Logo installation guidelines, files that are user customised need to be placed in the ProgramData folder. This includes the "logs" and "conf" folders. However, when moving these files and running lmadmin with the "-logDir" and "-configDir" properties, these don't seem to be updating the server.xml file with the new locations, so lmadmin won't start manually or as a service, and in the "web.log" the following error is thrown:

"lmadmin: Could not open configuration file C:Program Files (x86)\\<vendorName>lmadmin/conf/httpd.conf: The system cannot find the path specified."


Cause

Running lmadmin with the "-logDir" and "-configDir" properties, doesn't seem to be updating the server.xml file with the new locations, and lmadmin fails to start.

Resolution

The latest FlexNet Publisher toolkit release (v11.13.1.3) resolves this issue by introducing a new command-line option called "cacheDir".

Example of use:

lmadmin -cacheDir "C:\ProgramData\<vendorName>\lmadmin"
Was this article helpful? Yes No
No ratings
Version history
Last update:
‎Nov 14, 2018 10:28 PM
Updated by: