May 12, 2011 at 8:33 am
New to job...
in sql server 2008
My full backup failed
Msg 50000, Level 16, State 1, Server USxxxxxxxxxx, Procedure usp_FullBackupAllDB, Line 256
usp_FullBackupAllDB Failed
2
usp_FullBackupAllDB Return code = 1
"Error -100 during usxxxxxxxxxx SQL Server Backup
Not the space issue..
Any suggestions plzz
May 12, 2011 at 8:48 am
When it's not space it's permissions. Or maybe db in single user mode and can't connect.
May 12, 2011 at 11:34 am
Bad path specified ?
Can you run the code manually ?
May 16, 2011 at 7:31 am
Are you using a custom script or is that a 3rd party backup routine?
Another thing that comes up are locked files on the server. These can be caused when a regular system backup process locks the file while the SQL Server process is trying to write to it.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
May 17, 2011 at 5:09 am
Looks like an error in the script/stored procedure. Suggest you debug the script/stored procedure in a query window, and use PRINT statements liberally around line 256 to see what's going wrong.
SQL BAK Explorer - read SQL Server backup file details without SQL Server.
Supports backup files created with SQL Server 2005 up to SQL Server 2017.
May 17, 2011 at 5:23 am
It might be as stupid as a new db with an invalid character like ":" so that you can't output that name on the drive or you have "weird" characters in the db name that name brackets "[]" around the db name to make the dynamic sql work...
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply