Avoiding errors when using the user and pwd encrypted file with the -eh or -er options in the Harvest command line.

Document ID : KB000055419
Last Modified Date : 14/02/2018
Show Technical Document Details


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 set attribute for file: <encrypted file name>
On UNIX: "E0302014b: Incorrect login. Please try again."


The Harvest command line with the -eh or -er options expects one or other of the following to be true:

  1. 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.

  2. 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 c:\program files\CA\Harvest, then the hco command can specify the file fill path to the -eh option as follows:
      hco -b ... -eh "c:\program files\CA\harvest\demo.dfo"

Moreover, 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.

Other Relevant Information

Details on the svrenc command can be found in the AllFusion Harvest Change Manager Reference Guide.

File Attachments: