January 17, 2018 at 11:28 am
Hello everyone, this is my first post here so forgive me if doesn't fit all best practices.
I have migrated a SQL Server 2008 environment to SQL Server 2016. Used SSDT to migrate all the DTS and they're all running fine.
My problem is when I try to run those DTS packages from a Job.
I'm using the Protection Level as "EncryptSensitiveWithPassword", and here the error message I get:
Executed as user: Domain\User. Microsoft (R) SQL Server Execute Package Utility Version 13.0.1601.5 for 64-bit Copyright (C) 2016 Microsoft. All rights reserved. Started: 9:49:31 AM Error: 2018-01-17 09:49:31.54 Code: 0xC0010018 Source: DTS_NAME Description: Error loading value "<DTS:ConnectionManagers xmlns: DTS="www.microsoft.com/SqlServer/Dts"><DTS:ConnectionManager DTS:refId="Package.ConnectionManagers[INSTANCE\DATABASE.user]" DTS:CreationName="OLEDB" DTS: DTSID="{F6600160-C69F-4598-AA2E-1BF86" from node "DTS:ConnectionManagers". End Error Could not load package "\\SharedFolder\DTS_NAME.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: DTS_NAME Started: 9:49:31 AM Finished: 9:49:31 AM Elapsed: 0.063 seconds. The package could not be loaded. The step failed.
And from the Event Viewer->Windows Logs->System, this is the error message:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{2DC39BD2-9CFF-405D-A2FE-D246C976278C}
and APPID
{DB336D8E-32E5-42B9-B14B-58AAA87CEB06}
to the user Domain\User SID (S-1-5-21-1412644136-1311432621-2749495289-3095) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.
This is from the Job being executed in SSMS 17. But here's something interesting, if I change the Protection Level to "EncryptSensitiveWithUserKey" the Job executes with success.
Here's what I have tried to do to solve this, without success:
Every help is very welcome.
January 17, 2018 at 1:58 pm
Check that the 'Executed as user: Domain\User' has access to the share "\\SharedFolder\DTS_NAME.dtsx".
January 17, 2018 at 2:01 pm
Note that it's been called SSIS, not DTS, since 2005.
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 17, 2018 at 2:03 pm
Standard practice is to use Don't Save Sensitive and then use SSISDB environment variables to pass sensitive parameter values.
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 18, 2018 at 7:14 am
Evgeny Garaev - Wednesday, January 17, 2018 1:58 PMCheck that the 'Executed as user: Domain\User' has access to the share "\\SharedFolder\DTS_NAME.dtsx".
Thanks for the help. But the user has access to the shared folder.
January 18, 2018 at 7:34 am
Sorry for that, should have called them SSIS packages.
Phil Parkin - Wednesday, January 17, 2018 2:03 PMStandard practice is to use Don't Save Sensitive and then use SSISDB environment variables to pass sensitive parameter values.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply