I'm assuming it has something to do with the account under which my job step is running ? The only choice i have when setting up a job step is to run under the Sql My OS Command used on the job step and the message being returned are shown below. However when i attempt to invoke the package from a sql server job step, i getĪn error. If i call the package directly (via DTEXECUI for example), the package runs ok.
EPM COMPATIBLE WITH EXCEL 2010 64 BIT 32 BIT
Todd: Following up on prior discussion, i'm executing the 32 bit dtexec to call my ssis package. Source Microsoft Corporation Microsoft SqlServer v9 (C) 2005 Microsoft Corporaĭescription: component "Excel Source" (1) failed validation and returned errĭescription: One or more component failed validation.ĭescription: There were errors during task validation.ĭTExec: The package execution returned DTSER_FAILURE (1). The contact information for this component is "Excel Source: ProcessStagingData ProcessStagingData (DTS.Pipeline)ĭescription: The version of component "OLE DB Command" (64) is not compatiblĭescription: The component is missing, not registered, not upgradeable, or m Source: LoadStagingData LoadStagingData (DTS.Pipeline)ĭescription: The version of component "Excel Source" (1) is not compatible w Microsoft (R) SQL Server Execute Package UtilityĬopyright (C) Microsoft Corp 1984-2005. Is not compatible with this version of the data flow", that you're aware of ?Ĭ:\>"c:\program files (x86)\Microsoft SQL Server\90\DTS\Binn\DTEXEC.EXE" /SQL "ĮDIS_3_test19115" /DECRYPT EDIS /CHECKPOINTING OFF /REPORTING E /SERVER "emasl Any other causes of the message, "the version of component xxxxx Basically, the same result in my prior plaining that the version of the components are not compatible with the data flow. Then got the result below (a little cut off on the right). "\EDIS_3_test19115" /SERVER "emaslcdb2\sql2005_staging" /DECRYPT EDIS /CHECKPOINTING OFF /REPORTING E The above syntax actually didn't work from sqlagent job step.but as a test, i opened up the 32 bit command window (c:\windows\syswow64\cmd.exe) and then executed "C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTEXEC.EXE" /SQL The step failed.Ĭ:\Windows\SYSWOW64\CMD.EXE /C "C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTEXEC.EXE" /SQL "\EDIS_3_test19115" /SERVER "emaslcdb2\sql2005_staging" /DECRYPT EDIS /CHECKPOINTING OFF /REPORTING E End Error Error: ġ4:49:24.07 Code: 0xC0048021 Source: LoadStagingData Excel Source Description: The component is m.
End Error Error: ġ4:49:24.07 Code: 0xC0048020 Source: LoadStagingData DTS.Pipeline Description: The version of component "Excel Source" (1) is not compatible with this version of the DataFlow. End Error Error: 14:49:24.06Ĭode: 0xC0048020 Source: ProcessStagingData ProcessStagingData (DTS.Pipeline) Description: The version of component "OLE DB Command" (64) is not compatible with this version of the DataFlow. Source: LoadStagingData LoadStagingData (DTS.Pipeline) Description: The version of component "Excel Source" (1) is not compatible with this version of the DataFlow. Any thoughts ? thanksĬ:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTEXEC.EXE /SQL "\EDIS_3_test19115" /SERVER "emaslcdb2\sql2005_staging" /DECRYPT EDIS /CHECKPOINTING OFF /REPORTING EĮxecuted as user: EMASSIST\z_sqlagent.ge Utility Version.
EPM COMPATIBLE WITH EXCEL 2010 64 BIT 64 BIT
Per your instructions in posts above, i am launching the package using the "OS Command" option of the job step and specifically calling the 32īit version of DTEXEC.however i continue to get the "Version of component" issue that i had when i was callling the 64 bit version of DTEXEC. Todd: I am running an SSIS 2005 package (programatically created) on a 2005 instance installed on a 64 bit box.
0 kommentar(er)
