August 8, 2006 at 1:41 am
Hi,
I'm a newbie in SQL 2005. Currently I'm testing SSIS and I'm having problem copying a table from sql2k to sql2005 using a simple SSIS package (package created using Import/Export Wizard). Applied almost all the recommendations that can be found on the web on how to run an SSIS Package. I have checked on the security by way of proxy and all the methods mentioned in KB918760. But still my package fails everytime I run it as a job. It runs ok on the development studio and ssis service. By the way, the package is stored in MSDB.
Please help my back is up against the wall. Thanks in advance.
other info:
sql service: safi\sqltest with admin privileges
sql agent service: safi\sqltest with admin privileges
created the the package using safi\rbv account (admin)
it has all user rights assignments
August 8, 2006 at 8:10 am
Do you have any error checking enabled within the package? (click inside package, properties, designate a error log file location):
Also who is the JOB being executed by...right click on the job, view HISTORY, go to the END of the file and see what name is here:
Message
Executed as user:
Seems to be permission problems...
...Marsha
August 8, 2006 at 8:14 am
Just to check/confirm - the step in the job that is (should be) running the package - is the TYPE a SSIS Package, or are you using the CommandLine and then specifying a DTEXEC with the relevant commandline?
I've found it significantly easier to debug my jobs when running the package using DTEXEC from the commandline, and this also gives you the ability to choose the 'include step output in history' on the advanced tab on the job step.
August 9, 2006 at 12:24 am
August 9, 2006 at 12:28 am
August 9, 2006 at 2:58 am
August 9, 2006 at 4:45 am
Just as an FYI, the DTEXEC command line can run SSIS Package that are stored in SQL Server.
The syntax is along the lines of:
DTEXEC /SQL .....
August 9, 2006 at 7:08 pm
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply