SQL Server Integration Services package fails on DataReader

Share on Facebook

I had an Integration services package which I scheduled as an SQL server Job in SQL Server Management Studio and was working fine. A while later, I did some folder organisation on the server drive containing the ODBC Database in use by the IS Package (In this particular case, it was a Sage Line 50 ODBC Datasource). In my re-arranging files to mirror the structure on another server, I created fileshares which pointed to actual folders mapped then to drives using 'net share' command in login script.

Well, I discovered the scheduled IS packages were no longer running to success but failing. I was able to run them from SSBIDS (SQL Server Business Intelligence Development Studio), but they failed to execute from Management Studio as a job. I tried all tricks and it simply would fail.

To cut a long story short, I decided to simply try changing the ODBC Data Source path and not use the mapped drive and shared folder, but use the actual physical path to the package, and BINGO, It started working again. So if you have a similar problem, might not necessarily be an exact fix, but I hope this will point you in the right direction or at least give you another possible solution to try.

Cheers!

Digg It!DZone It!StumbleUponTechnoratiRedditDel.icio.usNewsVineFurlBlinkListkick it on DotNetKicks.comTwitThis

Comments are closed

About Me

When not scratching my head for solutions to software challenges, I spend my time playing with my little boy - Michael Jnr.

Quotations

"Success is the ability to go from one failure to another with no loss of enthusiasm."
Sir Winston Churchill

Donate with PayPal - it

Calendar

<<  February 2012  >>
MoTuWeThFrSaSu
303112345
6789101112
13141516171819
20212223242526
2728291234
567891011

View posts in large calendar

Disclaimer

The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway.

© Copyright 2005 - 2012

Search