January 6, 2015 at 9:53 am
Hi
We use a 'generic' datafeed that uses a SSIS package on a Central Management server (cms), which then targets individual servers where the dtsconfig files sit for each individual client. This was working fine, then we had a developer who edited the main 'generic' feed from the Central Management server for a new client (this work was carried out on his local machine), and I then uploaded the package to the CMS once he had finished. Everything at that point seemed to work - the datafeeds all completed.
Now we have added a new client server, the developers provided the new dtsconfig for that server. I created a job on the cms that targets the new server, and it uses the generic datafeed that all the other jobs use.
This new job keeps failing, with a message that references c:\foldername does not exist. All the configs point to the network drive 'S' and not 'C'
When I open the generic datafeed file on my local laptop I get the same error - ie c:\foldername does not exist and the package seems to have references to the work the developer carried out previously (ie the client names he was working on at the time seem to be in there).
Its appears the new server we have added does not let the dtsconfig file enter its values at run time ?
My knowledge of SSIS is very limited so apologies if i'm going into too much detail (or not enough)
Any ideas greatly received !!
January 6, 2015 at 9:59 am
What is the command line from the job step that runs the package?
John
January 6, 2015 at 10:18 am
So when I click on the properties of the job, then click on the Steps menu I see the Job step list.
There is 1 step in here. When i click on 'Edit' it opens the Job step Properties. In there i can see some tabs, General which shows the package path (which points to the msdb\datafeed\datafeedGenric), Configurations which points to the S drive dtsconfig file (the job targets the individual client server which we have just added), Command files (empty), Data Sources (which now has info from where the developer edited the package). The other tabs have nothing in them and then finally Command Line tab (is this what you mean ????) has the following:
/DTS "\MSDB\DataFeeds\DatafeedGeneric" /SERVER "cmsServer" /CONFIGFILE "S:\ssis\datafeeds\NewClientName\ConfigurationFiles\Live_NewClientName.dtsConfig" /CHECKPOINTING OFF /REPORTING E
January 6, 2015 at 10:42 am
Sounds like the dev might have hard-coded something into the package which is not being overridden by the config.
I'd spend a few minutes editing the package to see whether you can track this down.
January 6, 2015 at 2:42 pm
Check the package configurations inside the package as well (right-click on the control flow to get the context menu) and see if there are any configurations pointing to the C: drive.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
January 6, 2015 at 4:10 pm
Hi thanks for all the replies.
I was trawling through the internet and found something the same as the last post.
When I right click in control flow area and select 'Package Configurations' the window that opens has a tick in the 'Enable package configurations' and in the configurations there is an xml config type, with a configuration string of C:\stuff\datafeed\clientname dev was previoulsy working on\test_client name.dtsConfig
This seems to match what your are saying Koen. I'll try unticking it and upload the package again. Will do this tomorrow and get back to you.
Thanks
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply