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

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 alm
ost 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,
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...

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

---

Job that runs past the next scheduled start time

Hello group
I have a problem that I'm considering if the SQL Server Agent and Job
scheduling can help me solve.
I need to check some status very often (approximately every 30. sec.). I
have learned that you can get the job sceduling to start this often, so that
should not be a problem.
Normaly the job will just check this status and then stop.
Once in a while the status will signal that further processing should take
place. This processing may last more than 30 seconds, and therefore last
beyond the next start time of the job.
Is this a problem?
Will I have the same job running multiple times? That is not good.
When will the next job then start? Will it start 30 sec. after the long
running job completed, or will jobs queue op while the long running job is
processing so that I will get multiple starts when the first job completes?
I hope that you can understand my issue.
Regards
Anders> Will I have the same job running multiple times?
No. Agent is simple in this regard. If the job is already running when it is supposed to start, then
Agent will *not* start another instance of that job.
> When will the next job then start? Will it start 30 sec. after the long running job completed, or
> will jobs queue op while the long running job is processing so that I will get multiple starts
> when the first job completes?
Neither. It will start when it is supposed to. Say for simplicity of this example that you want to
start it every minute. Now, you have one occasion where it starts at 13:00:00 and it runs for 110
seconds. The job will not start at 13:01:00 since it is already running. As I said, this occasion
takes 110 seconds so it finishes at 13:01:50. Next time it is supposed to start is 13:02:00, and now
it isn't running so Agent will start it.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Anders K. Olsen" <akol_dk@.hotmail.com> wrote in message
news:OM4PQuc%23HHA.700@.TK2MSFTNGP05.phx.gbl...
> Hello group
> I have a problem that I'm considering if the SQL Server Agent and Job scheduling can help me
> solve.
> I need to check some status very often (approximately every 30. sec.). I have learned that you can
> get the job sceduling to start this often, so that should not be a problem.
> Normaly the job will just check this status and then stop.
> Once in a while the status will signal that further processing should take place. This processing
> may last more than 30 seconds, and therefore last beyond the next start time of the job.
> Is this a problem?
> Will I have the same job running multiple times? That is not good.
> When will the next job then start? Will it start 30 sec. after the long running job completed, or
> will jobs queue op while the long running job is processing so that I will get multiple starts
> when the first job completes?
> I hope that you can understand my issue.
> Regards
> Anders
>|||Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23GdwCgd%23HHA.1208@.TK2MSFTNGP03.phx.gbl...
>> Will I have the same job running multiple times?
> No. Agent is simple in this regard. If the job is already running when it
> is supposed to start, then Agent will *not* start another instance of that
> job.
Sometimes simple is good :-)
>> When will the next job then start? Will it start 30 sec. after the long
>> running job completed, or will jobs queue op while the long running job
>> is processing so that I will get multiple starts when the first job
>> completes?
> Neither. It will start when it is supposed to. Say for simplicity of this
> example that you want to start it every minute. Now, you have one occasion
> where it starts at 13:00:00 and it runs for 110 seconds. The job will not
> start at 13:01:00 since it is already running. As I said, this occasion
> takes 110 seconds so it finishes at 13:01:50. Next time it is supposed to
> start is 13:02:00, and now it isn't running so Agent will start it.
This is fine for our purposes, so we will continue along this line.
Thank you for your help.
Regards
Anderssql

Job Sequencing ?

I have a job that runs a batch file, tsql step, and then another batch file.
My question is will the agent say the first step is complete and move on
when it starts the batch file or will it know to wait until after the batch
has ran to start the second step?
TIA
--
nivekHi
It waits for the prior step to finish.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"nivek" <eckart_612@.hotmail.com> wrote in message
news:36GdnYIXz77QzN3fRVn-3A@.centurytel.net...
> I have a job that runs a batch file, tsql step, and then another batch
file.
> My question is will the agent say the first step is complete and move on
> when it starts the batch file or will it know to wait until after the
batch
> has ran to start the second step?
> TIA
> --
> nivek
>
>
>

Job Sequencing ?

I have a job that runs a batch file, tsql step, and then another batch file.
My question is will the agent say the first step is complete and move on
when it starts the batch file or will it know to wait until after the batch
has ran to start the second step?
TIA
nivekHi
It waits for the prior step to finish.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"nivek" <eckart_612@.hotmail.com> wrote in message
news:36GdnYIXz77QzN3fRVn-3A@.centurytel.net...
> I have a job that runs a batch file, tsql step, and then another batch
file.
> My question is will the agent say the first step is complete and move on
> when it starts the batch file or will it know to wait until after the
batch
> has ran to start the second step?
> TIA
> --
> nivek
>
>
>

Job Sequencing ?

I have a job that runs a batch file, tsql step, and then another batch file.
My question is will the agent say the first step is complete and move on
when it starts the batch file or will it know to wait until after the batch
has ran to start the second step?
TIA
nivek
Hi
It waits for the prior step to finish.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"nivek" <eckart_612@.hotmail.com> wrote in message
news:36GdnYIXz77QzN3fRVn-3A@.centurytel.net...
> I have a job that runs a batch file, tsql step, and then another batch
file.
> My question is will the agent say the first step is complete and move on
> when it starts the batch file or will it know to wait until after the
batch
> has ran to start the second step?
> TIA
> --
> nivek
>
>
>
sql

Job Scheduler

Hello,
Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
the first three weeks of the month and for the last week of the month have
the job run every 90 minutes.
Thanks in advance
stone outI doubt that you can do that via EM. Perhaps you wil, have to run some
script that determines a week's number and changes the schedule accordingly
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out|||You may be able to do this with multiple schedules.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out|||stoney wrote:
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2
> PM for the first three weeks of the month and for the last week of
> the month have the job run every 90 minutes.
> Thanks in advance
> stone out
Set up the schedule to run every 90 minutes. Using T-SQL, determine
where you are in the month and complete or terminate the script
accordingly.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Job Scheduler

Hello,
Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
the first three weeks of the month and for the last week of the month have
the job run every 90 minutes.
Thanks in advance
stone outI doubt that you can do that via EM. Perhaps you wil, have to run some
script that determines a week's number and changes the schedule accordingly
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out|||You may be able to do this with multiple schedules.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out|||stoney wrote:
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2
> PM for the first three weeks of the month and for the last week of
> the month have the job run every 90 minutes.
> Thanks in advance
> stone out
Set up the schedule to run every 90 minutes. Using T-SQL, determine
where you are in the month and complete or terminate the script
accordingly.
--
David Gugick
Quest Software
www.imceda.com
www.quest.comsql

Job Scheduler

Hello,
Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
the first three weeks of the month and for the last week of the month have
the job run every 90 minutes.
Thanks in advance
stone out
I doubt that you can do that via EM. Perhaps you wil, have to run some
script that determines a week's number and changes the schedule accordingly
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out
|||You may be able to do this with multiple schedules.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"stoney" <stoney@.discussions.microsoft.com> wrote in message
news:81122877-29AB-4F21-82E0-A0F6F337269D@.microsoft.com...
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2 PM for
> the first three weeks of the month and for the last week of the month have
> the job run every 90 minutes.
> Thanks in advance
> stone out
|||stoney wrote:
> Hello,
> Is it possible for me to schedule a job that runs @. 8 AM, 11 AM & 2
> PM for the first three weeks of the month and for the last week of
> the month have the job run every 90 minutes.
> Thanks in advance
> stone out
Set up the schedule to run every 90 minutes. Using T-SQL, determine
where you are in the month and complete or terminate the script
accordingly.
David Gugick
Quest Software
www.imceda.com
www.quest.com

Job runs succesfully, but database not updated

I have created a job to run an executable. This executable has to read an
Excelsheet in order to import the data into the database.
I got the message that the job has run succesfully, but the data is not in
the database.
My job looks like this:
c:\mydirectory\bin\excelimport.exe /Slocal) /D:DataComp 20051020
S: --> the local server
D:--> database name
Thank you for your help.
Kind regards,
LoHi
You don't say where the job expects the excel file to be! Have you looks at
SQL profiler to see what is happening when the program runs?
John
"lo" wrote:

> I have created a job to run an executable. This executable has to read an
> Excelsheet in order to import the data into the database.
> I got the message that the job has run succesfully, but the data is not in
> the database.
> My job looks like this:
> c:\mydirectory\bin\excelimport.exe /Slocal) /D:DataComp 20051020
> S: --> the local server
> D:--> database name
> --
> Thank you for your help.
> Kind regards,
> Lo|||I have run the profiler, but here as well I get no error message once or eve
r.
I have updated the string like this
c:\mydirectory\bin\excelimport.exe /Slocal) /D:[DataComp 20051020]
The path to the excel sheet is in the excelimport.exe.
Do you have any other idea'
Thank you for your help.
Kind regards,
Lo
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You don't say where the job expects the excel file to be! Have you looks a
t
> SQL profiler to see what is happening when the program runs?
> John
> "lo" wrote:
>|||Hi
I would not expect any error messages from SQL Profile, just the information
about which database it is running against and what SQL statements are being
executed by the job. You can then confirm that it is not connecting to the
correct database or that it is not finding the file.
Do you have a dynamic properties task to change the destination database?
You may want to see http://www.sqldts.com/default.aspx?252
John
"lo" wrote:
[vbcol=seagreen]
> I have run the profiler, but here as well I get no error message once or e
ver.
> I have updated the string like this
> c:\mydirectory\bin\excelimport.exe /Slocal) /D:[DataComp 20051020]
> The path to the excel sheet is in the excelimport.exe.
> Do you have any other idea'
>
> --
> Thank you for your help.
> Kind regards,
> Lo
>
> "John Bell" wrote:
>

Job runs succesfully, but database not updated

I have created a job to run an executable. This executable has to read an
Excelsheet in order to import the data into the database.
I got the message that the job has run succesfully, but the data is not in
the database.
My job looks like this:
c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
S: --> the local server
D:--> database name
--
Thank you for your help.
Kind regards,
LoHi
You don't say where the job expects the excel file to be! Have you looks at
SQL profiler to see what is happening when the program runs?
John
"lo" wrote:
> I have created a job to run an executable. This executable has to read an
> Excelsheet in order to import the data into the database.
> I got the message that the job has run succesfully, but the data is not in
> the database.
> My job looks like this:
> c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
> S: --> the local server
> D:--> database name
> --
> Thank you for your help.
> Kind regards,
> Lo|||I have run the profiler, but here as well I get no error message once or ever.
I have updated the string like this
c:\mydirectory\bin\excelimport.exe /S:(local) /D:[DataComp 20051020]
The path to the excel sheet is in the excelimport.exe.
Do you have any other idea'
Thank you for your help.
Kind regards,
Lo
"John Bell" wrote:
> Hi
> You don't say where the job expects the excel file to be! Have you looks at
> SQL profiler to see what is happening when the program runs?
> John
> "lo" wrote:
> > I have created a job to run an executable. This executable has to read an
> > Excelsheet in order to import the data into the database.
> > I got the message that the job has run succesfully, but the data is not in
> > the database.
> > My job looks like this:
> > c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
> > S: --> the local server
> > D:--> database name
> >
> > --
> > Thank you for your help.
> >
> > Kind regards,
> >
> > Lo|||Hi
I would not expect any error messages from SQL Profile, just the information
about which database it is running against and what SQL statements are being
executed by the job. You can then confirm that it is not connecting to the
correct database or that it is not finding the file.
Do you have a dynamic properties task to change the destination database?
You may want to see http://www.sqldts.com/default.aspx?252
John
"lo" wrote:
> I have run the profiler, but here as well I get no error message once or ever.
> I have updated the string like this
> c:\mydirectory\bin\excelimport.exe /S:(local) /D:[DataComp 20051020]
> The path to the excel sheet is in the excelimport.exe.
> Do you have any other idea'
>
> --
> Thank you for your help.
> Kind regards,
> Lo
>
> "John Bell" wrote:
> > Hi
> >
> > You don't say where the job expects the excel file to be! Have you looks at
> > SQL profiler to see what is happening when the program runs?
> >
> > John
> >
> > "lo" wrote:
> >
> > > I have created a job to run an executable. This executable has to read an
> > > Excelsheet in order to import the data into the database.
> > > I got the message that the job has run succesfully, but the data is not in
> > > the database.
> > > My job looks like this:
> > > c:\mydirectory\bin\excelimport.exe /S:(local) /D:DataComp 20051020
> > > S: --> the local server
> > > D:--> database name
> > >
> > > --
> > > Thank you for your help.
> > >
> > > Kind regards,
> > >
> > > Lo

job runs OK without schedule, does not complete with schedule

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

Job runs for a long time in SQL Server Agent 2005

I have an exe in C# in .Net 1.1. This accesses an Oracle database and an SQL Server 2000 database. It is scheduled in SQL Server Agent. It runs for normally 30 seconds and stops

Recently we migrated the database to SQL Server 2005. We created this job manually in SQL Server Agent. Even after running for 3 minutes it never stops (abnormal)

However this exe runs normally in the Windows 2003 scheduler and the command prompt.

Am stumped for an answer.

Any help

Thanks and regards

jarathna

Do have relevant oracle client drivers installed on this SQL 2005 instance?

Ibelieve this is something related to the Operating system related process, if this is scheduled via SQLagent job then ensure SQLserver serivces do have relevant privileges on that C# & Oracle based components share.

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

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 yousql

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

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

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 Run Time Notifications

Is there a way to send an email alert if a dts job runs
for more than a specific time. For example, I want to
send an alert if a job runs for more than 2 minutes.As the first step of your DTS job you could start another job that simply
waits 2 minutes (waitfor delay '00:02:00') and then checks the execution
status of the DTS job (you could use sp_help_job). It could then alert if
the job was still running (assuming the DTS job wouldn't start again before
the monitor finished). I'm sure there's a slicker way but that would be
relatively simple and robust
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Tim Savery" <Tim.Savery@.mbna.com> wrote in message
news:05a701c3a2df$b7115900$a001280a@.phx.gbl...
Is there a way to send an email alert if a dts job runs
for more than a specific time. For example, I want to
send an alert if a job runs for more than 2 minutes.|||To be sure whether the job is still in the current execution, you can
execute msdb..sp_help_job before the wait, and then check execute
sp_help_job and check last_run_date and last_run_time. If the job has been
restarted, these two values would have been changed.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Jasper Smith" <jasper_smith9@.hotmail.com> wrote in message
news:eiBPqZxoDHA.360@.TK2MSFTNGP12.phx.gbl...
> As the first step of your DTS job you could start another job that simply
> waits 2 minutes (waitfor delay '00:02:00') and then checks the execution
> status of the DTS job (you could use sp_help_job). It could then alert if
> the job was still running (assuming the DTS job wouldn't start again
before
> the monitor finished). I'm sure there's a slicker way but that would be
> relatively simple and robust
> --
> HTH
> Jasper Smith (SQL Server MVP)
> I support PASS - the definitive, global
> community for SQL Server professionals -
> http://www.sqlpass.org
> "Tim Savery" <Tim.Savery@.mbna.com> wrote in message
> news:05a701c3a2df$b7115900$a001280a@.phx.gbl...
> Is there a way to send an email alert if a dts job runs
> for more than a specific time. For example, I want to
> send an alert if a job runs for more than 2 minutes.
>

Job ran for -95444:-89:-43 hours ?

I have a nightly job that runs at 2.00 AM...On saturday night first it ran
for -95444:-89:-43 and again ran at 2.00 AM
I know this occured beacuse we went back one hr on saturday night at 2.00
AM...My question is why the job should run again resulting in a failed
status? SQL Server should not have run this the second time. I hope in SQL
2005 this does not happen.
Thanks,
RangaHi
This would depend on when/how the next run date is calculated. This may be
how the scheduler is designed to work. If you moved the job off the hour you
should not see this occurring.
John
"Ranga" wrote:

> I have a nightly job that runs at 2.00 AM...On saturday night first it ra
n
> for -95444:-89:-43 and again ran at 2.00 AM
> I know this occured beacuse we went back one hr on saturday night at 2.00
> AM...My question is why the job should run again resulting in a failed
> status? SQL Server should not have run this the second time. I hope in SQ
L
> 2005 this does not happen.
> Thanks,
> Ranga