Post reply

Failed executing API: CreateProcess. [SQLSTATE 42000] (Error 22029)

  • September 18, 2006 at 1:11 pm

    #62716

    I have recently experienced a problem with SQL server maintence packages on some recently built servers.

    I am getting a Failed executing API: CreateProcess. [SQLSTATE 42000] (Error 22029).  The step failed message in the job log file.

    I am getting this message on 4 different recently built servers - the servers all are running 2003 Server OS with SP1, Microsoft SQL 2000 with

    Service Pack 4. The SQL installation is a default installation, no named instance and Mixed authentication. The SA user has ownership rights to all

    databases on the server. The backup path is to a shared drive on the server - all users have access, domain user is granted full control.

    SQL Agent and server are using default logins on 2 of the  servers -

    on the other the SQL agent was logging in as a user that had admin privlidges in the SQL installation and was a Domain Admin as well.

    The problem appears to be with the stored proceedure that the the maintence package calls.

     

  • September 18, 2006 at 2:05 pm

    #661126

    John,

    this could be anything and it's pretty hard to tell without the exact error from the logfile. Your maintenace plan should make logfiles which you can find in the MSSQL\Log folder. These give you more detailed information. The error above is just a general message that sqlmaint.exe received an error.

    But from the fact that it appears on several servers at the same time, my guess would be that someone changed the password for the account which starts the SQL Agent service.

    Markus

    [font="Verdana"]Markus Bohse[/font]

  • September 18, 2006 at 2:20 pm

    #661129

    Are these jobs failing on MSDE Servers?

     

  • September 18, 2006 at 5:28 pm

    #661145

    No the server is not an MSDE server,

  • September 19, 2006 at 3:11 pm

    #661372

    Attempted to turn on log files for one of the servers that has the problem. Saved settings, stop/started SQL services. Log file will not write.

    Turned logging on for a server that is working correctly and logging works.

    The problem seems to be that the stored proceedure does not want to work. I have stopped SQL - uninstalled the server - booted the box then reinstalled SQL server, reapplied SP4 - problem is still happening.

     

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply