I installed a new SQL Server and implementd a maintenance plan for user databases. In doing so, all the jobs seem to work except the Integrity checks. These jobs fail with the following error:
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Has anyone seen this? Or has an idea how to fix it?
Thanks in advance.
way0utwest
I get the following error when I try to run my scheduled job.
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Any ideas Thanks in advance
Reddy
I have log shipping set up between 2 SQL 2000 SP1 Servers on Win 2000. The db is small 10 meg, and when the restore job on the backup server fails I am getting "sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed." as the message, the maint paln on the primary server show no error. Anyone seen this before? The restore has worked 3 out of 5 times
View 2 Replies View RelatedHi all help needed from your End.
I have a re-indexing stored procedure,yester day night it got failed
"Executed as user: CONNECTSRVmyadmin. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed."
what may be the reason..
I found this error in Job History, I need help to find out the reason and solution for the following errors.
The job failed. The Job was invoked by Schedule 9 (Schedule 1). The last step to run was step 1 (Step 1).
Executed as user: NT AUTHORITYSYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
This problem i found in Maintenance Plan & error log file:
Maintenance Plan:
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 927: [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'restore_test' cannot be opened. It is in the middle of a restore.
[Microsoft][ODBC SQL Server Driver][SQL
Error Log file:
BACKUP failed to complete the command BACKUP DATABASE [restore_test] TO DISK = N'E:SQL_Backups
estore_test
estore_test_db_2006 04160200.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
Please help me in find out the solution
I am having a problem with a Job Step that is failing. The actual Step runs
a Stored Procedure, but the Job keeps failing and returning the following
error
"sqlmaint.exe failed. [SQLSTATE 42000](Error 22029). The step failed."
Does anyone know what this means ?
Thanks.
OK this is a new error on me.
I have a SQL server 2000 on Windows Server 2003.
I have setup a Maint plan that backs up the user and system databases
and the transaction Logs on my user databases.
Does optimises and integrity checks on those databases as well.
I am not attempting to repair any minor problems.
I am not performing integrity checks before backing up the database
and transaction logs.
All of the databases that I am doing a transaction log backup on have
recovery mode of full.
When the jobs run they fail instantly with error code 22029.
Sqlmaint.exe failed to run. This was working up until the end of the
day on the Thursday before Good Friday. (last week) The transaction
log backup ran fine at 4:00 PM the same job failed at 8:00 PM. No
changes were made to the server during that time.
Another issue that started at the same time. I have a web page used to
grab data from a text file export and pull it into an AS400. I use
this server to house the DTS packages and stored procedures that the
process needs. I suddenly quit working when the jobs quit running.
We are in a mixed enviroment with most clients on AD and this server
and most others still in a NT 4 domain. We have been like this for at
least 3 months and everything has worked fine. I setup the various
users and systems the way the need to be, to work.
Originally the SQL Agent was running as a generic NT 4 Domain user with
local administrator rights to the local box and server role of system
administrator. The MSSQLSERVER and DTC services were running as the
built in system account.
Everything was happy then it broke.
When I reboot the server the jobs and the website work fine. Then
after a period of time that I have not figured out yet, but more than
15 minutes and less than 2 hours. Everything quits working.
I have changed all the services to run as a domain admin with SQL
system adminsitrator server role. Still same thing.
I have changed all the services to run as the built in system account.
Still same thing.
I run the sqlmaint from command line with the switches that I am using
in the maint jobs and it runs fine.
I have run dbcc checkdb on all the databases and they are fine.
The DTS packages and the stored procedures used by the website run fine
from with in Query analyzer.
Any help you can provide would be greatly appreciated.
Hi guys i used maintanance wizards to schedule, transactional log backups it gave me this error SQLMAINT.EXE Process exit code 1.
I went to job history and i get this error code SQL STATE 42000 error 22029.
if any one has hints on how to deal with this i will appreciate
We have a maintenance plan that runs every 15 minutes to backup a transaction log. It fails intermittantly with the message:
"sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed."
This is the only error message to be found in any of the logs. I've checked event viewer, the SQL error logs, exception log, maintenance plan log, sysdbmainplan_history table in msdb, but can't find any extra information. I checked the MSDN for info on this error and this did not add any extra light on the problem.
Does anyone have any ideas on how to de-bug this error?
regards
Stuart Ainsley
I have a situation where I am running sqlmaint on 10 - 12 databases on
the same server. All of them run successfully; However, one returns a
failure because of no message. MSDB is not full. There is no messages
in the errorlog. And the actual SQLMAINT executed just fine.
Any Clues?
Sometimes MS SQL is very frustrating!!!!!!!
I have a standard reorganise/reindex job running against a 32GB database on SQl Srever 2000. When trying to run the job it fails and returns Error 1105 <'PRIMARY' filegroup is full>. What's confusing me is that I have 53GB free on the drive on which my Primary file group sits.
Has anyone else come accross this problem when trying to set up a regular reindex job?
(more detail) the maintenance plan only includes the reorganisation/reindex job, no other jobs - including backing up the DB - are included. The DB in question is the only DB on the server: it's a test server.
Is anyone using the -DelBkUps option with their maintenance plan on
SQL 7.0?? if so is it actually deleting the files? Mine is running
but not deleting any of the old backup files.
thanks
I would like to run the following SQLMAINT command on my database every
14days:
At 2:00 AM, this command needs to kick off: SQLMAINT.EXE -D cabinet
-CkAl -CkCat -UpdSts -RebldIdx 100 -Rpt D:MSSQLLOGcab_maint.rpt
Question: How can I "kill" all users, then place the database in "dbo"
mode, run "SQLMAINT", and then release database access back to the
public - all in an automated process.
Any suggestions would be "GREATLY" appreciated.
Thanks,
Chris
Was wanting to get some feedback on using sqlmaint to produce database backups in a production environment. Especially on databases > 10GB. My preference is not to use it but I'm arguing with another DBA and wanted some outside feedback.
Thanks.
Carol
With MSDE 2K I get the following error message when trying to execute scheduled db maintenance/integrity checks:
"Failed executing API: CreateProcess. [SQLSTATE 42000] (Error 22029). The step failed. "
The Microsoft website tells me this is because sqlmaint.exe is not installed and that installing the latest service pack will solve the problem.
I installed the SP3a and sqlmaint.exe is in the following location:
C:/MSDE/Binn
But I still get the error...
Any Ideas?
I am a big fan of the backup naming convention used by maintenance plans and the SQLMAINT utility. My problem is that I want to use the same naming convention "db_name_diff_YYYYMMddhhmmss" because of my situation: I'm in California, my databases are in Pennsylvania, I don't have domain access to the servers, I use a scheduling tool (required) that only uses T-SQL or cmd line utilities, and I want the backups named as above. SQLMAINT provides for full and tlog backups, which I have set up, but I want to do diff backups the same way, with the same naming convention. Any ideas?
View 1 Replies View RelatedI am having problems running sqlmaint against my servers.
From a command line I am running c:sqlmaint -S servername -U "username" -A "password" -D database -UpdSts as a test.
All i get is the list of arguments displayed. This never seems to work.
Any Ideas??
I run the SQLMAINT.EXE utility nightly to do DBCC checkdb, checkalloc, and checkcat checks on all databases. On one server this check seems to lock up the server displaying error 17832, "unable to read login packets". Once this occurs the only way we can find to get out is to reboot the NT Server. We have observed this behaviour once every two or three weeks. Anyone seen anything similar?
View 1 Replies View RelatedDoes anyone know where I could get details on the various switches SqlMaint.exe offers and descriptions of each switches capabilities.
I know by typing in "sqlmaint", it will list all the various switches available but there is not description of what each one exactly means.
Thanks in advance. JLS
Can anyone tell me how to troubleshoot the following error:
'sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.'
Thank you,
Ryan
"sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed."
I get this error message when trying to execute one of the jobs created by the maintenance plan wizard.
Any ideas what caused this error?
hi guys !
I have a simple question , i am using the following command to backup transaction logs :
exec dbo.xp_sqlmaint '-D Northwind -BkUpMedia DISK -BkUpLog "d:sqlackup" -BkExt "TRN" '
does it truncate the tranlog after backup i.e remove the unused entries from there ?
thanks
Sami
P.S: can you please CC me with your answer at esa019c@motorola.com ?
SQL2000 SP3a I would like to generate an HTML output file as a report which should be possible. After creating the maintenance plan using the wizard I used the created syntax and established a second job which now uses the changed syntax - however the job doesnt run. In the log file it just states the basic sqlmaint switches.
Current job syntax - SQL uses build in system account.
EXECUTE master.dbo.xp_sqlmaint N'-PlanID 89CA81E2-181C-42F9- B39C-59EE21936079
-HTMLRpt "C:SystemDbs.html"
-DelHTMLRpt 1DAY
-VrfyBackup
-BkUpMedia DISK
-BkUpDB
-UseDefDir
-DelBkUps 2WEEKS
-CrBkSubDir
-BkExt "BAK"'
I have a maintenance plan on a client's site, there's only one databasein the plan and it's set to backup db and log, this job failsconsistently. The one step in the job contains this line:EXECUTE master.dbo.xp_sqlmaint N'-PlanID392B2334-6800-4655-A6C7-5414D9072505 -WriteHistory -VrfyBackup-BkUpMedia DISK -BkUpDB "C:Program FilesMicrosoft SQLServerMSSQLBACKUPDailyBackups" -DelBkUps 4WEEKS -BkExt "BAK"'Which fails if run in QA with the message:Server: Msg 22029, Level 16, State 1, Line 0sqlmaint.exe failed.I've searched for this error and cannot find anything to help.There's no "-S" in the path, it writes absolutely no history on theplan. I set the plan to write history in the log directory on theserver, it wrote nothing to that directory.The database doesn't get backed up but is able to be backed up manuallyto the path specified in the plan. I also have a separate job with aSQL backup statement in it that works OK so SQLAgent is working.
View 9 Replies View Related
I am using SQL 2000,everyday we are running database backup plan but it shows a error like "Executed as user: NT AUTHORITYSYSTEM. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed."
Our database recovery model is also in Full mode.Burt i don't know why its happening with us,before that database maintenance plan was working fine but for last 2 months its not working.
thanks,
-Amit
Hi,
I am trying to run the following:
SQLMAINT.EXE -USA -P -S abc -D db1 -CkDB -Rpt c:log_backup.rpt -DelTxtRpt 1days
But it simply returns the
SQLMaint switches and doesn't run the actual -CkDB?
Do I need to register any DLL to make this work ?
Thanks in advance,
I'm running SQLMaint.exe for DBCC and backups overnight, because I like the -BkUpOnlyIfClean switch, but I'm having a problem. I need
Due to space constraints, I need to overwrite the backup every night. The -DelBkUps switch is nice, but it accepts a parameter of weeks, not days. Is there some syntax I can use with SQLMaint.exe to get what I want, or am I going to have to do an NT 'at' commnad to get rid of the file just before th enext dump, or what? Any suggestions would be intensely appreciated.
I get the following error when I try to run the Integrity check aspect of my maintenance plan...
Executed as user: MISSIONAdministrator. sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
Microsoft indicates this is b/c sqlmaint.exe is not installed as part of MSDE 2K and that upgrading to latest service pack will solve.
The optimizations work fine...Is there a way to invoke the integrity check w/out using the maintenance plan wizard?
:mad: It seems that the SQLmaint is going to obsolete in SQL 2005, what happen to my "sophisticated" SQLmaint scripts!!!! Any help or comment?
View 8 Replies View RelatedNew to SQL Server.
I am looking at some legacy sqlmaint scripts.
If I don't see the switches
ReblIdx
or
UpdOptiStats
Does that mean that there are no database reorgs and no update system
catalog statistics being done?
The rebuild index switch is SQL Server speak for a reorg correct?
Thanks in advance.
Gerry
Hi! I have a SQL 7.0. The backups created by maintenance plan workedvery well before someone shut down the server to do some servermaintenance. After restart the server, the backup job is not workingany more. All the backups created by maintenance plan are not working,including the newely created one. The message is "Server: Msg 22029, Level 16, State 1, Line 0sqlmaint.exe failed."Please help me out!! Thanks.Saiyou
View 1 Replies View RelatedBoth "dump database" and "sqlmaint.exe -bkupdb" would be able to backup database, one important advantage I can see from "sqlmaint" is that it has the option to cleanup the very old generations of backups by using -delbkups option in a scheduled maintenance backup job, while the "dump database" would first create a dump device and it'll grow with time.
Is there any suggested way to use the "dump transaction" but still we can get control on the size of dasd used ?
Any negative part of using "sqlmaint" utitity to backup database as compared to the "dump database " utility ?
Anthony
We run SQLMaint hourly ( as a scheduled task ) to clear our transaction logs. Last night our hard drive filled up during a log dump, causing SQLMaint to fail, and a subsequent transaction filled up the log.
We succeeded in manually truncating and clearing the log, but SQLMaint still insists on us doing a DUMP DATABASE to clear the logs before it will run again. Unfortunately, we do not have enough space left on our hard drive to do a full database dump.
Is there any way of fooling SQLMaint into believing that a DUMP has been run? Some flag in a system table somewhere, or maybe a registry entry?
John Morrison
Hurst, TX