August 5, 2013 at 10:15 am
I have a master package that calls 10 child packages. I deployed the packages on sql server msdb database. From msdb if I am running the master package, then corresponding all the child packages are getting executed.
But when I am creating a Job where I am adding only the master package as the Step then I am getting error.
I tried creating job for single child package, it worked fine. But for the master package the job is failing.
Can anyone please help me out of this situation.....
Thanks
Rahul Sahay
August 5, 2013 at 2:26 pm
It might be useful if you posted the error.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 5, 2013 at 10:19 pm
is ur pkg stored in msdb or file system? are your pkgs connecting to external rdbms?
Im calling 15 child pkg from the master pkg stored on a file system no issues
It's better to fail while trying, rather than fail without trying!!!
August 5, 2013 at 10:49 pm
must be some permission issue with the execution account that agent job is running, did u tried with the file system ,plz post the error
August 6, 2013 at 12:31 am
the packages are deployed to the sqlserver ie msdb. so when I a running the master package from msdb it is working fine.
now when I am scheduling the master package in sqlserver agent I a getting error message:
"
Date,Source,Severity,Step ID,Server,Job Name,Step Name,Notifications,Message,Duration,Sql Severity,Sql Message ID,Operator Emailed,Operator Net sent,Operator Paged,Retries Attempted
08/06/2013 02:06:14,BlsToTls,Error,0,SQLHQ1,BlsToTls,(Job outcome),,The job failed. The Job was invoked by User STONEWOOD\rsahay. The last step to run was step 1 (Master Calling Child).,00:00:02,0,0,,,,0
08/06/2013 02:06:14,BlsToTls,Error,1,SQLHQ1,BlsToTls,Master Calling Child,,Executed as user: SQLHQ1\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 10.50.4000.0 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 2:06:14 AM Error: 2013-08-06 02:06:16.10 Code: 0xC00220E8 Source: Legal Entity Description: Error 0x80070003. Unable to access the package file<c/> "C:\Packages\BLStoTLSTransfer\BLStoTLSTransfer\pkgTLSLegalEntity.dtsx". Make sure the file exists and you have permission to access it. End Error Error: 2013-08-06 02:06:16.10 Code: 0xC00220DE Source: Legal Entity Description: Error 0x80070003 while loading package file "C:\Packages\BLStoTLSTransfer\BLStoTLSTransfer\pkgTLSLegalEntity.dtsx". The system cannot find the path specified. . End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 2:06:14 AM Finished: 2:06:16 AM Elapsed: 1.25 seconds. The package execution failed. The step failed.,00:00:02,0,0,,,,0
"
Thanks
Rahul Sahay
August 6, 2013 at 12:42 am
You said the packages are deployed to the MSDB, but the master package is still trying to locate packages on the C: drive. You need to update your execute package task with the correct location of your packages.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 6, 2013 at 12:57 am
when running the master package from msdb then the master package is picking all the child packages from sysssispackages tables in msdb.
But when trying to run from sqlserver agent it is referring the file system. is there a way by which I can configure this at runtime?
August 6, 2013 at 1:09 am
rahulsahay123 (8/6/2013)
when running the master package from msdb then the master package is picking all the child packages from sysssispackages tables in msdb.But when trying to run from sqlserver agent it is referring the file system. is there a way by which I can configure this at runtime?
If you run the package manually from MSDB, it runs on your computer, not on the server. That's why you don't get an error, because it can find the packages on your C: drive.
For more info, check out this blog post: Where is my SSIS package executed?
You can change the packages at runtime by using package configurations.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 6, 2013 at 1:27 am
From your job on that pkg, check the properties of the "Data Sources" then the Connection String
see attached pic
It's better to fail while trying, rather than fail without trying!!!
August 6, 2013 at 1:27 am
so you mean to say that I should store the package path in a sqlserver table. then I should use foreach container and declare a variable say v_package of type object and should loop the table to get the package path. is that correct?
but in my case I require the packages to be executed in a particular sequence. that's why I am using execute package task for each packages and picking the package location from file system which happens to be the connection manager for each package.
Can you please suggest if I can do anything different here in order to run the master package from sqlserver agent?
Thanks
August 6, 2013 at 1:38 am
rahulsahay123 (8/6/2013)
so you mean to say that I should store the package path in a sqlserver table. then I should use foreach container and declare a variable say v_package of type object and should loop the table to get the package path. is that correct?but in my case I require the packages to be executed in a particular sequence. that's why I am using execute package task for each packages and picking the package location from file system which happens to be the connection manager for each package.
Can you please suggest if I can do anything different here in order to run the master package from sqlserver agent?
Thanks
No, that's not what I am saying. You have two options: store the location of each child package in a SQL Server configuration table and then use package configurations to update those. So you need to create a table like that on every environment.
Or just store the connectionstring to the MSDB database, configure your execute package tasks to look for the packages in the MSDB database (even when you are developing in BIDS) and then simply configure the MSDB connection string.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
August 6, 2013 at 1:41 am
if I am checking the datasource from there then the packages path will be hardcoded. at the time of deployment only manifest file is transferred. is here a way by which I can change this location at runtime. that means since I am deploying all the packages to sqlserver msdb database so when I am running the master package from sqlserver agent it points to msdb database and run the child packages?
Thanks
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply