December 10, 2007 at 11:04 am
I have migrated some packages from SQL 2000 to SQL 2005 and tried scheduling these migrated packages in SQL SERVER 2005 Agent Jobs in another server. But the job failed with the error shown below
Message
The job failed. The Job was invoked by Schedule 1 (Export_YM_Manifest_7pm Daily). The last step to run was step 1 (Export_YM_Manifest).
I have administrator rights on the scheduling server and the packages have protection level as "EncryptSensitiveWithUserKey".
Does anybody have any ideas on how to resolve this problem??
December 10, 2007 at 12:57 pm
The server on which you scheduled the packages needs to have the SSIS services installed, needs to have the backward compatibility pack installed, and really should have the same service pack as the server in which you have stored the SSIS packages.
Scheduling a package on a remote server does not execute it on the server in which the package is stored. It executes the package on the server running the SQL Agent.
December 10, 2007 at 3:34 pm
All these have been already installed in the server...is there anything else to resolve this issue?
December 11, 2007 at 5:01 am
You need to tun on logging to get the actual error messages from your SSIS package.
As an alternative, log into the server that is executing the package with the login the agent job is running under (typically the service account for the SQL Agent service). Once logged in, connect to the server the package is stored on using management studio and execute the package manually to see the message output.
December 12, 2007 at 6:16 am
You can also set logging in the job step where the package is run. Send it to a text file and see what it says.
I'm wondering if the job can't find the package. Are you running the job step as an SSIS step or an OS Command line?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply