![]() Since *.1x.0 is not registered *is such a common error message, I post the solution here just to help others who might not aware of the real cause. A such scenario for me representing simply a bug.Īctually, the package is designed in 32-bit and executed in 64-bit environment when Run64BitRuntime is true. I must not to constraint to install the related 32-bit components, otherwise the Run64BitRuntime option is useless. Moreover, I've used SSDT for Visual Studio 2017 with the Run64BitRuntime option sets to True: this option has to function with the Microsoft Access Database Engine 2016 Redistributable 64-bit components when I debug the SSIS package. A such scenario for me representing simply a bug. Moreover, I've used SSDT for Visual Studio 2017 with the Run64BitRuntime option sets to True: this option has to function with the Microsoft Access Database Engine 2016 Redistributable 64-bit components when I debug the SSIS package. Why do I need to work with a 32-bit machine? 64-bit environments spread more and more. I repeat that my machine has Windows 10 64-bit, SQL Server 2017 64-bit and Office 2016 (and so Excel) 64-bit. If you have any compliments or complaints to MSDN Support, feel free to contact Novem8:37 AM This can be beneficial to other community members reading this thread. MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. It looks like you didn't install 32-bit ACE Driver. I've deployed the SSIS solution on the SSIS catalog and executed the deployed package.Īny suggests to me to solve this issue? Thanks I've created the necessary external and output columns for the Excel source and mapped between them,ĥ. I've set ValidateExternalMetadata to True for the Excel source,Ĥ. I've set DelayValidation to True for the Excel connection manager,ģ. I've created a variable to pass the sheet name,Ģ. It seems I've solved, maintaning the Microsoft Access Database Engine 2016 Redistributable components 64-bit!.ġ. If I open the advanced editor for the Excel source I can see an error message about .1x.0 is not registered.Īny suggests to me to solve this issue? Thanks All replies (8) I've tried to three different Excel versions for the Excel connection manager, 2007-2010, 20, but without any results. I've created an Excel connection manager, but when I use it for an Excel source I cannot read data. I've created a SSIS 2017 solution and for the project I've Run64BitRuntime option to True. I've created a sample Excel 2016 file to try to read from it. Moreover, I've installed Microsoft Access Database Engine 2016 Redistributable components. On my machine I've SQL Server 2017 64-bit and SSIS 2017, SSDT for Visual Studio 2017, Excel 2016 64-bit (Office Professional Plus).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |