I have a multistep job that has been working fine until recently, but for
some reason the server rebooted (power outage?) and ever since then the job
scheduler is not working as it should. The job starts, the 1st step
executes OK, but progress is not made to the next step and the job continues
to be in Execute mode.
...to work around this problem, I've disabled my job and have created 1 job
for each of the steps in my 'hanging' job. These smaller jobs run OK if I
don't attach a schedule to them, however, once I attach a schedule to each
job, the same problem recurs...the job completes OK, but the status of the
job remains Executing and never completes.
TIA for any suggestions and thoughts on this matter.I had a similar problem recently that was only resolved by re-installing the latest MDAC.|||Yes...that was it. Thank you very much.
"AC" <anonymous@.discussions.microsoft.com> wrote in message
news:DE5EBE1B-2562-4541-851A-3710A138E593@.microsoft.com...
> I had a similar problem recently that was only resolved by re-installing
the latest MDAC.sql
Showing posts with label working. Show all posts
Showing posts with label working. Show all posts
Friday, March 23, 2012
job run when idle
I'm trying to get a SQL Agent scheduled job working using the Schedule
Type of 'Start whenever the CPUs become idle', but it doesn't seem to
be working.
I setup a maintenance task to check db integrity (as a test), set it
to run today in about 2 minutes, changed the Schedule type to 'Start
on idle' and the 'Define idle CPU condition' and watched CPU
utilization and the monitor to see if it runs, but it never does.
What step am I missing?
Thanks!
Chris
I don't use this feature, and don't know anybody who uses this feature
(though that doesn't mean nobody uses it). The reason is that for a SQL
Server job, it's better to know when it'll run than it is to leave it to
'random' chances.
Linchi
"cbtechlists@.gmail.com" wrote:
> I'm trying to get a SQL Agent scheduled job working using the Schedule
> Type of 'Start whenever the CPUs become idle', but it doesn't seem to
> be working.
> I setup a maintenance task to check db integrity (as a test), set it
> to run today in about 2 minutes, changed the Schedule type to 'Start
> on idle' and the 'Define idle CPU condition' and watched CPU
> utilization and the monitor to see if it runs, but it never does.
> What step am I missing?
> Thanks!
> Chris
>
|||I'm with Linchi, CPU utilization jobs generally shouldn't be used. I
would use the performance counters on the machine to keeps a log for
an average day/week of work and design a date/time strategy around
that. It should give you the best times to run these types of things,
i.e. low cpu + low I/O + low users @. 4:00 am everyday. Also take into
account any data loads or batch executions of programs or ones that
users manually do.
On Mar 20, 9:44Xam, Linchi Shea <LinchiS...@.discussions.microsoft.com>
wrote:
> I don't use this feature, and don't know anybody who uses this feature
> (though that doesn't mean nobody uses it). The reason is that for a SQL
> Server job, it's better to know when it'll run than it is to leave it to
> 'random' chances.
> Linchi
>
> "cbtechli...@.gmail.com" wrote:
>
>
> - Show quoted text -
Type of 'Start whenever the CPUs become idle', but it doesn't seem to
be working.
I setup a maintenance task to check db integrity (as a test), set it
to run today in about 2 minutes, changed the Schedule type to 'Start
on idle' and the 'Define idle CPU condition' and watched CPU
utilization and the monitor to see if it runs, but it never does.
What step am I missing?
Thanks!
Chris
I don't use this feature, and don't know anybody who uses this feature
(though that doesn't mean nobody uses it). The reason is that for a SQL
Server job, it's better to know when it'll run than it is to leave it to
'random' chances.
Linchi
"cbtechlists@.gmail.com" wrote:
> I'm trying to get a SQL Agent scheduled job working using the Schedule
> Type of 'Start whenever the CPUs become idle', but it doesn't seem to
> be working.
> I setup a maintenance task to check db integrity (as a test), set it
> to run today in about 2 minutes, changed the Schedule type to 'Start
> on idle' and the 'Define idle CPU condition' and watched CPU
> utilization and the monitor to see if it runs, but it never does.
> What step am I missing?
> Thanks!
> Chris
>
|||I'm with Linchi, CPU utilization jobs generally shouldn't be used. I
would use the performance counters on the machine to keeps a log for
an average day/week of work and design a date/time strategy around
that. It should give you the best times to run these types of things,
i.e. low cpu + low I/O + low users @. 4:00 am everyday. Also take into
account any data loads or batch executions of programs or ones that
users manually do.
On Mar 20, 9:44Xam, Linchi Shea <LinchiS...@.discussions.microsoft.com>
wrote:
> I don't use this feature, and don't know anybody who uses this feature
> (though that doesn't mean nobody uses it). The reason is that for a SQL
> Server job, it's better to know when it'll run than it is to leave it to
> 'random' chances.
> Linchi
>
> "cbtechli...@.gmail.com" wrote:
>
>
> - Show quoted text -
job run when idle
I'm trying to get a SQL Agent scheduled job working using the Schedule
Type of 'Start whenever the CPUs become idle', but it doesn't seem to
be working.
I setup a maintenance task to check db integrity (as a test), set it
to run today in about 2 minutes, changed the Schedule type to 'Start
on idle' and the 'Define idle CPU condition' and watched CPU
utilization and the monitor to see if it runs, but it never does.
What step am I missing?
Thanks!
ChrisI don't use this feature, and don't know anybody who uses this feature
(though that doesn't mean nobody uses it). The reason is that for a SQL
Server job, it's better to know when it'll run than it is to leave it to
'random' chances.
Linchi
"cbtechlists@.gmail.com" wrote:
> I'm trying to get a SQL Agent scheduled job working using the Schedule
> Type of 'Start whenever the CPUs become idle', but it doesn't seem to
> be working.
> I setup a maintenance task to check db integrity (as a test), set it
> to run today in about 2 minutes, changed the Schedule type to 'Start
> on idle' and the 'Define idle CPU condition' and watched CPU
> utilization and the monitor to see if it runs, but it never does.
> What step am I missing?
> Thanks!
> Chris
>|||I'm with Linchi, CPU utilization jobs generally shouldn't be used. I
would use the performance counters on the machine to keeps a log for
an average day/week of work and design a date/time strategy around
that. It should give you the best times to run these types of things,
i.e. low cpu + low I/O + low users @. 4:00 am everyday. Also take into
account any data loads or batch executions of programs or ones that
users manually do.
On Mar 20, 9:44=A0am, Linchi Shea <LinchiS...@.discussions.microsoft.com>
wrote:
> I don't use this feature, and don't know anybody who uses this feature
> (though that doesn't mean nobody uses it). The reason is that for a SQL
> Server job, it's better to know when it'll run than it is to leave it to
> 'random' chances.
> Linchi
>
> "cbtechli...@.gmail.com" wrote:
> > I'm trying to get a SQL Agent scheduled job working using the Schedule
> > Type of 'Start whenever the CPUs become idle', but it doesn't seem to
> > be working.
> > I setup a maintenance task to check db integrity (as a test), set it
> > to run today in about 2 minutes, changed the Schedule type to 'Start
> > on idle' and the 'Define idle CPU condition' and watched CPU
> > utilization and the monitor to see if it runs, but it never does.
> > What step am I missing?
> > Thanks!
> > Chris- Hide quoted text -
> - Show quoted text -sql
Type of 'Start whenever the CPUs become idle', but it doesn't seem to
be working.
I setup a maintenance task to check db integrity (as a test), set it
to run today in about 2 minutes, changed the Schedule type to 'Start
on idle' and the 'Define idle CPU condition' and watched CPU
utilization and the monitor to see if it runs, but it never does.
What step am I missing?
Thanks!
ChrisI don't use this feature, and don't know anybody who uses this feature
(though that doesn't mean nobody uses it). The reason is that for a SQL
Server job, it's better to know when it'll run than it is to leave it to
'random' chances.
Linchi
"cbtechlists@.gmail.com" wrote:
> I'm trying to get a SQL Agent scheduled job working using the Schedule
> Type of 'Start whenever the CPUs become idle', but it doesn't seem to
> be working.
> I setup a maintenance task to check db integrity (as a test), set it
> to run today in about 2 minutes, changed the Schedule type to 'Start
> on idle' and the 'Define idle CPU condition' and watched CPU
> utilization and the monitor to see if it runs, but it never does.
> What step am I missing?
> Thanks!
> Chris
>|||I'm with Linchi, CPU utilization jobs generally shouldn't be used. I
would use the performance counters on the machine to keeps a log for
an average day/week of work and design a date/time strategy around
that. It should give you the best times to run these types of things,
i.e. low cpu + low I/O + low users @. 4:00 am everyday. Also take into
account any data loads or batch executions of programs or ones that
users manually do.
On Mar 20, 9:44=A0am, Linchi Shea <LinchiS...@.discussions.microsoft.com>
wrote:
> I don't use this feature, and don't know anybody who uses this feature
> (though that doesn't mean nobody uses it). The reason is that for a SQL
> Server job, it's better to know when it'll run than it is to leave it to
> 'random' chances.
> Linchi
>
> "cbtechli...@.gmail.com" wrote:
> > I'm trying to get a SQL Agent scheduled job working using the Schedule
> > Type of 'Start whenever the CPUs become idle', but it doesn't seem to
> > be working.
> > I setup a maintenance task to check db integrity (as a test), set it
> > to run today in about 2 minutes, changed the Schedule type to 'Start
> > on idle' and the 'Define idle CPU condition' and watched CPU
> > utilization and the monitor to see if it runs, but it never does.
> > What step am I missing?
> > Thanks!
> > Chris- Hide quoted text -
> - Show quoted text -sql
Wednesday, March 21, 2012
Job notification
Morning all!
My SQL server email job notifications have stopped working, but mails sent through the xp_sendmail command still work.
The only thing that has changed recently is the SQL server agent account passwords have been changed, these accounts are normal win2000 domain accounts.
Any ideas cos I am fully stumped?Have you tried testing the SQLMail Profile?
Support Services/SQLMail.
Are SQLMail and SQLAgentMail using the same mail profile?|||Already tested the SQL mail profile and that works ok,
How do I check which profile the sqlagentmail is using?|||Originally posted by SQLSlammer
Already tested the SQL mail profile and that works ok,
How do I check which profile the sqlagentmail is using?
Right click on SQL Agent/Properties and check that it is using the same mail profile.
My SQL server email job notifications have stopped working, but mails sent through the xp_sendmail command still work.
The only thing that has changed recently is the SQL server agent account passwords have been changed, these accounts are normal win2000 domain accounts.
Any ideas cos I am fully stumped?Have you tried testing the SQLMail Profile?
Support Services/SQLMail.
Are SQLMail and SQLAgentMail using the same mail profile?|||Already tested the SQL mail profile and that works ok,
How do I check which profile the sqlagentmail is using?|||Originally posted by SQLSlammer
Already tested the SQL mail profile and that works ok,
How do I check which profile the sqlagentmail is using?
Right click on SQL Agent/Properties and check that it is using the same mail profile.
Job not working in SQL server
Hi,
I have put a job with 3 steps.
But appear this message : "The job failed. The Job was
invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last step
to run was step 3 (IMPORT_DBF_TO_SQL)".
What I Can do to solve this problem'
ThanksYou need to see what Step 3 :- IMPORT_DBF_TO_SQL is trying to do.
I would imagine it executes a DTS Package, hopefully that DTS package was
designed to produce a Log output file. That Log file will give you the real
reason for the failure.
--
HTH
Ryan Waight, MCDBA, MCSE
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
> Hi,
> I have put a job with 3 steps.
> But appear this message : "The job failed. The Job was
> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last step
> to run was step 3 (IMPORT_DBF_TO_SQL)".
> What I Can do to solve this problem'
> Thanks
>|||Hi,
But its very strange, because i have in another SQL server
the same job and it's ok!!
the steps are:
1- DeleteCurrentData -- Transact-SQL Script
2- Convert DAT to DBF -- Transact-SQL Script
3- IMPORT_DBF_TO_SQL -- Operating System Command
>--Original Message--
>You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
trying to do.
>I would imagine it executes a DTS Package, hopefully that
DTS package was
>designed to produce a Log output file. That Log file will
give you the real
>reason for the failure.
>--
>HTH
>Ryan Waight, MCDBA, MCSE
>"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
>news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
>> Hi,
>> I have put a job with 3 steps.
>> But appear this message : "The job failed. The Job was
>> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
step
>> to run was step 3 (IMPORT_DBF_TO_SQL)".
>> What I Can do to solve this problem'
>> Thanks
>>
>
>.
>|||It is impossible for us to know why it fails when all you tell us is that it fails.
Specify an output file for that jobstep and look at the messages in there. Hopefully this program
produces output from which you can determine what it wrong.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:084901c3b4df$9edff550$a501280a@.phx.gbl...
> Hi,
> But its very strange, because i have in another SQL server
> the same job and it's ok!!
> the steps are:
> 1- DeleteCurrentData -- Transact-SQL Script
> 2- Convert DAT to DBF -- Transact-SQL Script
> 3- IMPORT_DBF_TO_SQL -- Operating System Command
>
>
> >--Original Message--
> >You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
> trying to do.
> >
> >I would imagine it executes a DTS Package, hopefully that
> DTS package was
> >designed to produce a Log output file. That Log file will
> give you the real
> >reason for the failure.
> >
> >--
> >HTH
> >Ryan Waight, MCDBA, MCSE
> >
> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
> >news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
> >> Hi,
> >>
> >> I have put a job with 3 steps.
> >> But appear this message : "The job failed. The Job was
> >> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
> step
> >> to run was step 3 (IMPORT_DBF_TO_SQL)".
> >>
> >> What I Can do to solve this problem'
> >>
> >> Thanks
> >>
> >>
> >
> >
> >.
> >|||In the output file the message that appear are
"SQL Server Scheduled Job 'import-DBF_to_SQL'
(0x3CB9A4AA25D87B408BF4C3272F2F4C8B) - Status: Failed -
Invoked on: 2003-11-27 04:00:00 - Message: The job
failed. The Job was invoked by Schedule 15
(IMPORT_DBF_TO_SQL). The last step to run was step 3
(IMPORT_DBF_TO_SQL). "
>--Original Message--
>It is impossible for us to know why it fails when all you
tell us is that it fails.
>Specify an output file for that jobstep and look at the
messages in there. Hopefully this program
>produces output from which you can determine what it
wrong.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
>news:084901c3b4df$9edff550$a501280a@.phx.gbl...
>> Hi,
>> But its very strange, because i have in another SQL
server
>> the same job and it's ok!!
>> the steps are:
>> 1- DeleteCurrentData -- Transact-SQL Script
>> 2- Convert DAT to DBF -- Transact-SQL Script
>> 3- IMPORT_DBF_TO_SQL -- Operating System Command
>>
>>
>> >--Original Message--
>> >You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
>> trying to do.
>> >
>> >I would imagine it executes a DTS Package, hopefully
that
>> DTS package was
>> >designed to produce a Log output file. That Log file
will
>> give you the real
>> >reason for the failure.
>> >
>> >--
>> >HTH
>> >Ryan Waight, MCDBA, MCSE
>> >
>> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in
message
>> >news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
>> >> Hi,
>> >>
>> >> I have put a job with 3 steps.
>> >> But appear this message : "The job failed. The Job
was
>> >> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
>> step
>> >> to run was step 3 (IMPORT_DBF_TO_SQL)".
>> >>
>> >> What I Can do to solve this problem'
>> >>
>> >> Thanks
>> >>
>> >>
>> >
>> >
>> >.
>> >
>
>.
>|||That is not the output file. In the job *step*, right tab, you have an option to specify an output
file for the jobstep. This is where all the messages from the command are written. After executing
the job, check this file.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:0a2d01c3b4fb$b7513790$a501280a@.phx.gbl...
> In the output file the message that appear are
> "SQL Server Scheduled Job 'import-DBF_to_SQL'
> (0x3CB9A4AA25D87B408BF4C3272F2F4C8B) - Status: Failed -
> Invoked on: 2003-11-27 04:00:00 - Message: The job
> failed. The Job was invoked by Schedule 15
> (IMPORT_DBF_TO_SQL). The last step to run was step 3
> (IMPORT_DBF_TO_SQL). "
>
> >--Original Message--
> >It is impossible for us to know why it fails when all you
> tell us is that it fails.
> >Specify an output file for that jobstep and look at the
> messages in there. Hopefully this program
> >produces output from which you can determine what it
> wrong.
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at: http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
> >news:084901c3b4df$9edff550$a501280a@.phx.gbl...
> >> Hi,
> >>
> >> But its very strange, because i have in another SQL
> server
> >> the same job and it's ok!!
> >> the steps are:
> >> 1- DeleteCurrentData -- Transact-SQL Script
> >> 2- Convert DAT to DBF -- Transact-SQL Script
> >> 3- IMPORT_DBF_TO_SQL -- Operating System Command
> >>
> >>
> >>
> >>
> >> >--Original Message--
> >> >You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
> >> trying to do.
> >> >
> >> >I would imagine it executes a DTS Package, hopefully
> that
> >> DTS package was
> >> >designed to produce a Log output file. That Log file
> will
> >> give you the real
> >> >reason for the failure.
> >> >
> >> >--
> >> >HTH
> >> >Ryan Waight, MCDBA, MCSE
> >> >
> >> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in
> message
> >> >news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
> >> >> Hi,
> >> >>
> >> >> I have put a job with 3 steps.
> >> >> But appear this message : "The job failed. The Job
> was
> >> >> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
> >> step
> >> >> to run was step 3 (IMPORT_DBF_TO_SQL)".
> >> >>
> >> >> What I Can do to solve this problem'
> >> >>
> >> >> Thanks
> >> >>
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
I have put a job with 3 steps.
But appear this message : "The job failed. The Job was
invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last step
to run was step 3 (IMPORT_DBF_TO_SQL)".
What I Can do to solve this problem'
ThanksYou need to see what Step 3 :- IMPORT_DBF_TO_SQL is trying to do.
I would imagine it executes a DTS Package, hopefully that DTS package was
designed to produce a Log output file. That Log file will give you the real
reason for the failure.
--
HTH
Ryan Waight, MCDBA, MCSE
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
> Hi,
> I have put a job with 3 steps.
> But appear this message : "The job failed. The Job was
> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last step
> to run was step 3 (IMPORT_DBF_TO_SQL)".
> What I Can do to solve this problem'
> Thanks
>|||Hi,
But its very strange, because i have in another SQL server
the same job and it's ok!!
the steps are:
1- DeleteCurrentData -- Transact-SQL Script
2- Convert DAT to DBF -- Transact-SQL Script
3- IMPORT_DBF_TO_SQL -- Operating System Command
>--Original Message--
>You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
trying to do.
>I would imagine it executes a DTS Package, hopefully that
DTS package was
>designed to produce a Log output file. That Log file will
give you the real
>reason for the failure.
>--
>HTH
>Ryan Waight, MCDBA, MCSE
>"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
>news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
>> Hi,
>> I have put a job with 3 steps.
>> But appear this message : "The job failed. The Job was
>> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
step
>> to run was step 3 (IMPORT_DBF_TO_SQL)".
>> What I Can do to solve this problem'
>> Thanks
>>
>
>.
>|||It is impossible for us to know why it fails when all you tell us is that it fails.
Specify an output file for that jobstep and look at the messages in there. Hopefully this program
produces output from which you can determine what it wrong.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:084901c3b4df$9edff550$a501280a@.phx.gbl...
> Hi,
> But its very strange, because i have in another SQL server
> the same job and it's ok!!
> the steps are:
> 1- DeleteCurrentData -- Transact-SQL Script
> 2- Convert DAT to DBF -- Transact-SQL Script
> 3- IMPORT_DBF_TO_SQL -- Operating System Command
>
>
> >--Original Message--
> >You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
> trying to do.
> >
> >I would imagine it executes a DTS Package, hopefully that
> DTS package was
> >designed to produce a Log output file. That Log file will
> give you the real
> >reason for the failure.
> >
> >--
> >HTH
> >Ryan Waight, MCDBA, MCSE
> >
> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
> >news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
> >> Hi,
> >>
> >> I have put a job with 3 steps.
> >> But appear this message : "The job failed. The Job was
> >> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
> step
> >> to run was step 3 (IMPORT_DBF_TO_SQL)".
> >>
> >> What I Can do to solve this problem'
> >>
> >> Thanks
> >>
> >>
> >
> >
> >.
> >|||In the output file the message that appear are
"SQL Server Scheduled Job 'import-DBF_to_SQL'
(0x3CB9A4AA25D87B408BF4C3272F2F4C8B) - Status: Failed -
Invoked on: 2003-11-27 04:00:00 - Message: The job
failed. The Job was invoked by Schedule 15
(IMPORT_DBF_TO_SQL). The last step to run was step 3
(IMPORT_DBF_TO_SQL). "
>--Original Message--
>It is impossible for us to know why it fails when all you
tell us is that it fails.
>Specify an output file for that jobstep and look at the
messages in there. Hopefully this program
>produces output from which you can determine what it
wrong.
>--
>Tibor Karaszi, SQL Server MVP
>Archive at: http://groups.google.com/groups?
oi=djq&as_ugroup=microsoft.public.sqlserver
>
>"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
>news:084901c3b4df$9edff550$a501280a@.phx.gbl...
>> Hi,
>> But its very strange, because i have in another SQL
server
>> the same job and it's ok!!
>> the steps are:
>> 1- DeleteCurrentData -- Transact-SQL Script
>> 2- Convert DAT to DBF -- Transact-SQL Script
>> 3- IMPORT_DBF_TO_SQL -- Operating System Command
>>
>>
>> >--Original Message--
>> >You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
>> trying to do.
>> >
>> >I would imagine it executes a DTS Package, hopefully
that
>> DTS package was
>> >designed to produce a Log output file. That Log file
will
>> give you the real
>> >reason for the failure.
>> >
>> >--
>> >HTH
>> >Ryan Waight, MCDBA, MCSE
>> >
>> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in
message
>> >news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
>> >> Hi,
>> >>
>> >> I have put a job with 3 steps.
>> >> But appear this message : "The job failed. The Job
was
>> >> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
>> step
>> >> to run was step 3 (IMPORT_DBF_TO_SQL)".
>> >>
>> >> What I Can do to solve this problem'
>> >>
>> >> Thanks
>> >>
>> >>
>> >
>> >
>> >.
>> >
>
>.
>|||That is not the output file. In the job *step*, right tab, you have an option to specify an output
file for the jobstep. This is where all the messages from the command are written. After executing
the job, check this file.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:0a2d01c3b4fb$b7513790$a501280a@.phx.gbl...
> In the output file the message that appear are
> "SQL Server Scheduled Job 'import-DBF_to_SQL'
> (0x3CB9A4AA25D87B408BF4C3272F2F4C8B) - Status: Failed -
> Invoked on: 2003-11-27 04:00:00 - Message: The job
> failed. The Job was invoked by Schedule 15
> (IMPORT_DBF_TO_SQL). The last step to run was step 3
> (IMPORT_DBF_TO_SQL). "
>
> >--Original Message--
> >It is impossible for us to know why it fails when all you
> tell us is that it fails.
> >Specify an output file for that jobstep and look at the
> messages in there. Hopefully this program
> >produces output from which you can determine what it
> wrong.
> >
> >--
> >Tibor Karaszi, SQL Server MVP
> >Archive at: http://groups.google.com/groups?
> oi=djq&as_ugroup=microsoft.public.sqlserver
> >
> >
> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
> >news:084901c3b4df$9edff550$a501280a@.phx.gbl...
> >> Hi,
> >>
> >> But its very strange, because i have in another SQL
> server
> >> the same job and it's ok!!
> >> the steps are:
> >> 1- DeleteCurrentData -- Transact-SQL Script
> >> 2- Convert DAT to DBF -- Transact-SQL Script
> >> 3- IMPORT_DBF_TO_SQL -- Operating System Command
> >>
> >>
> >>
> >>
> >> >--Original Message--
> >> >You need to see what Step 3 :- IMPORT_DBF_TO_SQL is
> >> trying to do.
> >> >
> >> >I would imagine it executes a DTS Package, hopefully
> that
> >> DTS package was
> >> >designed to produce a Log output file. That Log file
> will
> >> give you the real
> >> >reason for the failure.
> >> >
> >> >--
> >> >HTH
> >> >Ryan Waight, MCDBA, MCSE
> >> >
> >> >"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in
> message
> >> >news:0a4001c3b4d7$da8407c0$a301280a@.phx.gbl...
> >> >> Hi,
> >> >>
> >> >> I have put a job with 3 steps.
> >> >> But appear this message : "The job failed. The Job
> was
> >> >> invoked by Schedule 15 (IMPORT_DBF_TO_SQL). The last
> >> step
> >> >> to run was step 3 (IMPORT_DBF_TO_SQL)".
> >> >>
> >> >> What I Can do to solve this problem'
> >> >>
> >> >> Thanks
> >> >>
> >> >>
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >
Job not working
The output message is :
" DTSRun: Cannot create COM Server to load and execute
DTS Package. Error -2147221164 (80040154): Class not
registered "Was the package created on a different version of SQL Server ?
have you registered the DTS dlls?
If you have then you may want to reregister them.
Redistributing DTS with your program
http://www.sqldts.com/default.aspx?6,105,225,0,1
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:084a01c3b8bc$74b5a690$a501280a@.phx.gbl...
> The output message is :
> " DTSRun: Cannot create COM Server to load and execute
> DTS Package. Error -2147221164 (80040154): Class not
> registered "
>
" DTSRun: Cannot create COM Server to load and execute
DTS Package. Error -2147221164 (80040154): Class not
registered "Was the package created on a different version of SQL Server ?
have you registered the DTS dlls?
If you have then you may want to reregister them.
Redistributing DTS with your program
http://www.sqldts.com/default.aspx?6,105,225,0,1
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org
"Joao Sousa" <msousa@.pinheirosaltos.pt> wrote in message
news:084a01c3b8bc$74b5a690$a501280a@.phx.gbl...
> The output message is :
> " DTSRun: Cannot create COM Server to load and execute
> DTS Package. Error -2147221164 (80040154): Class not
> registered "
>
job in SQL
Hi..
I am working with an auction site ...I want to ask what I will use to open and close an auction
where the start and end date for the auction is stored in SQL server table...
I read many artical ..I think I will use job ?
can any one help me?
Hi, I'm not very clear about your requirment. Just some questions:
What's the meaning of 'open and close an auction'? Usually such business logic is implemented in application, and we use databases to manage the data, right? Do you mean you have an application to 'perform the auction', and you want to use SQL job to schedule it according to the date stored in some table, so that auctions can be automately opened and closed? Sadly to say it's too complex to use SQL job to do this; while much easier to use an application to control it--your application reads the start/end date from database table, then performs the auction process during the time between start/end date.
|||Hi..
Tank you for reply ...I have an auction site ... the auction will start in the start date that auctioneer decide it( the start date is store in SQL server table when auctioneer create it)...when the auction start it allow the user to bid on it until the end date then the auction will close and it will determine winner that have the highest bid...
what I use to mange opening & closing auction????
|||
Seems you need a project to do this... Other than the 'start time' and 'close time', the auction can also be closed under some conditions: e.g. if some one gives highest price and no one follows up, the auction is finished. So you have to build a project to implement the business of auction; SQL can be used to stored data as backend.
sqlMonday, March 12, 2012
Job fails due to domian acccont
I have job running under a domian\userraccont.. It use to work fine..
suddenly it stoppped working..below is the error message
"""""The job failed. Unable to determine if the owner
(HO_PDOMAIN\cyresextractprod) of job Cypress Reserves Extract Processing has
server access (reason: Could not obtain information about Windows NT
group/user 'HO_PDOMAIN\cyresextractprod'. [SQLSTATE 42000] (Error 819"""
I could not even get the user login info by isuing xp_logininfo command..
I will be gald if any 1 responseCould be
PRB: 8198 Error Message Returned from Job Owned by Windows NT Authenticated
User
http://support.microsoft.com/defaul...b;en-us;q241643
Since we don't allow users to create/own jobs we set all our jobs to be
owned by sa to avoid this issue. This may not be applicable in your
situation but it does mean we never run into this issue :-)
Also have a look at the KB articles returned by this search (watch for URL
wrapping)
%26CDID%3DEN-US-KB%26PRODLISTSRC%3DON&withinResults=&QuerySource=gASr_Query&Produc
t=sql2k&Queryc=8198&Query=8198&KeywordType=ALL&maxResults=25&Titles=false&numDays=
&InCC=on" target="_blank">http://support.microsoft.com/search...br />
&InCC=on
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Babu" <Babu@.discussions.microsoft.com> wrote in message
news:47299136-8FE8-4573-8C70-561EE1C27C04@.microsoft.com...
>
> I have job running under a domian\userraccont.. It use to work fine..
> suddenly it stoppped working..below is the error message
> """""The job failed. Unable to determine if the owner
> (HO_PDOMAIN\cyresextractprod) of job Cypress Reserves Extract Processing
> has
> server access (reason: Could not obtain information about Windows NT
> group/user 'HO_PDOMAIN\cyresextractprod'. [SQLSTATE 42000] (Error 819"
""
> I could not even get the user login info by isuing xp_logininfo command..
> I will be gald if any 1 response
suddenly it stoppped working..below is the error message
"""""The job failed. Unable to determine if the owner
(HO_PDOMAIN\cyresextractprod) of job Cypress Reserves Extract Processing has
server access (reason: Could not obtain information about Windows NT
group/user 'HO_PDOMAIN\cyresextractprod'. [SQLSTATE 42000] (Error 819"""
I could not even get the user login info by isuing xp_logininfo command..
I will be gald if any 1 responseCould be
PRB: 8198 Error Message Returned from Job Owned by Windows NT Authenticated
User
http://support.microsoft.com/defaul...b;en-us;q241643
Since we don't allow users to create/own jobs we set all our jobs to be
owned by sa to avoid this issue. This may not be applicable in your
situation but it does mean we never run into this issue :-)
Also have a look at the KB articles returned by this search (watch for URL
wrapping)
%26CDID%3DEN-US-KB%26PRODLISTSRC%3DON&withinResults=&QuerySource=gASr_Query&Produc
t=sql2k&Queryc=8198&Query=8198&KeywordType=ALL&maxResults=25&Titles=false&numDays=
&InCC=on" target="_blank">http://support.microsoft.com/search...br />
&InCC=on
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Babu" <Babu@.discussions.microsoft.com> wrote in message
news:47299136-8FE8-4573-8C70-561EE1C27C04@.microsoft.com...
>
> I have job running under a domian\userraccont.. It use to work fine..
> suddenly it stoppped working..below is the error message
> """""The job failed. Unable to determine if the owner
> (HO_PDOMAIN\cyresextractprod) of job Cypress Reserves Extract Processing
> has
> server access (reason: Could not obtain information about Windows NT
> group/user 'HO_PDOMAIN\cyresextractprod'. [SQLSTATE 42000] (Error 819"
""
> I could not even get the user login info by isuing xp_logininfo command..
> I will be gald if any 1 response
Friday, March 9, 2012
job failed on resource limit
Hi,
I have a job that pulls data from a linked server into
this server's database. I am working on sql server 2000.
It generally runs fine, but twice it failed on this error
message: 'OLE DB provider 'SQLOLEDB' reported an error.
Execution terminated by the provider because a resource
limit was reached. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ICommandText::Execute returned
0x80040e31: Execution terminated by the provider because
a resource limit was reached.]. [SQLSTATE 01000] (Error
7300). The step failed.'
When it says resource limit was reached, was it
complaining the number of connections at the linked server
has reached the limit?
Many thanks.
JJIt generally means a timeout has been exceeded (that's what 0x80040e31
means). You can increase the timeout to try and prevent this issue.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:09b401c371e7$6f7330b0$a101280a@.phx.gbl...
Hi,
I have a job that pulls data from a linked server into
this server's database. I am working on sql server 2000.
It generally runs fine, but twice it failed on this error
message: 'OLE DB provider 'SQLOLEDB' reported an error.
Execution terminated by the provider because a resource
limit was reached. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ICommandText::Execute returned
0x80040e31: Execution terminated by the provider because
a resource limit was reached.]. [SQLSTATE 01000] (Error
7300). The step failed.'
When it says resource limit was reached, was it
complaining the number of connections at the linked server
has reached the limit?
Many thanks.
JJ|||thanks, Jasper. Where should I go to adjust the time-out?
JJ
>--Original Message--
>It generally means a timeout has been exceeded (that's
what 0x80040e31
>means). You can increase the timeout to try and prevent
this issue.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"JJ Wang" <jwang@.leapwireless.com> wrote in message
>news:09b401c371e7$6f7330b0$a101280a@.phx.gbl...
>Hi,
>I have a job that pulls data from a linked server into
>this server's database. I am working on sql server 2000.
>It generally runs fine, but twice it failed on this error
>message: 'OLE DB provider 'SQLOLEDB' reported an error.
>Execution terminated by the provider because a resource
>limit was reached. [SQLSTATE 42000] (Error 7399)
>[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB
>Provider 'SQLOLEDB' ICommandText::Execute returned
>0x80040e31: Execution terminated by the provider because
>a resource limit was reached.]. [SQLSTATE 01000] (Error
>7300). The step failed.'
>When it says resource limit was reached, was it
>complaining the number of connections at the linked server
>has reached the limit?
>Many thanks.
>JJ
>
>.
>
I have a job that pulls data from a linked server into
this server's database. I am working on sql server 2000.
It generally runs fine, but twice it failed on this error
message: 'OLE DB provider 'SQLOLEDB' reported an error.
Execution terminated by the provider because a resource
limit was reached. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ICommandText::Execute returned
0x80040e31: Execution terminated by the provider because
a resource limit was reached.]. [SQLSTATE 01000] (Error
7300). The step failed.'
When it says resource limit was reached, was it
complaining the number of connections at the linked server
has reached the limit?
Many thanks.
JJIt generally means a timeout has been exceeded (that's what 0x80040e31
means). You can increase the timeout to try and prevent this issue.
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"JJ Wang" <jwang@.leapwireless.com> wrote in message
news:09b401c371e7$6f7330b0$a101280a@.phx.gbl...
Hi,
I have a job that pulls data from a linked server into
this server's database. I am working on sql server 2000.
It generally runs fine, but twice it failed on this error
message: 'OLE DB provider 'SQLOLEDB' reported an error.
Execution terminated by the provider because a resource
limit was reached. [SQLSTATE 42000] (Error 7399)
[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB
Provider 'SQLOLEDB' ICommandText::Execute returned
0x80040e31: Execution terminated by the provider because
a resource limit was reached.]. [SQLSTATE 01000] (Error
7300). The step failed.'
When it says resource limit was reached, was it
complaining the number of connections at the linked server
has reached the limit?
Many thanks.
JJ|||thanks, Jasper. Where should I go to adjust the time-out?
JJ
>--Original Message--
>It generally means a timeout has been exceeded (that's
what 0x80040e31
>means). You can increase the timeout to try and prevent
this issue.
>--
>HTH
>Jasper Smith (SQL Server MVP)
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>"JJ Wang" <jwang@.leapwireless.com> wrote in message
>news:09b401c371e7$6f7330b0$a101280a@.phx.gbl...
>Hi,
>I have a job that pulls data from a linked server into
>this server's database. I am working on sql server 2000.
>It generally runs fine, but twice it failed on this error
>message: 'OLE DB provider 'SQLOLEDB' reported an error.
>Execution terminated by the provider because a resource
>limit was reached. [SQLSTATE 42000] (Error 7399)
>[SQLSTATE 01000] (Error 7312) OLE DB error trace [OLE/DB
>Provider 'SQLOLEDB' ICommandText::Execute returned
>0x80040e31: Execution terminated by the provider because
>a resource limit was reached.]. [SQLSTATE 01000] (Error
>7300). The step failed.'
>When it says resource limit was reached, was it
>complaining the number of connections at the linked server
>has reached the limit?
>Many thanks.
>JJ
>
>.
>
Friday, February 24, 2012
JDBC sample code using named pipe and SQLServer 2005 driver?
Hi,
Does anybody have a working Java code sample that connects to an SQLServer 2005 database on a remote host, via the default named pipe, from a client using the SQLServer 2005 JDBC driver? Could you post it, or a pointer to it?
I've gotten java.sql DriverManager.getConnection() to work fine with TCP/IP connections before. But I'm a newbie with named pipes, and unclear on how the connection string/properties are different. I've tried to piece it together from multiple docs and threads, but haven't found sample code that quite fits my situation. I think a simple working example would best clarify the syntax.
The server is not using SQL Express. Most SQLServer configuration options are defaults; the named pipes protocol is enabled.
Thanks
Hi Dan,
The Microsoft SQL Server 2005 JDBC Driver does not support connections over named pipes. It only supports TCP/IP connections.
--David Olix
|||David,Thanks for the info and your quick response.
I suggest mentioning this in the JDBC docs. I couldn't find it in my searching.
- Dan N.
Subscribe to:
Posts (Atom)