February 11, 2009 at 4:58 am
SQL2005 Standard ed., Windows Server 2003 Standard ed.
My SSIS package does some fairly standard things: SQLTasks that execute stored procedures, Data Flow to read data into Sql Server from Oracle, write to a file...
It runs just fine when I use the "run Package" util in Integration Services Engine.
It also runs fine via dtexec as a CmdExec jobstep in an Agent job, running under a proxy I've set up.
For some reason when I try to run it as an SSIS jobstep, running under the same proxy, the job starts, but then hangs - no error or anything, and in fact it doesn't even show up in the "Running Jobs" section, which leads me to suspect that it's not *actually* running.
I tried each of my package steps on their own, and they all worked fine as SSIS-type jobsteps except for the Data Flow task, which would appear to be the culprit for the job hanging.
This Data Flow task uses the Oracle Provider for OLEDB (from ODAC), although whether this is relevant I haven't a clue.
It was my understanding that, under the hood, the SSIS subsystem in Sql Agent just runs dtexec.
I'm confused as to why the job would hang as an SSIS-type jobstep, and not as a CmdExec/dtexec step.
Has anyone experienced any similar behaviour, or can shed any light on this at all?
Many thanks
May 20, 2009 at 9:19 am
Did anyone have a solution for this? Im having similar problems with an SSIS package
August 20, 2009 at 12:58 pm
Not sure if anyone has gotten by this issue or not. I ran into the same thing. When I tried to execute my SSIS Package from with SQL Serve Agent, my job would start but would then just hang when the package was trying to query some information from a SQL Server table.
I worked with one of our DBAs and we noticed that the Named Pipes protocol was disabled. When we enabled this protocol from within SQL Server Configuration manager and restarted the services, my jobs then ran to completion from with SQL Server Agent.
June 21, 2010 at 10:35 am
I was having the same issue and found a rather strange solution. I found that if I connected to Integration Services via Management Studio, clicked on "run package" and then "command line", and then copied the exact "command line" syntax into my SQL job that it worked. The only difference between my original syntax and the copied version is that mine had "dtexec" at the front of it. I found that if i simply removed "dtexec" that the job would no longer hang. I don't understand it...but it seems to work.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply