August 3, 2011 at 8:22 am
Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:20:30 AM Progress: 2011-08-03 10:20:31.42 Source: {457F0481-277C-4B1E-ACFE-FD878EEBDE8E} Executing query "DECLARE @GUID UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:20:30 AM Finished: 10:20:31 AM Elapsed: 1.264 seconds. The package execution failed. The step failed.
I've executed DBCC CHECKDB on all databases and they've all run successfully reporting 0 errors. Any ideas?
August 3, 2011 at 8:29 am
Has that package ever work?
Do you have a more complete error / log message?
August 3, 2011 at 8:33 am
It has not worked yet, new job
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3042
Report was generated on "servername".
Maintenance Plan: TJUHMaint
Duration: 00:00:00
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity Task (servername)
Check Database integrity on Local server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Include indexes
Task start: 2011-08-03T10:20:31.
Task end: 2011-08-03T10:20:31.
Failed:(0) Alter failed for Server 'servername'.
August 3, 2011 at 8:35 am
jshurak (8/3/2011)
Failed:(0) Alter failed for Server 'servername'.
I think you want a trace to find out what's trying to alter what here...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 3, 2011 at 8:37 am
Can you confirm that you are on SQL 7.0? (you posted on sql 2005).
I've verrrry little experience on that version and nothing to test on.
August 3, 2011 at 8:48 am
Its definitely on 2005.
I will look into the trace
August 3, 2011 at 8:50 am
Ninja's_RGR'us (8/3/2011)
Can you confirm that you are on SQL 7.0? (you posted on sql 2005).
It's SQL 2005. The log he posted is clear about that.
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3042
Report was generated on "servername".
Maintenance Plan: TJUHMaint
Duration: 00:00:00
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity Task (servername)
Check Database integrity on Local server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
It skips any database in compat mode 7 because that compat mode is too low for the maintenance plan.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 3, 2011 at 8:51 am
Ok that's 2 ovbious misreads... time for a break.
L8rs.
August 3, 2011 at 9:11 am
I'm getting an error in the trace
Error 14216 (SQL 2005) Severity 10
Job Target Servers:
August 3, 2011 at 9:21 am
That's not an error. Sev 10 is an informational message.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 3, 2011 at 9:35 am
That's what stood out in bright red from the trace
August 3, 2011 at 10:15 am
A severity of 10 is not an error. Doesn't matter what color it is, it's an informational message. What you're looking for in the trace is what that ALTER is since your previous log clearly indicated that an ALTER was failing.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 3, 2011 at 11:12 am
Same thing going on here
http://www.sqlservercentral.com/Forums/Topic1077467-146-1.aspx
sp_configure 'Allow Updates', 0
RECONFIGURE
did the trick.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply