Troubleshooting
Click the Service/License File tab and choose Configure using Services. Select the correct service name (s) Click the Start/Stop/Reread tab and choose Stop Server. To start the licensing daemon, follow the steps below. In Windows Explorer, double-click the lmtools.exe utility. Check the following folder exists and has the 'C: Program Files (x86) IBM EHLLAPI' and has the 'PCSHLL32.DLL' file in it. If the folder does not exist, then contact your company IT team and request them to install the 'EHLLAPI' package.
- To obtain a license file: To run the lmtools.exe utility, on the Start menu (Windows) click Programs Autodesk License Manager Tools lmtools.exe. In the LMTOOLS dialog box, click Configuration Using Services. Click the Systems Settings tab. Locate the Computer/Hostname field and make a note of the Server Host Name.
- Acs License File Installation Failed. Of your usbpen -Mount ACSv5.8.0.32.iso in your VM CD DRIVE -Install ACS -VL TAKE AROUND 15 min depending on your gear.
- Acs License File Installation Failed Owners Manual For 2018 Kx 85 Bob Tricker Corporate Governance Pdf Applied Mathematics 1 By Gv Kumbhojkar Pdf Style Psr 2000 Free.
Problem
When running the install_acs_32_allusers.js or install_acs_64_allusers.js an error is presented stating Error line 579 path not found.
Cause
Microsoft OS Environment
Diagnosing The Problem
Acs License File Installation Failed To Work
Message box stating [Error line 579 path not found]
Resolving The Problem
The script uses Windows variables to create paths used for the deployment scripts.
The block of code represented by line 579 is as follows:
Shell3 = new ActiveXObject('WScript.Shell');
// Create local install path
// Create the IBM directory if it does not exist
if (!fso.FolderExists(target1)) {
fso.CreateFolder(target1);
}
// Create the IBM directory if it does not exist
if (!fso.FolderExists(log_target)) {
fso.CreateFolder(log_target);
}
The problem that has been identified is with the creation of the log_target folder creation. This is the install log we create.
We are looking at the %HOMEDRIVE% and %HOMEPATH% environment variables.
You can view the %HOMEPATH% and %HOMEDRIVE% variable by opening a Windows Command Prompt and entering the following commands:
echo %HOMEDRIVE%
echo %HOMEPATH%
As an example:
%HOMEPATH% is a value of usersjoeuser
%HOMEDRIVE% is a value of Z:
The would result in the value of log_target being Z:usersjoeuserIBM
In all cases we have seen, it's been an authority issue creating the path or an invalid value in one of the Windows variables.
Acs License File Installation Failed Without
There is also a development works article where a user reported this very issue. They resolved by modifying the deployment script. Support doesn't assist with modification of the scripts; however this may be a work around.Here's the link to the complete acritical, the issue is described in the comments:
https://www.ibm.com/developerworks/ibmi/library/i-ibmi-access-client-solutions-customization-trs/index.html
Changing the environmental variables would be the recommendation rather than modifying the scripts.
[{'Product':{'code':'SWG60','label':'IBM i'},'Business Unit':{'code':'BU054','label':'Systems w/TPS'},'Component':'Access Client Solutions','Platform':[{'code':'PF033','label':'Windows'}],'Version':'Version Independent','Edition':'All Editions','Line of Business':{'code':'LOB08','label':'Cognitive Systems'}}]
![Acs License File Installation Failed Acs License File Installation Failed](https://estanovo.weebly.com/uploads/1/2/3/9/123988062/552358392.png)
Document Information
Modified date:
18 December 2019
18 December 2019