?
Solved

SQL Server 2000 sqlmaint.exe maintenance plan execution error

Posted on 2008-10-09
3
Medium Priority
?
1,878 Views
Last Modified: 2012-05-05
I am experiencing a problem with my maintenance plans running under SQL Server 2000 running on Windows 2000. I suspect that the error (below) is occurring due to permissions problems with the user executing the maintenance plan. What permissions does the executing user need to hold and where do I verify this and change the details if necessary?

sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The Step failed.

Executed as user: NT Authority\SYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The Step failed.

0
Comment
Question by:james_j_hedges
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 6

Expert Comment

by:Jerryuk007
ID: 22677043
It seems MSSQL Services are started using Local System Account.
Sometimes when getting this error, a restart of MSSQL (or Server reboot) helps... (Of course make sure that MSSQL Agent is configured properly and started)

Also it's generally better to start MSSQL using a Domain User Account (also Local Administrator on the Database Server) as this generally give more "flexibility" over what you can do especially if you need that server to access Server Resources...

Jerry
0
 

Author Comment

by:james_j_hedges
ID: 22678275
Upon further investigation, it looks more like this is a generic error that is the result of one or more parts of that particular component of the maintenance plan failing. For example, not being able to perform optimisation jobs on databases that are not in single-user mode. In this instance, I suspect that this had nothing to do with permissions and more to do with SQL Server 2000's lack of detailed error reporting.
0
 
LVL 6

Accepted Solution

by:
Jerryuk007 earned 1500 total points
ID: 22685699
You're right on that. This error lacks details and is really generic.
In fact, often you will get it when MSSQL doesn't know what to say... ;-)

I don't believe Optimisation Jobs need the databases to be in Single User Mode though it's better if they are else you might get a warning about "spurius records..." or something.

Have you try a restart of MSSQL Services ?

Jerry
0

Featured Post

Migrating Your Company's PCs

To keep pace with competitors, businesses must keep employees productive, and that means providing them with the latest technology. This document provides the tips and tricks you need to help you migrate an outdated PC fleet to new desktops, laptops, and tablets.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
It is possible to export the data of a SQL Table in SSMS and generate INSERT statements. It's neatly tucked away in the generate scripts option of a database.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Via a live example, show how to extract information from SQL Server on Database, Connection and Server properties
Suggested Courses

800 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question