Please start any new threads on our new site at We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 Old Forums
 CLOSED - SQL Server 2005/Yukon
 Logging package execution.

Author  Topic 

Master Smack Fu Yak Hacker

2365 Posts

Posted - 2006-12-27 : 11:26:17
Has anybody had any luck logging package execution and errors in SSIS?

I have a package that executes just fine in debug mode, but fails as a job with the <sarcasm>incredibly useful</sarcasm> error message:
"Execution of job failed. See the history log for details."

So I check the job history and get other invaluable information, such as:
"The job failed. The Job was invoked by User blindman. The last step to run was step 1"

Ah, now all is clear. NOT!

So I try to enable logging to a text file to find out what is going on. Here is the crap that gets output:

OnError,HC1GEMSQLPRD1,NT AUTHORITY\SYSTEM,Transfer clas data,{DA16E07A-B8E8-450F-BDE6-EC244405D9D6},{1E59C18D-C24B-4709-9EC2-482302BD4A85},12/27/2006 11:19:05 AM,12/27/2006 11:19:05 AM,-1071611876,0x,The AcquireConnection method call to the connection manager "" failed with error code 0xC0202009.

Seriously. I have had so many problems with SQL Server 2005, and come so close to irretrievably losing invaluable data on so many occasions, and had so much downtime, that I could NEVER recommend that any of my clients upgrade to this. In its implementation and documentation SQL Server 2005 is as bad as Oracle.



22859 Posts

Posted - 2006-12-27 : 15:24:53
I feel your pain ... but that's all I can contribute I'm afraid

Go to Top of Page

Master Smack Fu Yak Hacker

3575 Posts

Posted - 2006-12-27 : 15:32:34
I'm a noob with SSIS, so I can't really help either.

FWIW, I've already logged 2 bugs with Microsoft re: SQL2K5 - and we are hardly using it. I am a little bit concerned about the product too and am eagerly awaiting SP2. It seems like SP1 just enabled features that were initially promised for the RTM (mirroring, etc.), it didn't really provide a bunch of bug fixes like I had anticipated.

I guess my advice is to log a call with microsoft, that is really all that I have been doing whenever I run into stuff like this.

Go to Top of Page

- Advertisement -