howard Posted January 7, 2002 Report Share Posted January 7, 2002 I am running Retrospect Server 5.6 on Windows NT4 and I can't get the Retrospect Helper service to start automatically which causes my backups to fail. When I start the service manually they work fine. Any suggestions? Link to comment Share on other sites More sharing options...
Mayoff Posted January 7, 2002 Report Share Posted January 7, 2002 Hi, What kind of errors do you get? The helper service is not needed for backup, only for complete system restores of Windows 2000 or XP registry's Link to comment Share on other sites More sharing options...
howard Posted January 8, 2002 Author Report Share Posted January 8, 2002 When the backups run by their schedule they fail due to insuffiecient permissions. However when I run them manually they work fine. I've set both the Retrospect Helper and Retrospect Launcher services to log on as Administrator. The Retrospect Helper service starts up ok when you turn it on manually, but then turns itself off again straight away. Link to comment Share on other sites More sharing options...
Mayoff Posted January 8, 2002 Report Share Posted January 8, 2002 Did you have this problem when the launcher service was configured for "system" account, which is the default? Are you accessing mapped network drives? The helper service is not used for backup, don't worry about configuring it. Please reset it back to "system account" General info: These permission errors can happen when doing a backup of a volume via Microsoft networking rather than a Retrospect Client. Permission errors may occur under the following conditions: 1. When the script was created you were logged in as user X. At the time of backup you are logged in as user Y who does not have permission to connect to the source server. NT/2000: -1001 (unknown Windows error) 98: -1017 (insufficient permissions) 2. When the script was created you were logged in as user X. At the time of backup you are not logged in. NT/2000: -1017 (insufficient permissions) 98: -1116 (can't access network volume) You may need to configure the Retrospect Launcher Service to automatically log into the shared volume using a non-"system" account for proper login to the shared network volume as follows: Windows NT 4.0 1. Open the Services Control Panel. 2. Select Retrospect Launcher, stop the service and then click the Startup button. 3. In the “Log On As” section select This Account. LocalSystem will appear in the field to the right. 4. Change “LocalSystem” to the account you want to use and then enter your password in the two password fields. (This allows automatic backup while logged in as the specified account, or while logged out.) 5. Restart the Launcher Service. Windows 2000/XP 1. Open the Services Control Panel under Administrative Tools. 2. Select Retrospect Launcher, stop the service and then click the Startup button. 3. In the “Log On As” section select This Account. LocalSystem will appear in the field to the right. 4. Change “LocalSystem” to the account you want to use and then enter your password in the two password fields. 5. Restart the Launcher Service. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.