exit code 10003: Lock error: Process already running or error creating local lock file Symptoms: The

error codes below appear in the client log file. Error <5064>: Cannot open file "C:\Program Files\Avamar\var\f_cache.dat" Info <5065>: Creating new cache file C:\Program Files\Avamar\var\f_cache.dat (2,884,128 bytes) Error <5803>: Error writing 32-byte header to cache file C:\Program Files\Avamar\var\f_cache.dat. Possibly out of disk space Info <5573>: - Loaded cache file C:\Program Files\Avamar\var\f_cache.dat (2,884,128 bytes) FATAL <5223>: Unable to open filename cache in directory 'C:\Program Files\Avamar\var' Info <6149>: Error summary: 3 errors: 5803, 5064, 5223 Info <6606>: Sending wrapup message to agent Info <5314>: Command failed (3 errors, exit code 10003: Lock error: Process already running or error creating local lock file) The backup job may fail repeatedly over several attempts. Environment: Avamar client for Windows v3.7.1-100 Likely to affect other versions

Cause: 1. There may be a failed Avtar job on the client workstation. 2. The drive the client is installed is full. Resolution: Cause 1: Check for failed or hung Avtar job on the client workstation by display all the running jobs in the task manager. On the client workstation: 1. 2. 3. 4. 5. Bring up the Windows Task Manager Click on the "Process" tab. Select "Show processes from all users" to display all jobs. Click on "Image Name" to sort the jobs alphabetically in descending order. Look for an avtar job that is still running. If an old avtar job is found then you have three ways to kill it. 1. Kill the job through the Windows Task Manager. 2. Kill the old job with the "kill.exe" command from the Windows Resource Kit. 3. Reboot the client.

Method 1: If you logged in to the workstation as a local administrator 1. Record the Process ID displayed with the avtar job. 2. Cick on the avtar job to highlight it. 3. Rght click on the job and select "End Process". If the job is terminated then try rerunning the job. If the error message "Cannot kill job from taskmanager" or "The operation could not be completed. Access is denied" error message is displayed then you will have to use method 2. The reason the job cannot be killed in this stage is because the ID you are logged in with does not have the administrative rights to kill the job. This issue is documented in MS KB 155075. Forr more information see, http://support.microsoft.com/kb/155075. Method 2: While logged in with an ID that has administrative rights on the client workstation: 1. Open a command shell. 2. Verify you have the "kill.exe" command installed on the workstation. 3. If the "kill.exe" command is not installed on the workstation then install it from the Windows Resource Kit. 4. Issue the "kill <Process ID>" command to kill the job from the command line. --kill -f 1828 process avtar.exe (1828) - '' killed --The kill command will reply that the job has been killed. 5. Verify the job has been killed by checking for the process in the Windows Task Manager. --pslist | find "av" avscc 2640 8 6 117 6388 0:00:09.390 0:33:34.201 avagent 2428 8 13 148 6100 0:00:10.734 0:13:22.286 --6. Rerun the job. Method 3: If all the above fail then reboot the client workstation. 1. Verify there are no avtar jobs running. 2. Rerun the Job. --Sample output from the msinfo32 command showing a "hung" avtar job. Note there are no resources allocated to the job. --System Information report written at: 12/06/2007 12:27:35 PM [Running Tasks]

Name Path Process ID Priority Min Working Set Max Working Set Start Time Version Size File Date avagent.exe c:\program files\avamar\bin\avagent.exe 2352 8 204800 1413120 11/20/2007 1:59:40 PM 3, 7, 1, 100 2.95 MB (3,092,539 bytes) 8/30/2005 3:40:18 PM avscc.exe c:\program files\avamar\bin\avscc.exe 2640 8 204800 1413120 12/6/2007 12:16:17 PM 3, 7, 1, 100 3.25 MB (3,407,935 bytes) 8/30/2005 3:40:32 PM avtar.exe \\?\c:\program files\avamar\bin\avtar.exe 1828 6 204800 1413120 11/16/2007 9:00:00 PM Unknown Unknown Unknown --Cause 2: Verify there is sufficient space on the drive where the client is installed. This issue is often resolved by reinstalling the client on a local drive with sufficient space for the cache files to go grow to their maximum size (RAM x 5/16). ---