Home > SSIS Best Practices > SQL Job Agent – Unable to give specific error messages for failed SSIS packages

SQL Job Agent – Unable to give specific error messages for failed SSIS packages

Below is the original post. After I post the blog, I was pretty sure that the Service Pack 3 should fix the problem.

Yes, it did!

Now the error message from a failed SSIS package is loud and clear.

——————————————————————————————————————–

It is very annoying that one of our development SQL Servers the SQL Job Agent was unable to give specific error messages for failed SSIS packages.

I’ve checked the SQL Server version/Build.

Microsoft SQL Server 2005 – 9.00.1399.06 (X64)   Oct 14 2005 00:35:21 

I think it’s missing SP 3, but am not sure if it will fix this problem.

From: Sherry
Sent: Friday, September 17, 2010 1:32 PM
To: All
Subject: RE: SQL Server Version/Build

I’ve created a SSIS package that will certainly fail to test if I can receive the error message from the SQL Job Agent.

Here is what I get from the test server. It’s very clear. It’s telling me which task failed and why. This is very helpful when we are troubleshooting our ETL process.

image

This is what I got from the XX server. Very generic, no specific information that can help me to do troubleshooting. I also checked the SQL job agent output file. It has many errors that I do not understand. Not sure if they are related.

image

Sherry

Categories: SSIS Best Practices
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: