Hco command encountered an error code 768
search cancel

Hco command encountered an error code 768

book

Article ID: 448700

calendar_today

Updated On:

Products

CA Harvest Software Change Manager CA Harvest Software Change Manager - OpenMake Meister

Issue/Introduction

When executing the hco command via Harvest Workbench to check out files to a network share (UNC path), the process fails with error code 768. This occurs even when the user has confirmed the destination path is valid.

Environment

  • CA Harvest Software Change Manager (SCM)
  • Windows Operating System
  • Network Share / UNC Path (e.g., \\\\####.####.host.co\\websdr$)

Cause

Error code 768 is a generic operating system return code typically indicating a "Network Name Not Found" or a permission denial. In the context of Harvest SCM, this failure generally stems from:

  1. Account Context: The process lacks permissions to access the network share, or the network share is unreachable.
  2. Special Characters: Share names or paths containing special characters (such as the dollar sign $) may cause command-line parsing failures if not properly handled.

Resolution

Follow these steps to resolve the error:

  1. Verify Network Share is Accessible: Ensure the network share is accessible through Windows Explorer. 

  2. Verify Permissions: Ensure the account executing the process (Windows user or Agent service account) has "Full Control" or "Read/Write" permissions on the target UNC path.  To do this, right click on the target folder in Windows Explorer and go to Properties, then view the "Security" tab to see what permissions have been granted.

  3. Test Manual Access: Log in with the account used by the Harvest process and attempt to manually create or copy a file to the network share \\\\####.####.host.co\\websdr$.

  4. Enclose Paths in Quotes: Enclose the destination path in double quotes within the hco command or Workbench settings to ensure the shell parses special characters correctly.

  5. Use Encrypted Credentials: If passing a password containing special characters via the command line, use the svrenc utility to create an encrypted password file and use the -eh parameter instead of -usr and -pw.

  6. Install Local Agent: If network share access remains inconsistent, install a Harvest SCM Agent directly on the target machine and perform the checkout to via the SCM Agent instead of a local checkout using a network share.

Additional Information

See also:

hco Command-Check-out

svrenc Command-Encrypt User and Password Credentials to a File

Install Harvest SCM Agent