SQL Server Performance

error 0x80040E21

Discussion in 'SQL Server 2005 Integration Services' started by takens, May 25, 2007.

  1. takens New Member

    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.
  2. satya Moderator

    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.
  3. takens New Member

    service pack 2
  4. satya Moderator

    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.
  5. takens New Member

    It's a new one.
  6. satya Moderator

    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.
  7. takens New Member

    It just import data and does not change any configuration.
  8. satya Moderator

    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.
  9. takens New Member

    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?
  10. satya Moderator

    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.
  11. takens New Member

    First, I called to ask for solution from microsoft and have to wait half an hour for solution to solve this problem.
  12. satya Moderator

    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.
  13. takens New Member

    still don't get the solution now, so I'll report bugs to that link
  14. satya Moderator

    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.
  15. takens New Member

    They will find the solution with their team, and tell me to call again in the next hour...

Share This Page