Found unknown column type conversion - by Christoph Muthmann

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


8
0
Sign in
to vote
ID 771818 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 11/21/2012 4:06:55 AM
Access Restriction Public

Description

I'm using SQL Server 2012 SP1 Client.
When I try in SSMS the task "Export Data" with a query, not the table itself and the table has colunns of type varchar, an error occurs. 
Error is e. g.: 
Found 2 unknown column type conversion(s)
You are only allowed to save the package

The version of the sql server database does not matter. The client makes the difference. 
Sign in to post a comment.
Posted by Microsoft on 6/17/2013 at 10:50 AM
Item moved to archive.
Posted by P'tite Poupoune Verreault on 4/25/2013 at 10:11 PM
well actually there is some server that you have to check to be sure your are installaling the right version for your systeme , you have to carefull
Posted by Microsoft on 4/25/2013 at 11:16 AM
Hello Christoph. Thanks for bringing this to our attention. This problem has been fixed. The correction will be included in a future release for SQL Server. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by Microsoft on 4/25/2013 at 11:16 AM
Hello Christoph. Thanks for bringing this to our attention. This problem has been fixed. The correction will be included in a future release for SQL Server. -Walter A Jokiel, Program Manager, SQL Server (wajokiel@microsoft.com)
Posted by JayKirkman on 3/29/2013 at 8:28 AM
Has there been any solution to this since it was reported on 20 FEB 13? I also have been having the problem, and have been unable to obtain a satisfactory solution. Thanks!
Posted by Microsoft on 2/20/2013 at 2:16 PM
Hello Christoph. Thank you for bringing this to our attention. We really do appreciate the feedback. We’ll investigate and get back to you.

Appreciated,
-Walter A Jokiel
Program Manager, SQL Server
Posted by Bjorn D. Jensen on 1/17/2013 at 1:06 AM
In some cases you can export the base tables instead,
but if they are big, this is not a real workaround.