January 19, 2017 at 3:20 pm
Hello, I hope some one can help explain and that it is an easy fix. Earlier today I was in an SSIS package, it has two different data connections to connect to Teradata, one uses ODBC and the Teradata connection info, and the other uses Affinity. I had an issue earlier, but a reboot solved, and there were no issues with packages or cubes.
Now when I open a SSIS package, I get errors and a message says its the package is corrupt. I try to make a new one with the wizard to build off the production one, and I get the same issue, and I get this same error message if I open any of my packages.
The error is:
Error 1 Error loading Load SQL SDyF.dtsx: The connection type "MSTERA" specified for connection manager "Teradata Connector 1" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name. C:\~\Load SQL SDyF.dtsx 1 1
I recall seeing this MSTERA name, I must have inadvertently left it on that when existing the package so I presume. This connector is used all throughout all my SSIS packages.
How can I get the connector changed correctly so when I open the package it wont read this wrong info and give the corrupt message again?
Many thanks,
JPQ
January 19, 2017 at 5:11 pm
quinn.jay - Thursday, January 19, 2017 3:20 PMHello, I hope some one can help explain and that it is an easy fix. Earlier today I was in an SSIS package, it has two different data connections to connect to Teradata, one uses ODBC and the Teradata connection info, and the other uses Affinity. I had an issue earlier, but a reboot solved, and there were no issues with packages or cubes.Now when I open a SSIS package, I get errors and a message says its the package is corrupt. I try to make a new one with the wizard to build off the production one, and I get the same issue, and I get this same error message if I open any of my packages.
The error is:
Error 1 Error loading Load SQL SDyF.dtsx: The connection type "MSTERA" specified for connection manager "Teradata Connector 1" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name. C:\~\Load SQL SDyF.dtsx 1 1I recall seeing this MSTERA name, I must have inadvertently left it on that when existing the package so I presume. This connector is used all throughout all my SSIS packages.
How can I get the connector changed correctly so when I open the package it wont read this wrong info and give the corrupt message again?
Many thanks,
JPQ
Do you know what it should be? You could always try text-editing the package XML (keep a 'before' copy though!)
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
January 19, 2017 at 6:19 pm
Phil Parkin - Thursday, January 19, 2017 5:11 PMquinn.jay - Thursday, January 19, 2017 3:20 PMHello, I hope some one can help explain and that it is an easy fix. Earlier today I was in an SSIS package, it has two different data connections to connect to Teradata, one uses ODBC and the Teradata connection info, and the other uses Affinity. I had an issue earlier, but a reboot solved, and there were no issues with packages or cubes.Now when I open a SSIS package, I get errors and a message says its the package is corrupt. I try to make a new one with the wizard to build off the production one, and I get the same issue, and I get this same error message if I open any of my packages.
The error is:
Error 1 Error loading Load SQL SDyF.dtsx: The connection type "MSTERA" specified for connection manager "Teradata Connector 1" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name. C:\~\Load SQL SDyF.dtsx 1 1I recall seeing this MSTERA name, I must have inadvertently left it on that when existing the package so I presume. This connector is used all throughout all my SSIS packages.
How can I get the connector changed correctly so when I open the package it wont read this wrong info and give the corrupt message again?
Many thanks,
JPQDo you know what it should be? You could always try text-editing the package XML (keep a 'before' copy though!)
No exactly, as all the connectors in the SSIS package are now completely gone.
I can find them in the SSDE Jobs area, by going to a package, and looking at the props and config, etc. and get the data that way.
I've never tried to text edit the XML, it seems to be a very unforgiving messy place, and I'm unsure about properly finding anything to edit.
January 19, 2017 at 6:37 pm
quinn.jay - Thursday, January 19, 2017 6:19 PMPhil Parkin - Thursday, January 19, 2017 5:11 PMquinn.jay - Thursday, January 19, 2017 3:20 PMHello, I hope some one can help explain and that it is an easy fix. Earlier today I was in an SSIS package, it has two different data connections to connect to Teradata, one uses ODBC and the Teradata connection info, and the other uses Affinity. I had an issue earlier, but a reboot solved, and there were no issues with packages or cubes.Now when I open a SSIS package, I get errors and a message says its the package is corrupt. I try to make a new one with the wizard to build off the production one, and I get the same issue, and I get this same error message if I open any of my packages.
The error is:
Error 1 Error loading Load SQL SDyF.dtsx: The connection type "MSTERA" specified for connection manager "Teradata Connector 1" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name. C:\~\Load SQL SDyF.dtsx 1 1I recall seeing this MSTERA name, I must have inadvertently left it on that when existing the package so I presume. This connector is used all throughout all my SSIS packages.
How can I get the connector changed correctly so when I open the package it wont read this wrong info and give the corrupt message again?
Many thanks,
JPQDo you know what it should be? You could always try text-editing the package XML (keep a 'before' copy though!)
No exactly, as all the connectors in the SSIS package are now completely gone.
I can find them in the SSDE Jobs area, by going to a package, and looking at the props and config, etc. and get the data that way.
I've never tried to text edit the XML, it seems to be a very unforgiving messy place, and I'm unsure about properly finding anything to edit.
Just a quick question: do you have the Teradata driver installed on the machine where you are trying to open the package?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
January 19, 2017 at 7:01 pm
Phil Parkin - Thursday, January 19, 2017 6:37 PMquinn.jay - Thursday, January 19, 2017 6:19 PMPhil Parkin - Thursday, January 19, 2017 5:11 PMquinn.jay - Thursday, January 19, 2017 3:20 PMHello, I hope some one can help explain and that it is an easy fix. Earlier today I was in an SSIS package, it has two different data connections to connect to Teradata, one uses ODBC and the Teradata connection info, and the other uses Affinity. I had an issue earlier, but a reboot solved, and there were no issues with packages or cubes.Now when I open a SSIS package, I get errors and a message says its the package is corrupt. I try to make a new one with the wizard to build off the production one, and I get the same issue, and I get this same error message if I open any of my packages.
The error is:
Error 1 Error loading Load SQL SDyF.dtsx: The connection type "MSTERA" specified for connection manager "Teradata Connector 1" is not recognized as a valid connection manager type. This error is returned when an attempt is made to create a connection manager for an unknown connection type. Check the spelling in the connection type name. C:\~\Load SQL SDyF.dtsx 1 1I recall seeing this MSTERA name, I must have inadvertently left it on that when existing the package so I presume. This connector is used all throughout all my SSIS packages.
How can I get the connector changed correctly so when I open the package it wont read this wrong info and give the corrupt message again?
Many thanks,
JPQDo you know what it should be? You could always try text-editing the package XML (keep a 'before' copy though!)
No exactly, as all the connectors in the SSIS package are now completely gone.
I can find them in the SSDE Jobs area, by going to a package, and looking at the props and config, etc. and get the data that way.
I've never tried to text edit the XML, it seems to be a very unforgiving messy place, and I'm unsure about properly finding anything to edit.Just a quick question: do you have the Teradata driver installed on the machine where you are trying to open the package?
Yes, I'm RDP to the server, and using VS 2013 local to the server, and both the Teradata ODBC 32 bit driver and the Affinity Teradata 4.0 64 bit drivers are on the server. BTW, not only are the TD connectors not in the SSIS package when I open it, neither are any of the MS connectors.
January 20, 2017 at 5:29 am
quinn.jay - Thursday, January 19, 2017 7:01 PMYes, I'm RDP to the server, and using VS 2013 local to the server, and both the Teradata ODBC 32 bit driver and the Affinity Teradata 4.0 64 bit drivers are on the server. BTW, not only are the TD connectors not in the SSIS package when I open it, neither are any of the MS connectors.
Just checking ... are you editing the .sln, or the dtsx file?
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
January 20, 2017 at 8:16 am
Phil Parkin - Friday, January 20, 2017 5:29 AMquinn.jay - Thursday, January 19, 2017 7:01 PMYes, I'm RDP to the server, and using VS 2013 local to the server, and both the Teradata ODBC 32 bit driver and the Affinity Teradata 4.0 64 bit drivers are on the server. BTW, not only are the TD connectors not in the SSIS package when I open it, neither are any of the MS connectors.
Just checking ... are you editing the .sln, or the dtsx file?
Not yet, I have been exhausting every check and look into every possibility. I've deduced that the actual tool, in this case, VS 2013 Shell Integrated with SSDT is bad. I've back checked with using VS15 from a PC to connect to the server where the files are, and can call them up and see the connectors. So I'm able to determine that the .dtsx files are ok. Also, I have opened the .dtsx file in VS13 on the server, and can search the file and find all the references and connection details in the file. I've tried getting at the work files may different ways. Even ran a repair on the VS13 and it didn't help.
Thankfully the packages running as jobs in the server are fine, they run, and I can go in a couple of different ways and drill in and see the connectors. I plan to import from here on an as needed basis as a point of another go-to back-up if need be.
Now I'm going to make another backup of the works files on the server. Leave VS13 in place. Install VS15 and SSDT, and proceed from there in hopes that it too will behave as my PC local install of VS15, as in, reads the .dtsx files and the connector data within.
January 24, 2017 at 11:09 am
quinn.jay - Friday, January 20, 2017 8:16 AMPhil Parkin - Friday, January 20, 2017 5:29 AMquinn.jay - Thursday, January 19, 2017 7:01 PMYes, I'm RDP to the server, and using VS 2013 local to the server, and both the Teradata ODBC 32 bit driver and the Affinity Teradata 4.0 64 bit drivers are on the server. BTW, not only are the TD connectors not in the SSIS package when I open it, neither are any of the MS connectors.
Just checking ... are you editing the .sln, or the dtsx file?
Not yet, I have been exhausting every check and look into every possibility. I've deduced that the actual tool, in this case, VS 2013 Shell Integrated with SSDT is bad. I've back checked with using VS15 from a PC to connect to the server where the files are, and can call them up and see the connectors. So I'm able to determine that the .dtsx files are ok. Also, I have opened the .dtsx file in VS13 on the server, and can search the file and find all the references and connection details in the file. I've tried getting at the work files may different ways. Even ran a repair on the VS13 and it didn't help.
Thankfully the packages running as jobs in the server are fine, they run, and I can go in a couple of different ways and drill in and see the connectors. I plan to import from here on an as needed basis as a point of another go-to back-up if need be.
Now I'm going to make another backup of the works files on the server. Leave VS13 in place. Install VS15 and SSDT, and proceed from there in hopes that it too will behave as my PC local install of VS15, as in, reads the .dtsx files and the connector data within.
UPDATE: After much checking, resting and reparing, it was determined that vS13 was corrupt, not the packages. So I left it alone as is, and installed VS15 Community, and installed SSDT, and all is well now. Many thanks for all the help in resolving this issue.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply