SSIS <none> text qualifier results in text file containing "_x003C_none_x003E"
There is a bug in SSIS when exporting data from SQL to a comma delimited text file where you specified no text qualifier. This bug apparently only occurs when you develop the SSIS on a x64 win7 PC and copy the .dtsx file (windows explorer copy/paste) to network path of a x86 SQL server and schedule the job to run from SQL Agent on the same x86 SQL server. When the SSIS runs, the text file is written out containing text qualifier = "“_x003C_none_x003E". If you look at " _x003C_none_x003E", it actually means <none>. x003C = "<" and x003E = ">". If you go into the SSIS package, double-click in the connection manager section to open the flat file connection manager editor and try to clear the text qualifier removing the <none>, the <none> value get added back in. The only work-around is to NOT open the flat file connection manager editor, but instead make the change using the property window and clear out any value in the TextQualifier field. Other similar problems occur when you actually want to put a real value in the text qualifier. For explain if you select the double-quote as the text qualifier and copy to a x86 server and run, you end up with a text file containing the value " _x0022" around each field instead of a double quote. In my mind this is a serious bug, I did some research and other people have been having this same issue. FYI, the SQL server is currently SQL2008 with SP2. I will try to get it updated to SP3/4 this weekend to see that will help. FYI2, when I am developing the SSIS using VS2008 and my local test/run is done through visual studio on my Dev PC (x64). Everything works fine this way. I do not have a instance of SQL on my machine so I did not test it running from SQL Agent on my PC.
November 19th, 2010 2:53pm

This might be a problem with BIDS. Some additional information on this problem. This is a simple .dtsx with a single Data Flow that exports SQL table to a flat file (comma-delimited, double-quote text qualifier) On Dev PC (x64 win7), open visual studio 2008, open .dtsx on the remote server via network path (\\server\share\file.dtsx), view flat file connection and change text qualifier to a double quote. Save and close out. Run SSIS via SQL Agent scheduled job for SQL instance on the x86 sql2008 server. View text file and all fields are qualified with _x0022 instead of a double quote. Remote Desktop into your SQL server directly, open visual studio 2008 on the server. When I view the flat file connection, the text qualifier actually says "_x0022". If I change to a double quote, save and run again. This time everything works. Very easy to replicate this bug. Since I am exporting to a text file and the text file was being FTP'd to our customers, this is a serious problem. Our customer was not able to process the text file.
Free Windows Admin Tool Kit Click here and download it now
November 19th, 2010 5:43pm

Is anybody else here running into this problem? Nobody has replied to this thread. I hope somebody from Microsoft can take a look at this. Any helpful comments would be appreciated
December 15th, 2010 10:42am

I just ran into this problem and was totally blown away. I've been using SSIS for 4-5 years and have never run into this problem before until last Friday. I deployed a simple change, completely unrelated to the flat file, and found out this Monday morning that everything run over the weekend was crapped, thanks to this bug. Ditto--this is serious defect that needs fixing.
Free Windows Admin Tool Kit Click here and download it now
December 20th, 2010 11:29am

I also got this problem. You guys have about the same setup as I have, so I can't add any useful info.
December 29th, 2010 4:19am

I also got this problem. You guys have about the same setup as I have, so I can't add any useful info other that I store the packages in Integration Services (database).
Free Windows Admin Tool Kit Click here and download it now
December 29th, 2010 4:19am

Also having the problem........... Any fix or workaround yet??
January 6th, 2011 11:36am

Yes, I have the problem too. The package is in the sql database and I am running it from a c# program. Is there any workaround?
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2011 5:20am

Ok (as identified svollhard above) the problem does occur when trying to run the x86 DTS package on a 64 bit machine. I switched to the 64 SSIS export package and it works fine. The x86 c# program can only run on the x64 machine so I do not know whether I can run my exe from an x86 machine.
February 14th, 2011 5:52am

Hi , This is a bug but there is no bug report anywhere . It was resolved with sql server 2008 sp1 cummulative update 6 (10.00.2757) or higher. Regards Kadir Evciler
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2011 10:44am

I experienced this issue when using SSIS (SQL SERVER 2008 SP2) in environment A and moving this to environment B with 2008 SQL SERVER SP1. Fixed by ensuring both environments have the same version of SQL SERVER 2008 and service packs.
April 7th, 2011 12:48pm

I experienced this issue when using SSIS (SQL SERVER 2008 SP2) in environment A and moving this to environment B with 2008 SQL SERVER SP1. Fixed by ensuring both environments have the same version of SQL SERVER 2008 and service packs. It seems this bug is still out there. I have this issue now. And, both my environment are SQL Server 2008 SP2(10.0.4279). OS: Win 2008 R2(x64). EDIT: I followed this link "http://www.dwbuilder.com/blog/2011/03/30/_x003c_none_x003e_-flat-file-connections/" to solve the issue.
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2011 2:12pm

I experienced this issue when using SSIS (SQL SERVER 2008 SP2) in environment A and moving this to environment B with 2008 SQL SERVER SP1. Fixed by ensuring both environments have the same version of SQL SERVER 2008 and service packs. It seems this bug is still out there. I have this issue now. And, both my environment are SQL Server 2008 SP2(10.0.4279). OS: Win 2008 R2(x64).
April 29th, 2011 2:12pm

This issue is caused by a change in SQL Server 2008 SP1 Cumulative Update 6 in the way SSIS reads and writes content to the DTSX file. This means that 2008 SP1 with CU 5 or lower will behave differently than 2008 SP1 CU 6 or higher (which includes 2008 SP2). For more information on why this is the case, please read Jamie Thomson's blog article about it. Talk to me now on
Free Windows Admin Tool Kit Click here and download it now
June 8th, 2011 1:49pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics