May 12, 2017 at 3:53 pm
Posted this under DTS by mistake. Hopefully this is the right place>
I have an Integration Services Project that uses two connections to transfer data from a cloud database to a local SQL Server database. The Cloud database uses a 32 bit ODBC Driver which has been set up using the 32 bit ODBC setup program. I also set up a 32 bit ODBC data source for the local SQL database. My Project runs fine in VS 2015. If I try to execute the .dtsx file using dtexec (verifying that I am running the 32 bit version of DTExec), it fails with the following:
Microsoft (R) SQL Server Execute Package Utility
Version 13.0.1601.5 for 32-bit
Copyright (C) 2016 Microsoft. All rights reserved.
Started: 2:31:59 PM
Error: 2017-05-12 14:31:59.26
Code: 0xC0010018
Source: Package
Description: Error loading value "<DTS:ConnectionManagers xmlns:DTS="www.microsoft.com/SqlServer/Dts"><DTS:ConnectionManager DTS:refId="Package.ConnectionManagers[VisionReportingData]"
DTS:CreationName="ODBC" DTS:DTSID="{0B7F485E-9C4C-4BC4-8D01-6903FC20BF74}" DTS:ObjectName="VisionReportin" from node "DTS:ConnectionManagers".
End Error
Could not load package "package.dtsx" because of error 0xC0010014.
Description: The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors.
This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails.
Source: Package
Started: 2:31:59 PM
Finished: 2:31:59 PM
Elapsed: 0.219 seconds
The connection it complains about is the SQL Server ODBC connection. It may have a problem with the cloud one, but just reports this on first. The "ObjectName" is cut off in the error message.
The version of DTEXEC I am using is from the ...\130\Binn Folder of SQl Server. There is no dtexec.exe in the 140\Binn folder.
I have moved the porgram to another machine with VS 2015 and SSIS for VS 2015 and it behaves execatly the same way.
Any help/ideas would be appreciated.
PS. The smiley faces are colons on the screen. No idea why they converted to them when pasted.
May 15, 2017 at 2:54 pm
Sue
May 15, 2017 at 6:22 pm
Hi Sue,
Thanks for your reply.
I already checked that and it didn't seem to make any difference. I'm installing VS2015 update 3 to see if that will halp.
May 16, 2017 at 11:13 am
As a thought - was the dtsx file originally created in Visual Studio 2015 with the BI development tools for 2016? If not, it may be set to run in some other version of SQL. I think you will want to use the dtexec that matches the version that the dtsx is set to run as.
I had a similar issue related to doing forced updating but mine was a little different. I tried to open a dtsx with visual studio 2012 after exporting the dtsx using SSMS 2016 and I got a very similar error message.
As for the error message getting cut of, if memory serves, you can view the full error in the event log of the system (I could be wrong, but pretty sure it logs it there by default).
Looking at that SSIS for VS 2015, I am wondering about the default version it sets things to. I am half expecting that it will set it to be compatible with SQL 2017 (aka vNext aka SQL version 14) and not with SQL 2016? If you open your dtsx file in notepad (or equivalent), what does the property "LastModifiedProductVersion" in the <DTS:Executeable> tag look like? Does it say 13.something.something.something or does it say 14? If it is 14, you will need to change your DTSX inside visual studio to compile for SQL 2016 (or older).
EDIT: Don't try changing that value from within notepad mind you as that'll create more headache for you. Do it inside visual studio.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply