Best practice: Installation of the Service Manager Dialog did not work.
Article ID: 88457
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
Symptoms
The setting up of the Service Manager Dialog aborted with the following message: Could not open the file named: …\8.00A\ServieManagerDialog\Windows\x64\SETUP.LST
After starting the Service Manager - Setup.exe, the following error occurred.
--- > Could not open the file named: …\8.00A\ServieManagerDialog\Windows\x64\SETUP.LST
Investigation
Usually the LST file message means that during installation there is no access to the SETUP.lst
Files or information needed for analysis:
The setting up of the Service Manager Dialog aborted with the following message: Could not open the file named: …\8.00A\ServieManagerDialog\Windows\x64\SETUP.LST
After starting the Service Manager - Setup.exe, the following error occurred.
<Please see attached file for image>
--- > Could not open the file named: …\8.00A\ServieManagerDialog\Windows\x64\SETUP.LST
Investigation
Usually the LST file message means that during installation there is no access to the SETUP.lst
Files or information needed for analysis:
- Which image and version of the Automation Engine is being installed?
- Version and architecture of the Operating System used?
- Is it an update or a new installation of the Automation Engine?
- Which user and permissions started the setup/ logged in during installation?
- The detailed directory from where the setup.exe is executed including the installation path.
Environment
Release: AOATAM99000-9.0-Automic-One Automation Tools-Application Manager
Component:
Component:
Resolution
There are various solutions available:
# Make sure that the Microsoft Visual C++ 2005 Redistributable Package is installed!
#The user does not have the permission to install software on the OS./ or start the setup.exe on a source path with no permissions on this specific directory of the file system.
#The source is corrupted.
#The source path / UNC – path to the Install Directory is too long. This occurs especially when the Setup.exe is located on a network path as shown below:
# Make sure that the Microsoft Visual C++ 2005 Redistributable Package is installed!
#The user does not have the permission to install software on the OS./ or start the setup.exe on a source path with no permissions on this specific directory of the file system.
#The source is corrupted.
#The source path / UNC – path to the Install Directory is too long. This occurs especially when the Setup.exe is located on a network path as shown below:
<Please see attached file for image>
align="bottom" border="0" alt=".png" src="http://ecmstage.ca.com/KB%20Asset%20Library/000008566_Embeded/.png" width="1146" height="55">Feedback
Yes
No
Powered by
