Workbench cannot find the remote agent file to check in
Article ID: 44974
Updated On:
Products
Issue/Introduction
The user created a remote agent connection in Workbench
They then right clicked on a package and selected the Check In process, specifying the remote agent server in the "Agent" field instead of "local". To gather the list of files to check in they clicked on the green "+" button next to the Name/Path/Modified On listbox.
On the Find Files window, they provided the folder and file name to check in and clicked "Find", but Workbench searched for a long time and never "found" the file.
Why did this happen?
Environment
Harvest Software Change Manager all versions
Resolution
There are many reasons why this could happen. Here are some troubleshooting tips that might help to find the cause of the problem:
- If the remote agent is on a Linux or Unix machine, make sure your capitalization and spelling of the file's name are correct. You can widen your search by using a wildcard (*) for some or all of the file name.
- Check to be sure the userid and password used to connect to the remote agent machine have the correct permissions to view the target folder and file.
- Go to the Agent connection in the Workbench Explorer pane and navigate to the folder to be sure the file exists.
- Increase the logging level on the agent process to gather more information about what might have gone wrong by adding one of these lines to the %CA_SCM_HOME%\HAgent.arg file on the remote agent server and restarting the agent process:
"-trlvl=1" will detect any connection or login problems the agent encounters.
"-trlvl=2" will detect any data transfer problems.
Note: The logging levels on the agent side cannot be combined, so you may need to try one level, and if you don't see any information in the agent log, change to the other level and then stop and restart the agent and try it again. After making any change to the %CA_SCM_HOME%\HAgent.arg file you will need to restart the SCM Agent process for the change to take effect.
- Try your checkin with the hci command, targeting the remote agent machine with the "-rm","-rport", "-rusr" and "-rpw" parameters. You can add the "-tr" parameter to get some additional debug logging in your hci.log file and perhaps find out why Harvest is having trouble finding the file that way. For example:
hci -b <brokername> -en <project> -st <state> -vp <viewpath> -cp <clientpath> -ur -s <filename> -op pc -if ne -rm <agenthostname> -rport <agentport> -rusr <agentuserid> -rpw <agentpassword> -tr
- Login to the remote agent computer with Putty or Remote Desktop and execute your Check In from there instead of from the Workbench machine.
Additional Information
Information on the hci command is found here: hci Command-Check-in
Feedback
