December 11, 2009 at 5:31 am
I have a SQL JOB (sql2005) that will run a SSIS Package i've created.
I run the Package from VS2005 Integration Services with no problem.
I can execute the JOB manually from SSMS and it executes with no problem.
However, the JOB DOES NOT run at the Scheduled time i've defined... :crazy:
Any help please...
JB 😎
December 11, 2009 at 5:41 am
Do you get an error? Or do you mean it doesn't run at all...
December 11, 2009 at 5:59 am
Schedule Enabled?
Step in job enabled?
Job Enabled?
SQL Agent running?
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This thing is addressing problems that dont exist. Its solution-ism at its worst. We are dumbing down machines that are inherently superior. - Gilfoyle
December 11, 2009 at 6:28 am
The thread is posted in SQL 7, 2000..that doesn't matter much.
In what Security context the SSIS Package is executing and where is the packages stored? File System or SQL Server?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
December 11, 2009 at 6:57 am
It simply doesn't execute at the scheduled time.
SQL Agent is running.
The JOB is Enabled.
If I manually execute the JOB (right click on JOB -> "Start JOB at Step..."), it works. EventViewer picks up the execution (with the folowwing message: 'Package "myPackage" started' & 'Package "myPackage" finished successfully') and the JOB does what it's supposed to.
Lets say the scheduled time is 11 a.m. (11:00:00) -> nothinh happens at this time. The JOB doesn't execute and EventVieer doesn't pick up any activity nor does the "History" of SQL Agent.
I gave other jobs that are running perfectly. I can't figure out what's the problem with this one :ermm:
December 11, 2009 at 7:01 am
What about the Security settings and the where is the SSIS Package deployed?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
December 11, 2009 at 7:16 am
I had this,, I restarted SQL server agent and the schedule started to work. I still haven't got an answer as to why it stopped working...
Is it 32 or 64 bit?
December 11, 2009 at 7:33 am
SQL 2005
Windows Server 2003
Tried restarting SQL Agent, still have the same problem 🙁
December 11, 2009 at 7:47 am
What about the SSIS package info I was asking? Under what security context is the step running?
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
December 11, 2009 at 7:51 am
What about the SSIS package info I was asking? Under what security context is the step running?
Hi Bru
but the job works fine when run manually,, does it still matter what security context the step is running.
December 11, 2009 at 7:54 am
Absolutely...
When you run manually, it is executing under your security context, but when scheduled it may not be so..
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
December 11, 2009 at 8:08 am
OK, i figured out the problem... but not the solution (yet) :p
This project is integrated in a Clustered Service. The SQL SMSS Instance and the SQL Server Agent are runnig on different Clusters... got get them running on the Clusters :w00t:
Hope that this works afterwards
Thanks all for your input/help
JB 😎
December 11, 2009 at 8:12 am
You are welcome !
Blog -- LearnSQLWithBru
Join on Facebook Page Facebook.comLearnSQLWithBru
Twitter -- BruMedishetty
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply