July 23, 2012 at 2:12 am
You still can use the same method, but you need to disable package configurations and rely solely on the configurations specified in the SQL Agent jobs.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 23, 2012 at 2:35 am
Sorry, disable package configurations? If I did this the package won't pick up any configurations I put in the configurations tab of the SQL Agent Job will it? Or do you mean, do as I did earlier in this post and leave "Enable package configurations" ticked in BIDS for the package but remove any configuration files in the package configuration window, putting whichever configuration file I want in to relevant SQL Agent Job's configuration window? Or are you referring to the Set Values tab in the SQL Agent Job? If the last one, I have around 80 of these variables so will be difficult to maintain.
Is there an alternative to what I've done here then out of interest? If so, I'll try and apply that with my next SSIS package. Probably gone too far with these for now if removing the package's attached configuration file will work.
July 23, 2012 at 3:13 am
I'm not 100% sure, but I don't think the checkbox for Enable Package Configurations needs to ticked in order to specify a config file in a job. I'll have to test it out sometime. If it is required, just select it but don't configure a configuration.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
July 23, 2012 at 5:24 am
That's great. THanks for your help here. Think I'll leave it in there to create the initial configuration file so it creates one that I can copy and amend to variations of the config, then re-deploy the package with that file removed.
I must admit, it does seem a crazy change by Microsoft this as it's designed to assist with dev v production environments ok, but has a horrible detrimental affect to packages that need to be run differently in the same environment, like in my instance. Yuk!
September 23, 2013 at 3:22 am
I have a XML config file just with one variable,
<?xml version="1.0"?>
<DTSConfiguration>
<DTSConfigurationHeading>
<DTSConfigurationFileInfo GeneratedBy="WARBABANK\parmeshwari.kumar" GeneratedFromPackageName="TestConfig" GeneratedFromPackageID="{28DFF61A-A509-4404-956D-9B2704C55848}" GeneratedDate="9/23/2013 11:02:21 AM"/>
</DTSConfigurationHeading>
<Configuration ConfiguredType="Property" Path="\Package.Variables[User::remotePath].Properties[Value]" ValueType="String">
<ConfiguredValue>HI Who are you?</ConfiguredValue>
</Configuration>
</DTSConfiguration>
I just added a SSIS with script task that will display messagebox with this value.
This runs in SSIS as package , but when I run this as job, this gives me "Exception has been thrown by the target of an invocation."
I had added this file under Configuration tab and executed. But this always gives me this error
Can you please help me to find this solution asap?
What package level protection we need to add?
Do we have to import package or we can use it from FileSystem ? (both way I tried)
expecting help
September 23, 2013 at 12:22 pm
Does the SQL Server Agent account have the right permissions to access the configuration file?
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
October 15, 2014 at 7:44 am
Hi,
I have the same problem.. when I moved the package from my local to Test server and specified the job to look at the XML configuration it is still try to connect to the connections that are locally mentioned in the package.
I am stuck here... I even removed the configurations from my package as mentioned earlier and depending on the xml config that is mentioned in SQL server job my job fails.
Can you please help me.
October 15, 2014 at 8:13 am
param_urpal (9/23/2013)
....expecting help
Maybe you should ask for help rather than expecting it!
October 15, 2014 at 1:21 pm
ranimsql (10/15/2014)
Hi,I have the same problem.. when I moved the package from my local to Test server and specified the job to look at the XML configuration it is still try to connect to the connections that are locally mentioned in the package.
I am stuck here... I even removed the configurations from my package as mentioned earlier and depending on the xml config that is mentioned in SQL server job my job fails.
Can you please help me.
Check the log and see if there are any configuration warnings.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
Viewing 9 posts - 16 through 23 (of 23 total)
You must be logged in to reply to this topic. Login to reply