When we have an hco command like this:
hco -b "<broker>" -en "<project>" -st "<state>" -vp "<viewpath>" -sy -r -op pc -s "*" -o "<logfilename>" -usr "<userid>" -pw "<password>"
We see an error like this:
I00060040: New connection with Broker hapdevel established.
Error: Unable to create session
Harvest Software Change Manager v12.x and higher
Unix/Linux/AIX environments
We found that the password included on the command line contained a special character, for example "$Example123".
Any time you include a parameter containing a special character in a Unix/Linux/AIX command it can cause unexpected side effects. This is because there are some special characters that the operating system reserves for its own use and that have a special meaning.
There are a couple of ways to work around this problem:
svrenc -f <encrypted password file name>
hco -b "<broker>" -en "<project>" -st "<state>" -vp "<viewpath>" -sy -r -op pc -s "*" -o "<logfilename>" -eh <encrypted password file name>
hco -b "<broker>" -en "<project>" -st "<state>" -vp "<viewpath>" -sy -r -op pc -s "*" -o "<logfilename>" -prompt
Information on the hco command can be found here: hco Command-Check-out
Information on the svrenc command can be found here: svrenc Command-Encrypt User and Password Credentials to a File
Information on the "-prompt" parameter can be found here: Get Started with CA Harvest SCM Commands - Common Options