Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Rebuild Index Error Expand / Collapse
Author
Message
Posted Tuesday, May 15, 2007 10:37 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, June 6, 2012 9:51 PM
Points: 96, Visits: 107

Since upgrading to SP2, we have been receiving the following error message when running our rebuild indexes job:

Description: The Execute method on the task returned error code 0x8007000E (Exception of type 'System.OutOfMemoryException' was thrown.). The Execute method must succeed, and indicate the result using an "out" parameter. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 1:00:00 AM Finished: 1:42:26 AM Elapsed: 2545.73 seconds. The package execution failed. The step failed.

Does anyone know how to get the job to complete successfully?  This job used to work prior to SP2. I've also deleted the job & recreated it, but that didn't help any.  Thank you for any advice.




Post #366065
Posted Monday, July 2, 2007 11:56 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, January 28, 2008 6:51 AM
Points: 2, Visits: 2

Did you ever find out what was happening here?  I am having the same problem.

Thanks!

Post #378342
Posted Monday, July 2, 2007 3:07 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, June 6, 2012 9:51 PM
Points: 96, Visits: 107
No, I haven't figured out the error message.  I just scripted the index rebuild job instead.


Post #378411
Posted Wednesday, July 4, 2007 7:22 PM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Friday, April 5, 2013 4:43 PM
Points: 1,473, Visits: 1,314

It might be the memory leak, a problem Microsoft is facing for a long time. Here are some links for your references.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=372940&SiteID=1

http://support.microsoft.com/kb/918643

It seems that Microsoft does not have a good solution for it at this moment.

Post #379067
Posted Thursday, July 26, 2007 10:17 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, June 15, 2009 3:22 PM
Points: 14, Visits: 73

I have gotten this error ever since upgrading to 3159, and it only occurs when i try and run a maintenance task for and integrity check.

 

Post #385494
Posted Monday, July 28, 2008 8:08 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, November 20, 2014 8:18 AM
Points: 13, Visits: 443
I am having the exact same problem. We have a database maintenance plan with 1 task in it named "Check Database Integrity Task". Task details: Connection = Local server connection, Database(s): Specific databases (I only have master checked), include indexes is unchecked. When I right click on the plan and click Execute, the plan fails. If I right click on the plan and click View History, it displays the information: Server FH_SQL\Veritas, Task detail: Check Database integrity on Local server connection Databases: master, Error number: 0, Error message: Alter failed for Server 'FH_SQL\\Veritas'. I do not know why this message displays the double '\\' for the named instance, and this may be part of the problem with the job failing. I have also checked "Reporting & logging option" and here are the details:
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3042
Report was generated on "FH_SQL\Veritas".
Maintenance Plan: MaintenancePlan Integrity Check Test
Duration: 00:00:00
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity (FH_SQL\Veritas)
Check Database integrity on Local server connection
Databases: master
Task start: 2008-07-28T10:00:54.
Task end: 2008-07-28T10:00:54.
FailedSad0) Alter failed for Server 'FH_SQL\\Veritas'.

Please let me know what you think and thank you!

Also, The last thing I did on the server was to move tempdb to another drive and I also changed the accounts that SQL server runs under. The SQL server and SQL server agent were localsystem and they are now different domain accounts.
Post #541924
Posted Monday, July 28, 2008 8:32 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, November 20, 2014 8:18 AM
Points: 13, Visits: 443
Here are the Job History details:
Date 7/28/2008 10:00:53 AM
Log Job History (MaintenancePlan Integrity Check Test.Subplan_1)

Step ID 1
Server FH_SQL\VERITAS
Job Name MaintenancePlan Integrity Check Test.Subplan_1
Step Name Subplan_1
Duration 00:00:01
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: TROTTLAW\fh_veritas_agent. 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:00:53 AM Progress: 2008-07-28 10:00:54.14 Source: {F1D53ECB-F1F2-46E5-841D-6388CE3E8A3C} Executing query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress DTExec: The package execution returned DTSER_FAILURE (1). Started: 10:00:53 AM Finished: 10:00:54 AM Elapsed: 1.563 seconds. The package execution failed. The step failed.
Post #541942
Posted Thursday, July 2, 2009 8:21 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, December 30, 2013 3:13 PM
Points: 1, Visits: 102
I still received this error after installing the critical update for SQL 2005 SP2. I found another article from MS that suggested running the below script, after running it the Maintenance Plan ran without errors:

sp_configure 'allow updates', 0
reconfigure with override
Post #746310
Posted Friday, June 13, 2014 7:47 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, November 17, 2014 2:08 PM
Points: 321, Visits: 1,290
Thank you this solution works for me .

Aim to inspire rather than to teach.
SQL Server DBA
Post #1580524
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse