SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Fix - Cannot create COM Server to load and execute DTS Package


Fix - Cannot create COM Server to load and execute DTS Package

Author
Message
Rhonda Veit
Rhonda Veit
Old Hand
Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)

Group: General Forum Members
Points: 321 Visits: 1

One of my production servers had showed all non-backup jobs had failed for that exact same reason. They would run fine from the DTS section, but not as a scheduled job.

The error was:

“Executed as user: DOMAIN\Administrator. DTSRun: Cannot create COM Server to load and execute DTS Package. Error -2147221008 (800401F0): CoInitialize has not been called. Process Exit Code -2147221008. The step failed.”

I researched on the internet and tried a couple things, but none of them helped. (Re-installing MDAC, reviewing local security policies…) But most of the info I found indicated it was a security issue and not a problem with the software.

After much looking around, I stumbled upon the answer. I went to the properties of the SQL Server Agent and reviewed the rights on it. They were correctly set to DOMAIN\Administrator. But on the last tab it listed a proxy user – and was using Windows authentication. I switched it to SQL authentication and gave it the sa username and password. The service restarted and lo-and-behold! the jobs started working.





GeBlack
GeBlack
SSC Eights!
SSC Eights! (923 reputation)SSC Eights! (923 reputation)SSC Eights! (923 reputation)SSC Eights! (923 reputation)SSC Eights! (923 reputation)SSC Eights! (923 reputation)SSC Eights! (923 reputation)SSC Eights! (923 reputation)

Group: General Forum Members
Points: 923 Visits: 23

I take it this is not a question, simply a public celebration

Congratulations





Rhonda Veit
Rhonda Veit
Old Hand
Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)Old Hand (321 reputation)

Group: General Forum Members
Points: 321 Visits: 1

Definitely a celebration!

Of course, I discovered more than one thing can cause that particular error. But figured since I stumbled upon this solution, I better post it somewhere for others to find.





Steve Collins
Steve Collins
SSC Rookie
SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)SSC Rookie (43 reputation)

Group: General Forum Members
Points: 43 Visits: 1
What are the other fixes? I tried this one and it didn't work.
hamishahern
hamishahern
SSC-Addicted
SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)

Group: General Forum Members
Points: 410 Visits: 1
I too am receiving a similiar error on a couple of my dts schedules out of 1,000.
When I restart the agent service the errors go away for a few days.

Executed as user: TPOWER\TMERADSQL. DTSRun: Cannot create COM Server to load and execute DTS Package. Error -2147221008 (800401F0): CoInitialize has not been called. Process Exit Code -2147221008. The step failed.

Something is leaking somewhere, I'm thinking maybe memory or com handles, I'm not too sure.
Either way, I think its something that MS should have fixed, considering we're now on SP3a.

I'm running Windows Server 2003, and this server only runs dts jobs.


Is it possible that had you not changed the security for the agent and restarted the service it could have worked from restarting the service?

I will try and change the agents login on mine and I'll let you know how I get on.

Anybody else got any possible working solutions?



Peter Gadsby
Peter Gadsby
SSCrazy
SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)SSCrazy (2.3K reputation)

Group: General Forum Members
Points: 2256 Visits: 305

Hi Grasshopper, I have exactly the same problem (Windows 2003). for days no problem then I get this failure which stops all jobs from running, the only cure seems to be restarting the agent.

Any help much appreciated

Peter G

Peter.Gadsby@ntl.com



Peter Gadsby
Business Intelligence Consultant
www.hgconsult.co.uk
hamishahern
hamishahern
SSC-Addicted
SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)SSC-Addicted (410 reputation)

Group: General Forum Members
Points: 410 Visits: 1
Its definately memory related, and the fact that restarting the Agent suggests that its the agent that is leaking the memory.

If anybody can reproduce it easily, perhaps we can send something to Microsoft to work on.



linabran
linabran
Valued Member
Valued Member (67 reputation)Valued Member (67 reputation)Valued Member (67 reputation)Valued Member (67 reputation)Valued Member (67 reputation)Valued Member (67 reputation)Valued Member (67 reputation)Valued Member (67 reputation)

Group: General Forum Members
Points: 67 Visits: 2
Muchas gracias, he buscado esta solucion hace mucho, acabo de realizar todo el proceso, espero que funcione bien, lastimosamente no puedo correr el proceso ya, pero mañana les confirmo.

Saludos.

Lina M.BigGrin
marina-342327
marina-342327
SSC Journeyman
SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)SSC Journeyman (75 reputation)

Group: General Forum Members
Points: 75 Visits: 63
Thanks for explanation!
Marina
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search