|
|
You're in the
sql server dts
group:Business intel SQL2005 packages
sql server dts:
Hi
I have developed a very simple package which copys a set of rows from 1 db to another. all works fine in the VS2005 BI and also can run the package.dtx from the desktop. But when I add this package to the the Jobs to schedule it to run, it fails on the first step. No reason why - just step 1 failed. Any ideas why this package cannot run by sql jobs agent. All passwords are provided in the code, and package runs on that machine from the desktop.
Hello Martin,
Have you got any logging on in the package? It does sound as though there is a security permission here though or something is required that is user specific like maybe a drive mapping. Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com [quoted text, click to view] > Hi I have developed a very simple package which copys a set of rows > from 1 db to another. all works fine in the VS2005 BI and also can > run the package.dtx from the desktop. But when I add this package to > the the Jobs to schedule it to run, it fails on the first step. No > reason why - just step 1 failed. > > Any ideas why this package cannot run by sql jobs agent. All > passwords are provided in the code, and package runs on that machine > from the desktop. > > Thanks >
No, how do you do that? In the job ? rgds M [quoted text, click to view] "Allan Mitchell" wrote:
> Hello Martin, > > Have you got any logging on in the package? > > It does sound as though there is a security permission here though or something > is required that is user specific like maybe a drive mapping. > > Allan Mitchell > www.SQLDTS.com > www.SQLIS.com > www.Konesans.com > > > Hi I have developed a very simple package which copys a set of rows > > from 1 db to another. all works fine in the VS2005 BI and also can > > run the package.dtx from the desktop. But when I add this package to > > the the Jobs to schedule it to run, it fails on the first step. No > > reason why - just step 1 failed. > > > > Any ideas why this package cannot run by sql jobs agent. All > > passwords are provided in the code, and package runs on that machine > > from the desktop. > > > > Thanks > > > >
Hello Martin,
I would personally do it in the package itself so in Control Flow, go to the SSIS menu and choose logging. Here is what BOL says about job steps. "Every job step runs in a specific security context. If the job step specifies a proxy, the job step runs in the security context of the credential for the proxy. If a job step does not specify a proxy, the job step runs in the context of the SQL Server Agent service account. Only members of the sysadmin fixed server role can create jobs that do not explicitly specify a proxy. Because job steps run in the context of a specific Microsoft Windows user, that user must have the permissions and configuration necessary for the job step to execute. For example, if you create a job that requires a drive letter or a Universal Naming Convention (UNC) path, the job steps may run under your Microsoft Windows user account while testing the tasks. However, the Windows user for the job step must also have the necessary permissions, drive letter configurations, or access to the required drive. Otherwise, the job step fails. To prevent this problem, ensure that the proxy for each job step has the necessary permissions for the task that the job step performs" Also have a look here. http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com [quoted text, click to view] > No, how do you do that? In the job ? > > rgds > M > "Allan Mitchell" wrote: > >> Hello Martin, >> >> Have you got any logging on in the package? >> >> It does sound as though there is a security permission here though or >> something is required that is user specific like maybe a drive >> mapping. >> >> Allan Mitchell >> www.SQLDTS.com >> www.SQLIS.com >> www.Konesans.com >>> Hi I have developed a very simple package which copys a set of rows >>> from 1 db to another. all works fine in the VS2005 BI and also >>> can run the package.dtx from the desktop. But when I add this >>> package to the the Jobs to schedule it to run, it fails on the >>> first step. No reason why - just step 1 failed. >>> >>> Any ideas why this package cannot run by sql jobs agent. All >>> passwords are provided in the code, and package runs on that machine >>> from the desktop. >>> >>> Thanks >>>
Hi
Ok, I switched on Logging, and it writes to a text file on the c: it all works in the VS environment and from Commnadline. But not in SQL server. And when it runs in Sql server I get no log info either. Something strange going on, because other packages have worked previously. [quoted text, click to view] "Allan Mitchell" wrote:
> Hello Martin, > > I would personally do it in the package itself so in Control Flow, go to > the SSIS menu and choose logging. Here is what BOL says about job steps. > > "Every job step runs in a specific security context. If the job step specifies > a proxy, the job step runs in the security context of the credential for > the proxy. If a job step does not specify a proxy, the job step runs in the > context of the SQL Server Agent service account. Only members of the sysadmin > fixed server role can create jobs that do not explicitly specify a proxy. > > Because job steps run in the context of a specific Microsoft Windows user, > that user must have the permissions and configuration necessary for the job > step to execute. For example, if you create a job that requires a drive letter > or a Universal Naming Convention (UNC) path, the job steps may run under > your Microsoft Windows user account while testing the tasks. However, the > Windows user for the job step must also have the necessary permissions, drive > letter configurations, or access to the required drive. Otherwise, the job > step fails. To prevent this problem, ensure that the proxy for each job step > has the necessary permissions for the task that the job step performs" > > Also have a look here. > > > http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html > > > Allan Mitchell > www.SQLDTS.com > www.SQLIS.com > www.Konesans.com > > > No, how do you do that? In the job ? > > > > rgds > > M > > "Allan Mitchell" wrote: > > > >> Hello Martin, > >> > >> Have you got any logging on in the package? > >> > >> It does sound as though there is a security permission here though or > >> something is required that is user specific like maybe a drive > >> mapping. > >> > >> Allan Mitchell > >> www.SQLDTS.com > >> www.SQLIS.com > >> www.Konesans.com > >>> Hi I have developed a very simple package which copys a set of rows > >>> from 1 db to another. all works fine in the VS2005 BI and also > >>> can run the package.dtx from the desktop. But when I add this > >>> package to the the Jobs to schedule it to run, it fails on the > >>> first step. No reason why - just step 1 failed. > >>> > >>> Any ideas why this package cannot run by sql jobs agent. All > >>> passwords are provided in the code, and package runs on that machine > >>> from the desktop. > >>> > >>> Thanks > >>> > >
Hello Martin,
OK when you say it does not work in SQL Server then I presume you mean there is no logging happens when you riun the package as a job. If this is the case then it would seem the packaage does not even get as far as executing. You need to check permissions, syntax Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com [quoted text, click to view] > Hi > Ok, I switched on Logging, and it writes to a text file on the c: it > all > works in the VS environment and from Commnadline. But not in SQL > server. > And when it runs in Sql server I get no log info either. > Something strange going on, because other packages have worked > previously. > > "Allan Mitchell" wrote: > >> Hello Martin, >> >> I would personally do it in the package itself so in Control Flow, go >> to the SSIS menu and choose logging. Here is what BOL says about job >> steps. >> >> "Every job step runs in a specific security context. If the job step >> specifies a proxy, the job step runs in the security context of the >> credential for the proxy. If a job step does not specify a proxy, the >> job step runs in the context of the SQL Server Agent service account. >> Only members of the sysadmin fixed server role can create jobs that >> do not explicitly specify a proxy. >> >> Because job steps run in the context of a specific Microsoft Windows >> user, that user must have the permissions and configuration necessary >> for the job step to execute. For example, if you create a job that >> requires a drive letter or a Universal Naming Convention (UNC) path, >> the job steps may run under your Microsoft Windows user account while >> testing the tasks. However, the Windows user for the job step must >> also have the necessary permissions, drive letter configurations, or >> access to the required drive. Otherwise, the job step fails. To >> prevent this problem, ensure that the proxy for each job step has the >> necessary permissions for the task that the job step performs" >> >> Also have a look here. >> >> http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html >> >> Allan Mitchell >> www.SQLDTS.com >> www.SQLIS.com >> www.Konesans.com >>> No, how do you do that? In the job ? >>> >>> rgds >>> M >>> "Allan Mitchell" wrote: >>>> Hello Martin, >>>> >>>> Have you got any logging on in the package? >>>> >>>> It does sound as though there is a security permission here though >>>> or something is required that is user specific like maybe a drive >>>> mapping. >>>> >>>> Allan Mitchell >>>> www.SQLDTS.com >>>> www.SQLIS.com >>>> www.Konesans.com >>>>> Hi I have developed a very simple package which copys a set of >>>>> rows from 1 db to another. all works fine in the VS2005 BI and >>>>> also can run the package.dtx from the desktop. But when I add >>>>> this package to the the Jobs to schedule it to run, it fails on >>>>> the first step. No reason why - just step 1 failed. >>>>> >>>>> Any ideas why this package cannot run by sql jobs agent. All >>>>> passwords are provided in the code, and package runs on that >>>>> machine from the desktop. >>>>> >>>>> Thanks >>>>>
Hi
Ok, I have logging working on it now. And the error is ,The AcquireConnection method call to the connection manager "xxx" failed with error code 0xC0202009. I have saved the password in connection in the package and all works fine, but for some reason connection uid and pwd are not being saved in the package so I guess it hits this cannot login error. This only happens when you create a Job in SQL server and import this package from the file system You can run this package from the file system by double clicking the package.dtsx or running in VS2005. And all works fine. I am scratching my head with this one?! [quoted text, click to view] "Allan Mitchell" wrote:
> Hello Martin, > > OK when you say it does not work in SQL Server then I presume you mean there > is no logging happens when you riun the package as a job. If this is the > case then it would seem the packaage does not even get as far as executing. > > You need to check permissions, syntax > > Allan Mitchell > www.SQLDTS.com > www.SQLIS.com > www.Konesans.com > > > Hi > > Ok, I switched on Logging, and it writes to a text file on the c: it > > all > > works in the VS environment and from Commnadline. But not in SQL > > server. > > And when it runs in Sql server I get no log info either. > > Something strange going on, because other packages have worked > > previously. > > > > "Allan Mitchell" wrote: > > > >> Hello Martin, > >> > >> I would personally do it in the package itself so in Control Flow, go > >> to the SSIS menu and choose logging. Here is what BOL says about job > >> steps. > >> > >> "Every job step runs in a specific security context. If the job step > >> specifies a proxy, the job step runs in the security context of the > >> credential for the proxy. If a job step does not specify a proxy, the > >> job step runs in the context of the SQL Server Agent service account. > >> Only members of the sysadmin fixed server role can create jobs that > >> do not explicitly specify a proxy. > >> > >> Because job steps run in the context of a specific Microsoft Windows > >> user, that user must have the permissions and configuration necessary > >> for the job step to execute. For example, if you create a job that > >> requires a drive letter or a Universal Naming Convention (UNC) path, > >> the job steps may run under your Microsoft Windows user account while > >> testing the tasks. However, the Windows user for the job step must > >> also have the necessary permissions, drive letter configurations, or > >> access to the required drive. Otherwise, the job step fails. To > >> prevent this problem, ensure that the proxy for each job step has the > >> necessary permissions for the task that the job step performs" > >> > >> Also have a look here. > >> > >> http://wiki.sqlis.com/default.aspx/SQLISWiki/ScheduledPackages.html > >> > >> Allan Mitchell > >> www.SQLDTS.com > >> www.SQLIS.com > >> www.Konesans.com > >>> No, how do you do that? In the job ? > >>> > >>> rgds > >>> M > >>> "Allan Mitchell" wrote: > >>>> Hello Martin, > >>>> > >>>> Have you got any logging on in the package? > >>>> > >>>> It does sound as though there is a security permission here though > >>>> or something is required that is user specific like maybe a drive > >>>> mapping. > >>>> > >>>> Allan Mitchell > >>>> www.SQLDTS.com > >>>> www.SQLIS.com > >>>> www.Konesans.com > >>>>> Hi I have developed a very simple package which copys a set of > >>>>> rows from 1 db to another. all works fine in the VS2005 BI and > >>>>> also can run the package.dtx from the desktop. But when I add > >>>>> this package to the the Jobs to schedule it to run, it fails on > >>>>> the first step. No reason why - just step 1 failed. > >>>>> > >>>>> Any ideas why this package cannot run by sql jobs agent. All > >>>>> passwords are provided in the code, and package runs on that > >>>>> machine from the desktop. > >>>>> > >>>>> Thanks > >>>>> > >
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |