Help Please I got some problem while trying to deploy package to server. Cannot save the package ".....product.dtsx" to SQL server "......" TO save the SQLServer method has encounter OleDB error code 0x80040E21 (Invalid Character Value for cast specification). The SQL statement that was issued has failed.
What is the service pack level on SQL Server & client? Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
Is it an upgraded DTS package or a new one? What are steps involved in that package? Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
How about steps in that DTS package? Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
Strange, the error 0x80040E21 can happen if you use an OpenStatic ADODB.Recordset object to open Excel, or use an OpenKeyset recordset to perform paging, Within the import process if you are executing a stored procedure, make sure you do so through the connection.execute() method, rather than a command object, and add the following two lines of code to the beginning of your procedure: SET ANSI_NULLS OFF SET NOCOUNT ON Also ensure MDAC version matches on the client and server, as this can be a culprit in some ocassions. Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
Thank you so much for your help, I'll try to check it and tell you about the result. Do you have any comment for this error that I can check it for fixing this problem?
Well as of now nothing succeeds, I suggest to report inhttp://connect.microsoft.com site for a feedback. Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
First, I called to ask for solution from microsoft and have to wait half an hour for solution to solve this problem.
So did you get the solution then, the link i have referred is to report bugs for a fix. Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.
What was the suggestion when called for MS support in thsi case. Satya SKJ Microsoft SQL Server MVP Writer, Contributing Editor & Moderator http://www.SQL-Server-Performance.Com This posting is provided AS IS with no rights for the sake of knowledge sharing. Knowledge is of two kinds. We know a subject ourselves or we know where we can find information on it.