SSIS Packages are running on Staging but not on the Production Server - little bit Urgent my friends
-
Hi, I have some SSIS Packages that are getting executed using a .Net Application, when I execute them in Staging Environment they are properly executing and importing the Data, but when I execute them on Production Server they are not importing the Data, I am unable to debug because its a Production Server, I have enabled Logging on the Packages to write into a Table, still the error message is not much useful any help would be greatly helpful. Thanks in advance. The error message I am getting into the ErrorLog Table is:
Execution failed for SSIS Package: BillingDataLoad, Error description: FileFullName: Source Is Db, SSISPackageName: BillingDataLoad.dtsx, Source : Microsoft.SqlServer.Dts.Runtime.TaskHost, InformationCode : 1074041076, Description : Lookup has cached 16 rows. , SubComponent: Lookup [82], HelpFiledtsmsg110.rll, HelpContext0, IdofInterfaceWithError{B6F6D221-FC27-4F71-B5A0-597583986C28}
When I implemented SSIS Logging in my Application, I found that both 32 bit Jet 4.0 and 64 bit Ace 12.0 drivers are not registered on Production Server. But there are 32 bit and 64 bit Ace 14.0 drivers are there, then why Package is not able to execute on Production? Are Ace 14.0 64 bit and Ace 12.0 64 bit drivers not compatible to each other? Another thing is, even though I have Ace 14.0 drivers on my local machine Data tools 2012 is taking Ace 12.0 64 bit drivers when I Create Data flow task using an xlsx file as data source? Why is it not taking Ace 14.0 drivers instead, I am creating the packages with Visual studio 2012 and .Net 4.0. Why is my Package taking Ace 12.0 drivers by default and expecting it to be registered on the Server. Is there any solution for me? Can anybody please suggest me, so any change I have to make should have solid ground because I am going to make that change on the Production server. Please help I need some guidance or a link anything. By the way I tried both the .xls and .xlsx files and run Package under both 32 bit and 64 bit modes in both cases its failing, because 32 bit failing for Jet drivers not registered and 64 bit is failing by saying Ace 12.0 not registered when Ace 14.0 is registered there.
Description {0}Excel Source failed validation and returned error code 0xC020801C.
, HelpContext {0}0, HelpFile {0}dtsmsg110.rll, IDOfInterfaceWithError {0}{B6F6D221-FC27-4F71-B5A0-597583986C28}, Source {0}
Data Flow Task, Subcomponent {0}SSIS.Pipeline, Timestamp {0}9/27/2017 5:03:34 PM, ErrorCode {0}-1073450985
Description {0}SS -
Hi, I have some SSIS Packages that are getting executed using a .Net Application, when I execute them in Staging Environment they are properly executing and importing the Data, but when I execute them on Production Server they are not importing the Data, I am unable to debug because its a Production Server, I have enabled Logging on the Packages to write into a Table, still the error message is not much useful any help would be greatly helpful. Thanks in advance. The error message I am getting into the ErrorLog Table is:
Execution failed for SSIS Package: BillingDataLoad, Error description: FileFullName: Source Is Db, SSISPackageName: BillingDataLoad.dtsx, Source : Microsoft.SqlServer.Dts.Runtime.TaskHost, InformationCode : 1074041076, Description : Lookup has cached 16 rows. , SubComponent: Lookup [82], HelpFiledtsmsg110.rll, HelpContext0, IdofInterfaceWithError{B6F6D221-FC27-4F71-B5A0-597583986C28}
When I implemented SSIS Logging in my Application, I found that both 32 bit Jet 4.0 and 64 bit Ace 12.0 drivers are not registered on Production Server. But there are 32 bit and 64 bit Ace 14.0 drivers are there, then why Package is not able to execute on Production? Are Ace 14.0 64 bit and Ace 12.0 64 bit drivers not compatible to each other? Another thing is, even though I have Ace 14.0 drivers on my local machine Data tools 2012 is taking Ace 12.0 64 bit drivers when I Create Data flow task using an xlsx file as data source? Why is it not taking Ace 14.0 drivers instead, I am creating the packages with Visual studio 2012 and .Net 4.0. Why is my Package taking Ace 12.0 drivers by default and expecting it to be registered on the Server. Is there any solution for me? Can anybody please suggest me, so any change I have to make should have solid ground because I am going to make that change on the Production server. Please help I need some guidance or a link anything. By the way I tried both the .xls and .xlsx files and run Package under both 32 bit and 64 bit modes in both cases its failing, because 32 bit failing for Jet drivers not registered and 64 bit is failing by saying Ace 12.0 not registered when Ace 14.0 is registered there.
Description {0}Excel Source failed validation and returned error code 0xC020801C.
, HelpContext {0}0, HelpFile {0}dtsmsg110.rll, IDOfInterfaceWithError {0}{B6F6D221-FC27-4F71-B5A0-597583986C28}, Source {0}
Data Flow Task, Subcomponent {0}SSIS.Pipeline, Timestamp {0}9/27/2017 5:03:34 PM, ErrorCode {0}-1073450985
Description {0}SS -
Hi, I have some SSIS Packages that are getting executed using a .Net Application, when I execute them in Staging Environment they are properly executing and importing the Data, but when I execute them on Production Server they are not importing the Data, I am unable to debug because its a Production Server, I have enabled Logging on the Packages to write into a Table, still the error message is not much useful any help would be greatly helpful. Thanks in advance. The error message I am getting into the ErrorLog Table is:
Execution failed for SSIS Package: BillingDataLoad, Error description: FileFullName: Source Is Db, SSISPackageName: BillingDataLoad.dtsx, Source : Microsoft.SqlServer.Dts.Runtime.TaskHost, InformationCode : 1074041076, Description : Lookup has cached 16 rows. , SubComponent: Lookup [82], HelpFiledtsmsg110.rll, HelpContext0, IdofInterfaceWithError{B6F6D221-FC27-4F71-B5A0-597583986C28}
When I implemented SSIS Logging in my Application, I found that both 32 bit Jet 4.0 and 64 bit Ace 12.0 drivers are not registered on Production Server. But there are 32 bit and 64 bit Ace 14.0 drivers are there, then why Package is not able to execute on Production? Are Ace 14.0 64 bit and Ace 12.0 64 bit drivers not compatible to each other? Another thing is, even though I have Ace 14.0 drivers on my local machine Data tools 2012 is taking Ace 12.0 64 bit drivers when I Create Data flow task using an xlsx file as data source? Why is it not taking Ace 14.0 drivers instead, I am creating the packages with Visual studio 2012 and .Net 4.0. Why is my Package taking Ace 12.0 drivers by default and expecting it to be registered on the Server. Is there any solution for me? Can anybody please suggest me, so any change I have to make should have solid ground because I am going to make that change on the Production server. Please help I need some guidance or a link anything. By the way I tried both the .xls and .xlsx files and run Package under both 32 bit and 64 bit modes in both cases its failing, because 32 bit failing for Jet drivers not registered and 64 bit is failing by saying Ace 12.0 not registered when Ace 14.0 is registered there.
Description {0}Excel Source failed validation and returned error code 0xC020801C.
, HelpContext {0}0, HelpFile {0}dtsmsg110.rll, IDOfInterfaceWithError {0}{B6F6D221-FC27-4F71-B5A0-597583986C28}, Source {0}
Data Flow Task, Subcomponent {0}SSIS.Pipeline, Timestamp {0}9/27/2017 5:03:34 PM, ErrorCode {0}-1073450985
Description {0}SS -
Following certainly suggests that more information is available. DtsError.IDOfInterfaceWithError Property (Microsoft.SqlServer.Dts.Runtime)[^]
Hi, Thank you, I did implement it in my Application, I found that both 32 bit Jet 4.0 and 64 bit Ace 12.0 drivers are not registered on Production Server. But there are 32 bit and 64 bit Ace 14.0 drivers are there, then why Package is not able to execute? Are Ace 14.0 64 bit and Ace 12.0 64 bit drivers not compatible to each other? Another thing is, even though I have Ace 14.0 drivers on my local machine Data tools 2012 is taking Ace 12.0 64 bit drivers when I Create Data flow task using an xlsx file as data source? Why is it not taking Ace 14.0 drivers instead, I am creating the packages with Visual studio 2012 and .Net 4.0. Why is my Package taking Ace 12.0 drivers by default and expecting it to be registered on the Server. Is there any solution for me? Can anybody please suggest me, so any change I have to make should have solid ground because I am going to make that change on the Production server. Please help I need some guidance or a link anything. By the way I tried both the .xls and .xlsx files and run Package under both 32 bit and 64 bit modes in both cases its failing because 32 bit failing for Jet drivers not registered and 64 bit is failing because Ace 12.0 specifically not registered when Ace 14.0 is registered there. Thanks, Abdul Aleem "There is already enough hatred in the world lets spread love, compassion and affection."