Errors with encrypted files in the Harvest command line
Article ID: 55419
Updated On:
Products
Issue/Introduction
User has verified that the user and password used to create the .dfo file; by using svrenc -f command, are correct but, when using the Harvest command line with the -eh or -er options, errors like the following are seen:
On Windows: "ERROR: Unable to open file: <encrypted file name> On UNIX: "E0302014b: Incorrect login. Please try again."
Environment
Harvest Software Change Manager all versions
Resolution
The Harvest command line with the -eh or -er options expects one or other of the following to be true:
- The encrypted user/pwd file to be in the current directory where the command line is running, e.g. on a Windows machine, to run 'hco' from directory c:\temp, user needs to make sure that the .dfo file is also located in c:\temp.
- The encrypted user/pwd file full path to be specified with the - eh or -er options, e.g. if the .dfo encryption file is called demo.dfo and is located in the directory %CA_SCM_HOME%, then the hco command can specify the file fill path to the -eh option as follows:
hco -b ... -eh "C:\Program Files\CA\scm\demo.dfo"
Additional Information
When running the Harvest command line in a multiplatform environment, for example, Broker on Solaris, Agents on AIX and HP/UX, Command Line client on Linux and Windows GUI clients, it is a good practice to generate the .dfo file locally on each platform separately, e.g. if a user wants to run the 'hco' command from the Solaris Broker box and Linux client box against a HP/UX agent, it is recommended to run "svrenc -f" individually on both Solaris and Linux to generate two .dfo files for these two different platforms.
Details on the -eh and -er options for command line utilities are found here: Getting Started with CA Harvest SCM Commands - User Credentials
Details on the svrenc command are found here: svrenc Command-Encrypt User and Password Credentials to a File
Feedback
