RobHoglund Posted February 26, 2005 Report Share Posted February 26, 2005 I am having an issue backing up SQL Server databases with version 6.5 for Small Business Server. The backup will run fine for several days, then unexpectedly the backup of SQL Server fails stating it cannot access the database (error -1221). I try to edit the script and access the database, but when it prompts me for user id and password for Windows authentication, it still cannot access the database. User id and password are valid, I can access the database outside Retrospect. Only solution is to reboot the server. This solves the problem temporarily, but after several days I get the same error. Any ideas? Link to comment Share on other sites More sharing options...
natew Posted March 3, 2005 Report Share Posted March 3, 2005 Hi What OS are you running this on? My guess is that it is an authentication failure for the Retrospect backup user. Have you created the Retrospect backup user account or are you using the admin account in the Retrospect security preferences? Thanks Nate Link to comment Share on other sites More sharing options...
RobHoglund Posted March 5, 2005 Author Report Share Posted March 5, 2005 Hi Nate. I am running Windows Small Business Server 2003, i.e. Windows Server 2003. I have not created the Retrospect backup user account as I was using the Administrator account. What I don't understand is why it would work for several days then just stop. Checked all the event logs and nothing jumps out at me that would indicate a failure. The Administrator account can still get at the databases, just not through Retrospect. Thanks for your help. Rob Link to comment Share on other sites More sharing options...
natew Posted March 7, 2005 Report Share Posted March 7, 2005 Hi I had an exchange install go bad like this in the same way once. I had to run the exchange installer again to get it sorted out. You might want to try starting Retrospect with clean settings files to see if that helps. Just move the config65.dat and config65.bak files to your desktop. These files are normally located in documents and settings\all users\application data\Retrospect. Thanks Nate Link to comment Share on other sites More sharing options...
RobHoglund Posted March 7, 2005 Author Report Share Posted March 7, 2005 Nate, OK, I moved the config65.dat and config65.bak files to the desktop and started over. Doing this didn't seem to help though, I am still experiencing the same problem. Regards, Rob Link to comment Share on other sites More sharing options...
natew Posted March 8, 2005 Report Share Posted March 8, 2005 Hi Since a reboot fixes the problem I suspect it has something to do with authentication on the machine in general. Do you see any errors in the Windows event log once the problem starts to occur? Thanks Nate Link to comment Share on other sites More sharing options...
rvines Posted July 7, 2005 Report Share Posted July 7, 2005 I am unable to authenticate via retrospect to the sql server. I've tried changing the password on the sa account, authenticating via Domain login. Nothing works. Anyone have any ideas? Link to comment Share on other sites More sharing options...
nembot Posted July 8, 2005 Report Share Posted July 8, 2005 Hi, If you have a specific username and password(different from the one you use to authenticate in Windows) for SQL, you should make sure that the SQL user account is included in the Windows Active directory and user interface and that this user belong to the Domain admin group.If your SQL user is not in the Windows user admin group, you won't have access to that SQL server for backup. Thanks. Link to comment Share on other sites More sharing options...
jon_freestone Posted September 1, 2006 Report Share Posted September 1, 2006 I currently have exactly the same problem. Works for a short while then drops out. I'll let you know if I manage to get to the bottom of it. Weird thing is I can still authenticate into the SQL server from ANY other program, just not Retrospect. Retrospect 6.5.350 Windows SBS 2003 Link to comment Share on other sites More sharing options...
tonylees Posted September 13, 2006 Report Share Posted September 13, 2006 me too - exact same problem. tech support were no help in resolving it. Link to comment Share on other sites More sharing options...
Mayoff Posted September 13, 2006 Report Share Posted September 13, 2006 Version 6.5 is now 3 versions old (6.5, 7.0 7.5) and a lot of changes and bug fixes have been made to SQL support over the years. If you have not tried version 7.5, I would recommend downloading the trial to see if it resolves this issue. Link to comment Share on other sites More sharing options...
tonylees Posted September 13, 2006 Report Share Posted September 13, 2006 sorry, wasn't clear - customer actually has v7.0 with latest patches. Reading the forum and posting just now made me double check *everything*. RBU had been hidden from the exchange GAL (Global Address List) - unhide it and bingo it works fine again! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.