Hello. I have an SSIS package, which runs fine in Visual Studio. I create
and deploy the package to the SQL Server set all the connection properties,
etc... and then schdule the package to run in teh job agent. The package has
many steps, including running an external program and eventually a data flow
that contains a Fuzzy Lookup task. While running via the job agent the
package fails at that data flow task. All other flows and commends run
before it.

Is there something I'm missing with in the Fuzzy Lookup that needs to done
for deployment?

I have not gotten any telling error messages.

Thanks in advance
Andrew

Hi Andrew,

9 times out of 10 the problem with a package that fails when run from
a Job but works when run from the Dev environment is permissions.

Please make sure that the account the SQL Agent job is running under
has the correct permissions in the database and filesystem (i.e.
access to all the required tables, directories, and applications). If
you are still having trouble after that, please post the specific
error message that the package is producing.

Good luck!
J

Hi Andrew,

9 times out of 10 the problem with a package that fails when run from
a Job but works when run from the Dev environment is permissions.

Please make sure that the account the SQL Agent job is running under
has the correct permissions in the database and filesystem (i.e.
access to all the required tables, directories, and applications). If
you are still having trouble after that, please post the specific
error message that the package is producing.

Good luck!
J

Hi Andrew,

9 times out of 10 the problem with a package that fails when run from
a Job but works when run from the Dev environment is permissions.

Please make sure that the account the SQL Agent job is running under
has the correct permissions in the database and filesystem (i.e.
access to all the required tables, directories, and applications). If
you are still having trouble after that, please post the specific
error message that the package is producing.

Good luck!
J

Hi Andrew,

9 times out of 10 the problem with a package that fails when run from
a Job but works when run from the Dev environment is permissions.

Please make sure that the account the SQL Agent job is running under
has the correct permissions in the database and filesystem (i.e.
access to all the required tables, directories, and applications). If
you are still having trouble after that, please post the specific
error message that the package is producing.

Good luck!
J

Hi Andrew,

9 times out of 10 the problem with a package that fails when run from
a Job but works when run from the Dev environment is permissions.

Please make sure that the account the SQL Agent job is running under
has the correct permissions in the database and filesystem (i.e.
access to all the required tables, directories, and applications). If
you are still having trouble after that, please post the specific
error message that the package is producing.

Good luck!
J

Hi Andrew,

9 times out of 10 the problem with a package that fails when run from
a Job but works when run from the Dev environment is permissions.

Please make sure that the account the SQL Agent job is running under
has the correct permissions in the database and filesystem (i.e.
access to all the required tables, directories, and applications). If
you are still having trouble after that, please post the specific
error message that the package is producing.

Good luck!
J

Hi Andrew,

9 times out of 10 the problem with a package that fails when run from
a Job but works when run from the Dev environment is permissions.

Please make sure that the account the SQL Agent job is running under
has the correct permissions in the database and filesystem (i.e.
access to all the required tables, directories, and applications). If
you are still having trouble after that, please post the specific
error message that the package is producing.

Good luck!
J

Hi Andrew,

9 times out of 10 the problem with a package that fails when run from
a Job but works when run from the Dev environment is permissions.

Please make sure that the account the SQL Agent job is running under
has the correct permissions in the database and filesystem (i.e.
access to all the required tables, directories, and applications). If
you are still having trouble after that, please post the specific
error message that the package is producing.

Good luck!
J