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,

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

No, how do you do that? In the job ?

rgds
M

"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/S...dPackages.html


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,

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 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?!






"Allan Mitchell" wrote: