October 18, 2018 at 1:11 pm
Hello, I am on Windows Server 2012 R2 SE, and SQL Server 2016 SP1, and I have developed several packages with Visual Studio 2015 Community, SSDT 14, using Attunity 4 and Teradata 15.1 Drivers and utilities.
Now I have upgraded the Teradata Drivers and Utilities to 16.2, kept Attunity 4, and installed Visual Studio 2017 Pro, with SSDT 15.
One note: I had all the tools and drivers on the C:\ of the server, and after all the uninstall to save space on C:\ as it was limited, I installed VS17 on D:\. Teradata and Attunity are installed on C:\.
Now any existing package I open, any package I create new, and import an existing package within the tool, as well create new by export out of production, I get a series of errors about the Connection Manager and Attunity/Teradata, etc which I expect, HOWEVER, I can’t open or display the contents/design of a package.
The first main error I get, and the following errors are:
“Microsoft Visual Studio is unable to load this document: Object reference not set to an instance of an object.”
Then followed by 15 errors all complaining about a missing component of Attunity and Teradata, etc…
I was able to try and create a Connection Manager, however MSTERA is not in the list, as it once was with VS15.
Please let me know what other additional details I can share to help resolve.
Thank you
October 18, 2018 at 5:37 pm
Update, thinking that maybe I needed to degrade the VS17 to VS15 for perhaps a compatibility, well, TLDR, its not different...
I left VS17Pro and its SSDT 15 in place, and installed VS2015Pro and SSDT 14, and tried to open an existing package, and I'm getting the same exact error previously mentioned as I do in VS17. I can open a package as long as a connection manager is not used in its design, but cant if a package uses a connection manager in it, and I presume one that uses the Attunity/Teradata (MSTERA). I try to create a new connection manger in VS15, and just like in VS17, it can't see MSTERA in the long listing of connections. I reinstalled both Attunity 32 and 64 bit connectors, didn't make any difference.On the package with a connection manager that has (had) MSTERA, these is the string of errors it complains about various incantations of Teradata and Attunity and MSTERA not there, not found ,etc, let me know if I need to post that.
October 18, 2018 at 8:50 pm
I've now installed Attunity 5, and made progress, but still not out of the woods. I can now open the package that has a connection manager in use in the design. However, the connection manager still has issues, though I can see the MSTERA in the list, which is good news. The latest error I get now when in the conn man and I run a test:
"Error at Load SQL Daily CRU Facts [Connection manager "Teradata Connector 1"]: Failed to establish an ODBC connection with the database server. Verify that the Teradata ODBC Driver for Windows x86 is installed properly. SqlState = IM002 Message = [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
I have gone to both ODBC 32 and 64 and I have the TD driver in there, on the driver tab, even got it set with User, File, and DSN on both as well.
What am I missing?
October 19, 2018 at 7:29 am
In trying to set target server version: 2016, Run64bitRuntime : false, (In VS17, and in VS15) I went into the package, went to Debug folder, traced to Load ProjectName Properties, and in the dialog box, in Configuration properties, on Debugging, I see Run64BitRunTime set to True/False. It was set to True, and I set to False, and apply. It seems to make no difference, as I then go to edit or even create a new connection manager, selecting MSTERA, and then try to test, and I still get the same error message (when set for 64 or 32 in debug) and its this:
"Failed to establish an ODBC connection with the database server. Verify that the Teradata ODBC Driver for Windows x86 is installed properly. SqlState = IM002 Message = [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
January 29, 2019 at 8:45 pm
quinn.jay - Friday, October 19, 2018 7:29 AMIn trying to set target server version: 2016, Run64bitRuntime : false, (In VS17, and in VS15) I went into the package, went to Debug folder, traced to Load ProjectName Properties, and in the dialog box, in Configuration properties, on Debugging, I see Run64BitRunTime set to True/False. It was set to True, and I set to False, and apply. It seems to make no difference, as I then go to edit or even create a new connection manager, selecting MSTERA, and then try to test, and I still get the same error message (when set for 64 or 32 in debug) and its this:"Failed to establish an ODBC connection with the database server. Verify that the Teradata ODBC Driver for Windows x86 is installed properly. SqlState = IM002 Message = [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
Hi Jay,
I'm having the same exact issue... have you find any resolution for this?
Any help is greatly appreciated.
Thanks
January 30, 2019 at 7:11 am
I just encountered the same exact issue. A standard ODBC connector works fine in SSIS. Attunity Teradata Connector 5.0 in VS2015 does not.
January 30, 2019 at 7:38 am
shivak626 - Tuesday, January 29, 2019 8:45 PMquinn.jay - Friday, October 19, 2018 7:29 AMIn trying to set target server version: 2016, Run64bitRuntime : false, (In VS17, and in VS15) I went into the package, went to Debug folder, traced to Load ProjectName Properties, and in the dialog box, in Configuration properties, on Debugging, I see Run64BitRunTime set to True/False. It was set to True, and I set to False, and apply. It seems to make no difference, as I then go to edit or even create a new connection manager, selecting MSTERA, and then try to test, and I still get the same error message (when set for 64 or 32 in debug) and its this:"Failed to establish an ODBC connection with the database server. Verify that the Teradata ODBC Driver for Windows x86 is installed properly. SqlState = IM002 Message = [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
Hi Jay,
I'm having the same exact issue... have you find any resolution for this?
Any help is greatly appreciated.
Thanks
Yes, I removed VS2017, installed VS2015Community, removed both Attunity v 4 and 5, and went with ODBC for source and destination for Teradata. VS2017 is incompatible for SSAS on a SQL Server 2016 platform. Also, there is confusion for Attunity v 4 and 5 with the Teradata Driver and TTU of 1v 6.2 and interfacing with the connection manager of VS15 and VS17, hence, why I ripped it all out and went with generic ODBC. What a complete nightmare.
January 30, 2019 at 7:45 am
quinn.jay - Wednesday, January 30, 2019 7:38 AMshivak626 - Tuesday, January 29, 2019 8:45 PMquinn.jay - Friday, October 19, 2018 7:29 AMIn trying to set target server version: 2016, Run64bitRuntime : false, (In VS17, and in VS15) I went into the package, went to Debug folder, traced to Load ProjectName Properties, and in the dialog box, in Configuration properties, on Debugging, I see Run64BitRunTime set to True/False. It was set to True, and I set to False, and apply. It seems to make no difference, as I then go to edit or even create a new connection manager, selecting MSTERA, and then try to test, and I still get the same error message (when set for 64 or 32 in debug) and its this:"Failed to establish an ODBC connection with the database server. Verify that the Teradata ODBC Driver for Windows x86 is installed properly. SqlState = IM002 Message = [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
Hi Jay,
I'm having the same exact issue... have you find any resolution for this?
Any help is greatly appreciated.
Thanks
Yes, I removed VS2017, installed VS2015Community, removed both Attunity v 4 and 5, and went with ODBC for source and destination for Teradata. VS2017 is incompatible for SSAS on a SQL Server 2016 platform. Also, there is confusion for Attunity v 4 and 5 with the Teradata Driver and TTU of 1v 6.2 and interfacing with the connection manager of VS15 and VS17, hence, why I ripped it all out and went with generic ODBC. What a complete nightmare.
Oh okay ....Thanks for the reply.
January 30, 2019 at 8:09 am
shivak626 - Wednesday, January 30, 2019 7:45 AMquinn.jay - Wednesday, January 30, 2019 7:38 AMshivak626 - Tuesday, January 29, 2019 8:45 PMquinn.jay - Friday, October 19, 2018 7:29 AMIn trying to set target server version: 2016, Run64bitRuntime : false, (In VS17, and in VS15) I went into the package, went to Debug folder, traced to Load ProjectName Properties, and in the dialog box, in Configuration properties, on Debugging, I see Run64BitRunTime set to True/False. It was set to True, and I set to False, and apply. It seems to make no difference, as I then go to edit or even create a new connection manager, selecting MSTERA, and then try to test, and I still get the same error message (when set for 64 or 32 in debug) and its this:"Failed to establish an ODBC connection with the database server. Verify that the Teradata ODBC Driver for Windows x86 is installed properly. SqlState = IM002 Message = [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified"
Hi Jay,
I'm having the same exact issue... have you find any resolution for this?
Any help is greatly appreciated.
Thanks
Yes, I removed VS2017, installed VS2015Community, removed both Attunity v 4 and 5, and went with ODBC for source and destination for Teradata. VS2017 is incompatible for SSAS on a SQL Server 2016 platform. Also, there is confusion for Attunity v 4 and 5 with the Teradata Driver and TTU of 1v 6.2 and interfacing with the connection manager of VS15 and VS17, hence, why I ripped it all out and went with generic ODBC. What a complete nightmare.
Oh okay ....Thanks for the reply.
I hope what I shared helps you and others. What various combos did you try to find that somethings don't work, or partially work? What's your SQL Server version, Data Warehouse brand/version, and DB driver versions, etc?
January 30, 2019 at 2:34 pm
I was actually able to resolve it by renaming the teradata ODBC driver from Teradata Database Driver 16.20 to just Teradata. Now having issues with not being able to get the schema in a Teradata source or destination component
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply