January 9, 2009 at 12:15 am
I have a SSIS package that uses dtsConfig files. When I deploy the package using the Package Installation Wizard, it appears to create these dtsConfig files on my PC, rather than the server. I can run the package with no problems through Integration Services. However, when I create a job with the SQL Server Agent and then try to run the SSIS package, the job fails with the following message:
Executed as user: HNEAHS\srv_appdevsql. ...00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 6:03:28 PM Warning: 2009-01-09 18:03:28.66 Code: 0x80012012 Source: ssisMidgard_Load Description: The configuration file name "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\solnMIDGARD\ssisMidgard_Load_sqlMidgard.dtsConfig" is not valid. Check the configuration file name. End Warning Warning: 2009-01-09 18:03:28.66 Code: 0x80012012 Source: ssisMidgard_Load Description: The configuration file name "C:\Program Files\Microsoft SQL Server\90\DTS\Packages\solnMIDGARD\ssisMidgard_Load_CodeFiles.dtsConfig" is not valid. Check the configuration file name. End Warning Warning: 2009-01-09 18:03:28.66 Code: 0x80012059 Source: ssisMidgard_Load Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to... The package execution fa... The step failed.
The package has a protection level of EncryptSensitiveWithPassword.
January 9, 2009 at 12:36 am
This is happening because when you run the package from SQL Agent job it runs on the server and not your local machine; And the config file is not present on the server.
You need to copy the config file at same location as your local.
-Vikas Bindra
January 21, 2009 at 8:43 am
I am also getting same error message. Verified, Config file is available on server at below highlighted path. Since I have executed this package on server using BIDS so config file is available at that path also.
Executed as user: XXXXXXXX\srv_sql. ...00.4035.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 10:23:33 AM Warning: 2009-01-21 10:24:34.62 Code: 0x80012012 Source: pkg_security_master Description: The configuration file name "d:\Program Files\Microsoft SQL Server (x86)\90\DTS\Packages\PRJ_CDW_MASTERS\prod_security_master_config.dtsConfig" is not valid. Check the configuration file name. End Warning Warning: 2009-01-21 10:24:34.62 Code: 0x80012059 Source: pkg_security_master Description: Failed to load at least one of the configuration entries for the package. Check configurations entries and previous warnings to see descriptions of which configuration failed. End Warning Progress: 2009-01-21 10:24:34.67 Source: security_master table Validating: 0% complete End Progress Progress: 2009-01-21 10:24:34.67 Source: security_master table Validating: 33% complete End Pro... The package execution fa... The step failed.
January 21, 2009 at 2:05 pm
If you are trying to run this package as job make sure that the SQL Server Agent has permission the folder where the config file is present. This is Jobs run under SQL Server Agent account and not your security context.
To check log on to the server using the SQL Server Agent account and try to access the config file.
HTH
~Mukti
January 21, 2009 at 3:44 pm
I copied the files to the server, and I found I need to specify the configuration files in the Job Task as well. If you go into the step that runs the SSIS package, you'll see a tab called "Configurations." If you specify the configuration files in there as well, you should be OK (I had other issues dealing with security to contend with as well :angry:).
I guess this is because the SQL Server Agent is part of the Database Engine, not Integration Services. Or it could just be Microsoft.
July 23, 2010 at 3:19 am
Hi,
I create portable ssis package using .dtsconfig file for database connections and variables. I use single .dtsconfig file for single SSIS project and my project contain number of .dtsx files with variables. When I add single .dtsconfig file in package configurations of each .dtsx file its work/run fine. But when I run it using SQL Server Agent Job with same .dtsconfig file to make package zero deployment, it gives error like ‘DTExec: Could not import the configuration file \\ccr7\Tech\InvestToolsDataFromccr10\SSiSDB03\SSiSRun2k8\UDL\IS1046-47 Trace-PutCall.dtsConfig.’ because particular .dtsx files contain only 3 variables out of 6 which are in .dtsconfig file. But when I create separate .dtsconfig file with only 3 variables which used in that particular .dtsx file then job work without error.
So please help me how to use single .dtsconfig file which contain all variable to avoid create multiple .dtsconfig files?
Thanks
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply