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 123»»»

sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed. Expand / Collapse
Author
Message
Posted Wednesday, July 28, 2004 12:25 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, February 20, 2007 7:17 AM
Points: 69, Visits: 1

At my Company, I set up a Maintenence Plan to back up one of our Databases (quite large) prior to the monthend processing. This was to ensure if data needed prior to month end load, data would be avaialble. I can run this myself and it works fine, but as a scheduled job it received this error. Does anyone know the answer to this. Additional info is that I set the plan to delete any backup old than three months, which hasn't been reached yet.

Error received -

sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Post #128881
Posted Thursday, July 29, 2004 12:03 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, November 15, 2013 1:41 AM
Points: 9, Visits: 9

I've had the very same error occur in the last couple of weeks - I spent some time on the Microsoft Website (Uncle Bill's Domain) and it seems that it relates to the ability of the server to take the database into single-user mode (which it allegedly needs to perform some maintenance tasks (integrity checks in my case)). On my SQL box, it seems that a BackupExec job runs under the NT System Account on the SQL's local OS - this is preventing single-user mode. We are currently looking to kill this BackupExec job for a couple of hours on a Sunday so that the integrity checks can be run. I hope this helps,

Diarmuid.

Post #129134
Posted Thursday, July 29, 2004 12:14 PM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, October 20, 2014 3:22 PM
Points: 508, Visits: 244
good luck!  I've had an open issue with MS for over a month now, trying to get this figured out.  And I'm only dealing with a one user local MSDE setup.  What I can tell you from my experience, is that if I configure the MSSQLSERVER service to run under a Domain\User account that has admin priveledges to the machine, everything works fine.  When I put MSSQLSERVER back to Local System, it fails every time, regardless of who initiates the job.  The same configuration (Account = Local System) works wonderfully for the other 95% of my users.
  In short, the workaround for me was to set the MSSQLSERVER service to run under the user's WinNT Domain\User account.  Be warned though, that changing the users password may have detrimental consequences.  I haven't tested that.
  If I ever get my schedule to match with my helpful MS engineers' and figure out the problem, I'll let you know.
 



Post #129140
Posted Thursday, July 29, 2004 2:14 PM


SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, September 29, 2014 12:25 PM
Points: 77, Visits: 183
Have you checked the maint plan history to see where the failure occured and what may have been successful? I have found that it is very helpful on telling you what went wrong, which for me was usually a wrong setting. Try this article to see if it will help.
http://support.microsoft.com/default.aspx?scid=kb;en-us;288577



Post #129159
Posted Thursday, July 7, 2005 5:48 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, June 16, 2014 9:46 PM
Points: 284, Visits: 263

I also faced this problem when i schedule a database optimization jon on SQL 7.0 with Sp2 box. Clueless about what cause the problem.

- S Sivaprasad



Sivaprasad S - [ SIVA ]http://sivasql.blogspot.com/
Post #197936
Posted Thursday, July 7, 2005 1:14 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, November 15, 2013 1:41 AM
Points: 9, Visits: 9

Strangely enough - I have since deleted the job, re-created it (exactly the same tasks as before) and all is now running well.

 

Diarmuid

Post #198323
Posted Thursday, July 7, 2005 8:18 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Monday, March 13, 2006 8:09 AM
Points: 64, Visits: 1
Some days back, me too had the same error in my plan, and on my standby server i deleted some old backups, and then again restarted my job..it worked fine then..i believe it was due to lack of space but the error thrown is misleading..
Post #198431
Posted Friday, July 8, 2005 8:43 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 12:28 PM
Points: 76, Visits: 1,217
I'm having the same problem during the optimization step of one on the db on a server.  The server has 300 GB free space and nothing else is running at the time.  All of the other db on this server have the same plans (run as the same user, backup to the same directory,) but they all work fine.  Any ideas what I'm missing?  Thanks.


Post #198705
Posted Monday, July 11, 2005 9:06 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, October 20, 2014 3:22 PM
Points: 508, Visits: 244
fyi.  the resolution to my error was to register SQLDMO.DLL in C:\Program Files\Microsoft SQL Server\80\Tools\Binn.  Apparently, due to in improper installation, the dll was not registered for all users of the system.
 



Post #199379
Posted Thursday, July 14, 2005 2:13 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Monday, June 16, 2014 9:46 PM
Points: 284, Visits: 263

Have a look on this link.

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q288577



Sivaprasad S - [ SIVA ]http://sivasql.blogspot.com/
Post #200926
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse