JDBC Driver issue: running

Showing posts with label running. Show all posts

Friday, March 30, 2012

Jobs

I have created several jobs which contains several steps inside it. Now with the schedule it runs very frequently and more than 100 jobs are running almost simulteneously. so I want to limit the number of jobs running at a time say at a time I want to run 10 jobs after that other 10 set and s
How can I do it help me ou
Regards
SunilYou can adapt schedules, or you can create a wrapper job. This wrapper job
can start other jobs on each own step using the sp_start_job system SP.
--
Dejan Sarka, SQL Server MVP
Please reply only to the newsgroups.
"Sunil" <anonymous@.discussions.microsoft.com> wrote in message
news:9250860D-15DE-408D-A5A8-3CA7FAD56CC4@.microsoft.com...
> I have created several jobs which contains several steps inside it. Now
with the schedule it runs very frequently and more than 100 jobs are running
almost simulteneously. so I want to limit the number of jobs running at a
time say at a time I want to run 10 jobs after that other 10 set and so
>
> How can I do it help me out
> Regards,
> Sunil

JOBS

Hi All,
I am currently running a job that backs up a database using
the following code
BACKUP DATABASE [Leads] TO DISK = N'\\mymachine\d$\backup\leads.bak' WITH INIT , NOUNLOAD ,
NAME = N'Leads backup2', SKIP , STATS = 10, noFORMAT
this most of the time works fine but every now and again it
complete's fine but keeps the database locked open, is
there any way to fix this'
Thanks PhilWhat exactly do you mean by "Locked Open"?
--
Andrew J. Kelly SQL MVP
"Phil" <harlequintp@.blazemail.com> wrote in message
news:051801c3fabf$38fedc30$a101280a@.phx.gbl...
> Hi All,
> I am currently running a job that backs up a database using
> the following code
> BACKUP DATABASE [Leads] TO DISK => N'\\mymachine\d$\backup\leads.bak' WITH INIT , NOUNLOAD ,
> NAME = N'Leads backup2', SKIP , STATS = 10, noFORMAT
> this most of the time works fine but every now and again it
> complete's fine but keeps the database locked open, is
> there any way to fix this'
> Thanks Phil|||Sorry I should of been a little clearer, what I mean is
although the job says that it has completed, if you look
at the locks section in the SQL Enterprise Window, you
can still see a lock on the database showing the code
featured below.
Thanks again for your help!
Phil
>--Original Message--
>What exactly do you mean by "Locked Open"?
>--
>Andrew J. Kelly SQL MVP
>
>"Phil" <harlequintp@.blazemail.com> wrote in message
>news:051801c3fabf$38fedc30$a101280a@.phx.gbl...
>> Hi All,
>> I am currently running a job that backs up a database
using
>> the following code
>> BACKUP DATABASE [Leads] TO DISK =>> N'\\mymachine\d$\backup\leads.bak' WITH INIT ,
NOUNLOAD ,
>> NAME = N'Leads backup2', SKIP , STATS = 10,
noFORMAT
>> this most of the time works fine but every now and
again it
>> complete's fine but keeps the database locked open, is
>> there any way to fix this'
>> Thanks Phil
>
>.
>|||You have to be even clear than that<g>. What type of lock does it have?
Are these locks causing problems? It is normal for any connection to a db
to have at least a shared lock on the db. You also have to refresh EM in
order for most of the windows to show up to date information.
--
Andrew J. Kelly SQL MVP
<anonymous@.discussions.microsoft.com> wrote in message
news:0bd801c3fb1f$b4c51a40$a401280a@.phx.gbl...
> Sorry I should of been a little clearer, what I mean is
> although the job says that it has completed, if you look
> at the locks section in the SQL Enterprise Window, you
> can still see a lock on the database showing the code
> featured below.
> Thanks again for your help!
> Phil
> >--Original Message--
> >What exactly do you mean by "Locked Open"?
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"Phil" <harlequintp@.blazemail.com> wrote in message
> >news:051801c3fabf$38fedc30$a101280a@.phx.gbl...
> >> Hi All,
> >>
> >> I am currently running a job that backs up a database
> using
> >> the following code
> >>
> >> BACKUP DATABASE [Leads] TO DISK => >> N'\\mymachine\d$\backup\leads.bak' WITH INIT ,
> NOUNLOAD ,
> >> NAME = N'Leads backup2', SKIP , STATS = 10,
> noFORMAT
> >>
> >> this most of the time works fine but every now and
> again it
> >> complete's fine but keeps the database locked open, is
> >> there any way to fix this'
> >>
> >> Thanks Phil
> >
> >
> >.
> >sql

Jobs

quote:

> I have created several jobs which contains several steps inside it. Now

with the schedule it runs very frequently and more than 100 jobs are running
almost simulteneously. so I want to limit the number of jobs running at a
time say at a time I want to run 10 jobs after that other 10 set and so

quote:

>
> How can I do it help me out
> Regards,
> Sunil

JOBS

Wednesday, March 28, 2012

Job Status Wrong

Hello,
In my Enterprise Manager i see one job that i know its running(i look
locally on server) and jobs status appear like job is not executing(job
status is wrong)
Is there any patch to apply to EM?
Thanks and best regards.
Hi
I take it that by wrong status, you mean it is showing as sleeping under
current activity in Enterprise Manager. This is quiet normal as Sql Server
pages in and out processes as it runs them. If you keep refreshing it you may
catch it as active.
If you want to check that it is actually doing something, you can monitor it
with profiler or if you double click on the current activity, you get details
of the current SQL statement being performed. If you refresh that you should
see it change.
Hope this helps
John
"CC&JM" wrote:

> Hello,
> In my Enterprise Manager i see one job that i know its running(i look
> locally on server) and jobs status appear like job is not executing(job
> status is wrong)
> Is there any patch to apply to EM?
> Thanks and best regards.
|||Hello John,
Thanks for your answer, now i see the status of the job quit well but
yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
Date" showed 12:00.
I know that the problem was with my EM because in the EM of my partner i saw
the job status normally.
Thanks John,
Best regards
"John Bandettini" wrote:
[vbcol=seagreen]
> Hi
> I take it that by wrong status, you mean it is showing as sleeping under
> current activity in Enterprise Manager. This is quiet normal as Sql Server
> pages in and out processes as it runs them. If you keep refreshing it you may
> catch it as active.
> If you want to check that it is actually doing something, you can monitor it
> with profiler or if you double click on the current activity, you get details
> of the current SQL statement being performed. If you refresh that you should
> see it change.
> Hope this helps
> John
> "CC&JM" wrote:
|||Hi
I misunderstood your problem, I thought you were looking at current
activity. If you were looking at jobs and the job did not seem to be running,
did you refresh the display? Once you have opened something in Enterprise
manager, like jobs it will not automatically refresh. You need to either
right click and choose refresh or press F5.
Regards
John
"CC&JM" wrote:
[vbcol=seagreen]
> Hello John,
> Thanks for your answer, now i see the status of the job quit well but
> yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
> and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
> Date" showed 12:00.
> I know that the problem was with my EM because in the EM of my partner i saw
> the job status normally.
> Thanks John,
> Best regards
> "John Bandettini" wrote:
sql

Job Status Wrong

Hello,
In my Enterprise Manager i see one job that i know its running(i look
locally on server) and jobs status appear like job is not executing(job
status is wrong)
Is there any patch to apply to EM?
Thanks and best regards.Hi
I take it that by wrong status, you mean it is showing as sleeping under
current activity in Enterprise Manager. This is quiet normal as Sql Server
pages in and out processes as it runs them. If you keep refreshing it you may
catch it as active.
If you want to check that it is actually doing something, you can monitor it
with profiler or if you double click on the current activity, you get details
of the current SQL statement being performed. If you refresh that you should
see it change.
Hope this helps
John
"CC&JM" wrote:
> Hello,
> In my Enterprise Manager i see one job that i know its running(i look
> locally on server) and jobs status appear like job is not executing(job
> status is wrong)
> Is there any patch to apply to EM?
> Thanks and best regards.|||Hello John,
Thanks for your answer, now i see the status of the job quit well but
yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
Date" showed 12:00.
I know that the problem was with my EM because in the EM of my partner i saw
the job status normally.
Thanks John,
Best regards
"John Bandettini" wrote:
> Hi
> I take it that by wrong status, you mean it is showing as sleeping under
> current activity in Enterprise Manager. This is quiet normal as Sql Server
> pages in and out processes as it runs them. If you keep refreshing it you may
> catch it as active.
> If you want to check that it is actually doing something, you can monitor it
> with profiler or if you double click on the current activity, you get details
> of the current SQL statement being performed. If you refresh that you should
> see it change.
> Hope this helps
> John
> "CC&JM" wrote:
> > Hello,
> >
> > In my Enterprise Manager i see one job that i know its running(i look
> > locally on server) and jobs status appear like job is not executing(job
> > status is wrong)
> > Is there any patch to apply to EM?
> >
> > Thanks and best regards.|||Hi
I misunderstood your problem, I thought you were looking at current
activity. If you were looking at jobs and the job did not seem to be running,
did you refresh the display? Once you have opened something in Enterprise
manager, like jobs it will not automatically refresh. You need to either
right click and choose refresh or press F5.
Regards
John
"CC&JM" wrote:
> Hello John,
> Thanks for your answer, now i see the status of the job quit well but
> yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
> and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
> Date" showed 12:00.
> I know that the problem was with my EM because in the EM of my partner i saw
> the job status normally.
> Thanks John,
> Best regards
> "John Bandettini" wrote:
> > Hi
> >
> > I take it that by wrong status, you mean it is showing as sleeping under
> > current activity in Enterprise Manager. This is quiet normal as Sql Server
> > pages in and out processes as it runs them. If you keep refreshing it you may
> > catch it as active.
> >
> > If you want to check that it is actually doing something, you can monitor it
> > with profiler or if you double click on the current activity, you get details
> > of the current SQL statement being performed. If you refresh that you should
> > see it change.
> >
> > Hope this helps
> >
> > John
> >
> > "CC&JM" wrote:
> >
> > > Hello,
> > >
> > > In my Enterprise Manager i see one job that i know its running(i look
> > > locally on server) and jobs status appear like job is not executing(job
> > > status is wrong)
> > > Is there any patch to apply to EM?
> > >
> > > Thanks and best regards.

Job Status Wrong

Hello,
In my Enterprise Manager i see one job that i know its running(i look
locally on server) and jobs status appear like job is not executing(job
status is wrong)
Is there any patch to apply to EM?
Thanks and best regards.Hi
I take it that by wrong status, you mean it is showing as sleeping under
current activity in Enterprise Manager. This is quiet normal as Sql Server
pages in and out processes as it runs them. If you keep refreshing it you ma
y
catch it as active.
If you want to check that it is actually doing something, you can monitor it
with profiler or if you double click on the current activity, you get detail
s
of the current SQL statement being performed. If you refresh that you should
see it change.
Hope this helps
John
"CC&JM" wrote:

> Hello,
> In my Enterprise Manager i see one job that i know its running(i look
> locally on server) and jobs status appear like job is not executing(job
> status is wrong)
> Is there any patch to apply to EM?
> Thanks and best regards.|||Hello John,
Thanks for your answer, now i see the status of the job quit well but
yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Run
Date" showed 12:00.
I know that the problem was with my EM because in the EM of my partner i saw
the job status normally.
Thanks John,
Best regards
"John Bandettini" wrote:
[vbcol=seagreen]
> Hi
> I take it that by wrong status, you mean it is showing as sleeping under
> current activity in Enterprise Manager. This is quiet normal as Sql Server
> pages in and out processes as it runs them. If you keep refreshing it you
may
> catch it as active.
> If you want to check that it is actually doing something, you can monitor
it
> with profiler or if you double click on the current activity, you get deta
ils
> of the current SQL statement being performed. If you refresh that you shou
ld
> see it change.
> Hope this helps
> John
> "CC&JM" wrote:
>|||Hi
I misunderstood your problem, I thought you were looking at current
activity. If you were looking at jobs and the job did not seem to be running
,
did you refresh the display? Once you have opened something in Enterprise
manager, like jobs it will not automatically refresh. You need to either
right click and choose refresh or press F5.
Regards
John
"CC&JM" wrote:
[vbcol=seagreen]
> Hello John,
> Thanks for your answer, now i see the status of the job quit well but
> yesterday i had a job that runs 4 example at 10:00 12:00 14:00 and so on..
> and at 18:00 when i look at EM "Last Run Status" showed 10:00 and "Next Ru
n
> Date" showed 12:00.
> I know that the problem was with my EM because in the EM of my partner i s
aw
> the job status normally.
> Thanks John,
> Best regards
> "John Bandettini" wrote:
>

Job Status Suspended

i am trying to code a proc that tests whether a job is running. i
understand how to get job status from the xp_sqlagent_enum_jobs via the
current execution status and i also understand that status = 4 means
the job is idle. what does status =5 (suspended) mean? The BOL
information seems to indicate that the job isnt running when status is
either 4 or 5 (status 0 = not idle and not suspended)
thanks
markHow about this bit of TSQL
select step_id FROM
msdb.dbo.sysjobhistory
WHERE instance_id =
(SELECT max(instance_id) FROM msdb.dbo.sysjobhistory h
INNER JOIN msdb.dbo.sysjobs j ON h.job_id=j.job_id
WHERE j.[name] = 'Your Job Name')
This will extract the current step that a job is on. If a has completed, the
step_id will be zero. If it hasn't completed, the step_id will be non-zero.
"markfcook@.gmail.com" wrote:

> i am trying to code a proc that tests whether a job is running. i
> understand how to get job status from the xp_sqlagent_enum_jobs via the
> current execution status and i also understand that status = 4 means
> the job is idle. what does status =5 (suspended) mean? The BOL
> information seems to indicate that the job isnt running when status is
> either 4 or 5 (status 0 = not idle and not suspended)
> thanks
> mark
>

job status

Hi,
Is it possible to find out the current status of a job (sql 2000 sql job),
i.e. whether it is idle/running/failed, etc
Thanks in advance!!Try giving select privilages to msdb..sysjobhistory and msdb..sysjobs
tables.
select name,run_status from msdb..sysjobhistory a,sysjobs b
where a.job_id=b.job_id
and name='name of the job'
explanation for run_status:- You could write a case statement with
run_status with below description.
0 = Failed
1 = Succeeded
2 = Retry
3 = Canceled
4 = In progress
Thanks
Hari
"AppleDopod" <hk_007@.hotmail.com> wrote in message
news:%23NlymnYUHHA.4872@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Is it possible to find out the current status of a job (sql 2000 sql job),
> i.e. whether it is idle/running/failed, etc
> Thanks in advance!!
>|||Please have a look at this script:
http://www.replicationanswers.com/Downloads/KillRunningJobs.txt. You can
use -- 1 = Executing, 2 = Waiting For Thread, 3 = Between Retries, 4 = Idle,
5 = Suspended, 6 = [obsolete], 7 = PerformingCompletionActions to modify it
as you like.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.comsql

job status

Hi,
Is it possible to find out the current status of a job (sql 2000 sql job),
i.e. whether it is idle/running/failed, etc
Thanks in advance!!Try giving select privilages to msdb..sysjobhistory and msdb..sysjobs
tables.
select name,run_status from msdb..sysjobhistory a,sysjobs b
where a.job_id=b.job_id
and name='name of the job'
explanation for run_status:- You could write a case statement with
run_status with below description.
0 = Failed
1 = Succeeded
2 = Retry
3 = Canceled
4 = In progress
Thanks
Hari
"AppleDopod" <hk_007@.hotmail.com> wrote in message
news:%23NlymnYUHHA.4872@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Is it possible to find out the current status of a job (sql 2000 sql job),
> i.e. whether it is idle/running/failed, etc
> Thanks in advance!!
>|||Please have a look at this script:
http://www.replicationanswers.com/D...unningJobs.txt. You can
use -- 1 = Executing, 2 = Waiting For Thread, 3 = Between Retries, 4 = Idle,
5 = Suspended, 6 = [obsolete], 7 = PerformingCompletionActions to modify
it
as you like.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

job status

Hi,
Is it possible to find out the current status of a job (sql 2000 sql job),
i.e. whether it is idle/running/failed, etc
Thanks in advance!!
Try giving select privilages to msdb..sysjobhistory and msdb..sysjobs
tables.
select name,run_status from msdb..sysjobhistory a,sysjobs b
where a.job_id=b.job_id
and name='name of the job'
explanation for run_status:- You could write a case statement with
run_status with below description.
0 = Failed
1 = Succeeded
2 = Retry
3 = Canceled
4 = In progress
Thanks
Hari
"AppleDopod" <hk_007@.hotmail.com> wrote in message
news:%23NlymnYUHHA.4872@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Is it possible to find out the current status of a job (sql 2000 sql job),
> i.e. whether it is idle/running/failed, etc
> Thanks in advance!!
>
|||Please have a look at this script:
http://www.replicationanswers.com/Downloads/KillRunningJobs.txt. You can
use -- 1 = Executing, 2 = Waiting For Thread, 3 = Between Retries, 4 = Idle,
5 = Suspended, 6 = [obsolete], 7 = PerformingCompletionActions to modify it
as you like.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Monday, March 26, 2012

Job scheduling

As opposed to running a job every X minutes, is there a way to schedule a
job to re-start X minutes after it finishes successfully ?
Is this the correct newsgroup for this question ?Untested, but it should work:
schedule the job to run every 1 minute
Add an additional step to the end of the job that will only execute if =
the steps ahead of the job complete successfully that does a WAITFOR =
DELAY.
--=20
Keith
"rob" <rwc1960@.bellsouth.net> wrote in message =
news:XBg6c.47748$xL3.43022@.bignews1.bellsouth.net...
> As opposed to running a job every X minutes, is there a way to =
schedule a
> job to re-start X minutes after it finishes successfully ?
>=20
> Is this the correct newsgroup for this question ?
>=20
>=20
>|||Another option could be to end each job with a jobstep which executes
sp_add_jobschedule to schedule the job again, based on the desired interval.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:eobvl4ODEHA.3584@.TK2MSFTNGP11.phx.gbl...
Untested, but it should work:
schedule the job to run every 1 minute
Add an additional step to the end of the job that will only execute if the
steps ahead of the job complete successfully that does a WAITFOR DELAY.
Keith
"rob" <rwc1960@.bellsouth.net> wrote in message
news:XBg6c.47748$xL3.43022@.bignews1.bellsouth.net...
> As opposed to running a job every X minutes, is there a way to schedule a
> job to re-start X minutes after it finishes successfully ?
> Is this the correct newsgroup for this question ?
>
>

Job Scheduler

Hello,

I am have problems running a couple of jobs. It makes no sense. I have checked and made sure the agent service is running the same user level permissions as I am. I run the job manually from SMS and it works fine.

User is a Windows Login.

Any suggestions would be greatly appreciated.

Date 6/11/2007 6:00:01 AM
Log Job History (BidBackLog)

Step ID 1
Server TWSQLRPTS
Job Name BidBackLog
Step Name Step1
Duration 00:00:21
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: TWDOMAIN\SQLADMIN. ... 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 6:00:01 AM Error: 2007-06-11 06:00:22.50 Code: 0xC0202009 Source: BidBacklog Connection manager "TWSQLRPTS.HomeBASE" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login failed for user 'TWDOMAIN\SQLADMIN'.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Cannot open database "HomeBASE" requested by the login. The login failed.". End Error Error: 2007-06-11 06:00:22.50 Code: 0xC020801C Source: DTSTask_DTSDataPumpTask_1 OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager ... The package execution fa... The step failed.

TrussworksLeo1 wrote:

Hello,
I am have problems running a couple of jobs. It makes no sense. I have checked and made sure the agent service is running the same user level permissions as I am. I run the job manually from SMS and it works fine.
User is a Windows Login.
Any suggestions would be greatly appreciated.
Date 6/11/2007 6:00:01 AM
Log Job History (BidBackLog)
Step ID 1
Server TWSQLRPTS
Job Name BidBackLog
Step Name Step1
Duration 00:00:21
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: TWDOMAIN\SQLADMIN. ... 9.00.3042.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 6:00:01 AM Error: 2007-06-11 06:00:22.50 Code: 0xC0202009 Source: BidBacklog Connection manager "TWSQLRPTS.HomeBASE" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login failed for user 'TWDOMAIN\SQLADMIN'.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Cannot open database "HomeBASE" requested by the login. The login failed.". End Error Error: 2007-06-11 06:00:22.50 Code: 0xC020801C Source: DTSTask_DTSDataPumpTask_1 OLE DB Source [1] Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager ... The package execution fa... The step failed.

The user, TWDOMAIN\SQLADMIN doesn't have access to the databases... You're likely using windows authentication for your database connections, and when Agent runs the job, the user account is that of the SQL Server service account. (In this case ...\SQLADMIN)|||

Phil,

Thanks for the reply.

I have checked the permissions. The user is the owner of the databases that it is writting to, but it reads from a database that has mirroring setup. It will not let me change permisssions on that database. Do you know a way around this?

Thanks, Leo

Friday, March 23, 2012

job running with status performing completion action

I noticed this morning that
I have a job status "performing completion action" for one of mine sql scheduled task job.

The job executes a dts pkg (which I just rum manually, and all worked fine)

What does it mean?, I can not stop this job and refresh is not working ether.
What I can do?

Thank you,
Lclose your em and reopen it. it does not refresh very well.|||Sorry,
What is a EM and how I can close it / reopen it.
I'm a user, who is just trying to find out more about processies.

Thank you|||enterprise manager has a problem refreshing sometimes. if you are looking at jobs, i assume this is the application you are looking at.|||I did close it, the message still there.|||close your em and reopen it. it does not refresh very well...or right-click on the job and choose "refresh job" ;)

I also had this happen recently because our jobs are set up to send email notifications when the job is complete, and the servers(s) in question were unable to send emails because the network was having email problems. I ended up stopping and starting the mail service (xp_stopmail, xp_startmail) and the problem was fixed.

Then I had to send an abusive email off to the network admin group for not letting us know when they were going to intentionally damage the network.|||THANK YOU FOR ALL SUGGESTIONS, BUT WE HAD TO RESTART THE SERVER.
AS WELL AS OUT MAIL SERVER WAS REBOOTED.

jOB TASK WAS NOT ABLE TO SEND AN E-MAIL DUE TO MAIL SERVER FAILRE,

THANK YOU|||Yeah, I was gonna say...

issue the xp_stopmail and xp_startmail on the affected server, OR reboot the entire infrastructure.

either one will work ;)

Job running status

In SQL 2000, go to Management, than Jobs, you will see a list of all jobs and their running status. I would like to programmatically display the same on my web page. I can call sysjobs table to get the jobs and use sysjobschedules to determine whether it's been scheduled or not. Then use sysjobhistory to obtain their running history. But how and where do I get the Next Run Date information? Is this calculated or stored somewhere?

Can anyone give me some help on how to work with sysjobs, sysjobschedules, and sysjobhistory tables? All I am trying to do is to build a web-based app that does the same thing as the Enterprise Manager is doing - create and schedule a job, and monitor the job status.

Thanks a lot!

Penn

Performing query directly to system tables is not recommended, as the schema of system tables/views may change even between different builds. Instead, you can use some system procedures to get detailed information about agent jobs, for example:

exec msdb..sp_help_job @.job_name='Expired subscription clean up'

So you can call such system procedures from your code using SqlDataAdapter and then fill the result sets into DataSet for future using. For more information about system procedures, please refer to:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_sp_00_519s.asp

job running SSIS package keeps failing but the SSIS package by itself runs perfectly fine

Hey, I've a few jobs which call SSIS packages. If I run the SSIS package, it runs fine but if I try to run the job which calls this package, it fails. Can someone help me troubleshoot this issue? None of my jobs that call an SSIS package work. All of them fail.

Thank you

Tej

Need to add some mopre to the description of my problem. These packages were originally on a SQL 2000 server. I migrated them to SSIS. When I run a package it says

'SSIS package <package name> starting.
Error: 0x0 at <package name>: System.Runtime.InteropServices.COMException (0x80040427): Execution was canceled by user.
at DTS.PackageClass.Execute()
at Microsoft.SqlServer.Dts.Tasks.Exec80PackageTask.Exec80PackageTask.ExecuteThread() Task failed: <package name> Warning: 0x80019002
at <package name>: The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors. SSIS package <package name> finished: Failure.'

This is in Article 904796. But the thing is these packages were never MetaDataServices.. I had them on SQL Server and now on a file system. I imported them in a SSIS project and have it on a share. but it still gives me the above error.

Thank you

Tej

|||

I have the same problem. Except that I have had these packages working prior to this failure. I tried re-installing the SQL Server 200 DTS Designer components as suggested in the article, but to no avail. Same result. I will be very interested if you get any helpful responses.

|||

Hey Peter. First of all, when I put these in MSDB, they worked fine. Also, I didn't try this but try to look for the security part for every package in its properties. It's encrypted with User Key or something. Remove the encryption and it should be fine.

Let me know how it goes. Thanks

|||

so, sounds like the common issue of getting agent and package permissions in sync.

for others, the KB
An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step

http://support.microsoft.com/?kbid=918760

|||

I have the same problem.

My solution is to click on the "Load DTS Package Internally" and it works perfectly. Hope this would help.

|||Hey. I think I've figured out what the problem is. SSIS by default stores the packes encrypted by user key. It's in th eproperties of the package. If you use, SQL Server encryption which I used, it removes that encryption. Also, if you want to use th efile system for this, you might want to go to the properties of the package and say no encryption instead of encrypting by user key. This should work just fine... Thank you

job running SSIS package keeps failing but the SSIS package by itself runs perfectly fine

Thank you

Tej

Need to add some mopre to the description of my problem. These packages were originally on a SQL 2000 server. I migrated them to SSIS. When I run a package it says

Thank you

Tej

|||

Let me know how it goes. Thanks

|||

so, sounds like the common issue of getting agent and package permissions in sync.

for others, the KB
An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step

http://support.microsoft.com/?kbid=918760

|||

I have the same problem.

My solution is to click on the "Load DTS Package Internally" and it works perfectly. Hope this would help.

job running SSIS package keeps failing but the SSIS package by itself runs perfectly fine

Thank you

Tej

Need to add some mopre to the description of my problem. These packages were originally on a SQL 2000 server. I migrated them to SSIS. When I run a package it says

Thank you

Tej

|||

Let me know how it goes. Thanks

|||

so, sounds like the common issue of getting agent and package permissions in sync.

for others, the KB
An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step

http://support.microsoft.com/?kbid=918760

|||

I have the same problem.

My solution is to click on the "Load DTS Package Internally" and it works perfectly. Hope this would help.

JOb running SSIS package

I have an issue when a job is scheduled to run a SSIS package. The package (exporte a table to a text file) runs fine from microsoft visual studio but when i create a job and run it, i get the following error:

[298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'VOLCANO\Administrator', error code 0x534. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

Can you tell me what operating system you have? Windows 2000, Windows 2003?

Thanks
Ovidiu Burlacu

|||i'm using windows 2003. I found out what was wrong, when I create the job i changed the owner to 'sa' instead and it now works fine. Thanks for your help anyway.
|||when i turn on the computer i get error messages about an open file? everything listed in the menu includes this axel but i canoot open it and I need to fix this error, it is preventing me from installing a camera. any help?

|||

This forum (and the error above) is for SQL Server Integration Services - is your question related to that?

JOb running SSIS package

[298] SQLServer Error: 15404, Could not obtain information about Windows NT group/user 'VOLCANO\Administrator', error code 0x534. [SQLSTATE 42000] (ConnIsLoginSysAdmin)

Can you tell me what operating system you have? Windows 2000, Windows 2003?

Thanks
Ovidiu Burlacu

|||i'm using windows 2003. I found out what was wrong, when I create the job i changed the owner to 'sa' instead and it now works fine. Thanks for your help anyway.|||when i turn on the computer i get error messages about an open file? everything listed in the menu includes this axel but i canoot open it and I need to fix this error, it is preventing me from installing a camera. any help?

|||

This forum (and the error above) is for SQL Server Integration Services - is your question related to that?

Friday, March 30, 2012

Jobs

JOBS

Jobs

JOBS

Wednesday, March 28, 2012

Job Status Wrong

Job Status Wrong

Job Status Wrong

Job Status Suspended

job status

job status

job status

Monday, March 26, 2012

Job scheduling

Job Scheduler

Friday, March 23, 2012

job running with status performing completion action

Job running status

job running SSIS package keeps failing but the SSIS package by itself runs perfectly fine

job running SSIS package keeps failing but the SSIS package by itself runs perfectly fine

job running SSIS package keeps failing but the SSIS package by itself runs perfectly fine

JOb running SSIS package

JOb running SSIS package

JDBC Driver issue

Blog Archive

About Me