December 16, 2009 at 11:15 am
Hi,
I have a SQL Server 2005 instance in server A in domain 'abc' and the network drive is on a Server called Server B in domain 'xyz'
Now, I need to take backup of databases from Server A to Server B. I'm able to access the backup drive on Server B from Server A as below:
Start->Run->\\Server B\Z$\Backups
But the backup of database is failing with the below message:
Query:
exec dbo.BackupDB 'ReportServer','\\Server B\Z$\Backups\','full'
Results:
Msg 3201, Level 16, State 1, Procedure BackupDatabase, Line 52
Cannot open backup device '\\Server B\Z$\Backups\ReportServer_12-16-2009.bak'. Operating system error 1330(Logon failure: the specified account password has expired.).
Msg 3013, Level 16, State 1, Procedure BackupDatabase, Line 52
BACKUP DATABASE is terminating abnormally.
Msg 3201, Level 16, State 2, Procedure BackupDatabase, Line 67
Cannot open backup device '\\Server B\Z$\Backups\ReportServer_12-16-2009.bak'. Operating system error 1330(Logon failure: the specified account password has expired.).
Msg 3013, Level 16, State 1, Procedure BackupDatabase, Line 67
VERIFY DATABASE is terminating abnormally.
Please advice me..
December 16, 2009 at 11:21 am
The error message pretty much tells you what is wrong. The password for the account attempting to login to the server has expired. You need to change the password. If this is a service account used for this, you really need to have it set to not expire the password. You should also be using a very strong password as well.
December 17, 2009 at 4:53 pm
Thanks Lynn,
I have verified that the service account is not expired and set to never expire. But still getting the same error. Anything else need to verify. Please advice
December 17, 2009 at 6:48 pm
First question, why are you backing up to a network drive because 2005 does not like that. Better to backup local and then move across the network.
Second: Which account is SQL Server logged in as? Next, how about the user and finally may want o check which account the server was logged in as. OF course if you are doing it via a job, then you have to check the account of the SQLServer agent as well. Just because you are able to see a drive does not mean the account used by SQL Server can do so as well.
I think you will solve your issues by the above, but seriously consider backing up local first
MD
Marvin Dillard
Senior Consultant
Claraview Inc
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply