Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
SuperJB
Starting Member
12 Posts |
 Posted - 2013-06-05 : 04:35:13
|
Hello everyone,I've developed a SSIS package that reads info from a config file. In BIDS 2008 it works like a charm. I then created a SQL Job that invokes this job and uses that config file during execution.I have developed several other SSIS Packages, deployed them to the same SSIS Server, created the new SQL Job on a server where other SQL Jobs are already running, put the config file in the exact same folder where other config files are, set the SQL Job to run as the same owner as the other SQL Jobs and configured the Step (there is only one step in the SQL Job) to run as the same proxy account as all the other steps in the SQL Jobs... but every time I run the SQL Job, I get the following error:"DTExec: Could not import the configuration file BlaBlaBla.dtsConfig"I understand the error is 99% due to some permission issue, but, given that everything is configured the same way as other SQL Jobs that are running, do you see anything else I may be missing?Thanks in advance,SuperJB  |
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2013-06-05 : 04:48:26
|
| was the file in the same folder path in local machine too? if not did you repoint it to point to correct location in server?Or are you using indirect configuration method?------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/https://www.facebook.com/VmBlogs |
 |
|
|
SuperJB
Starting Member
12 Posts |
Posted - 2013-06-05 : 04:52:31
|
| Hi Visakh,All SSIS Packages are deployed on a SSIS Server - Server A.The SQL Job was created on another server - Server B.The config file is stored in Server B as well.The reason I'm going crazy with is that I've gone over every single step over and over... there are 3 other SQL Jobs setup on Server B configured exactly the same way (all use config files as well).SuperJB |
|
|
|
visakh16
Very Important crosS Applying yaK Herder
52326 Posts |
Posted - 2013-06-05 : 04:55:05
|
| but my question was whether the file path was same when you created package locally? if not, did you repoint it to correct location in ServerB after deploying it in ServerA? unless you do that it wont be able to fetch itALternatively you could use Indirect configuration method to pass path through a environment variable or through registry entry------------------------------------------------------------------------------------------------------SQL Server MVPhttp://visakhm.blogspot.com/https://www.facebook.com/VmBlogs |
|
|
|
SuperJB
Starting Member
12 Posts |
Posted - 2013-06-06 : 05:44:40
|
| Hi everyone,I finally sorted out the problem. Got thank BIDS 2008 for not working properly :-/So I had a local variable on the package setup as a string. On the config file, this same variable was setup as a int32 (totally my fault, must have been a stupid copy paste I did).But, BIDS2008 gave me absolutely NO WARNING, NO ERROR and the package ran perfectly on my local machine via BIDS.When deploying to the SSIS Server and trying to run the package with that config file, SQL Server looks at the config file, sees a variable typed as int32 with a string value and gives the error:"DTExec: Could not import the configuration file" Thanks to anyone who replied to this!SuperJB |
|
|
|
|
|
|
|
|
DTExec: Could not import the configuration file