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 |
|
abidba
Starting Member
26 Posts |
Posted - 2009-10-08 : 15:18:52
|
| hello:I have a problem with backup: Following is the error message:Date 10/8/2009 2:58:41 PMLog Job History (DAILY.BACKUPS)Step ID 1Server ServerJob Name BACKUPSStep Name BACKUPSDuration 00:02:13Sql Severity 0Sql Message ID 0Operator Emailed Operator Net sent Operator Paged Retries Attempted 0MessageExecuted as user: Server\SYSTEM. ...on 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 2:58:41 PM Progress: 2009-10-08 14:59:11.89 Source: {577EAAF1-EE6E-45E0-B176-49B76A03C0EE} Executing query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress Progress: 2009-10-08 14:59:12.17 Source: Check Database Integrity Task Executing query "USE [master] ".: 50% complete End Progress Progress: 2009-10-08 14:59:13.55 Source: Check Database Integrity Task Executing query "DBCC CHECKDB WITH NO_INFOMSGS ".: 100% complete End Progress Progress: 2009-10-08 14:59:13.55 Source: Check Database Integrity Task Executing query "USE [model] ".: 50% complete End Progress Progress: 2009-10-08 14:59:13.89 Source: Check Database Integrity Task Executing query "DBCC CHECKDB WITH NO_INFOMSGS ".: 100% complete End Progress Progress: 2009-10-08 1... The package execution fa... The step failed. |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-10-08 : 15:32:56
|
Please run the following and post the full resultsDBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS --Gail ShawSQL Server MVP |
 |
|
|
abidba
Starting Member
26 Posts |
Posted - 2009-10-08 : 15:37:34
|
| Should i have to run this command manually against each database? |
 |
|
|
abidba
Starting Member
26 Posts |
Posted - 2009-10-08 : 15:42:37
|
| Gail:I did not get any resuts. After i run above command on each database: I gotCommand(s) completed successfully. |
 |
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2009-10-08 : 16:15:40
|
| Ok, then it's not corruption. You're going to have to get the full error message to go any further. It's cut off.Find the job in question, go to the job step, the advanced properties. There's a space there to put a file name to log errors to. Do that, run the job again, get the full error messages from the file and post here.--Gail ShawSQL Server MVP |
 |
|
|
abidba
Starting Member
26 Posts |
Posted - 2009-10-08 : 16:43:40
|
| This is what i got:Microsoft (R) SQL Server Execute Package UtilityVersion 9.00.4035.00 for 32-bitCopyright (C) Microsoft Corp 1984-2005. All rights reserved.Started: 4:40:46 PMDTExec: The package execution returned DTSER_FAILURE (1).Started: 4:40:46 PMFinished: 4:42:54 PMElapsed: 127.719 seconds |
 |
|
|
jeffw8713
Aged Yak Warrior
819 Posts |
Posted - 2009-10-11 : 13:14:06
|
| Go to the maintenance plan, right-click on the maintenance plan and View History. In that view, you will open the plan that failed and find the task that failed.From there you should be able to identify what is causing that task in your maintenance plan to fail. |
 |
|
|
|
|
|