Jump to content
Sign in to follow this  
RobHoglund

Authentication Failure

Recommended Posts

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?

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

 

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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!

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×