Published: January 11, 2007
Last Updated: 2009-12-18
- Guard1 Plus versions: 2.0x, 2.5x, 2.60, 2.7x, 2.8x, 3.x
- Mini-Attendant versions: 2.x
When opening the Attendant, Mini-Attendant or Mini-Attendant File Manager
After starting the PC when Attendant, Mini-Attendant or Mini-Attendant File Manager is set to "Launch when my computer starts"
You receive the following error:
- 76: Path not found
This error may be preceded/followed by There was an error trying to process download file...
- Your Windows User Account does not have sufficient permissions
- The shared folder used by Mini-Attendant and Mini-Attendant File Manager is unavailable
- Permissions for the shared folder used by Mini-Attendant and Mini-Attendant File Manager are not set correctly
- The path set for the Mini-Attendant destionation folder or Mini-Attendant File Manager source folder is invalid
If the error occurs when opening the Attendant, or when starting the PC if the Attendant is set to launch when the computer starts:
Log in to Windows as Local Administrator and launch attempt to perform the action again. If the error does not recur, assign the following minimum required permissions to all User Accounts that will be using Guard1 Plus and/or Rounds Tracker:
- "Modify" permissions to the product installation folder (C:\Program Files\Guard1 Plus or C:\TimeKeeping Systems\Guard1 Plus) and all sub-folders
- "Full" permissions to the Registry key HKEY_LOCAL_MACHINE\Software\TimeKeeping Systems Inc. (32-bit) or HKEY_LOCAL_MACHINE\Software\Wow6432Node\TimeKeeping Systems Inc. and all sub-keys
If the error occurs opening Mini-Attendant or Mini-Attendant File Manager, or when starting the PC if the application is set to launch when the computer starts:
- Verify that the destination (MA) or source (MAFM) path is valid, and that you can access the target folder in My Computer.
- Verify that the share and folder permissions for the destination (MA) or source (MAFM) folder are set to "Modify" for Everyone.
- If the destination (MA) or source (MAFM) folder is mapped to a local drive, verify that the path is entered in UNC format (i.e. \\ServerName\FolderName) in the MA or MAFM options. (Do this by clicking Browse, then browsing to the shared folder via My Network Places.) If MA or MAFM is set to launch when the computer starts, the application may be loading before Windows completes the drive mapping process, and the application can't access the path. Using a UNC path will enable the application to access the path immediately.