Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Running SSIS fails on local server, not remotely Expand / Collapse
Author
Message
Posted Thursday, July 5, 2012 2:22 PM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, September 5, 2014 10:13 AM
Points: 27, Visits: 154
I have a very simple SQL Server 2008 R2 SSIS package that imports 4 .csv files into a table.

If I deploy the SSIS package to the remote SQL server and run it interactively from SSMS on my client machine, the package runs fine.

If I run that exact same SSIS package from SSMS on the actual SQL server, it fails with data conversion errors "Output Column [ColumnName] failed because truncation would occur...." on all columns in the .csv file. Scheduling the SSIS package raises the same data conversion errors.

I am logged in as the same user on both machines, and the location of the .csv files is the same (on the SQL server).

Does anyone know of something that would cause a single SSIS package to fail when executed locally on the SQL server, but NOT when executed remotely? I could have expected permissions errors, but data conversion errors? Any help would be appreciated!
Post #1325717
Posted Thursday, July 5, 2012 10:43 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, July 15, 2014 5:24 PM
Points: 262, Visits: 681
I've seen that error when the text qualifier gets modified. Check out this blog post from @JamieT.



Rick Krueger

Follow @dataogre
Post #1325838
Posted Friday, July 6, 2012 1:14 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, October 6, 2014 6:14 AM
Points: 564, Visits: 888
Chi Chi Cabron (7/5/2012)
I have a very simple SQL Server 2008 R2 SSIS package that imports 4 .csv files into a table.

If I deploy the SSIS package to the remote SQL server and run it interactively from SSMS on my client machine, the package runs fine.

If I run that exact same SSIS package from SSMS on the actual SQL server, it fails with data conversion errors "Output Column [ColumnName] failed because truncation would occur...." on all columns in the .csv file. Scheduling the SSIS package raises the same data conversion errors.

I am logged in as the same user on both machines, and the location of the .csv files is the same (on the SQL server).

Does anyone know of something that would cause a single SSIS package to fail when executed locally on the SQL server, but NOT when executed remotely? I could have expected permissions errors, but data conversion errors? Any help would be appreciated!


In both cases destination database and table remain same ?


--rhythmk
------------------------------------------------------------------
To post your question use below link

http://www.sqlservercentral.com/articles/Best+Practices/61537/
Post #1325876
Posted Friday, July 6, 2012 10:54 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, September 5, 2014 10:13 AM
Points: 27, Visits: 154
Rick Krueger (7/5/2012)
I've seen that error when the text qualifier gets modified. Check out this blog post from @JamieT.


That did it, thanks!
Post #1326215
Posted Monday, July 9, 2012 12:17 AM


Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Monday, October 6, 2014 6:14 AM
Points: 564, Visits: 888
Chi Chi Cabron (7/6/2012)
Rick Krueger (7/5/2012)
I've seen that error when the text qualifier gets modified. Check out this blog post from @JamieT.


That did it, thanks!


Great !! But could you please post your findings and solution.


--rhythmk
------------------------------------------------------------------
To post your question use below link

http://www.sqlservercentral.com/articles/Best+Practices/61537/
Post #1326666
Posted Monday, July 9, 2012 9:37 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Friday, September 5, 2014 10:13 AM
Points: 27, Visits: 154
rhythmk (7/9/2012)
Chi Chi Cabron (7/6/2012)
Rick Krueger (7/5/2012)
I've seen that error when the text qualifier gets modified. Check out this blog post from @JamieT.


That did it, thanks!


Great !! But could you please post your findings and solution.


I went to the post at http://sqlblog.com/blogs/jamie_thomson/archive/2010/11/25/sql-server-2008-sp1-cu-6-includes-small-changes-to-dtsx-files.aspx

This article states that the text qualifier property in the dtsx file pre-CU6 is read as ' " ' (double quotes), but post-CU6 it is read as "_x0022_".

Examples from the article:
Pre-CU6: <DTS:Property DTS:Name="TextQualifier" xml:space="preserve">"</DTS:Property>

Post-CU6: <DTS:Property DTS:Name="TextQualifier" xml:space="preserve">_x0022_</DTS:Property>


I checked the dtsx file I was running and, sure enough, the text qualifier character was "_x0022_". Checked the version of SQL Server on my local machine and it was completely up to date. Checked the version on the remote server and it was at CU 4 (d'oh!). So the server didn't know how to interpret the "_x0022_" text qualifier and was failing, but my client, being up-to-date, interpreted it correctly and worked. Or at least that's my interpretation.

Changing the text qualifier to " (double quotes) in the dtsx package allowed it to run on the server (CU4), but it would fail when I tried to run from my local client.

So I updated the SQL server (which should have been done, anyway) and now everything works as it should.

Like the blog post says:
There is of course a simple but important lesson here – make sure your developer workstations are running the same builds as your DEV, Test, UAT and Production boxes. Its the sort of problem that you should only encounter once because you’ll never make this stupid mistake twice. Right?
Post #1326931
Posted Monday, August 27, 2012 3:42 PM


Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, September 23, 2014 10:28 AM
Points: 23, Visits: 220
wow i could never guess that could be the issue! it helped me, thanks for sharing the link!
Post #1350626
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse