|
|
|
Old Hand
 
Group: General Forum Members
Last Login: 2 days ago @ 5:19 PM
Points: 324,
Visits: 769
|
|
I have problems with several SQL Server 2005 Maintenance Jobs that run continuously. They start but, never complete. This occurs on all jobs that run a SSIS package. Jobs that only run T-SQL run fine. The job never fails and other error message cannot be found. I have checked the SQL logs as well as the Windows logs. The only message I can find is an informational Windows system log that appears every time the job runs. Obviously, this is the cause, or related to it, but I cannot find a solution.
******************************
Windows System Log:
Event Source: Application Popup
Event ID: 26
Description:
Application popup: DTExec.exe - Application Error : The application failed to initialize properly (0xc0000142). Click on OK to terminate the application.
******************************
Server Info:
Microsoft SQL Server 2005 - 9.00.4035.00 (X64)
Standard Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
******************************
Package Info:
Job Command Line: /SQL "Maintenance Plans\DbMaintenancePlan" /SERVER "(local)" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /SET "\Package\Daily_Log_Backup.Disable";false /REPORTING E
******************************
Thank you for your help.
Jon
|
|
|
|
|
Ten Centuries
Group: General Forum Members
Last Login: Tuesday, February 14, 2012 8:31 PM
Points: 1,048,
Visits: 1,875
|
|
I would recommend that you reinstall your SSIS client. There is something wrong going on.
---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/
|
|
|
|
|
Old Hand
Group: General Forum Members
Last Login: 2 days ago @ 5:19 PM
Points: 324,
Visits: 769
|
|
Thanks Cozy. I will consider this after more troubleshooting. To rule out a possible client issue I created a backup plan from my workstation as well as from the server. Same result. Other servers work fine.
I have discovered that I can execute the package from the command line:
DTExec /SQL "Maintenance Plans\DbMaintenancePlan" /SERVER "(local)" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /SET "\Package\Daily_Log_Backup.Disable";false /REPORTING E
So, I now know the command works, just not from the job. Thinking it was a possible permissions issue, I changed the job to run as local admin. Same result: job never completes and no error messages other than the informational Windows message. And nothing is in the job logs.
|
|
|
|
|
Ten Centuries
Group: General Forum Members
Last Login: Tuesday, February 14, 2012 8:31 PM
Points: 1,048,
Visits: 1,875
|
|
Have you used Process Monitor before? It is for tracing the operations with files and the registry. It will help you find what is going on, though it may take a awhile, browsing thru the logs.
---
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/
|
|
|
|
|
Forum Newbie
Group: General Forum Members
Last Login: Tuesday, June 21, 2011 9:38 PM
Points: 1,
Visits: 77
|
|
| Did you got the solution for this. I am getting the same error too and on 64bit machine.
|
|
|
|
|
Old Hand
Group: General Forum Members
Last Login: Tuesday, January 31, 2012 12:27 PM
Points: 352,
Visits: 812
|
|
| One thing to try is to run the 32 bit version of DTExec to verify you get the same result. I had to do this once because one of the OLE drivers was 32 bit. Now I can't explain why it worked from the command line. I agree it does sound like a permissions error. Another thing would be to setup a proxy under your credentials and try to run it under that proxy. If it works then it was permissions error.
|
|
|
|
|
SSC-Enthusiastic
Group: General Forum Members
Last Login: Friday, October 14, 2011 12:52 AM
Points: 135,
Visits: 46
|
|
| Was there any solution to this. I am having the same problem?
|
|
|
|
|
Old Hand
Group: General Forum Members
Last Login: 2 days ago @ 5:19 PM
Points: 324,
Visits: 769
|
|
I apologize to everyone for not posting back my findings. Unfortunately, I don’t have a definitive solution for you, but I can share with you what I found. This is one of those messy servers that DBAs inherit sometimes and I have been so busy cleaning up I forgot to post back. This problem went away after I consolidated many SQL Server Replication Jobs. I am not sure why, but I suspect it had something to do with the non-interactive desktop heap (KB 824422).
After searching on the Internet for some time, as I am sure you are doing right now, I came across MS KB 824422 (http://support.microsoft.com/kb/824422)This was close to my problem, but not exactly. The KB did make me think about how many processes where running concurrently. The following week I was getting several replication job errors, which as you know run SQL Jobs. We did have a couple hundred SQL Server replication jobs run continuously. Don’t ask me why so many, as I said, I inherited this mess  , but consolidating the replication jobs had been a task I wanted to get done since I was hired. I decided to start that task and see what happens. Sure enough, the errors went away.  Keep in mind, I did NOT make any registry changes as the KB suggested. I just reduced the number of concurrent SQL Jobs.
It would be great if some could confirm that the non-interactive desktop heap limitation was the problem.
Regards,
Jon
|
|
|
|
|
SSC-Enthusiastic
Group: General Forum Members
Last Login: Saturday, February 11, 2012 8:13 AM
Points: 153,
Visits: 63
|
|
I too am having the same problem. I did try the non-interactive desktop heap limitation but it did not make any difference.
|
|
|
|
|
Old Hand
Group: General Forum Members
Last Login: 2 days ago @ 5:19 PM
Points: 324,
Visits: 769
|
|
kpanchal (7/6/2010)
I too am having the same problem. I did try the non-interactive desktop heap limitation but it did not make any difference.
kpanchal,
Ultimately, I fixed my problem by reducing the number of concurrent SQL jobs. I wish I new a little more how this works with Windows, but basically there is a memory limitation on how many processes can run at once. While I think the default configuration is more than adequate for most circumstances, I think I just had an unusually large number of jobs running concurrently.
Do you have a lot jobs running at the same time?
Jon
|
|
|
|
