Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
DBA007
Posting Yak Master
145 Posts |
Posted - 2010-01-15 : 12:24:44
|
Hi team,i have a scheduled job for the backup process of all databases,but the job was failed with error. SQL Backup failed with exit code: 1010 SQL error code: 9987 [SQLSTATE 42000] (Error 50000). The step failed. |
|
tripodal
Constraint Violating Yak Guru
259 Posts |
Posted - 2010-01-15 : 12:35:11
|
Which Step failed? |
|
|
DBA007
Posting Yak Master
145 Posts |
Posted - 2010-01-15 : 12:42:25
|
the second step on job has failed,which was used for Backup process. |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-01-15 : 13:00:15
|
I [continue to] hate the backup wizard |
|
|
DBA007
Posting Yak Master
145 Posts |
Posted - 2010-01-15 : 14:49:45
|
HI,can any one have the solution for this problem? |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-01-15 : 14:52:19
|
There just isn't enough information in the error message to know what may be the problem. That's a key problem with the maintenance wizard I'm afraid.You might find something more in the SQL Server Error Log |
|
|
DBA007
Posting Yak Master
145 Posts |
Posted - 2010-01-15 : 14:56:27
|
Error Log details:--Failed to get configuration from server. Check that the SQL Server instance is running and that you have the SQL Server System Administrator server role. Error code: <value>. [Also check that the database is not currently in use.]For certain timeout conditions, a more detailed description may be presented with this error code:Failed to get the configuration from the server because the timeout interval has elapsed. Check that the SQL Server instance is running, that you have the SQL Server System Administrator server role, and that no other processes are blocking the backup or restore process. If the problem recurs, try increasing the value of the VDITimeout registry setting in HKEY_LOCAL_MACHINE\SOFTWARE\Red Gate\SQL Backup\BackupSettingsGlobal\[InstanceName].or,Failed to get the configuration from the server because the timeout interval has elapsed. SQL Backup required <bytes> bytes of free SQL Server memory, which was not available. [You can reduce the memory requirements by reducing the number of backup files/threads used in the backup.To configure the VDITimeout registry key, open the registry editor, locate the SQL Backup entries for the relevant SQL Server instance, and add a DWORD entry named "VDITimeout". Enter a duration that you feel is adequate for SQL Server to respond. The duration must be entered in seconds (in hexadecimal). |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-01-15 : 15:13:56
|
Check the Red Gate knowledge base (http://www.red-gate.com/supportcenter/Content.aspx?p=SQL%20Backup&c=knowledgebase%5CSQL_Backup%5CKB200708000083.htm) or contact Red Gate supportBy the way, has it ever worked or is this a new error? |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-01-16 : 03:16:54
|
Are we walking Red Gate's backup, not SQL's, here? |
|
|
russell
Pyro-ma-ni-yak
5072 Posts |
Posted - 2010-01-17 : 10:25:48
|
Log entry indicates Red Gate |
|
|
Kristen
Test
22859 Posts |
Posted - 2010-01-17 : 14:27:07
|
Yeah I saw that. If its the case it would have been helpful if O/P had mentioned it ... |
|
|
|
|
|
|
|