How do you schedule stored procedures? I can see no way of linking them to the job scheduler.
Also, how do I time the stored proc. schedule to activate after a scheduled DTS package?
Thanks again guys!OK, I see how to schedule a stored proc...by just scheduling an execute command.
But I still cant see how to time this with the scheduling of a DTS package.|||You create a new DTS.
You drop your connection,
You drop "Execute SQL TASK". You write your SQL-query
(example: "exec myproc")
you choose "save as" and name your DTS.
Now you will have a DTS in the list, and you right click on it and choose "Scedule Package"
Good luck!|||Its possible to execute and schedule a stored procedure using job scheduler just mention SP name and select connected database, schedule it.
Showing posts with label time. Show all posts
Showing posts with label time. Show all posts
Friday, March 30, 2012
Scheduling SQL Server 2005 report server
I'm looking a way to schedule a report to be generated in pre-define time and push it out to my users through email or file share any format (excell, Word, etc). Any help would be greatly appreciated.
When you view the report in a browser you'll see four tabs - View, Properties, History, Subscriptions. Create a new subscription and then enter the recipient (actual email address required) and select the Render Format as Excel, PDF, Web Archive etc. You can also set the date, time and frequency of the subscription.
Hope this helps,
Aidan
Scheduling reports to run
Is there a way to schedule reports to run on a specif day and time and save them to excel files?
Hello John,
Yes, of course you can.
Open Report Manager. (http://ServerName/Reports) and drill down to your report you want to schedule. Click on the Properties tab from the tob and the Data Sources tab from the left. Verify that you connection is correct and select 'Credentials stored securely in the report server' and give it an account to run the report. Then go to the Subscriptions tab from the top and hit 'New Subscription'. If you want to save to Excel, then select 'Report Server File Share' and set your options. Down at the bottom, you can set the schedule of the report.
Hope this helps.
Jarret
|||Thanks, Jarret. That's easy enough.sqlscheduling reports to refresh
Hi all!
Is it possible to schedule reports to refresh overnight? Particularly if
they take a long time to return data - for example in business objects i
would normally schedule a report to refresh overnight via the broadcast
agent console...is the same thing at all possible in reporting services?
does RS have sheduling functionality?
many thanks
GregYes, it has extensive functionality in this area.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg" <Greg@.discussions.microsoft.com> wrote in message
news:5E5D3B2C-AE87-4ABB-8E84-469A51511863@.microsoft.com...
> Hi all!
> Is it possible to schedule reports to refresh overnight? Particularly if
> they take a long time to return data - for example in business objects i
> would normally schedule a report to refresh overnight via the broadcast
> agent console...is the same thing at all possible in reporting services?
> does RS have sheduling functionality?
> many thanks
> Greg|||ok.....anything further? lol
HOW DO I DO IT!!!
anyone'
"Bruce L-C [MVP]" wrote:
> Yes, it has extensive functionality in this area.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Greg" <Greg@.discussions.microsoft.com> wrote in message
> news:5E5D3B2C-AE87-4ABB-8E84-469A51511863@.microsoft.com...
> > Hi all!
> >
> > Is it possible to schedule reports to refresh overnight? Particularly if
> > they take a long time to return data - for example in business objects i
> > would normally schedule a report to refresh overnight via the broadcast
> > agent console...is the same thing at all possible in reporting services?
> > does RS have sheduling functionality?
> >
> > many thanks
> >
> > Greg
>
>|||It seemed like you just wondered if it was possible. I thought that maybe
you weren't using Reporting Services and were just making plans.
Anyway, a few of what you need to understand. Search in books online for
snapshot, schedule and history. Reading up on those things should get you
started. Here are a few links to get you rolling:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsmain/htm/rsc_ov_using_v1_4u43.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_catalog_v1_9zsm.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_scheduling_v1_2qgk.asp
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg" <Greg@.discussions.microsoft.com> wrote in message
news:593EBCB8-9CA6-42BB-994C-CFAB8F44495F@.microsoft.com...
> ok.....anything further? lol
> HOW DO I DO IT!!!
> anyone'
> "Bruce L-C [MVP]" wrote:
>> Yes, it has extensive functionality in this area.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Greg" <Greg@.discussions.microsoft.com> wrote in message
>> news:5E5D3B2C-AE87-4ABB-8E84-469A51511863@.microsoft.com...
>> > Hi all!
>> >
>> > Is it possible to schedule reports to refresh overnight? Particularly
>> > if
>> > they take a long time to return data - for example in business objects
>> > i
>> > would normally schedule a report to refresh overnight via the
>> > broadcast
>> > agent console...is the same thing at all possible in reporting
>> > services?
>> > does RS have sheduling functionality?
>> >
>> > many thanks
>> >
>> > Greg
>>
Is it possible to schedule reports to refresh overnight? Particularly if
they take a long time to return data - for example in business objects i
would normally schedule a report to refresh overnight via the broadcast
agent console...is the same thing at all possible in reporting services?
does RS have sheduling functionality?
many thanks
GregYes, it has extensive functionality in this area.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg" <Greg@.discussions.microsoft.com> wrote in message
news:5E5D3B2C-AE87-4ABB-8E84-469A51511863@.microsoft.com...
> Hi all!
> Is it possible to schedule reports to refresh overnight? Particularly if
> they take a long time to return data - for example in business objects i
> would normally schedule a report to refresh overnight via the broadcast
> agent console...is the same thing at all possible in reporting services?
> does RS have sheduling functionality?
> many thanks
> Greg|||ok.....anything further? lol
HOW DO I DO IT!!!
anyone'
"Bruce L-C [MVP]" wrote:
> Yes, it has extensive functionality in this area.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Greg" <Greg@.discussions.microsoft.com> wrote in message
> news:5E5D3B2C-AE87-4ABB-8E84-469A51511863@.microsoft.com...
> > Hi all!
> >
> > Is it possible to schedule reports to refresh overnight? Particularly if
> > they take a long time to return data - for example in business objects i
> > would normally schedule a report to refresh overnight via the broadcast
> > agent console...is the same thing at all possible in reporting services?
> > does RS have sheduling functionality?
> >
> > many thanks
> >
> > Greg
>
>|||It seemed like you just wondered if it was possible. I thought that maybe
you weren't using Reporting Services and were just making plans.
Anyway, a few of what you need to understand. Search in books online for
snapshot, schedule and history. Reading up on those things should get you
started. Here are a few links to get you rolling:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsmain/htm/rsc_ov_using_v1_4u43.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_catalog_v1_9zsm.asp
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rswork/htm/rms_scheduling_v1_2qgk.asp
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg" <Greg@.discussions.microsoft.com> wrote in message
news:593EBCB8-9CA6-42BB-994C-CFAB8F44495F@.microsoft.com...
> ok.....anything further? lol
> HOW DO I DO IT!!!
> anyone'
> "Bruce L-C [MVP]" wrote:
>> Yes, it has extensive functionality in this area.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Greg" <Greg@.discussions.microsoft.com> wrote in message
>> news:5E5D3B2C-AE87-4ABB-8E84-469A51511863@.microsoft.com...
>> > Hi all!
>> >
>> > Is it possible to schedule reports to refresh overnight? Particularly
>> > if
>> > they take a long time to return data - for example in business objects
>> > i
>> > would normally schedule a report to refresh overnight via the
>> > broadcast
>> > agent console...is the same thing at all possible in reporting
>> > services?
>> > does RS have sheduling functionality?
>> >
>> > many thanks
>> >
>> > Greg
>>
Wednesday, March 28, 2012
Scheduling multiple reports at one time
Hi,
I need my reports to run at the 4rth day of every month. I have packs of reports, and typically upto 18 reports in a pack and these packs have to run on the 4rth of every month.
How can i schedule the 18 reports to run at the same time. I don't want to schedule a time for every report ,this is very laborious.Is there any option in SSRS for simulataneously scheduling of these reports?
Thanks
Hi,
You can achieve this functionality by using a Shared Schedule.
In the case the question is if you can assign the schedule to all reports at once, the answer is not by using the web interface, but you can create an script to do so.
In the case you're asking to chain the report processing (i.e.:start report 2 when report 1 is finished), you will need to revert to a script again.
HTH,
Jordi Rambla
MVP SQL Server (Reporting Services)
Certia - rambla informàtica (http://www.certia.net)
Solid Quality Learning (http://www.solidqualitylearning.com)
Scheduling Info.
Hi
I am using RS 2000. Currently I am scheduling the job by manually giving the date, time. Is there any possibility to make it as data driven so that I can configure each user with different timings.
Regards,
Venkataraman M
You can create multiple data driven subscriptions to run at different schedules for different users or user groups. You can filter users for which the subscription is run in data driven subscription query.
Scheduling enable tick box not working
Hi all,
I have a simple question, as follows.
I have set up a couple of jobs which I have scheduled to
run around the same time each night.
One of the jobs works fine, but the other does not run, I
have lloked into the problem and found that the tick box
which enables scheduling, unchecks it's self each night.
Is this possible and how can I stop it.
Both jobs were set-up in exactly the same manner.
Cheers.Hi,
Is that job scheduled to run "One Time".
Check that by looking in to the "schedule" property of that job. If it is
the case make the job "Recurring"
Thanks
Hari
MCDBA
"Gazzer J" <anonymous@.discussions.microsoft.com> wrote in message
news:f99901c43e39$fc06ab50$a001280a@.phx.gbl...
> Hi all,
> I have a simple question, as follows.
> I have set up a couple of jobs which I have scheduled to
> run around the same time each night.
> One of the jobs works fine, but the other does not run, I
> have lloked into the problem and found that the tick box
> which enables scheduling, unchecks it's self each night.
> Is this possible and how can I stop it.
> Both jobs were set-up in exactly the same manner.
> Cheers.|||There is a bug that can cause something like this. Do you
have any warnings in the SQL Agent log along the lines of
Possible date calculation spin for Schedule nn
If you have these warnings make sure you are on the latest
service pack. You may also want to try adding a minute or
two to the scheduled time as this can often correct the
problems with the data calculation "confusion" that SQL
Agent sometimes experiences.
-Sue
On Thu, 20 May 2004 00:13:43 -0700, "Gazzer J"
<anonymous@.discussions.microsoft.com> wrote:
>Hi all,
>I have a simple question, as follows.
>I have set up a couple of jobs which I have scheduled to
>run around the same time each night.
>One of the jobs works fine, but the other does not run, I
>have lloked into the problem and found that the tick box
>which enables scheduling, unchecks it's self each night.
>Is this possible and how can I stop it.
>Both jobs were set-up in exactly the same manner.
>Cheers.
I have a simple question, as follows.
I have set up a couple of jobs which I have scheduled to
run around the same time each night.
One of the jobs works fine, but the other does not run, I
have lloked into the problem and found that the tick box
which enables scheduling, unchecks it's self each night.
Is this possible and how can I stop it.
Both jobs were set-up in exactly the same manner.
Cheers.Hi,
Is that job scheduled to run "One Time".
Check that by looking in to the "schedule" property of that job. If it is
the case make the job "Recurring"
Thanks
Hari
MCDBA
"Gazzer J" <anonymous@.discussions.microsoft.com> wrote in message
news:f99901c43e39$fc06ab50$a001280a@.phx.gbl...
> Hi all,
> I have a simple question, as follows.
> I have set up a couple of jobs which I have scheduled to
> run around the same time each night.
> One of the jobs works fine, but the other does not run, I
> have lloked into the problem and found that the tick box
> which enables scheduling, unchecks it's self each night.
> Is this possible and how can I stop it.
> Both jobs were set-up in exactly the same manner.
> Cheers.|||There is a bug that can cause something like this. Do you
have any warnings in the SQL Agent log along the lines of
Possible date calculation spin for Schedule nn
If you have these warnings make sure you are on the latest
service pack. You may also want to try adding a minute or
two to the scheduled time as this can often correct the
problems with the data calculation "confusion" that SQL
Agent sometimes experiences.
-Sue
On Thu, 20 May 2004 00:13:43 -0700, "Gazzer J"
<anonymous@.discussions.microsoft.com> wrote:
>Hi all,
>I have a simple question, as follows.
>I have set up a couple of jobs which I have scheduled to
>run around the same time each night.
>One of the jobs works fine, but the other does not run, I
>have lloked into the problem and found that the tick box
>which enables scheduling, unchecks it's self each night.
>Is this possible and how can I stop it.
>Both jobs were set-up in exactly the same manner.
>Cheers.
Scheduling enable tick box not working
Hi all,
I have a simple question, as follows.
I have set up a couple of jobs which I have scheduled to
run around the same time each night.
One of the jobs works fine, but the other does not run, I
have lloked into the problem and found that the tick box
which enables scheduling, unchecks it's self each night.
Is this possible and how can I stop it.
Both jobs were set-up in exactly the same manner.
Cheers.Hi,
Is that job scheduled to run "One Time".
Check that by looking in to the "schedule" property of that job. If it is
the case make the job "Recurring"
Thanks
Hari
MCDBA
"Gazzer J" <anonymous@.discussions.microsoft.com> wrote in message
news:f99901c43e39$fc06ab50$a001280a@.phx.gbl...
> Hi all,
> I have a simple question, as follows.
> I have set up a couple of jobs which I have scheduled to
> run around the same time each night.
> One of the jobs works fine, but the other does not run, I
> have lloked into the problem and found that the tick box
> which enables scheduling, unchecks it's self each night.
> Is this possible and how can I stop it.
> Both jobs were set-up in exactly the same manner.
> Cheers.|||There is a bug that can cause something like this. Do you
have any warnings in the SQL Agent log along the lines of
Possible date calculation spin for Schedule nn
If you have these warnings make sure you are on the latest
service pack. You may also want to try adding a minute or
two to the scheduled time as this can often correct the
problems with the data calculation "confusion" that SQL
Agent sometimes experiences.
-Sue
On Thu, 20 May 2004 00:13:43 -0700, "Gazzer J"
<anonymous@.discussions.microsoft.com> wrote:
>Hi all,
>I have a simple question, as follows.
>I have set up a couple of jobs which I have scheduled to
>run around the same time each night.
>One of the jobs works fine, but the other does not run, I
>have lloked into the problem and found that the tick box
>which enables scheduling, unchecks it's self each night.
>Is this possible and how can I stop it.
>Both jobs were set-up in exactly the same manner.
>Cheers.
I have a simple question, as follows.
I have set up a couple of jobs which I have scheduled to
run around the same time each night.
One of the jobs works fine, but the other does not run, I
have lloked into the problem and found that the tick box
which enables scheduling, unchecks it's self each night.
Is this possible and how can I stop it.
Both jobs were set-up in exactly the same manner.
Cheers.Hi,
Is that job scheduled to run "One Time".
Check that by looking in to the "schedule" property of that job. If it is
the case make the job "Recurring"
Thanks
Hari
MCDBA
"Gazzer J" <anonymous@.discussions.microsoft.com> wrote in message
news:f99901c43e39$fc06ab50$a001280a@.phx.gbl...
> Hi all,
> I have a simple question, as follows.
> I have set up a couple of jobs which I have scheduled to
> run around the same time each night.
> One of the jobs works fine, but the other does not run, I
> have lloked into the problem and found that the tick box
> which enables scheduling, unchecks it's self each night.
> Is this possible and how can I stop it.
> Both jobs were set-up in exactly the same manner.
> Cheers.|||There is a bug that can cause something like this. Do you
have any warnings in the SQL Agent log along the lines of
Possible date calculation spin for Schedule nn
If you have these warnings make sure you are on the latest
service pack. You may also want to try adding a minute or
two to the scheduled time as this can often correct the
problems with the data calculation "confusion" that SQL
Agent sometimes experiences.
-Sue
On Thu, 20 May 2004 00:13:43 -0700, "Gazzer J"
<anonymous@.discussions.microsoft.com> wrote:
>Hi all,
>I have a simple question, as follows.
>I have set up a couple of jobs which I have scheduled to
>run around the same time each night.
>One of the jobs works fine, but the other does not run, I
>have lloked into the problem and found that the tick box
>which enables scheduling, unchecks it's self each night.
>Is this possible and how can I stop it.
>Both jobs were set-up in exactly the same manner.
>Cheers.
Scheduling enable tick box not working
Hi all,
I have a simple question, as follows.
I have set up a couple of jobs which I have scheduled to
run around the same time each night.
One of the jobs works fine, but the other does not run, I
have lloked into the problem and found that the tick box
which enables scheduling, unchecks it's self each night.
Is this possible and how can I stop it.
Both jobs were set-up in exactly the same manner.
Cheers.
Hi,
Is that job scheduled to run "One Time".
Check that by looking in to the "schedule" property of that job. If it is
the case make the job "Recurring"
Thanks
Hari
MCDBA
"Gazzer J" <anonymous@.discussions.microsoft.com> wrote in message
news:f99901c43e39$fc06ab50$a001280a@.phx.gbl...
> Hi all,
> I have a simple question, as follows.
> I have set up a couple of jobs which I have scheduled to
> run around the same time each night.
> One of the jobs works fine, but the other does not run, I
> have lloked into the problem and found that the tick box
> which enables scheduling, unchecks it's self each night.
> Is this possible and how can I stop it.
> Both jobs were set-up in exactly the same manner.
> Cheers.
|||There is a bug that can cause something like this. Do you
have any warnings in the SQL Agent log along the lines of
Possible date calculation spin for Schedule nn
If you have these warnings make sure you are on the latest
service pack. You may also want to try adding a minute or
two to the scheduled time as this can often correct the
problems with the data calculation "confusion" that SQL
Agent sometimes experiences.
-Sue
On Thu, 20 May 2004 00:13:43 -0700, "Gazzer J"
<anonymous@.discussions.microsoft.com> wrote:
>Hi all,
>I have a simple question, as follows.
>I have set up a couple of jobs which I have scheduled to
>run around the same time each night.
>One of the jobs works fine, but the other does not run, I
>have lloked into the problem and found that the tick box
>which enables scheduling, unchecks it's self each night.
>Is this possible and how can I stop it.
>Both jobs were set-up in exactly the same manner.
>Cheers.
I have a simple question, as follows.
I have set up a couple of jobs which I have scheduled to
run around the same time each night.
One of the jobs works fine, but the other does not run, I
have lloked into the problem and found that the tick box
which enables scheduling, unchecks it's self each night.
Is this possible and how can I stop it.
Both jobs were set-up in exactly the same manner.
Cheers.
Hi,
Is that job scheduled to run "One Time".
Check that by looking in to the "schedule" property of that job. If it is
the case make the job "Recurring"
Thanks
Hari
MCDBA
"Gazzer J" <anonymous@.discussions.microsoft.com> wrote in message
news:f99901c43e39$fc06ab50$a001280a@.phx.gbl...
> Hi all,
> I have a simple question, as follows.
> I have set up a couple of jobs which I have scheduled to
> run around the same time each night.
> One of the jobs works fine, but the other does not run, I
> have lloked into the problem and found that the tick box
> which enables scheduling, unchecks it's self each night.
> Is this possible and how can I stop it.
> Both jobs were set-up in exactly the same manner.
> Cheers.
|||There is a bug that can cause something like this. Do you
have any warnings in the SQL Agent log along the lines of
Possible date calculation spin for Schedule nn
If you have these warnings make sure you are on the latest
service pack. You may also want to try adding a minute or
two to the scheduled time as this can often correct the
problems with the data calculation "confusion" that SQL
Agent sometimes experiences.
-Sue
On Thu, 20 May 2004 00:13:43 -0700, "Gazzer J"
<anonymous@.discussions.microsoft.com> wrote:
>Hi all,
>I have a simple question, as follows.
>I have set up a couple of jobs which I have scheduled to
>run around the same time each night.
>One of the jobs works fine, but the other does not run, I
>have lloked into the problem and found that the tick box
>which enables scheduling, unchecks it's self each night.
>Is this possible and how can I stop it.
>Both jobs were set-up in exactly the same manner.
>Cheers.
Scheduling DTS packages in SQLServer 2005 via the Run Time utility
All,
I installed SQLServer 2005 on a new box and installed the DTS Runtime
utility as well so that the DTS packages run in the 2005 environment.
I imported all the DTS packages but I dont know how to schedule each of
them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
package would create and schedule a job. I'm not sure how to do it here other
than creating the job manually.
Thanks,
rgnCreate an Agent job with a CmdExec jobstep. In this jobstep, you execute DTSRUN.EXE with appropriate
command-line options (see 2000 Books Online for documentation of the command-line options for
DTSRUN.EXE).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
> package would create and schedule a job. I'm not sure how to do it here other
> than creating the job manually.
> Thanks,
> rgn
>|||rgn,
Apparently, since DTS is being deprecated the scheduling function did not
move over with the legacy support.
However, creating your own job is pretty easy, especially if you examine the
job definitions created for you on your SQL Server 2000 server. In fact, you
may be able to simply script out the jobs from SQL Server 2000 and run those
scripts on your 2005 SQL Server.
Some adjustements may be necessary. For example, if the same logins used
for the jobs on 2000 do not exist on your new 2005 server, you will need to
adjust the scripts to point to the logins you wish to use.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> DTS
> package would create and schedule a job. I'm not sure how to do it here
> other
> than creating the job manually.
> Thanks,
> rgn
>|||Tibor/Russell,
I should have been clearer in my earlier post. I can create a job for each
one of the DTS packages with DTSRUN. However, I dont know how to generate the
encrypted details of the package name, login name, Password ... etc.
It is against our SOX policy to include password in open text.
THis example is for a different DTS on a different server altogether.[DTSRun
/~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371 ]
Thanks,
rgn
"Russell Fields" wrote:
> rgn,
> Apparently, since DTS is being deprecated the scheduling function did not
> move over with the legacy support.
> However, creating your own job is pretty easy, especially if you examine the
> job definitions created for you on your SQL Server 2000 server. In fact, you
> may be able to simply script out the jobs from SQL Server 2000 and run those
> scripts on your 2005 SQL Server.
> Some adjustements may be necessary. For example, if the same logins used
> for the jobs on 2000 do not exist on your new 2005 server, you will need to
> adjust the scripts to point to the logins you wish to use.
> RLF
>
> "rgn" <rgn@.discussions.microsoft.com> wrote in message
> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> > All,
> >
> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
> > utility as well so that the DTS packages run in the 2005 environment.
> >
> > I imported all the DTS packages but I dont know how to schedule each of
> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> > DTS
> > package would create and schedule a job. I'm not sure how to do it here
> > other
> > than creating the job manually.
> >
> > Thanks,
> > rgn
> >
> >
>
>|||rgn,
I poked around a bit and found that the encrypted details are not as secure
as you might wish. So... user beware. Here is how you can generate one:
dtsrun /S ServerName /E /N PackagePathAndName /!Y
You will see that it gives a different encryption each time, but try it out
and see if the results work for you.
Since you are in SQL Server 2005, I encourage you to study up on SQL Agent
Proxies, which use Credentials for Logins to switch execution context before
running the Operating System step of DTSRUN. If that works for you, you can
run your DTS Packages without any user names or passwords in the command
line. Much more secure.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:C777E793-E904-4D38-A361-E642C056AF7A@.microsoft.com...
> Tibor/Russell,
> I should have been clearer in my earlier post. I can create a job for each
> one of the DTS packages with DTSRUN. However, I dont know how to generate
> the
> encrypted details of the package name, login name, Password ... etc.
> It is against our SOX policy to include password in open text.
> THis example is for a different DTS on a different server
> altogether.[DTSRun
> /~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371
> ]
> Thanks,
> rgn
> "Russell Fields" wrote:
>> rgn,
>> Apparently, since DTS is being deprecated the scheduling function did not
>> move over with the legacy support.
>> However, creating your own job is pretty easy, especially if you examine
>> the
>> job definitions created for you on your SQL Server 2000 server. In fact,
>> you
>> may be able to simply script out the jobs from SQL Server 2000 and run
>> those
>> scripts on your 2005 SQL Server.
>> Some adjustements may be necessary. For example, if the same logins used
>> for the jobs on 2000 do not exist on your new 2005 server, you will need
>> to
>> adjust the scripts to point to the logins you wish to use.
>> RLF
>>
>> "rgn" <rgn@.discussions.microsoft.com> wrote in message
>> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
>> > All,
>> >
>> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
>> > utility as well so that the DTS packages run in the 2005 environment.
>> >
>> > I imported all the DTS packages but I dont know how to schedule each of
>> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on
>> > a
>> > DTS
>> > package would create and schedule a job. I'm not sure how to do it here
>> > other
>> > than creating the job manually.
>> >
>> > Thanks,
>> > rgn
>> >
>> >
>>sql
I installed SQLServer 2005 on a new box and installed the DTS Runtime
utility as well so that the DTS packages run in the 2005 environment.
I imported all the DTS packages but I dont know how to schedule each of
them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
package would create and schedule a job. I'm not sure how to do it here other
than creating the job manually.
Thanks,
rgnCreate an Agent job with a CmdExec jobstep. In this jobstep, you execute DTSRUN.EXE with appropriate
command-line options (see 2000 Books Online for documentation of the command-line options for
DTSRUN.EXE).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a DTS
> package would create and schedule a job. I'm not sure how to do it here other
> than creating the job manually.
> Thanks,
> rgn
>|||rgn,
Apparently, since DTS is being deprecated the scheduling function did not
move over with the legacy support.
However, creating your own job is pretty easy, especially if you examine the
job definitions created for you on your SQL Server 2000 server. In fact, you
may be able to simply script out the jobs from SQL Server 2000 and run those
scripts on your 2005 SQL Server.
Some adjustements may be necessary. For example, if the same logins used
for the jobs on 2000 do not exist on your new 2005 server, you will need to
adjust the scripts to point to the logins you wish to use.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> All,
> I installed SQLServer 2005 on a new box and installed the DTS Runtime
> utility as well so that the DTS packages run in the 2005 environment.
> I imported all the DTS packages but I dont know how to schedule each of
> them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> DTS
> package would create and schedule a job. I'm not sure how to do it here
> other
> than creating the job manually.
> Thanks,
> rgn
>|||Tibor/Russell,
I should have been clearer in my earlier post. I can create a job for each
one of the DTS packages with DTSRUN. However, I dont know how to generate the
encrypted details of the package name, login name, Password ... etc.
It is against our SOX policy to include password in open text.
THis example is for a different DTS on a different server altogether.[DTSRun
/~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371 ]
Thanks,
rgn
"Russell Fields" wrote:
> rgn,
> Apparently, since DTS is being deprecated the scheduling function did not
> move over with the legacy support.
> However, creating your own job is pretty easy, especially if you examine the
> job definitions created for you on your SQL Server 2000 server. In fact, you
> may be able to simply script out the jobs from SQL Server 2000 and run those
> scripts on your 2005 SQL Server.
> Some adjustements may be necessary. For example, if the same logins used
> for the jobs on 2000 do not exist on your new 2005 server, you will need to
> adjust the scripts to point to the logins you wish to use.
> RLF
>
> "rgn" <rgn@.discussions.microsoft.com> wrote in message
> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
> > All,
> >
> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
> > utility as well so that the DTS packages run in the 2005 environment.
> >
> > I imported all the DTS packages but I dont know how to schedule each of
> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on a
> > DTS
> > package would create and schedule a job. I'm not sure how to do it here
> > other
> > than creating the job manually.
> >
> > Thanks,
> > rgn
> >
> >
>
>|||rgn,
I poked around a bit and found that the encrypted details are not as secure
as you might wish. So... user beware. Here is how you can generate one:
dtsrun /S ServerName /E /N PackagePathAndName /!Y
You will see that it gives a different encryption each time, but try it out
and see if the results work for you.
Since you are in SQL Server 2005, I encourage you to study up on SQL Agent
Proxies, which use Credentials for Logins to switch execution context before
running the Operating System step of DTSRUN. If that works for you, you can
run your DTS Packages without any user names or passwords in the command
line. Much more secure.
RLF
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:C777E793-E904-4D38-A361-E642C056AF7A@.microsoft.com...
> Tibor/Russell,
> I should have been clearer in my earlier post. I can create a job for each
> one of the DTS packages with DTSRUN. However, I dont know how to generate
> the
> encrypted details of the package name, login name, Password ... etc.
> It is against our SOX policy to include password in open text.
> THis example is for a different DTS on a different server
> altogether.[DTSRun
> /~Z0xBBA31CD08C42214454A70882A4D929948FA0915B8AA465A7BEF16CCA4AC7639EB256D85DB6780227228D2D92A3FF92D1AAC3354C13AF4CCF5704F24B8EA95C5C95E33BE0EAF73A5ED7C9F1D9AA391B364F64B7473F9E27823B3EF142CE09CF1F1BF7E08A031026BC2F7E03E544C824E13C2584B3C7197F19A12371
> ]
> Thanks,
> rgn
> "Russell Fields" wrote:
>> rgn,
>> Apparently, since DTS is being deprecated the scheduling function did not
>> move over with the legacy support.
>> However, creating your own job is pretty easy, especially if you examine
>> the
>> job definitions created for you on your SQL Server 2000 server. In fact,
>> you
>> may be able to simply script out the jobs from SQL Server 2000 and run
>> those
>> scripts on your 2005 SQL Server.
>> Some adjustements may be necessary. For example, if the same logins used
>> for the jobs on 2000 do not exist on your new 2005 server, you will need
>> to
>> adjust the scripts to point to the logins you wish to use.
>> RLF
>>
>> "rgn" <rgn@.discussions.microsoft.com> wrote in message
>> news:5B08D6C7-9A39-49AF-8EA5-532627D5E310@.microsoft.com...
>> > All,
>> >
>> > I installed SQLServer 2005 on a new box and installed the DTS Runtime
>> > utility as well so that the DTS packages run in the 2005 environment.
>> >
>> > I imported all the DTS packages but I dont know how to schedule each of
>> > them. Would anyone know. In SQLServer 2000, "Schedule Package" menu on
>> > a
>> > DTS
>> > package would create and schedule a job. I'm not sure how to do it here
>> > other
>> > than creating the job manually.
>> >
>> > Thanks,
>> > rgn
>> >
>> >
>>sql
Monday, March 26, 2012
Scheduling Complete and Differential backups
I'm new to the SQL 7 scene but would like a few things clearing up with regards to scheduling backups.
Our backup time of databases has recently changed. I've scheduled in the new database backup using Enterprise Manager with the new time.
I expected the backup to take place at the new time, which it does, but when I came to restoring the database I've noticed that the old backup time is still being carried out. How do I cancel or get rid of the old backup time?
Secondly, If I do a complete backup of the database using Enterprise Manager, can I deattach the transactional log and delete the transactional log before reattaching in order to free up MG?
Thirdly, is carrying out a complete backup of the database via Enterprise Manager enough to ensure a full backup of the database should anything go wrong?
I would like help on these matters please as I need these clearing up. thanking you in advance!!!It sounds like you might have two scheduled jobs running one for the old time and one for the new time if so find the old job and delete it.
If you need to restore your database to a point in time you need the transaction log. A full backup backs up the database and the T-log together so you will only be able to restore to the last time you did the full backup.
If the transaction log is getting to large you can truncate the log which is sort of the same thing as deleting but doesn't actually get rid of the .ldf file. If you truncate the log without first backing it up you lose all those transactions from the last time the log was backed up!
If you need to restore to a point in time you need the T-log. Say you do a full backup every night and a T-log backup every hour. We will say that SQL fails on Tuesday at 1:45pm. To restore you would backup the current T-log because the next scheduled T-log backup will not occur until 2pm. and it contains the active portion of the log and you need to recover it by backing it up. You then would apply the full backup and all T-log backups in sequence up to the point of failure.
If you have SQL installed then you should have Books Online installed. You should find it in the menu. They have exhaustive information that talks about backup strategies. I suggest you take some time to read up on it it's well worth the time.
Best Regards|||[QUOTE][SIZE=1]Originally posted by mkal
It sounds like you might have two scheduled jobs running one for the old time and one for the new time if so find the old job and delete it.
Thats the thing, I'm pretty sure I deleted the old Database_bk file and created a new one in the 'MSSQL\Backup' folder but still the old backup time is there when doing a restore. I'll have another go.
As for the tranasactional backup, we currently carry out a Complete backup of a weekend and a differential backup every night which is scheduled using the Enterprise Manager but there is no option to backup the Transaction log. How is this done?
You'll have to bear with me on this one as I'm still a newbie and require a lot of patience.
Thanks v.much for the reply|||I'm still getting two lots of complete backups to restore as well as two lots of differential backups to restore having changed the times of when the backups are scheduled using Enterprise Manager.
Is there anyway I can get it so that there is only one backup scheduled?|||Deleting the backup file is not the same as deleting the job. In Enterprise Manager expand out the server you create the backups for. Click on the Management folder and then SQL Server Agent and then click on jobs. In the right hand pane you should see a list of jobs. There should be the one for your backup and possibly others. To explore what the job is doing right click on it and choose properties. You then can take a look at what's going on.
To free up space on the drive where the T-log is you can run a script see below, just replace the info between the <> (but don't include the <>) with the name of the database, name of the log file and the size expressed as an integer you want the file to become.
The following is from BOL:
If target_size is specified, DBCC SHRINKFILE attempts to shrink the file to the specified size. Used pages in the part of the file to be freed are relocated to available free space in the part of the file retained. For example, if there is a 10-MB data file, a DBCC SHRINKFILE with a target_size of 8 causes all used pages in the last 2 MB of the file to be reallocated into any available free slots in the first 8 MB of the file. DBCC SHRINKFILE does not shrink a file past the size needed to store the data in the file. For example, if 7 MB of a 10-MB data file is used, a DBCC SHRINKFILE statement with a target_size of 6 shrinks the file to only 7 MB, not 6 MB.
Backup log <DatabaseName> with truncate_only
GO
DBCC SHRINKFILE (<LogFile_Name, <targetsize>)
GO
Creating a full backup backs up the data and the T-log, so you can recover everything up to the day and time you performed the backup.
It doesn't back up the database structure i.e. tables, constraints, PK/FK. You should script your database to make sure that in the event of a major crash you can recreate the database and reload it from the backups.
To script your database use Enterprise Manager. Right click on the database you wish to script, choose 'All Tasks' and then Generate SQL Script.
Best Regards
Mike|||Cheers Mike,
When I went into the Management\SQLServerAgent\Jobs folder and sure enough I seen a whole load of jobs that had been duplicated. I have gotten rid of the ones that are now redundant and have left the jobs that run at a later time (the ones I need) in there. I'm quite sure that this will work but I will need to check in the morning after the databases have been backed up.
A big thank you mate for your help and persevering with me.|||One more thing about log backups. For this to take place you must have the recovery model of the database set to full and there must be at least one full database backup must exist.
To check the recoverty model right click on the database and choose properties. Go the options tab and where it says 'Recovery model' choose full.
Now when you right click on the database and choose 'All Tasks' and the 'Database Backup' you will see a radio button to perform a log backup.
Glad I could help.
Our backup time of databases has recently changed. I've scheduled in the new database backup using Enterprise Manager with the new time.
I expected the backup to take place at the new time, which it does, but when I came to restoring the database I've noticed that the old backup time is still being carried out. How do I cancel or get rid of the old backup time?
Secondly, If I do a complete backup of the database using Enterprise Manager, can I deattach the transactional log and delete the transactional log before reattaching in order to free up MG?
Thirdly, is carrying out a complete backup of the database via Enterprise Manager enough to ensure a full backup of the database should anything go wrong?
I would like help on these matters please as I need these clearing up. thanking you in advance!!!It sounds like you might have two scheduled jobs running one for the old time and one for the new time if so find the old job and delete it.
If you need to restore your database to a point in time you need the transaction log. A full backup backs up the database and the T-log together so you will only be able to restore to the last time you did the full backup.
If the transaction log is getting to large you can truncate the log which is sort of the same thing as deleting but doesn't actually get rid of the .ldf file. If you truncate the log without first backing it up you lose all those transactions from the last time the log was backed up!
If you need to restore to a point in time you need the T-log. Say you do a full backup every night and a T-log backup every hour. We will say that SQL fails on Tuesday at 1:45pm. To restore you would backup the current T-log because the next scheduled T-log backup will not occur until 2pm. and it contains the active portion of the log and you need to recover it by backing it up. You then would apply the full backup and all T-log backups in sequence up to the point of failure.
If you have SQL installed then you should have Books Online installed. You should find it in the menu. They have exhaustive information that talks about backup strategies. I suggest you take some time to read up on it it's well worth the time.
Best Regards|||[QUOTE][SIZE=1]Originally posted by mkal
It sounds like you might have two scheduled jobs running one for the old time and one for the new time if so find the old job and delete it.
Thats the thing, I'm pretty sure I deleted the old Database_bk file and created a new one in the 'MSSQL\Backup' folder but still the old backup time is there when doing a restore. I'll have another go.
As for the tranasactional backup, we currently carry out a Complete backup of a weekend and a differential backup every night which is scheduled using the Enterprise Manager but there is no option to backup the Transaction log. How is this done?
You'll have to bear with me on this one as I'm still a newbie and require a lot of patience.
Thanks v.much for the reply|||I'm still getting two lots of complete backups to restore as well as two lots of differential backups to restore having changed the times of when the backups are scheduled using Enterprise Manager.
Is there anyway I can get it so that there is only one backup scheduled?|||Deleting the backup file is not the same as deleting the job. In Enterprise Manager expand out the server you create the backups for. Click on the Management folder and then SQL Server Agent and then click on jobs. In the right hand pane you should see a list of jobs. There should be the one for your backup and possibly others. To explore what the job is doing right click on it and choose properties. You then can take a look at what's going on.
To free up space on the drive where the T-log is you can run a script see below, just replace the info between the <> (but don't include the <>) with the name of the database, name of the log file and the size expressed as an integer you want the file to become.
The following is from BOL:
If target_size is specified, DBCC SHRINKFILE attempts to shrink the file to the specified size. Used pages in the part of the file to be freed are relocated to available free space in the part of the file retained. For example, if there is a 10-MB data file, a DBCC SHRINKFILE with a target_size of 8 causes all used pages in the last 2 MB of the file to be reallocated into any available free slots in the first 8 MB of the file. DBCC SHRINKFILE does not shrink a file past the size needed to store the data in the file. For example, if 7 MB of a 10-MB data file is used, a DBCC SHRINKFILE statement with a target_size of 6 shrinks the file to only 7 MB, not 6 MB.
Backup log <DatabaseName> with truncate_only
GO
DBCC SHRINKFILE (<LogFile_Name, <targetsize>)
GO
Creating a full backup backs up the data and the T-log, so you can recover everything up to the day and time you performed the backup.
It doesn't back up the database structure i.e. tables, constraints, PK/FK. You should script your database to make sure that in the event of a major crash you can recreate the database and reload it from the backups.
To script your database use Enterprise Manager. Right click on the database you wish to script, choose 'All Tasks' and then Generate SQL Script.
Best Regards
Mike|||Cheers Mike,
When I went into the Management\SQLServerAgent\Jobs folder and sure enough I seen a whole load of jobs that had been duplicated. I have gotten rid of the ones that are now redundant and have left the jobs that run at a later time (the ones I need) in there. I'm quite sure that this will work but I will need to check in the morning after the databases have been backed up.
A big thank you mate for your help and persevering with me.|||One more thing about log backups. For this to take place you must have the recovery model of the database set to full and there must be at least one full database backup must exist.
To check the recoverty model right click on the database and choose properties. Go the options tab and where it says 'Recovery model' choose full.
Now when you right click on the database and choose 'All Tasks' and the 'Database Backup' you will see a radio button to perform a log backup.
Glad I could help.
Scheduling A Stored Procedure?
Hi,
We are using SQL Server 2000. Is it possible to somehow schedule a stored
procedure to run at a specified date and time? I know that its possible
with DTS packages, but this is just a stored proc that performs a
calculation. We want it to run at a certain time every day.
JDSQL Agent - add a job
in EM it's under <server> - Management - SQL Agent - Jobs.
Joe Delphi wrote:
> Hi,
> We are using SQL Server 2000. Is it possible to somehow schedule a stored
> procedure to run at a specified date and time? I know that its possible
> with DTS packages, but this is just a stored proc that performs a
> calculation. We want it to run at a certain time every day.
>
> JD
>|||On Wed, 30 Nov 2005 19:59:44 -0600, Trey Walpole
<treypole@.newsgroups.nospam> wrote:
>SQL Agent - add a job
>in EM it's under <server> - Management - SQL Agent - Jobs.
>Joe Delphi wrote:
or you can run it from inside a DTS package.
J.|||Another alternative:
You can create a bat file that will run the stored procedure using osql.exe.
Then schedule that bat file to run using windows scheduler.
Lucas
"jxstern" wrote:
> On Wed, 30 Nov 2005 19:59:44 -0600, Trey Walpole
> <treypole@.newsgroups.nospam> wrote:
> or you can run it from inside a DTS package.
> J.
>
We are using SQL Server 2000. Is it possible to somehow schedule a stored
procedure to run at a specified date and time? I know that its possible
with DTS packages, but this is just a stored proc that performs a
calculation. We want it to run at a certain time every day.
JDSQL Agent - add a job
in EM it's under <server> - Management - SQL Agent - Jobs.
Joe Delphi wrote:
> Hi,
> We are using SQL Server 2000. Is it possible to somehow schedule a stored
> procedure to run at a specified date and time? I know that its possible
> with DTS packages, but this is just a stored proc that performs a
> calculation. We want it to run at a certain time every day.
>
> JD
>|||On Wed, 30 Nov 2005 19:59:44 -0600, Trey Walpole
<treypole@.newsgroups.nospam> wrote:
>SQL Agent - add a job
>in EM it's under <server> - Management - SQL Agent - Jobs.
>Joe Delphi wrote:
or you can run it from inside a DTS package.
J.|||Another alternative:
You can create a bat file that will run the stored procedure using osql.exe.
Then schedule that bat file to run using windows scheduler.
Lucas
"jxstern" wrote:
> On Wed, 30 Nov 2005 19:59:44 -0600, Trey Walpole
> <treypole@.newsgroups.nospam> wrote:
> or you can run it from inside a DTS package.
> J.
>
Scheduling a query to be executed at given time in SQL Server 2005
Hi friend!
I want to schedule a query or procedure running at given time regularly eg: at 12AM daily. Please tell me how to do that in sql server 2005.
We use SQL server 2005 developer edition.
Thanks in advance.
SS2005 has a scheduller, SS Agent. Make sure it is installed and the service is up and running. You can get access to it through SSManagement Studio. BTW, this is a SSIS forum; if you have further question I will move this thread to a more appropiate forum.Wednesday, March 21, 2012
Scheduled Profiler
I need to get performance stats off a number of live servers. The stats need to cover the time from 07:00 to 19:00 every day.
I'm after things like CPU, Memory and IO, but also I want things like transactions and stored procedures.
Can profiler provide this kind of information, and can I schedule the jobs?
The systems are all running on Windows server 2003 and SQL Server 2005.
Thanks
Gary
Hi,
You should schedule a t-sql task with SQL Server Agent.
Use the sp_trace_create to create a trace, sp_trace_setevent to set up your events for monitoring and sp_trace_setstatus to start, stop or pause a trace.
I hope it helps.
Regards,
Janos
|||Scheduling server traces is what you would want to do as Janos posted. Rather than trying to set up all of the statements and events yourself, it's much easier to just use Profiler to create the script file. Create the trace you want in Profiler and then go to the menu to File, Export and then select Script Trace Definition. This will create the server trace file that you can schedule in SQL Agent. You can then open these files in profiler, import them into a table for analysis, etc. It's the same file format that Profiler uses.
-Sue
|||refer these links
http://vyaskn.tripod.com/server_side_tracing_in_sql_server.htm
http://msdn2.microsoft.com/en-us/library/ms191006.aspx
Madhu
Scheduled jobs not repeating (log shipping restore)
I have several log shipping restore jobs that are scheduled to start at
the same time and repeat every 15 minutes. This has worked correctly
until last w
when some of the jobs would only run once. No errors
were produced and Agent said the jobs completed successfully, no reason
given as to why they failed to repeat.
Does anyone have any suggestions?
Thanks,
CurtIn order to try helping you I would need to know more details about what has
lead to the change in system's behavior. Did you add new jobs, did the
system go under heavy load, have you changed schedules manually etc. ?
It would also help if you look at agent's error log for some clues.
Ciprian Gerea
SDE, SqlServer
This posting is provided "AS IS" with no warranties, and confers no rights.
<curtmorrison@.yahoo.com> wrote in message
news:1145901222.247025.29230@.t31g2000cwb.googlegroups.com...
>I have several log shipping restore jobs that are scheduled to start at
> the same time and repeat every 15 minutes. This has worked correctly
> until last w when some of the jobs would only run once. No errors
> were produced and Agent said the jobs completed successfully, no reason
> given as to why they failed to repeat.
> Does anyone have any suggestions?
> Thanks,
> Curt
>|||Is it possible that if the job is set the repeat every 15 minutes, but
the inital job takes over 2 hours to complete, the agent scheduler will
give up on it? The jobs that are repeating correctly only take about 10
minutes at most to complete, while all the jobs that are failing to
repeat are averaging about 1.5 hours.|||The scheduler does not give up on the job, but the job won't be executed if
it's already running. After the 2 hour time period elapses, does the
recurring job get rescheduled?
Ciprian Gerea
SDE, SqlServer
This posting is provided "AS IS" with no warranties, and confers no rights.
<curtmorrison@.yahoo.com> wrote in message
news:1145995810.372988.102280@.e56g2000cwe.googlegroups.com...
> Is it possible that if the job is set the repeat every 15 minutes, but
> the inital job takes over 2 hours to complete, the agent scheduler will
> give up on it? The jobs that are repeating correctly only take about 10
> minutes at most to complete, while all the jobs that are failing to
> repeat are averaging about 1.5 hours.
>|||After the 2 hour time period elapses, the recurring job doesn't run
again until the following day as scheduled.
the same time and repeat every 15 minutes. This has worked correctly
until last w
when some of the jobs would only run once. No errorswere produced and Agent said the jobs completed successfully, no reason
given as to why they failed to repeat.
Does anyone have any suggestions?
Thanks,
CurtIn order to try helping you I would need to know more details about what has
lead to the change in system's behavior. Did you add new jobs, did the
system go under heavy load, have you changed schedules manually etc. ?
It would also help if you look at agent's error log for some clues.
Ciprian Gerea
SDE, SqlServer
This posting is provided "AS IS" with no warranties, and confers no rights.
<curtmorrison@.yahoo.com> wrote in message
news:1145901222.247025.29230@.t31g2000cwb.googlegroups.com...
>I have several log shipping restore jobs that are scheduled to start at
> the same time and repeat every 15 minutes. This has worked correctly
> until last w
when some of the jobs would only run once. No errors> were produced and Agent said the jobs completed successfully, no reason
> given as to why they failed to repeat.
> Does anyone have any suggestions?
> Thanks,
> Curt
>|||Is it possible that if the job is set the repeat every 15 minutes, but
the inital job takes over 2 hours to complete, the agent scheduler will
give up on it? The jobs that are repeating correctly only take about 10
minutes at most to complete, while all the jobs that are failing to
repeat are averaging about 1.5 hours.|||The scheduler does not give up on the job, but the job won't be executed if
it's already running. After the 2 hour time period elapses, does the
recurring job get rescheduled?
Ciprian Gerea
SDE, SqlServer
This posting is provided "AS IS" with no warranties, and confers no rights.
<curtmorrison@.yahoo.com> wrote in message
news:1145995810.372988.102280@.e56g2000cwe.googlegroups.com...
> Is it possible that if the job is set the repeat every 15 minutes, but
> the inital job takes over 2 hours to complete, the agent scheduler will
> give up on it? The jobs that are repeating correctly only take about 10
> minutes at most to complete, while all the jobs that are failing to
> repeat are averaging about 1.5 hours.
>|||After the 2 hour time period elapses, the recurring job doesn't run
again until the following day as scheduled.
Tuesday, March 20, 2012
scheduled jobs and daylight savings time
This must've been convered before, but I can seem to find a solution to it. Daylight Savings Time is about to end in my area, at which time the clocks will go backwards from 1:59am to 1:00am.
I have scheduled jobs that run every minute, and I'm expecting that when the clock rolls back, they will stop running for the gained hour until the clock catches back up.
So, I need an automated way to correct this.
I was looking at the msdb..sysjobschedules table, at the next_run_time column. But it doesn't make much sense. That value will periodically update, but it is always a good bit behind the next run time reported in EM. And manually updating it seems to have no effect.
Is there a way to get a job to run or to recalculate the next run time via tsql script?you can start a job via tsql with a call to msdb.dbo.sp_start_job.
it's got an entry in BOL.
If my memory serves correctly, EM figures out when the job is running next by calling msdb.dbo.sp_help_job (also in BOL). EDIT: you could verify this by turning on profiler and then opening up the job activity UI in EM.|||A googled about a bit, and found an article (http://blog.ragan.com/archives/sqlblog/2004/11/mvp_ron_talmage.html) that seems to explain it all. The next_run_time in the system table is "left hanging" by the time change. The next_run_time is reset to 2:01, and SQL Agent dutifully waits until 2:01 arrives, even it if is an hour away from 2:00. If you get the job to run at the second 1:01 AM, it should execute normally for the rest of the extra hour. The only problem is, getting it to run at that time. I don't suppose you have a server kicking about that does not change it's time automatically?|||Well, I can't seem to get it working.
On a test server I stopped my jobs (they run every minute). I then set the clock back and hour. I waited several minutes and as I expected, the jobs didn't start. So I executed sp_start_job, which did start the job. I expected that when the job completed, it would re-calculate the next-run time, but that didn't happen. So I ran sp_help_job. No change. I then manually updated the next_run_time and set the value to 0, then manually started the job again. Still no change. I even stopped and restarted the SQL Server Agent. Nothing.
I can't seem to get it to recalculate the next-run time. Frustrating.
There must be an easy solution, it seems like it would be a somewhat common problem.|||Found a way to trick it. If I run sp_update_jobschedule and disable and re-enable the schedule, it re-calcs the time and my jobs start back on schedule.
sp_update_jobschedule @.name = 'schedulename', @.job_name = 'jobname', @.enabled = 0
sp_update_jobschedule @.name = 'schedulename', @.job_name = 'jobname', @.enabled = 1
Thanks for the replies so far.|||Just in case anyone needs it, here is a script which forces all the enabled jobs to re-calc their start times.
DECLARE @.jobname varchar(128)
DECLARE @.schedname varchar(128)
DECLARE tableCursor INSENSITIVE CURSOR FOR
SELECT job.name, sched.name
FROM msdb.dbo.sysjobs job, msdb.dbo.sysjobschedules sched
WHERE job.job_id = sched.job_id
AND job.enabled = 1
AND sched.enabled = 1
OPEN tableCursor
IF @.@.CURSOR_ROWS <> 0
BEGIN
FETCH NEXT FROM tableCursor INTO @.jobname, @.schedname
WHILE (@.@.FETCH_STATUS = 0)
BEGIN
-------------
EXEC msdb.dbo.sp_update_jobschedule @.name = @.schedname, @.job_name = @.jobname, @.enabled = 0
EXEC msdb.dbo.sp_update_jobschedule @.name = @.schedname, @.job_name = @.jobname, @.enabled = 1
-------------
FETCH NEXT FROM tableCursor INTO @.jobname, @.schedname
END -- WHILE (@.@.FETCH_STATUS = 0)
END -- IF @.@.CURSOR_ROWS <> 0
CLOSE tableCursor
DEALLOCATE tableCursor
I have scheduled jobs that run every minute, and I'm expecting that when the clock rolls back, they will stop running for the gained hour until the clock catches back up.
So, I need an automated way to correct this.
I was looking at the msdb..sysjobschedules table, at the next_run_time column. But it doesn't make much sense. That value will periodically update, but it is always a good bit behind the next run time reported in EM. And manually updating it seems to have no effect.
Is there a way to get a job to run or to recalculate the next run time via tsql script?you can start a job via tsql with a call to msdb.dbo.sp_start_job.
it's got an entry in BOL.
If my memory serves correctly, EM figures out when the job is running next by calling msdb.dbo.sp_help_job (also in BOL). EDIT: you could verify this by turning on profiler and then opening up the job activity UI in EM.|||A googled about a bit, and found an article (http://blog.ragan.com/archives/sqlblog/2004/11/mvp_ron_talmage.html) that seems to explain it all. The next_run_time in the system table is "left hanging" by the time change. The next_run_time is reset to 2:01, and SQL Agent dutifully waits until 2:01 arrives, even it if is an hour away from 2:00. If you get the job to run at the second 1:01 AM, it should execute normally for the rest of the extra hour. The only problem is, getting it to run at that time. I don't suppose you have a server kicking about that does not change it's time automatically?|||Well, I can't seem to get it working.
On a test server I stopped my jobs (they run every minute). I then set the clock back and hour. I waited several minutes and as I expected, the jobs didn't start. So I executed sp_start_job, which did start the job. I expected that when the job completed, it would re-calculate the next-run time, but that didn't happen. So I ran sp_help_job. No change. I then manually updated the next_run_time and set the value to 0, then manually started the job again. Still no change. I even stopped and restarted the SQL Server Agent. Nothing.
I can't seem to get it to recalculate the next-run time. Frustrating.
There must be an easy solution, it seems like it would be a somewhat common problem.|||Found a way to trick it. If I run sp_update_jobschedule and disable and re-enable the schedule, it re-calcs the time and my jobs start back on schedule.
sp_update_jobschedule @.name = 'schedulename', @.job_name = 'jobname', @.enabled = 0
sp_update_jobschedule @.name = 'schedulename', @.job_name = 'jobname', @.enabled = 1
Thanks for the replies so far.|||Just in case anyone needs it, here is a script which forces all the enabled jobs to re-calc their start times.
DECLARE @.jobname varchar(128)
DECLARE @.schedname varchar(128)
DECLARE tableCursor INSENSITIVE CURSOR FOR
SELECT job.name, sched.name
FROM msdb.dbo.sysjobs job, msdb.dbo.sysjobschedules sched
WHERE job.job_id = sched.job_id
AND job.enabled = 1
AND sched.enabled = 1
OPEN tableCursor
IF @.@.CURSOR_ROWS <> 0
BEGIN
FETCH NEXT FROM tableCursor INTO @.jobname, @.schedname
WHILE (@.@.FETCH_STATUS = 0)
BEGIN
-------------
EXEC msdb.dbo.sp_update_jobschedule @.name = @.schedname, @.job_name = @.jobname, @.enabled = 0
EXEC msdb.dbo.sp_update_jobschedule @.name = @.schedname, @.job_name = @.jobname, @.enabled = 1
-------------
FETCH NEXT FROM tableCursor INTO @.jobname, @.schedname
END -- WHILE (@.@.FETCH_STATUS = 0)
END -- IF @.@.CURSOR_ROWS <> 0
CLOSE tableCursor
DEALLOCATE tableCursor
scheduled job runs forewer
Hello,
I have scheduled job that are scheduled to run every 2 hours.
Its exec stored procedures. Normal execution time is up to 10 min.
But recently job not running successfully, its just executes forever. So I had to kill that job and I run it manually.
Please help,
I have no idea why it stops executing on its own by the schedule.
Thank you,did you use sp_who2 to see if it is blocked?
did you use dbcc_inputbuffer or sql_handle to see if the code executing changed?
did you create an output file in the job scheduler to capture output from the job steps?
did you change the procs to write to the output file as each starts, runs, and ends?
did you logically think "what can i do to troubleshoot this issue?"
did you google for similar situations?
did you look at the "sticky" at the top of the forum to see what you might need to add to your post to help us help you?|||Thank you for all of the suggestions you have for me.
I will try them one by one.|||How about trying one of the easiest things, stop and start the sql agent. Sometimes the scheduler gets wacked out and a simple stop and start will fix it.|||Does the code contains loops or cursors?|||Does the code contains loops or cursors?
while (1=1)
begin
print 'probably'
end|||The procedure does contain cursors and it runs Ok via SQL Query Analyzer, but once I add it up to SQL Server Agent Job it takes forever...
I do have an output file to capture output from the job steps, but since the job never been completed, and I had to kill it, there are no completion info.
If I will stop and start the sql agent before execution of this job, how the other scheduled processes be affected by that?
Thank you|||Whatever other issues may be occurring, step #1 is to drop the cursors and use set-based operations.|||Unless the jobs sends separate e-mails to employees, for example...|||The procedure does send an e-mail to few employees. The proc was written way before I started my work within the company, I already suggested to go trough code, and rewrite some sql - got rejection, so not sure how else to handle the issues.
Thank you.|||...I already suggested to go trough code, and rewrite some sql - got rejectionBlindman's principle of employement: Never work for people who aren't as smart as you.|||Does that make you unemployed Blinddude? :p|||Does that make you unemployed Blinddude? :p
More like unemployable.;)
hmscott|||that's how you guys have so much time to post.|||your boss doesn't have to be as smart as you.
what's important is that he/she does what you tell them to do. :)
I have scheduled job that are scheduled to run every 2 hours.
Its exec stored procedures. Normal execution time is up to 10 min.
But recently job not running successfully, its just executes forever. So I had to kill that job and I run it manually.
Please help,
I have no idea why it stops executing on its own by the schedule.
Thank you,did you use sp_who2 to see if it is blocked?
did you use dbcc_inputbuffer or sql_handle to see if the code executing changed?
did you create an output file in the job scheduler to capture output from the job steps?
did you change the procs to write to the output file as each starts, runs, and ends?
did you logically think "what can i do to troubleshoot this issue?"
did you google for similar situations?
did you look at the "sticky" at the top of the forum to see what you might need to add to your post to help us help you?|||Thank you for all of the suggestions you have for me.
I will try them one by one.|||How about trying one of the easiest things, stop and start the sql agent. Sometimes the scheduler gets wacked out and a simple stop and start will fix it.|||Does the code contains loops or cursors?|||Does the code contains loops or cursors?
while (1=1)
begin
print 'probably'
end|||The procedure does contain cursors and it runs Ok via SQL Query Analyzer, but once I add it up to SQL Server Agent Job it takes forever...
I do have an output file to capture output from the job steps, but since the job never been completed, and I had to kill it, there are no completion info.
If I will stop and start the sql agent before execution of this job, how the other scheduled processes be affected by that?
Thank you|||Whatever other issues may be occurring, step #1 is to drop the cursors and use set-based operations.|||Unless the jobs sends separate e-mails to employees, for example...|||The procedure does send an e-mail to few employees. The proc was written way before I started my work within the company, I already suggested to go trough code, and rewrite some sql - got rejection, so not sure how else to handle the issues.
Thank you.|||...I already suggested to go trough code, and rewrite some sql - got rejectionBlindman's principle of employement: Never work for people who aren't as smart as you.|||Does that make you unemployed Blinddude? :p|||Does that make you unemployed Blinddude? :p
More like unemployable.;)
hmscott|||that's how you guys have so much time to post.|||your boss doesn't have to be as smart as you.
what's important is that he/she does what you tell them to do. :)
Scheduled job finish time
I would like to find out how long the last execution of a scheduled
task takes to run. Each job i'm looking at has only 1 task. I'm not
crazy about the idea of creating a fake job step to be able to see when
that step starts to know when the "real" job step ended. Is there a
good way to find out the run duration for a job?
KalvinNot sure I follow you. If you right click on the job and choose History you
can see the time the job took. If you check the box for the details it will
expand and show each step as well. If you only have one step (which every
job needs) it is pretty obvious either way.
Andrew J. Kelly SQL MVP
"Kalvin" <ktuel@.streck.com> wrote in message
news:1121874591.381433.81960@.g44g2000cwa.googlegroups.com...
>I would like to find out how long the last execution of a scheduled
> task takes to run. Each job i'm looking at has only 1 task. I'm not
> crazy about the idea of creating a fake job step to be able to see when
> that step starts to know when the "real" job step ended. Is there a
> good way to find out the run duration for a job?
> Kalvin
>|||Would the following system SP give you what you need:
sp_help_jobhistory [ [ @.job_id = ] job_id ]
[ , [ @.job_name = ] 'job_name' ]
[ , [ @.step_id = ] step_id ]
[ , [ @.sql_message_id = ] sql_message_id ]
[ , [ @.sql_severity = ] sql_severity ]
[ , [ @.start_run_date = ] start_run_date ]
[ , [ @.end_run_date = ] end_run_date ]
[ , [ @.start_run_time = ] start_run_time ]
[ , [ @.end_run_time = ] end_run_time ]
[ , [ @.minimum_run_duration = ] minimum_run_duration ]
[ , [ @.run_status = ] run_status ]
[ , [ @.minimum_retries = ] minimum_retries ]
[ , [ @.oldest_first = ] oldest_first ]
[ , [ @.server = ] 'server' ]
[ , [ @.mode = ] 'mode' ]
"Kalvin" <ktuel@.streck.com> wrote in message
news:1121874591.381433.81960@.g44g2000cwa.googlegroups.com...
>I would like to find out how long the last execution of a scheduled
> task takes to run. Each job i'm looking at has only 1 task. I'm not
> crazy about the idea of creating a fake job step to be able to see when
> that step starts to know when the "real" job step ended. Is there a
> good way to find out the run duration for a job?
> Kalvin
>|||yes, that does it.
Thanks
Kalvin
*** Sent via Developersdex http://www.examnotes.net ***
task takes to run. Each job i'm looking at has only 1 task. I'm not
crazy about the idea of creating a fake job step to be able to see when
that step starts to know when the "real" job step ended. Is there a
good way to find out the run duration for a job?
KalvinNot sure I follow you. If you right click on the job and choose History you
can see the time the job took. If you check the box for the details it will
expand and show each step as well. If you only have one step (which every
job needs) it is pretty obvious either way.
Andrew J. Kelly SQL MVP
"Kalvin" <ktuel@.streck.com> wrote in message
news:1121874591.381433.81960@.g44g2000cwa.googlegroups.com...
>I would like to find out how long the last execution of a scheduled
> task takes to run. Each job i'm looking at has only 1 task. I'm not
> crazy about the idea of creating a fake job step to be able to see when
> that step starts to know when the "real" job step ended. Is there a
> good way to find out the run duration for a job?
> Kalvin
>|||Would the following system SP give you what you need:
sp_help_jobhistory [ [ @.job_id = ] job_id ]
[ , [ @.job_name = ] 'job_name' ]
[ , [ @.step_id = ] step_id ]
[ , [ @.sql_message_id = ] sql_message_id ]
[ , [ @.sql_severity = ] sql_severity ]
[ , [ @.start_run_date = ] start_run_date ]
[ , [ @.end_run_date = ] end_run_date ]
[ , [ @.start_run_time = ] start_run_time ]
[ , [ @.end_run_time = ] end_run_time ]
[ , [ @.minimum_run_duration = ] minimum_run_duration ]
[ , [ @.run_status = ] run_status ]
[ , [ @.minimum_retries = ] minimum_retries ]
[ , [ @.oldest_first = ] oldest_first ]
[ , [ @.server = ] 'server' ]
[ , [ @.mode = ] 'mode' ]
"Kalvin" <ktuel@.streck.com> wrote in message
news:1121874591.381433.81960@.g44g2000cwa.googlegroups.com...
>I would like to find out how long the last execution of a scheduled
> task takes to run. Each job i'm looking at has only 1 task. I'm not
> crazy about the idea of creating a fake job step to be able to see when
> that step starts to know when the "real" job step ended. Is there a
> good way to find out the run duration for a job?
> Kalvin
>|||yes, that does it.
Thanks
Kalvin
*** Sent via Developersdex http://www.examnotes.net ***
Monday, March 12, 2012
Scheduled email subscription can't be sent out on time
I have a report which is scheduled to be sent out by email every Tuesday at
4pm. It used to run and be sent out on time. Then I changed the report a
little adding a couple more subreports, the report being sent out that week
was a few minutes delayed but it was ok. Then I installed Reporting Services
SP1 and from that week the report was delayed over 12 hours to be sent out
and it is like this since then. I dropped the old shared schedule and added a
new shaed schedule but the report still can't be sent out on time. Does
anybody have any idea how to fix it?
Thanks,
MaryIs you Sql Server on the same box? Is it possible the clock on the machine
that has SQL is 12 hours off?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> I have a report which is scheduled to be sent out by email every Tuesday
at
> 4pm. It used to run and be sent out on time. Then I changed the report a
> little adding a couple more subreports, the report being sent out that
week
> was a few minutes delayed but it was ok. Then I installed Reporting
Services
> SP1 and from that week the report was delayed over 12 hours to be sent out
> and it is like this since then. I dropped the old shared schedule and
added a
> new shaed schedule but the report still can't be sent out on time. Does
> anybody have any idea how to fix it?
> Thanks,
> Mary|||Daniel,
Thank you for your response. Sql Server is on the same box, and the clock on
that machine is fine. The report was sent out on time before I installed SP1.
Any idea about why this could happen?
Thanks.
"Daniel Reib [MSFT]" wrote:
> Is you Sql Server on the same box? Is it possible the clock on the machine
> that has SQL is 12 hours off?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mary" <Mary@.discussions.microsoft.com> wrote in message
> news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > I have a report which is scheduled to be sent out by email every Tuesday
> at
> > 4pm. It used to run and be sent out on time. Then I changed the report a
> > little adding a couple more subreports, the report being sent out that
> week
> > was a few minutes delayed but it was ok. Then I installed Reporting
> Services
> > SP1 and from that week the report was delayed over 12 hours to be sent out
> > and it is like this since then. I dropped the old shared schedule and
> added a
> > new shaed schedule but the report still can't be sent out on time. Does
> > anybody have any idea how to fix it?
> >
> > Thanks,
> >
> > Mary
>
>|||Can you look at the SQL job that was created to see when it is scheduled to
fire.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> Daniel,
> Thank you for your response. Sql Server is on the same box, and the clock
on
> that machine is fine. The report was sent out on time before I installed
SP1.
> Any idea about why this could happen?
> Thanks.
> "Daniel Reib [MSFT]" wrote:
> > Is you Sql Server on the same box? Is it possible the clock on the
machine
> > that has SQL is 12 hours off?
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > I have a report which is scheduled to be sent out by email every
Tuesday
> > at
> > > 4pm. It used to run and be sent out on time. Then I changed the report
a
> > > little adding a couple more subreports, the report being sent out that
> > week
> > > was a few minutes delayed but it was ok. Then I installed Reporting
> > Services
> > > SP1 and from that week the report was delayed over 12 hours to be sent
out
> > > and it is like this since then. I dropped the old shared schedule and
> > added a
> > > new shaed schedule but the report still can't be sent out on time.
Does
> > > anybody have any idea how to fix it?
> > >
> > > Thanks,
> > >
> > > Mary
> >
> >
> >|||Ok, I am assuming that is what you expect. The next thing to check would be
to check the history of the job. Make sure that it is firing when you
expect. If they are then look in the ReportServerService<date>.log file.
Around the time the schedule is fired an event should be picked up from the
Event table, and this should be logged.
Can you verify that all of this is happening.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> Daniel,
> The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> Thanks
> "Daniel Reib [MSFT]" wrote:
> > Can you look at the SQL job that was created to see when it is scheduled
to
> > fire.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > Daniel,
> > >
> > > Thank you for your response. Sql Server is on the same box, and the
clock
> > on
> > > that machine is fine. The report was sent out on time before I
installed
> > SP1.
> > > Any idea about why this could happen?
> > >
> > > Thanks.
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > Is you Sql Server on the same box? Is it possible the clock on the
> > machine
> > > > that has SQL is 12 hours off?
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > I have a report which is scheduled to be sent out by email every
> > Tuesday
> > > > at
> > > > > 4pm. It used to run and be sent out on time. Then I changed the
report
> > a
> > > > > little adding a couple more subreports, the report being sent out
that
> > > > week
> > > > > was a few minutes delayed but it was ok. Then I installed
Reporting
> > > > Services
> > > > > SP1 and from that week the report was delayed over 12 hours to be
sent
> > out
> > > > > and it is like this since then. I dropped the old shared schedule
and
> > > > added a
> > > > > new shaed schedule but the report still can't be sent out on time.
> > Does
> > > > > anybody have any idea how to fix it?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Mary
> > > >
> > > >
> > > >
> >
> >
> >|||Daniel,
One thing I want to mention is that I changed the schedule to the new
schedule last week for the report to be sent out on every Monday 4pm with
which the latest running time was on 8/09 at 4pm. I checked the history of
the job and it was running at 8/09/2004 4pm. Then I checked the log file
around that time. There is no any event for this job on 8/09 at 4pm, but I
found the event for this job on the log file dated at 8/10/2004 2:02am which
was the actual time this report was sent out this morning. I cut that part of
the log file for this job and paste it here:
ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56 AM.
ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at 8/10/2004 2:02:56
AM.
Thanks
"Daniel Reib [MSFT]" wrote:
> Ok, I am assuming that is what you expect. The next thing to check would be
> to check the history of the job. Make sure that it is firing when you
> expect. If they are then look in the ReportServerService<date>.log file.
> Around the time the schedule is fired an event should be picked up from the
> Event table, and this should be logged.
> Can you verify that all of this is happening.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mary" <Mary@.discussions.microsoft.com> wrote in message
> news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > Daniel,
> >
> > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> >
> > Thanks
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > Can you look at the SQL job that was created to see when it is scheduled
> to
> > > fire.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > Daniel,
> > > >
> > > > Thank you for your response. Sql Server is on the same box, and the
> clock
> > > on
> > > > that machine is fine. The report was sent out on time before I
> installed
> > > SP1.
> > > > Any idea about why this could happen?
> > > >
> > > > Thanks.
> > > >
> > > > "Daniel Reib [MSFT]" wrote:
> > > >
> > > > > Is you Sql Server on the same box? Is it possible the clock on the
> > > machine
> > > > > that has SQL is 12 hours off?
> > > > >
> > > > > --
> > > > > -Daniel
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > >
> > > > >
> > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > I have a report which is scheduled to be sent out by email every
> > > Tuesday
> > > > > at
> > > > > > 4pm. It used to run and be sent out on time. Then I changed the
> report
> > > a
> > > > > > little adding a couple more subreports, the report being sent out
> that
> > > > > week
> > > > > > was a few minutes delayed but it was ok. Then I installed
> Reporting
> > > > > Services
> > > > > > SP1 and from that week the report was delayed over 12 hours to be
> sent
> > > out
> > > > > > and it is like this since then. I dropped the old shared schedule
> and
> > > > > added a
> > > > > > new shaed schedule but the report still can't be sent out on time.
> > > Does
> > > > > > anybody have any idea how to fix it?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Mary
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||What happens if you run the job manually. Right click on the Sql Agent job
and choose start job. This should cause the job to execute.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> Daniel,
> One thing I want to mention is that I changed the schedule to the new
> schedule last week for the report to be sent out on every Monday 4pm with
> which the latest running time was on 8/09 at 4pm. I checked the history
of
> the job and it was running at 8/09/2004 4pm. Then I checked the log file
> around that time. There is no any event for this job on 8/09 at 4pm, but I
> found the event for this job on the log file dated at 8/10/2004 2:02am
which
> was the actual time this report was sent out this morning. I cut that part
of
> the log file for this job and paste it here:
> ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56 AM.
> ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at 8/10/2004
2:02:56
> AM.
> Thanks
> "Daniel Reib [MSFT]" wrote:
> > Ok, I am assuming that is what you expect. The next thing to check
would be
> > to check the history of the job. Make sure that it is firing when you
> > expect. If they are then look in the ReportServerService<date>.log
file.
> > Around the time the schedule is fired an event should be picked up from
the
> > Event table, and this should be logged.
> >
> > Can you verify that all of this is happening.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > Daniel,
> > >
> > > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> > >
> > > Thanks
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > Can you look at the SQL job that was created to see when it is
scheduled
> > to
> > > > fire.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > Daniel,
> > > > >
> > > > > Thank you for your response. Sql Server is on the same box, and
the
> > clock
> > > > on
> > > > > that machine is fine. The report was sent out on time before I
> > installed
> > > > SP1.
> > > > > Any idea about why this could happen?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > Is you Sql Server on the same box? Is it possible the clock on
the
> > > > machine
> > > > > > that has SQL is 12 hours off?
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > I have a report which is scheduled to be sent out by email
every
> > > > Tuesday
> > > > > > at
> > > > > > > 4pm. It used to run and be sent out on time. Then I changed
the
> > report
> > > > a
> > > > > > > little adding a couple more subreports, the report being sent
out
> > that
> > > > > > week
> > > > > > > was a few minutes delayed but it was ok. Then I installed
> > Reporting
> > > > > > Services
> > > > > > > SP1 and from that week the report was delayed over 12 hours to
be
> > sent
> > > > out
> > > > > > > and it is like this since then. I dropped the old shared
schedule
> > and
> > > > > > added a
> > > > > > > new shaed schedule but the report still can't be sent out on
time.
> > > > Does
> > > > > > > anybody have any idea how to fix it?
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Mary
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||When you manually start the job a row should be placed in the Event table in
the report server database. Is this happening? Also can you tell me the
value for the element PollingInterval in the rsreportserver.config file.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> I just manually started the job 10 minutes ago and the SQL job was running
> successfully. But there was no event fired around that time for this job
when
> I checked the report server log file and also there was no email coming in
to
> the mailbox so far.
> "Daniel Reib [MSFT]" wrote:
> > What happens if you run the job manually. Right click on the Sql Agent
job
> > and choose start job. This should cause the job to execute.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > Daniel,
> > >
> > > One thing I want to mention is that I changed the schedule to the new
> > > schedule last week for the report to be sent out on every Monday 4pm
with
> > > which the latest running time was on 8/09 at 4pm. I checked the
history
> > of
> > > the job and it was running at 8/09/2004 4pm. Then I checked the log
file
> > > around that time. There is no any event for this job on 8/09 at 4pm,
but I
> > > found the event for this job on the log file dated at 8/10/2004 2:02am
> > which
> > > was the actual time this report was sent out this morning. I cut that
part
> > of
> > > the log file for this job and paste it here:
> > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56 AM.
> > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at 8/10/2004
> > 2:02:56
> > > AM.
> > >
> > > Thanks
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > Ok, I am assuming that is what you expect. The next thing to check
> > would be
> > > > to check the history of the job. Make sure that it is firing when
you
> > > > expect. If they are then look in the ReportServerService<date>.log
> > file.
> > > > Around the time the schedule is fired an event should be picked up
from
> > the
> > > > Event table, and this should be logged.
> > > >
> > > > Can you verify that all of this is happening.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > Daniel,
> > > > >
> > > > > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> > > > >
> > > > > Thanks
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > Can you look at the SQL job that was created to see when it is
> > scheduled
> > > > to
> > > > > > fire.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > Daniel,
> > > > > > >
> > > > > > > Thank you for your response. Sql Server is on the same box,
and
> > the
> > > > clock
> > > > > > on
> > > > > > > that machine is fine. The report was sent out on time before I
> > > > installed
> > > > > > SP1.
> > > > > > > Any idea about why this could happen?
> > > > > > >
> > > > > > > Thanks.
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > Is you Sql Server on the same box? Is it possible the clock
on
> > the
> > > > > > machine
> > > > > > > > that has SQL is 12 hours off?
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > I have a report which is scheduled to be sent out by email
> > every
> > > > > > Tuesday
> > > > > > > > at
> > > > > > > > > 4pm. It used to run and be sent out on time. Then I
changed
> > the
> > > > report
> > > > > > a
> > > > > > > > > little adding a couple more subreports, the report being
sent
> > out
> > > > that
> > > > > > > > week
> > > > > > > > > was a few minutes delayed but it was ok. Then I installed
> > > > Reporting
> > > > > > > > Services
> > > > > > > > > SP1 and from that week the report was delayed over 12
hours to
> > be
> > > > sent
> > > > > > out
> > > > > > > > > and it is like this since then. I dropped the old shared
> > schedule
> > > > and
> > > > > > > > added a
> > > > > > > > > new shaed schedule but the report still can't be sent out
on
> > time.
> > > > > > Does
> > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > >
> > > > > > > > > Mary
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||So try this:
Turn off the reportServer service
Run the job manually
See if a row is in the events table
Turn on the ReportServer service
See if row disappears
Send me the latest reportserverservice<date>.log file
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:79C1481E-78A5-4594-8758-8AECD43776A6@.microsoft.com...
> Daniel,
> I checked Event table in report server database on that machine and there
is
> currently no row in that table. The value for PollingInterval is 10.
> Thanks
>
> "Daniel Reib [MSFT]" wrote:
> > When you manually start the job a row should be placed in the Event
table in
> > the report server database. Is this happening? Also can you tell me
the
> > value for the element PollingInterval in the rsreportserver.config file.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> > > I just manually started the job 10 minutes ago and the SQL job was
running
> > > successfully. But there was no event fired around that time for this
job
> > when
> > > I checked the report server log file and also there was no email
coming in
> > to
> > > the mailbox so far.
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > What happens if you run the job manually. Right click on the Sql
Agent
> > job
> > > > and choose start job. This should cause the job to execute.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > > > Daniel,
> > > > >
> > > > > One thing I want to mention is that I changed the schedule to the
new
> > > > > schedule last week for the report to be sent out on every Monday
4pm
> > with
> > > > > which the latest running time was on 8/09 at 4pm. I checked the
> > history
> > > > of
> > > > > the job and it was running at 8/09/2004 4pm. Then I checked the
log
> > file
> > > > > around that time. There is no any event for this job on 8/09 at
4pm,
> > but I
> > > > > found the event for this job on the log file dated at 8/10/2004
2:02am
> > > > which
> > > > > was the actual time this report was sent out this morning. I cut
that
> > part
> > > > of
> > > > > the log file for this job and paste it here:
> > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56
AM.
> > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at
8/10/2004
> > > > 2:02:56
> > > > > AM.
> > > > >
> > > > > Thanks
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > Ok, I am assuming that is what you expect. The next thing to
check
> > > > would be
> > > > > > to check the history of the job. Make sure that it is firing
when
> > you
> > > > > > expect. If they are then look in the
ReportServerService<date>.log
> > > > file.
> > > > > > Around the time the schedule is fired an event should be picked
up
> > from
> > > > the
> > > > > > Event table, and this should be logged.
> > > > > >
> > > > > > Can you verify that all of this is happening.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > > > Daniel,
> > > > > > >
> > > > > > > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > Can you look at the SQL job that was created to see when it
is
> > > > scheduled
> > > > > > to
> > > > > > > > fire.
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > > > Daniel,
> > > > > > > > >
> > > > > > > > > Thank you for your response. Sql Server is on the same
box,
> > and
> > > > the
> > > > > > clock
> > > > > > > > on
> > > > > > > > > that machine is fine. The report was sent out on time
before I
> > > > > > installed
> > > > > > > > SP1.
> > > > > > > > > Any idea about why this could happen?
> > > > > > > > >
> > > > > > > > > Thanks.
> > > > > > > > >
> > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > >
> > > > > > > > > > Is you Sql Server on the same box? Is it possible the
clock
> > on
> > > > the
> > > > > > > > machine
> > > > > > > > > > that has SQL is 12 hours off?
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > -Daniel
> > > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > confers
> > > > no
> > > > > > > > rights.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > >
news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > > > I have a report which is scheduled to be sent out by
email
> > > > every
> > > > > > > > Tuesday
> > > > > > > > > > at
> > > > > > > > > > > 4pm. It used to run and be sent out on time. Then I
> > changed
> > > > the
> > > > > > report
> > > > > > > > a
> > > > > > > > > > > little adding a couple more subreports, the report
being
> > sent
> > > > out
> > > > > > that
> > > > > > > > > > week
> > > > > > > > > > > was a few minutes delayed but it was ok. Then I
installed
> > > > > > Reporting
> > > > > > > > > > Services
> > > > > > > > > > > SP1 and from that week the report was delayed over 12
> > hours to
> > > > be
> > > > > > sent
> > > > > > > > out
> > > > > > > > > > > and it is like this since then. I dropped the old
shared
> > > > schedule
> > > > > > and
> > > > > > > > > > added a
> > > > > > > > > > > new shaed schedule but the report still can't be sent
out
> > on
> > > > time.
> > > > > > > > Does
> > > > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > >
> > > > > > > > > > > Mary
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||I turned off reportServe service and ran the job manually, there was no row
in Event table. Then I turned on the service and there is still no row in
that table. We have some jobs scheduled to run every 10 minutes, so the log
file is big. I don't see anywhere I can send attachment, so I'm sending you
the part aroud 3:24pm when the job was last run. Again, I don't see anything
in the log file for this job around 3:24pm.
ReportingServicesService!library!d98!08/11/2004-15:23:52:: i INFO:
Initializing EnableExecutionLogging to 'True' as specified in Server system
properties.
ReportingServicesService!library!230!8/11/2004-15:23:52:: i INFO:
Initializing EnableExecutionLogging to 'True' as specified in Server system
properties.
ReportingServicesService!library!cf0!8/11/2004-15:23:52:: i INFO:
Initializing EnableExecutionLogging to 'True' as specified in Server system
properties.
ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004 3:23:52
PM.
ReportingServicesService!library!cf0!8/11/2004-15:23:52:: Schedule
87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004 3:23:52
PM.
ReportingServicesService!dbpolling!230!8/11/2004-15:23:52:: EventPolling
finished processing item 4cd4644b-8a15-43fd-baf1-c2ca8cbcd0d9
ReportingServicesService!dbpolling!d44!8/11/2004-15:23:52:: EventPolling
processing 1 more items. 4 Total items in internal queue.
ReportingServicesService!dbpolling!230!8/11/2004-15:23:52:: EventPolling
processing item a2ff2ad5-dc41-442b-ba91-d3a9e1d76a47
ReportingServicesService!dbpolling!cf0!8/11/2004-15:23:52:: EventPolling
finished processing item ec3f0cbd-0ec0-44bd-b714-6af044c06ba0
ReportingServicesService!library!d98!08/11/2004-15:23:52:: Schedule
87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 08/11/2004
15:23:52.
ReportingServicesService!dbpolling!d98!08/11/2004-15:23:52:: EventPolling
finished processing item b98d78ad-15dd-48ce-8c32-8db9fc716d61
ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
87d27b74-96a1-4f41-9df0-c451424665cf executed at 8/11/2004 3:23:52 PM.
ReportingServicesService!schedule!230!8/11/2004-15:23:52:: Updating report
execution snapshot for report /Summary Open Order Reports/OOCByDateFDR
ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54:: EventPolling
polling service stopped
ReportingServicesService!dbpolling!8c0!8/11/2004-15:23:54:: EventPolling
heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
NotificationPolling polling service stopped
ReportingServicesService!dbpolling!c48!8/11/2004-15:23:54::
NotificationPolling heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54:: SchedulePolling
polling service stopped
ReportingServicesService!servicecontroller!9e8!8/11/2004-15:23:54:: Service
controller exiting.
ReportingServicesService!processing!bc8!8/11/2004-15:23:54:: e ERROR:
Throwing
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query
execution failed for data set 'GMS'., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query
execution failed for data set 'GMS'. -->
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at
System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at
Microsoft.ReportingServices.DataExtensions.CommandWrapper.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.ReportProcessing.a0.v()
-- End of inner exception stack trace --
"Daniel Reib [MSFT]" wrote:
> So try this:
> Turn off the reportServer service
> Run the job manually
> See if a row is in the events table
> Turn on the ReportServer service
> See if row disappears
> Send me the latest reportserverservice<date>.log file
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mary" <Mary@.discussions.microsoft.com> wrote in message
> news:79C1481E-78A5-4594-8758-8AECD43776A6@.microsoft.com...
> > Daniel,
> >
> > I checked Event table in report server database on that machine and there
> is
> > currently no row in that table. The value for PollingInterval is 10.
> >
> > Thanks
> >
> >
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > When you manually start the job a row should be placed in the Event
> table in
> > > the report server database. Is this happening? Also can you tell me
> the
> > > value for the element PollingInterval in the rsreportserver.config file.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> > > > I just manually started the job 10 minutes ago and the SQL job was
> running
> > > > successfully. But there was no event fired around that time for this
> job
> > > when
> > > > I checked the report server log file and also there was no email
> coming in
> > > to
> > > > the mailbox so far.
> > > >
> > > > "Daniel Reib [MSFT]" wrote:
> > > >
> > > > > What happens if you run the job manually. Right click on the Sql
> Agent
> > > job
> > > > > and choose start job. This should cause the job to execute.
> > > > >
> > > > > --
> > > > > -Daniel
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > >
> > > > >
> > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > > > > Daniel,
> > > > > >
> > > > > > One thing I want to mention is that I changed the schedule to the
> new
> > > > > > schedule last week for the report to be sent out on every Monday
> 4pm
> > > with
> > > > > > which the latest running time was on 8/09 at 4pm. I checked the
> > > history
> > > > > of
> > > > > > the job and it was running at 8/09/2004 4pm. Then I checked the
> log
> > > file
> > > > > > around that time. There is no any event for this job on 8/09 at
> 4pm,
> > > but I
> > > > > > found the event for this job on the log file dated at 8/10/2004
> 2:02am
> > > > > which
> > > > > > was the actual time this report was sent out this morning. I cut
> that
> > > part
> > > > > of
> > > > > > the log file for this job and paste it here:
> > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56
> AM.
> > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at
> 8/10/2004
> > > > > 2:02:56
> > > > > > AM.
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > >
> > > > > > > Ok, I am assuming that is what you expect. The next thing to
> check
> > > > > would be
> > > > > > > to check the history of the job. Make sure that it is firing
> when
> > > you
> > > > > > > expect. If they are then look in the
> ReportServerService<date>.log
> > > > > file.
> > > > > > > Around the time the schedule is fired an event should be picked
> up
> > > from
> > > > > the
> > > > > > > Event table, and this should be logged.
> > > > > > >
> > > > > > > Can you verify that all of this is happening.
> > > > > > >
> > > > > > > --
> > > > > > > -Daniel
> > > > > > > This posting is provided "AS IS" with no warranties, and confers
> no
> > > > > rights.
> > > > > > >
> > > > > > >
> > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > > > > Daniel,
> > > > > > > >
> > > > > > > > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > >
> > > > > > > > > Can you look at the SQL job that was created to see when it
> is
> > > > > scheduled
> > > > > > > to
> > > > > > > > > fire.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > -Daniel
> > > > > > > > > This posting is provided "AS IS" with no warranties, and
> confers
> > > no
> > > > > > > rights.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > > > > Daniel,
> > > > > > > > > >
> > > > > > > > > > Thank you for your response. Sql Server is on the same
> box,
> > > and
> > > > > the
> > > > > > > clock
> > > > > > > > > on
> > > > > > > > > > that machine is fine. The report was sent out on time
> before I
> > > > > > > installed
> > > > > > > > > SP1.
> > > > > > > > > > Any idea about why this could happen?
> > > > > > > > > >
> > > > > > > > > > Thanks.
> > > > > > > > > >
> > > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > > >
> > > > > > > > > > > Is you Sql Server on the same box? Is it possible the
> clock
> > > on
> > > > > the
> > > > > > > > > machine
> > > > > > > > > > > that has SQL is 12 hours off?
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > -Daniel
> > > > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > > confers
> > > > > no
> > > > > > > > > rights.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > > >
> news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > > > > I have a report which is scheduled to be sent out by
> email
> > > > > every
> > > > > > > > > Tuesday
> > > > > > > > > > > at
> > > > > > > > > > > > 4pm. It used to run and be sent out on time. Then I
> > > changed
> > > > > the
> > > > > > > report
> > > > > > > > > a
> > > > > > > > > > > > little adding a couple more subreports, the report
> being
> > > sent
> > > > > out
> > > > > > > that
> > > > > > > > > > > week
> > > > > > > > > > > > was a few minutes delayed but it was ok. Then I
> installed
> > > > > > > Reporting
> > > > > > > > > > > Services
> > > > > > > > > > > > SP1 and from that week the report was delayed over 12
> > > hours to
> > > > > be
> > > > > > > sent
> > > > > > > > > out
> > > > > > > > > > > > and it is like this since then. I dropped the old
> shared
> > > > > schedule
> > > > > > > and
> > > > > > > > > > > added a
> > > > > > > > > > > > new shaed schedule but the report still can't be sent
> out
> > > on
> > > > > time.
> > > > > > > > > Does
> > > > > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks,
> > > > > > > > > > > >
> > > > > > > > > > > > Mary
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Ok, now we are getting somewhere. The fact that there was no row in the
event table after the job was fired is a problem. All the job does is call
a stored procedure which should enter a row in the event table. You say the
job fires successfully? There are no errors reported? Who is the job
owner?
Can you try running the command that the job runs from Query Analyzer? Run
it as the same user as the job. Does that add a row. If not was there an
error? You might also try running just the SQL in the stored proc that is
called, does that succeed? Do these with the reportServer service turned
off, otherwise if the row does get in then it will pick it up and delete the
row.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:778ADD45-9F76-4EAE-A58E-071B2DBC2AFA@.microsoft.com...
> I turned off reportServe service and ran the job manually, there was no
row
> in Event table. Then I turned on the service and there is still no row in
> that table. We have some jobs scheduled to run every 10 minutes, so the
log
> file is big. I don't see anywhere I can send attachment, so I'm sending
you
> the part aroud 3:24pm when the job was last run. Again, I don't see
anything
> in the log file for this job around 3:24pm.
> ReportingServicesService!library!d98!08/11/2004-15:23:52:: i INFO:
> Initializing EnableExecutionLogging to 'True' as specified in Server
system
> properties.
> ReportingServicesService!library!230!8/11/2004-15:23:52:: i INFO:
> Initializing EnableExecutionLogging to 'True' as specified in Server
system
> properties.
> ReportingServicesService!library!cf0!8/11/2004-15:23:52:: i INFO:
> Initializing EnableExecutionLogging to 'True' as specified in Server
system
> properties.
> ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
> 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004
3:23:52
> PM.
> ReportingServicesService!library!cf0!8/11/2004-15:23:52:: Schedule
> 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004
3:23:52
> PM.
> ReportingServicesService!dbpolling!230!8/11/2004-15:23:52:: EventPolling
> finished processing item 4cd4644b-8a15-43fd-baf1-c2ca8cbcd0d9
> ReportingServicesService!dbpolling!d44!8/11/2004-15:23:52:: EventPolling
> processing 1 more items. 4 Total items in internal queue.
> ReportingServicesService!dbpolling!230!8/11/2004-15:23:52:: EventPolling
> processing item a2ff2ad5-dc41-442b-ba91-d3a9e1d76a47
> ReportingServicesService!dbpolling!cf0!8/11/2004-15:23:52:: EventPolling
> finished processing item ec3f0cbd-0ec0-44bd-b714-6af044c06ba0
> ReportingServicesService!library!d98!08/11/2004-15:23:52:: Schedule
> 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 08/11/2004
> 15:23:52.
> ReportingServicesService!dbpolling!d98!08/11/2004-15:23:52:: EventPolling
> finished processing item b98d78ad-15dd-48ce-8c32-8db9fc716d61
> ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
> 87d27b74-96a1-4f41-9df0-c451424665cf executed at 8/11/2004 3:23:52 PM.
> ReportingServicesService!schedule!230!8/11/2004-15:23:52:: Updating report
> execution snapshot for report /Summary Open Order Reports/OOCByDateFDR
> ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54:: EventPolling
> polling service stopped
> ReportingServicesService!dbpolling!8c0!8/11/2004-15:23:54:: EventPolling
> heartbeat thread exiting for stop.
> ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
> NotificationPolling polling service stopped
> ReportingServicesService!dbpolling!c48!8/11/2004-15:23:54::
> NotificationPolling heartbeat thread exiting for stop.
> ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
SchedulePolling
> polling service stopped
> ReportingServicesService!servicecontroller!9e8!8/11/2004-15:23:54::
Service
> controller exiting.
> ReportingServicesService!processing!bc8!8/11/2004-15:23:54:: e ERROR:
> Throwing
> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Query
> execution failed for data set 'GMS'., ;
> Info:
> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Query
> execution failed for data set 'GMS'. -->
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior)
> at
>
System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(Comman
dBehavior behavior)
> at
>
Microsoft.ReportingServices.DataExtensions.CommandWrapper.ExecuteReader(Comm
andBehavior behavior)
> at Microsoft.ReportingServices.ReportProcessing.a0.v()
> -- End of inner exception stack trace --
>
> "Daniel Reib [MSFT]" wrote:
> > So try this:
> >
> > Turn off the reportServer service
> > Run the job manually
> > See if a row is in the events table
> > Turn on the ReportServer service
> > See if row disappears
> > Send me the latest reportserverservice<date>.log file
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:79C1481E-78A5-4594-8758-8AECD43776A6@.microsoft.com...
> > > Daniel,
> > >
> > > I checked Event table in report server database on that machine and
there
> > is
> > > currently no row in that table. The value for PollingInterval is 10.
> > >
> > > Thanks
> > >
> > >
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > When you manually start the job a row should be placed in the Event
> > table in
> > > > the report server database. Is this happening? Also can you tell
me
> > the
> > > > value for the element PollingInterval in the rsreportserver.config
file.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> > > > > I just manually started the job 10 minutes ago and the SQL job was
> > running
> > > > > successfully. But there was no event fired around that time for
this
> > job
> > > > when
> > > > > I checked the report server log file and also there was no email
> > coming in
> > > > to
> > > > > the mailbox so far.
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > What happens if you run the job manually. Right click on the
Sql
> > Agent
> > > > job
> > > > > > and choose start job. This should cause the job to execute.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > > > > > Daniel,
> > > > > > >
> > > > > > > One thing I want to mention is that I changed the schedule to
the
> > new
> > > > > > > schedule last week for the report to be sent out on every
Monday
> > 4pm
> > > > with
> > > > > > > which the latest running time was on 8/09 at 4pm. I checked
the
> > > > history
> > > > > > of
> > > > > > > the job and it was running at 8/09/2004 4pm. Then I checked
the
> > log
> > > > file
> > > > > > > around that time. There is no any event for this job on 8/09
at
> > 4pm,
> > > > but I
> > > > > > > found the event for this job on the log file dated at
8/10/2004
> > 2:02am
> > > > > > which
> > > > > > > was the actual time this report was sent out this morning. I
cut
> > that
> > > > part
> > > > > > of
> > > > > > > the log file for this job and paste it here:
> > > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56::
Schedule
> > > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004
2:02:56
> > AM.
> > > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56::
Schedule
> > > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at
> > 8/10/2004
> > > > > > 2:02:56
> > > > > > > AM.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > Ok, I am assuming that is what you expect. The next thing
to
> > check
> > > > > > would be
> > > > > > > > to check the history of the job. Make sure that it is
firing
> > when
> > > > you
> > > > > > > > expect. If they are then look in the
> > ReportServerService<date>.log
> > > > > > file.
> > > > > > > > Around the time the schedule is fired an event should be
picked
> > up
> > > > from
> > > > > > the
> > > > > > > > Event table, and this should be logged.
> > > > > > > >
> > > > > > > > Can you verify that all of this is happening.
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > > > > > Daniel,
> > > > > > > > >
> > > > > > > > > The SQL job is scheduled to fire on Every week on Tuesday
4pm.
> > > > > > > > >
> > > > > > > > > Thanks
> > > > > > > > >
> > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > >
> > > > > > > > > > Can you look at the SQL job that was created to see when
it
> > is
> > > > > > scheduled
> > > > > > > > to
> > > > > > > > > > fire.
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > -Daniel
> > > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > confers
> > > > no
> > > > > > > > rights.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > >
news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > > > > > Daniel,
> > > > > > > > > > >
> > > > > > > > > > > Thank you for your response. Sql Server is on the same
> > box,
> > > > and
> > > > > > the
> > > > > > > > clock
> > > > > > > > > > on
> > > > > > > > > > > that machine is fine. The report was sent out on time
> > before I
> > > > > > > > installed
> > > > > > > > > > SP1.
> > > > > > > > > > > Any idea about why this could happen?
> > > > > > > > > > >
> > > > > > > > > > > Thanks.
> > > > > > > > > > >
> > > > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Is you Sql Server on the same box? Is it possible
the
> > clock
> > > > on
> > > > > > the
> > > > > > > > > > machine
> > > > > > > > > > > > that has SQL is 12 hours off?
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > -Daniel
> > > > > > > > > > > > This posting is provided "AS IS" with no warranties,
and
> > > > confers
> > > > > > no
> > > > > > > > > > rights.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in
message
> > > > > > > > > > > >
> > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > > > > > I have a report which is scheduled to be sent out
by
> > email
> > > > > > every
> > > > > > > > > > Tuesday
> > > > > > > > > > > > at
> > > > > > > > > > > > > 4pm. It used to run and be sent out on time. Then
I
> > > > changed
> > > > > > the
> > > > > > > > report
> > > > > > > > > > a
> > > > > > > > > > > > > little adding a couple more subreports, the report
> > being
> > > > sent
> > > > > > out
> > > > > > > > that
> > > > > > > > > > > > week
> > > > > > > > > > > > > was a few minutes delayed but it was ok. Then I
> > installed
> > > > > > > > Reporting
> > > > > > > > > > > > Services
> > > > > > > > > > > > > SP1 and from that week the report was delayed over
12
> > > > hours to
> > > > > > be
> > > > > > > > sent
> > > > > > > > > > out
> > > > > > > > > > > > > and it is like this since then. I dropped the old
> > shared
> > > > > > schedule
> > > > > > > > and
> > > > > > > > > > > > added a
> > > > > > > > > > > > > new shaed schedule but the report still can't be
sent
> > out
> > > > on
> > > > > > time.
> > > > > > > > > > Does
> > > > > > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Mary
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||My guess is the service you are turning on and off is actually pointing to
the other DB. You should run rsconfig to make sure it is pointing to the
database you think it is.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:363E5281-4099-447F-81DB-AED237198B5B@.microsoft.com...
> Daniel,
> WhenI tried to run the command the job runs, I realized I was wrong at
some
> point. There are actually two report server database on the same machine
with
> another one is called ReporterverII (I guess it resulted from two times of
> the initial installations). So the job command is actually using
> ReportServerII database but all I checked yesterday was another
ReportServer
> database. Here is what I did today: I turned off ReporServer service and
> manully started the SQL job with the job successfully ran at 12:13pm, then
I
> found there was a row added to the Event table with this job ID but with
> TimeEntered was 16:13pm. Then I truned on the ReportServer service, that
row
> is still in the Event table. I checked log file around that time stamp,
and I
> didn't find anything for this job. Also there is no email coming in so
far.
> Hope I'm not cofussing you.
> Thanks
> "Daniel Reib [MSFT]" wrote:
> > Ok, now we are getting somewhere. The fact that there was no row in the
> > event table after the job was fired is a problem. All the job does is
call
> > a stored procedure which should enter a row in the event table. You say
the
> > job fires successfully? There are no errors reported? Who is the job
> > owner?
> >
> > Can you try running the command that the job runs from Query Analyzer?
Run
> > it as the same user as the job. Does that add a row. If not was there
an
> > error? You might also try running just the SQL in the stored proc that
is
> > called, does that succeed? Do these with the reportServer service
turned
> > off, otherwise if the row does get in then it will pick it up and delete
the
> > row.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:778ADD45-9F76-4EAE-A58E-071B2DBC2AFA@.microsoft.com...
> > > I turned off reportServe service and ran the job manually, there was
no
> > row
> > > in Event table. Then I turned on the service and there is still no row
in
> > > that table. We have some jobs scheduled to run every 10 minutes, so
the
> > log
> > > file is big. I don't see anywhere I can send attachment, so I'm
sending
> > you
> > > the part aroud 3:24pm when the job was last run. Again, I don't see
> > anything
> > > in the log file for this job around 3:24pm.
> > >
> > > ReportingServicesService!library!d98!08/11/2004-15:23:52:: i INFO:
> > > Initializing EnableExecutionLogging to 'True' as specified in Server
> > system
> > > properties.
> > > ReportingServicesService!library!230!8/11/2004-15:23:52:: i INFO:
> > > Initializing EnableExecutionLogging to 'True' as specified in Server
> > system
> > > properties.
> > > ReportingServicesService!library!cf0!8/11/2004-15:23:52:: i INFO:
> > > Initializing EnableExecutionLogging to 'True' as specified in Server
> > system
> > > properties.
> > > ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
> > > 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004
> > 3:23:52
> > > PM.
> > > ReportingServicesService!library!cf0!8/11/2004-15:23:52:: Schedule
> > > 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004
> > 3:23:52
> > > PM.
> > > ReportingServicesService!dbpolling!230!8/11/2004-15:23:52::
EventPolling
> > > finished processing item 4cd4644b-8a15-43fd-baf1-c2ca8cbcd0d9
> > > ReportingServicesService!dbpolling!d44!8/11/2004-15:23:52::
EventPolling
> > > processing 1 more items. 4 Total items in internal queue.
> > > ReportingServicesService!dbpolling!230!8/11/2004-15:23:52::
EventPolling
> > > processing item a2ff2ad5-dc41-442b-ba91-d3a9e1d76a47
> > > ReportingServicesService!dbpolling!cf0!8/11/2004-15:23:52::
EventPolling
> > > finished processing item ec3f0cbd-0ec0-44bd-b714-6af044c06ba0
> > > ReportingServicesService!library!d98!08/11/2004-15:23:52:: Schedule
> > > 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 08/11/2004
> > > 15:23:52.
> > > ReportingServicesService!dbpolling!d98!08/11/2004-15:23:52::
EventPolling
> > > finished processing item b98d78ad-15dd-48ce-8c32-8db9fc716d61
> > > ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
> > > 87d27b74-96a1-4f41-9df0-c451424665cf executed at 8/11/2004 3:23:52 PM.
> > > ReportingServicesService!schedule!230!8/11/2004-15:23:52:: Updating
report
> > > execution snapshot for report /Summary Open Order Reports/OOCByDateFDR
> > > ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
EventPolling
> > > polling service stopped
> > > ReportingServicesService!dbpolling!8c0!8/11/2004-15:23:54::
EventPolling
> > > heartbeat thread exiting for stop.
> > > ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
> > > NotificationPolling polling service stopped
> > > ReportingServicesService!dbpolling!c48!8/11/2004-15:23:54::
> > > NotificationPolling heartbeat thread exiting for stop.
> > > ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
> > SchedulePolling
> > > polling service stopped
> > > ReportingServicesService!servicecontroller!9e8!8/11/2004-15:23:54::
> > Service
> > > controller exiting.
> > > ReportingServicesService!processing!bc8!8/11/2004-15:23:54:: e ERROR:
> > > Throwing
> > >
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> > Query
> > > execution failed for data set 'GMS'., ;
> > > Info:
> > >
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> > Query
> > > execution failed for data set 'GMS'. -->
> > > System.Threading.ThreadAbortException: Thread was being aborted.
> > > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> > > cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> > > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> > behavior)
> > > at
> > >
> >
System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(Comman
> > dBehavior behavior)
> > > at
> > >
> >
Microsoft.ReportingServices.DataExtensions.CommandWrapper.ExecuteReader(Comm
> > andBehavior behavior)
> > > at Microsoft.ReportingServices.ReportProcessing.a0.v()
> > > -- End of inner exception stack trace --
> > >
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > So try this:
> > > >
> > > > Turn off the reportServer service
> > > > Run the job manually
> > > > See if a row is in the events table
> > > > Turn on the ReportServer service
> > > > See if row disappears
> > > > Send me the latest reportserverservice<date>.log file
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:79C1481E-78A5-4594-8758-8AECD43776A6@.microsoft.com...
> > > > > Daniel,
> > > > >
> > > > > I checked Event table in report server database on that machine
and
> > there
> > > > is
> > > > > currently no row in that table. The value for PollingInterval is
10.
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > When you manually start the job a row should be placed in the
Event
> > > > table in
> > > > > > the report server database. Is this happening? Also can you
tell
> > me
> > > > the
> > > > > > value for the element PollingInterval in the
rsreportserver.config
> > file.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> > > > > > > I just manually started the job 10 minutes ago and the SQL job
was
> > > > running
> > > > > > > successfully. But there was no event fired around that time
for
> > this
> > > > job
> > > > > > when
> > > > > > > I checked the report server log file and also there was no
email
> > > > coming in
> > > > > > to
> > > > > > > the mailbox so far.
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > What happens if you run the job manually. Right click on
the
> > Sql
> > > > Agent
> > > > > > job
> > > > > > > > and choose start job. This should cause the job to execute.
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > > > > > > > Daniel,
> > > > > > > > >
> > > > > > > > > One thing I want to mention is that I changed the schedule
to
> > the
> > > > new
> > > > > > > > > schedule last week for the report to be sent out on every
> > Monday
> > > > 4pm
> > > > > > with
> > > > > > > > > which the latest running time was on 8/09 at 4pm. I
checked
> > the
> > > > > > history
> > > > > > > > of
> > > > > > > > > the job and it was running at 8/09/2004 4pm. Then I
checked
> > the
> > > > log
> > > > > > file
> > > > > > > > > around that time. There is no any event for this job on
8/09
> > at
> > > > 4pm,
> > > > > > but I
> > > > > > > > > found the event for this job on the log file dated at
> > 8/10/2004
> > > > 2:02am
> > > > > > > > which
> > > > > > > > > was the actual time this report was sent out this morning.
I
> > cut
> > > > that
> > > > > > part
> > > > > > > > of
> > > > > > > > > the log file for this job and paste it here:
> > > > > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56::
> > Schedule
> > > > > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004
> > 2:02:56
> > > > AM.
> > > > > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56::
> > Schedule
> > > > > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed
at
> > > > 8/10/2004
> > > > > > > > 2:02:56
> > > > > > > > > AM.
> > > > > > > > >
> > > > > > > > > Thanks
> > > > > > > > >
> > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > >
> > > > > > > > > > Ok, I am assuming that is what you expect. The next
thing
> > to
> > > > check
> > > > > > > > would be
> > > > > > > > > > to check the history of the job. Make sure that it is
> > firing
> > > > when
> > > > > > you
> > > > > > > > > > expect. If they are then look in the
> > > > ReportServerService<date>.log
> > > > > > > > file.
> > > > > > > > > > Around the time the schedule is fired an event should be
> > picked
> > > > up
> > > > > > from
> > > > > > > > the
> > > > > > > > > > Event table, and this should be logged.
> > > > > > > > > >
> > > > > > > > > > Can you verify that all of this is happening.
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > -Daniel
> > > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > confers
> > > > no
> > > > > > > > rights.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > >
news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > > > > > > > Daniel,
> > > > > > > > > > >
> > > > > > > > > > > The SQL job is scheduled to fire on Every week on
Tuesday
> > 4pm.
> > > > > > > > > > >
> > > > > > > > > > > Thanks
> > > > > > > > > > >
> > > > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Can you look at the SQL job that was created to see
when
> > it
> > > > is
> > > > > > > > scheduled
> > > > > > > > > > to
> > > > > > > > > > > > fire.
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > -Daniel
> > > > > > > > > > > > This posting is provided "AS IS" with no warranties,
and
> > > > confers
> > > > > > no
> > > > > > > > > > rights.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in
message
> > > > > > > > > > > >
> > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > > > > > > > Daniel,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thank you for your response. Sql Server is on the
same
> > > > box,
> > > > > > and
> > > > > > > > the
> > > > > > > > > > clock
> > > > > > > > > > > > on
> > > > > > > > > > > > > that machine is fine. The report was sent out on
time
> > > > before I
> > > > > > > > > > installed
> > > > > > > > > > > > SP1.
> > > > > > > > > > > > > Any idea about why this could happen?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks.
> > > > > > > > > > > > >
> > > > > > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Is you Sql Server on the same box? Is it
possible
> > the
> > > > clock
> > > > > > on
> > > > > > > > the
> > > > > > > > > > > > machine
> > > > > > > > > > > > > > that has SQL is 12 hours off?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > -Daniel
> > > > > > > > > > > > > > This posting is provided "AS IS" with no
warranties,
> > and
> > > > > > confers
> > > > > > > > no
> > > > > > > > > > > > rights.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in
> > message
> > > > > > > > > > > > > >
> > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > > > > > > > I have a report which is scheduled to be sent
out
> > by
> > > > email
> > > > > > > > every
> > > > > > > > > > > > Tuesday
> > > > > > > > > > > > > > at
> > > > > > > > > > > > > > > 4pm. It used to run and be sent out on time.
Then
> > I
> > > > > > changed
> > > > > > > > the
> > > > > > > > > > report
> > > > > > > > > > > > a
> > > > > > > > > > > > > > > little adding a couple more subreports, the
report
> > > > being
> > > > > > sent
> > > > > > > > out
> > > > > > > > > > that
> > > > > > > > > > > > > > week
> > > > > > > > > > > > > > > was a few minutes delayed but it was ok. Then
I
> > > > installed
> > > > > > > > > > Reporting
> > > > > > > > > > > > > > Services
> > > > > > > > > > > > > > > SP1 and from that week the report was delayed
over
> > 12
> > > > > > hours to
> > > > > > > > be
> > > > > > > > > > sent
> > > > > > > > > > > > out
> > > > > > > > > > > > > > > and it is like this since then. I dropped the
old
> > > > shared
> > > > > > > > schedule
> > > > > > > > > > and
> > > > > > > > > > > > > > added a
> > > > > > > > > > > > > > > new shaed schedule but the report still can't
be
> > sent
> > > > out
> > > > > > on
> > > > > > > > time.
> > > > > > > > > > > > Does
> > > > > > > > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanks,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Mary
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
4pm. It used to run and be sent out on time. Then I changed the report a
little adding a couple more subreports, the report being sent out that week
was a few minutes delayed but it was ok. Then I installed Reporting Services
SP1 and from that week the report was delayed over 12 hours to be sent out
and it is like this since then. I dropped the old shared schedule and added a
new shaed schedule but the report still can't be sent out on time. Does
anybody have any idea how to fix it?
Thanks,
MaryIs you Sql Server on the same box? Is it possible the clock on the machine
that has SQL is 12 hours off?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> I have a report which is scheduled to be sent out by email every Tuesday
at
> 4pm. It used to run and be sent out on time. Then I changed the report a
> little adding a couple more subreports, the report being sent out that
week
> was a few minutes delayed but it was ok. Then I installed Reporting
Services
> SP1 and from that week the report was delayed over 12 hours to be sent out
> and it is like this since then. I dropped the old shared schedule and
added a
> new shaed schedule but the report still can't be sent out on time. Does
> anybody have any idea how to fix it?
> Thanks,
> Mary|||Daniel,
Thank you for your response. Sql Server is on the same box, and the clock on
that machine is fine. The report was sent out on time before I installed SP1.
Any idea about why this could happen?
Thanks.
"Daniel Reib [MSFT]" wrote:
> Is you Sql Server on the same box? Is it possible the clock on the machine
> that has SQL is 12 hours off?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mary" <Mary@.discussions.microsoft.com> wrote in message
> news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > I have a report which is scheduled to be sent out by email every Tuesday
> at
> > 4pm. It used to run and be sent out on time. Then I changed the report a
> > little adding a couple more subreports, the report being sent out that
> week
> > was a few minutes delayed but it was ok. Then I installed Reporting
> Services
> > SP1 and from that week the report was delayed over 12 hours to be sent out
> > and it is like this since then. I dropped the old shared schedule and
> added a
> > new shaed schedule but the report still can't be sent out on time. Does
> > anybody have any idea how to fix it?
> >
> > Thanks,
> >
> > Mary
>
>|||Can you look at the SQL job that was created to see when it is scheduled to
fire.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> Daniel,
> Thank you for your response. Sql Server is on the same box, and the clock
on
> that machine is fine. The report was sent out on time before I installed
SP1.
> Any idea about why this could happen?
> Thanks.
> "Daniel Reib [MSFT]" wrote:
> > Is you Sql Server on the same box? Is it possible the clock on the
machine
> > that has SQL is 12 hours off?
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > I have a report which is scheduled to be sent out by email every
Tuesday
> > at
> > > 4pm. It used to run and be sent out on time. Then I changed the report
a
> > > little adding a couple more subreports, the report being sent out that
> > week
> > > was a few minutes delayed but it was ok. Then I installed Reporting
> > Services
> > > SP1 and from that week the report was delayed over 12 hours to be sent
out
> > > and it is like this since then. I dropped the old shared schedule and
> > added a
> > > new shaed schedule but the report still can't be sent out on time.
Does
> > > anybody have any idea how to fix it?
> > >
> > > Thanks,
> > >
> > > Mary
> >
> >
> >|||Ok, I am assuming that is what you expect. The next thing to check would be
to check the history of the job. Make sure that it is firing when you
expect. If they are then look in the ReportServerService<date>.log file.
Around the time the schedule is fired an event should be picked up from the
Event table, and this should be logged.
Can you verify that all of this is happening.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> Daniel,
> The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> Thanks
> "Daniel Reib [MSFT]" wrote:
> > Can you look at the SQL job that was created to see when it is scheduled
to
> > fire.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > Daniel,
> > >
> > > Thank you for your response. Sql Server is on the same box, and the
clock
> > on
> > > that machine is fine. The report was sent out on time before I
installed
> > SP1.
> > > Any idea about why this could happen?
> > >
> > > Thanks.
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > Is you Sql Server on the same box? Is it possible the clock on the
> > machine
> > > > that has SQL is 12 hours off?
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > I have a report which is scheduled to be sent out by email every
> > Tuesday
> > > > at
> > > > > 4pm. It used to run and be sent out on time. Then I changed the
report
> > a
> > > > > little adding a couple more subreports, the report being sent out
that
> > > > week
> > > > > was a few minutes delayed but it was ok. Then I installed
Reporting
> > > > Services
> > > > > SP1 and from that week the report was delayed over 12 hours to be
sent
> > out
> > > > > and it is like this since then. I dropped the old shared schedule
and
> > > > added a
> > > > > new shaed schedule but the report still can't be sent out on time.
> > Does
> > > > > anybody have any idea how to fix it?
> > > > >
> > > > > Thanks,
> > > > >
> > > > > Mary
> > > >
> > > >
> > > >
> >
> >
> >|||Daniel,
One thing I want to mention is that I changed the schedule to the new
schedule last week for the report to be sent out on every Monday 4pm with
which the latest running time was on 8/09 at 4pm. I checked the history of
the job and it was running at 8/09/2004 4pm. Then I checked the log file
around that time. There is no any event for this job on 8/09 at 4pm, but I
found the event for this job on the log file dated at 8/10/2004 2:02am which
was the actual time this report was sent out this morning. I cut that part of
the log file for this job and paste it here:
ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56 AM.
ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at 8/10/2004 2:02:56
AM.
Thanks
"Daniel Reib [MSFT]" wrote:
> Ok, I am assuming that is what you expect. The next thing to check would be
> to check the history of the job. Make sure that it is firing when you
> expect. If they are then look in the ReportServerService<date>.log file.
> Around the time the schedule is fired an event should be picked up from the
> Event table, and this should be logged.
> Can you verify that all of this is happening.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mary" <Mary@.discussions.microsoft.com> wrote in message
> news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > Daniel,
> >
> > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> >
> > Thanks
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > Can you look at the SQL job that was created to see when it is scheduled
> to
> > > fire.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > Daniel,
> > > >
> > > > Thank you for your response. Sql Server is on the same box, and the
> clock
> > > on
> > > > that machine is fine. The report was sent out on time before I
> installed
> > > SP1.
> > > > Any idea about why this could happen?
> > > >
> > > > Thanks.
> > > >
> > > > "Daniel Reib [MSFT]" wrote:
> > > >
> > > > > Is you Sql Server on the same box? Is it possible the clock on the
> > > machine
> > > > > that has SQL is 12 hours off?
> > > > >
> > > > > --
> > > > > -Daniel
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > >
> > > > >
> > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > I have a report which is scheduled to be sent out by email every
> > > Tuesday
> > > > > at
> > > > > > 4pm. It used to run and be sent out on time. Then I changed the
> report
> > > a
> > > > > > little adding a couple more subreports, the report being sent out
> that
> > > > > week
> > > > > > was a few minutes delayed but it was ok. Then I installed
> Reporting
> > > > > Services
> > > > > > SP1 and from that week the report was delayed over 12 hours to be
> sent
> > > out
> > > > > > and it is like this since then. I dropped the old shared schedule
> and
> > > > > added a
> > > > > > new shaed schedule but the report still can't be sent out on time.
> > > Does
> > > > > > anybody have any idea how to fix it?
> > > > > >
> > > > > > Thanks,
> > > > > >
> > > > > > Mary
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||What happens if you run the job manually. Right click on the Sql Agent job
and choose start job. This should cause the job to execute.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> Daniel,
> One thing I want to mention is that I changed the schedule to the new
> schedule last week for the report to be sent out on every Monday 4pm with
> which the latest running time was on 8/09 at 4pm. I checked the history
of
> the job and it was running at 8/09/2004 4pm. Then I checked the log file
> around that time. There is no any event for this job on 8/09 at 4pm, but I
> found the event for this job on the log file dated at 8/10/2004 2:02am
which
> was the actual time this report was sent out this morning. I cut that part
of
> the log file for this job and paste it here:
> ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56 AM.
> ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at 8/10/2004
2:02:56
> AM.
> Thanks
> "Daniel Reib [MSFT]" wrote:
> > Ok, I am assuming that is what you expect. The next thing to check
would be
> > to check the history of the job. Make sure that it is firing when you
> > expect. If they are then look in the ReportServerService<date>.log
file.
> > Around the time the schedule is fired an event should be picked up from
the
> > Event table, and this should be logged.
> >
> > Can you verify that all of this is happening.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > Daniel,
> > >
> > > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> > >
> > > Thanks
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > Can you look at the SQL job that was created to see when it is
scheduled
> > to
> > > > fire.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > Daniel,
> > > > >
> > > > > Thank you for your response. Sql Server is on the same box, and
the
> > clock
> > > > on
> > > > > that machine is fine. The report was sent out on time before I
> > installed
> > > > SP1.
> > > > > Any idea about why this could happen?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > Is you Sql Server on the same box? Is it possible the clock on
the
> > > > machine
> > > > > > that has SQL is 12 hours off?
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > I have a report which is scheduled to be sent out by email
every
> > > > Tuesday
> > > > > > at
> > > > > > > 4pm. It used to run and be sent out on time. Then I changed
the
> > report
> > > > a
> > > > > > > little adding a couple more subreports, the report being sent
out
> > that
> > > > > > week
> > > > > > > was a few minutes delayed but it was ok. Then I installed
> > Reporting
> > > > > > Services
> > > > > > > SP1 and from that week the report was delayed over 12 hours to
be
> > sent
> > > > out
> > > > > > > and it is like this since then. I dropped the old shared
schedule
> > and
> > > > > > added a
> > > > > > > new shaed schedule but the report still can't be sent out on
time.
> > > > Does
> > > > > > > anybody have any idea how to fix it?
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Mary
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||When you manually start the job a row should be placed in the Event table in
the report server database. Is this happening? Also can you tell me the
value for the element PollingInterval in the rsreportserver.config file.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> I just manually started the job 10 minutes ago and the SQL job was running
> successfully. But there was no event fired around that time for this job
when
> I checked the report server log file and also there was no email coming in
to
> the mailbox so far.
> "Daniel Reib [MSFT]" wrote:
> > What happens if you run the job manually. Right click on the Sql Agent
job
> > and choose start job. This should cause the job to execute.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > Daniel,
> > >
> > > One thing I want to mention is that I changed the schedule to the new
> > > schedule last week for the report to be sent out on every Monday 4pm
with
> > > which the latest running time was on 8/09 at 4pm. I checked the
history
> > of
> > > the job and it was running at 8/09/2004 4pm. Then I checked the log
file
> > > around that time. There is no any event for this job on 8/09 at 4pm,
but I
> > > found the event for this job on the log file dated at 8/10/2004 2:02am
> > which
> > > was the actual time this report was sent out this morning. I cut that
part
> > of
> > > the log file for this job and paste it here:
> > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56 AM.
> > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at 8/10/2004
> > 2:02:56
> > > AM.
> > >
> > > Thanks
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > Ok, I am assuming that is what you expect. The next thing to check
> > would be
> > > > to check the history of the job. Make sure that it is firing when
you
> > > > expect. If they are then look in the ReportServerService<date>.log
> > file.
> > > > Around the time the schedule is fired an event should be picked up
from
> > the
> > > > Event table, and this should be logged.
> > > >
> > > > Can you verify that all of this is happening.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > Daniel,
> > > > >
> > > > > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> > > > >
> > > > > Thanks
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > Can you look at the SQL job that was created to see when it is
> > scheduled
> > > > to
> > > > > > fire.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > Daniel,
> > > > > > >
> > > > > > > Thank you for your response. Sql Server is on the same box,
and
> > the
> > > > clock
> > > > > > on
> > > > > > > that machine is fine. The report was sent out on time before I
> > > > installed
> > > > > > SP1.
> > > > > > > Any idea about why this could happen?
> > > > > > >
> > > > > > > Thanks.
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > Is you Sql Server on the same box? Is it possible the clock
on
> > the
> > > > > > machine
> > > > > > > > that has SQL is 12 hours off?
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > I have a report which is scheduled to be sent out by email
> > every
> > > > > > Tuesday
> > > > > > > > at
> > > > > > > > > 4pm. It used to run and be sent out on time. Then I
changed
> > the
> > > > report
> > > > > > a
> > > > > > > > > little adding a couple more subreports, the report being
sent
> > out
> > > > that
> > > > > > > > week
> > > > > > > > > was a few minutes delayed but it was ok. Then I installed
> > > > Reporting
> > > > > > > > Services
> > > > > > > > > SP1 and from that week the report was delayed over 12
hours to
> > be
> > > > sent
> > > > > > out
> > > > > > > > > and it is like this since then. I dropped the old shared
> > schedule
> > > > and
> > > > > > > > added a
> > > > > > > > > new shaed schedule but the report still can't be sent out
on
> > time.
> > > > > > Does
> > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > >
> > > > > > > > > Mary
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||So try this:
Turn off the reportServer service
Run the job manually
See if a row is in the events table
Turn on the ReportServer service
See if row disappears
Send me the latest reportserverservice<date>.log file
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:79C1481E-78A5-4594-8758-8AECD43776A6@.microsoft.com...
> Daniel,
> I checked Event table in report server database on that machine and there
is
> currently no row in that table. The value for PollingInterval is 10.
> Thanks
>
> "Daniel Reib [MSFT]" wrote:
> > When you manually start the job a row should be placed in the Event
table in
> > the report server database. Is this happening? Also can you tell me
the
> > value for the element PollingInterval in the rsreportserver.config file.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> > > I just manually started the job 10 minutes ago and the SQL job was
running
> > > successfully. But there was no event fired around that time for this
job
> > when
> > > I checked the report server log file and also there was no email
coming in
> > to
> > > the mailbox so far.
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > What happens if you run the job manually. Right click on the Sql
Agent
> > job
> > > > and choose start job. This should cause the job to execute.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > > > Daniel,
> > > > >
> > > > > One thing I want to mention is that I changed the schedule to the
new
> > > > > schedule last week for the report to be sent out on every Monday
4pm
> > with
> > > > > which the latest running time was on 8/09 at 4pm. I checked the
> > history
> > > > of
> > > > > the job and it was running at 8/09/2004 4pm. Then I checked the
log
> > file
> > > > > around that time. There is no any event for this job on 8/09 at
4pm,
> > but I
> > > > > found the event for this job on the log file dated at 8/10/2004
2:02am
> > > > which
> > > > > was the actual time this report was sent out this morning. I cut
that
> > part
> > > > of
> > > > > the log file for this job and paste it here:
> > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56
AM.
> > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at
8/10/2004
> > > > 2:02:56
> > > > > AM.
> > > > >
> > > > > Thanks
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > Ok, I am assuming that is what you expect. The next thing to
check
> > > > would be
> > > > > > to check the history of the job. Make sure that it is firing
when
> > you
> > > > > > expect. If they are then look in the
ReportServerService<date>.log
> > > > file.
> > > > > > Around the time the schedule is fired an event should be picked
up
> > from
> > > > the
> > > > > > Event table, and this should be logged.
> > > > > >
> > > > > > Can you verify that all of this is happening.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > > > Daniel,
> > > > > > >
> > > > > > > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > Can you look at the SQL job that was created to see when it
is
> > > > scheduled
> > > > > > to
> > > > > > > > fire.
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > > > Daniel,
> > > > > > > > >
> > > > > > > > > Thank you for your response. Sql Server is on the same
box,
> > and
> > > > the
> > > > > > clock
> > > > > > > > on
> > > > > > > > > that machine is fine. The report was sent out on time
before I
> > > > > > installed
> > > > > > > > SP1.
> > > > > > > > > Any idea about why this could happen?
> > > > > > > > >
> > > > > > > > > Thanks.
> > > > > > > > >
> > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > >
> > > > > > > > > > Is you Sql Server on the same box? Is it possible the
clock
> > on
> > > > the
> > > > > > > > machine
> > > > > > > > > > that has SQL is 12 hours off?
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > -Daniel
> > > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > confers
> > > > no
> > > > > > > > rights.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > >
news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > > > I have a report which is scheduled to be sent out by
> > > > every
> > > > > > > > Tuesday
> > > > > > > > > > at
> > > > > > > > > > > 4pm. It used to run and be sent out on time. Then I
> > changed
> > > > the
> > > > > > report
> > > > > > > > a
> > > > > > > > > > > little adding a couple more subreports, the report
being
> > sent
> > > > out
> > > > > > that
> > > > > > > > > > week
> > > > > > > > > > > was a few minutes delayed but it was ok. Then I
installed
> > > > > > Reporting
> > > > > > > > > > Services
> > > > > > > > > > > SP1 and from that week the report was delayed over 12
> > hours to
> > > > be
> > > > > > sent
> > > > > > > > out
> > > > > > > > > > > and it is like this since then. I dropped the old
shared
> > > > schedule
> > > > > > and
> > > > > > > > > > added a
> > > > > > > > > > > new shaed schedule but the report still can't be sent
out
> > on
> > > > time.
> > > > > > > > Does
> > > > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > >
> > > > > > > > > > > Mary
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||I turned off reportServe service and ran the job manually, there was no row
in Event table. Then I turned on the service and there is still no row in
that table. We have some jobs scheduled to run every 10 minutes, so the log
file is big. I don't see anywhere I can send attachment, so I'm sending you
the part aroud 3:24pm when the job was last run. Again, I don't see anything
in the log file for this job around 3:24pm.
ReportingServicesService!library!d98!08/11/2004-15:23:52:: i INFO:
Initializing EnableExecutionLogging to 'True' as specified in Server system
properties.
ReportingServicesService!library!230!8/11/2004-15:23:52:: i INFO:
Initializing EnableExecutionLogging to 'True' as specified in Server system
properties.
ReportingServicesService!library!cf0!8/11/2004-15:23:52:: i INFO:
Initializing EnableExecutionLogging to 'True' as specified in Server system
properties.
ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004 3:23:52
PM.
ReportingServicesService!library!cf0!8/11/2004-15:23:52:: Schedule
87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004 3:23:52
PM.
ReportingServicesService!dbpolling!230!8/11/2004-15:23:52:: EventPolling
finished processing item 4cd4644b-8a15-43fd-baf1-c2ca8cbcd0d9
ReportingServicesService!dbpolling!d44!8/11/2004-15:23:52:: EventPolling
processing 1 more items. 4 Total items in internal queue.
ReportingServicesService!dbpolling!230!8/11/2004-15:23:52:: EventPolling
processing item a2ff2ad5-dc41-442b-ba91-d3a9e1d76a47
ReportingServicesService!dbpolling!cf0!8/11/2004-15:23:52:: EventPolling
finished processing item ec3f0cbd-0ec0-44bd-b714-6af044c06ba0
ReportingServicesService!library!d98!08/11/2004-15:23:52:: Schedule
87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 08/11/2004
15:23:52.
ReportingServicesService!dbpolling!d98!08/11/2004-15:23:52:: EventPolling
finished processing item b98d78ad-15dd-48ce-8c32-8db9fc716d61
ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
87d27b74-96a1-4f41-9df0-c451424665cf executed at 8/11/2004 3:23:52 PM.
ReportingServicesService!schedule!230!8/11/2004-15:23:52:: Updating report
execution snapshot for report /Summary Open Order Reports/OOCByDateFDR
ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54:: EventPolling
polling service stopped
ReportingServicesService!dbpolling!8c0!8/11/2004-15:23:54:: EventPolling
heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
NotificationPolling polling service stopped
ReportingServicesService!dbpolling!c48!8/11/2004-15:23:54::
NotificationPolling heartbeat thread exiting for stop.
ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54:: SchedulePolling
polling service stopped
ReportingServicesService!servicecontroller!9e8!8/11/2004-15:23:54:: Service
controller exiting.
ReportingServicesService!processing!bc8!8/11/2004-15:23:54:: e ERROR:
Throwing
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query
execution failed for data set 'GMS'., ;
Info:
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query
execution failed for data set 'GMS'. -->
System.Threading.ThreadAbortException: Thread was being aborted.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior)
at
System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(CommandBehavior behavior)
at
Microsoft.ReportingServices.DataExtensions.CommandWrapper.ExecuteReader(CommandBehavior behavior)
at Microsoft.ReportingServices.ReportProcessing.a0.v()
-- End of inner exception stack trace --
"Daniel Reib [MSFT]" wrote:
> So try this:
> Turn off the reportServer service
> Run the job manually
> See if a row is in the events table
> Turn on the ReportServer service
> See if row disappears
> Send me the latest reportserverservice<date>.log file
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Mary" <Mary@.discussions.microsoft.com> wrote in message
> news:79C1481E-78A5-4594-8758-8AECD43776A6@.microsoft.com...
> > Daniel,
> >
> > I checked Event table in report server database on that machine and there
> is
> > currently no row in that table. The value for PollingInterval is 10.
> >
> > Thanks
> >
> >
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > When you manually start the job a row should be placed in the Event
> table in
> > > the report server database. Is this happening? Also can you tell me
> the
> > > value for the element PollingInterval in the rsreportserver.config file.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> > > > I just manually started the job 10 minutes ago and the SQL job was
> running
> > > > successfully. But there was no event fired around that time for this
> job
> > > when
> > > > I checked the report server log file and also there was no email
> coming in
> > > to
> > > > the mailbox so far.
> > > >
> > > > "Daniel Reib [MSFT]" wrote:
> > > >
> > > > > What happens if you run the job manually. Right click on the Sql
> Agent
> > > job
> > > > > and choose start job. This should cause the job to execute.
> > > > >
> > > > > --
> > > > > -Daniel
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > >
> > > > >
> > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > > > > Daniel,
> > > > > >
> > > > > > One thing I want to mention is that I changed the schedule to the
> new
> > > > > > schedule last week for the report to be sent out on every Monday
> 4pm
> > > with
> > > > > > which the latest running time was on 8/09 at 4pm. I checked the
> > > history
> > > > > of
> > > > > > the job and it was running at 8/09/2004 4pm. Then I checked the
> log
> > > file
> > > > > > around that time. There is no any event for this job on 8/09 at
> 4pm,
> > > but I
> > > > > > found the event for this job on the log file dated at 8/10/2004
> 2:02am
> > > > > which
> > > > > > was the actual time this report was sent out this morning. I cut
> that
> > > part
> > > > > of
> > > > > > the log file for this job and paste it here:
> > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004 2:02:56
> AM.
> > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56:: Schedule
> > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at
> 8/10/2004
> > > > > 2:02:56
> > > > > > AM.
> > > > > >
> > > > > > Thanks
> > > > > >
> > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > >
> > > > > > > Ok, I am assuming that is what you expect. The next thing to
> check
> > > > > would be
> > > > > > > to check the history of the job. Make sure that it is firing
> when
> > > you
> > > > > > > expect. If they are then look in the
> ReportServerService<date>.log
> > > > > file.
> > > > > > > Around the time the schedule is fired an event should be picked
> up
> > > from
> > > > > the
> > > > > > > Event table, and this should be logged.
> > > > > > >
> > > > > > > Can you verify that all of this is happening.
> > > > > > >
> > > > > > > --
> > > > > > > -Daniel
> > > > > > > This posting is provided "AS IS" with no warranties, and confers
> no
> > > > > rights.
> > > > > > >
> > > > > > >
> > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > > > > Daniel,
> > > > > > > >
> > > > > > > > The SQL job is scheduled to fire on Every week on Tuesday 4pm.
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > >
> > > > > > > > > Can you look at the SQL job that was created to see when it
> is
> > > > > scheduled
> > > > > > > to
> > > > > > > > > fire.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > -Daniel
> > > > > > > > > This posting is provided "AS IS" with no warranties, and
> confers
> > > no
> > > > > > > rights.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > > > > Daniel,
> > > > > > > > > >
> > > > > > > > > > Thank you for your response. Sql Server is on the same
> box,
> > > and
> > > > > the
> > > > > > > clock
> > > > > > > > > on
> > > > > > > > > > that machine is fine. The report was sent out on time
> before I
> > > > > > > installed
> > > > > > > > > SP1.
> > > > > > > > > > Any idea about why this could happen?
> > > > > > > > > >
> > > > > > > > > > Thanks.
> > > > > > > > > >
> > > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > > >
> > > > > > > > > > > Is you Sql Server on the same box? Is it possible the
> clock
> > > on
> > > > > the
> > > > > > > > > machine
> > > > > > > > > > > that has SQL is 12 hours off?
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > -Daniel
> > > > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > > confers
> > > > > no
> > > > > > > > > rights.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > > >
> news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > > > > I have a report which is scheduled to be sent out by
> > > > > every
> > > > > > > > > Tuesday
> > > > > > > > > > > at
> > > > > > > > > > > > 4pm. It used to run and be sent out on time. Then I
> > > changed
> > > > > the
> > > > > > > report
> > > > > > > > > a
> > > > > > > > > > > > little adding a couple more subreports, the report
> being
> > > sent
> > > > > out
> > > > > > > that
> > > > > > > > > > > week
> > > > > > > > > > > > was a few minutes delayed but it was ok. Then I
> installed
> > > > > > > Reporting
> > > > > > > > > > > Services
> > > > > > > > > > > > SP1 and from that week the report was delayed over 12
> > > hours to
> > > > > be
> > > > > > > sent
> > > > > > > > > out
> > > > > > > > > > > > and it is like this since then. I dropped the old
> shared
> > > > > schedule
> > > > > > > and
> > > > > > > > > > > added a
> > > > > > > > > > > > new shaed schedule but the report still can't be sent
> out
> > > on
> > > > > time.
> > > > > > > > > Does
> > > > > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks,
> > > > > > > > > > > >
> > > > > > > > > > > > Mary
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||Ok, now we are getting somewhere. The fact that there was no row in the
event table after the job was fired is a problem. All the job does is call
a stored procedure which should enter a row in the event table. You say the
job fires successfully? There are no errors reported? Who is the job
owner?
Can you try running the command that the job runs from Query Analyzer? Run
it as the same user as the job. Does that add a row. If not was there an
error? You might also try running just the SQL in the stored proc that is
called, does that succeed? Do these with the reportServer service turned
off, otherwise if the row does get in then it will pick it up and delete the
row.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:778ADD45-9F76-4EAE-A58E-071B2DBC2AFA@.microsoft.com...
> I turned off reportServe service and ran the job manually, there was no
row
> in Event table. Then I turned on the service and there is still no row in
> that table. We have some jobs scheduled to run every 10 minutes, so the
log
> file is big. I don't see anywhere I can send attachment, so I'm sending
you
> the part aroud 3:24pm when the job was last run. Again, I don't see
anything
> in the log file for this job around 3:24pm.
> ReportingServicesService!library!d98!08/11/2004-15:23:52:: i INFO:
> Initializing EnableExecutionLogging to 'True' as specified in Server
system
> properties.
> ReportingServicesService!library!230!8/11/2004-15:23:52:: i INFO:
> Initializing EnableExecutionLogging to 'True' as specified in Server
system
> properties.
> ReportingServicesService!library!cf0!8/11/2004-15:23:52:: i INFO:
> Initializing EnableExecutionLogging to 'True' as specified in Server
system
> properties.
> ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
> 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004
3:23:52
> PM.
> ReportingServicesService!library!cf0!8/11/2004-15:23:52:: Schedule
> 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004
3:23:52
> PM.
> ReportingServicesService!dbpolling!230!8/11/2004-15:23:52:: EventPolling
> finished processing item 4cd4644b-8a15-43fd-baf1-c2ca8cbcd0d9
> ReportingServicesService!dbpolling!d44!8/11/2004-15:23:52:: EventPolling
> processing 1 more items. 4 Total items in internal queue.
> ReportingServicesService!dbpolling!230!8/11/2004-15:23:52:: EventPolling
> processing item a2ff2ad5-dc41-442b-ba91-d3a9e1d76a47
> ReportingServicesService!dbpolling!cf0!8/11/2004-15:23:52:: EventPolling
> finished processing item ec3f0cbd-0ec0-44bd-b714-6af044c06ba0
> ReportingServicesService!library!d98!08/11/2004-15:23:52:: Schedule
> 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 08/11/2004
> 15:23:52.
> ReportingServicesService!dbpolling!d98!08/11/2004-15:23:52:: EventPolling
> finished processing item b98d78ad-15dd-48ce-8c32-8db9fc716d61
> ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
> 87d27b74-96a1-4f41-9df0-c451424665cf executed at 8/11/2004 3:23:52 PM.
> ReportingServicesService!schedule!230!8/11/2004-15:23:52:: Updating report
> execution snapshot for report /Summary Open Order Reports/OOCByDateFDR
> ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54:: EventPolling
> polling service stopped
> ReportingServicesService!dbpolling!8c0!8/11/2004-15:23:54:: EventPolling
> heartbeat thread exiting for stop.
> ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
> NotificationPolling polling service stopped
> ReportingServicesService!dbpolling!c48!8/11/2004-15:23:54::
> NotificationPolling heartbeat thread exiting for stop.
> ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
SchedulePolling
> polling service stopped
> ReportingServicesService!servicecontroller!9e8!8/11/2004-15:23:54::
Service
> controller exiting.
> ReportingServicesService!processing!bc8!8/11/2004-15:23:54:: e ERROR:
> Throwing
> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Query
> execution failed for data set 'GMS'., ;
> Info:
> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
Query
> execution failed for data set 'GMS'. -->
> System.Threading.ThreadAbortException: Thread was being aborted.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
behavior)
> at
>
System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(Comman
dBehavior behavior)
> at
>
Microsoft.ReportingServices.DataExtensions.CommandWrapper.ExecuteReader(Comm
andBehavior behavior)
> at Microsoft.ReportingServices.ReportProcessing.a0.v()
> -- End of inner exception stack trace --
>
> "Daniel Reib [MSFT]" wrote:
> > So try this:
> >
> > Turn off the reportServer service
> > Run the job manually
> > See if a row is in the events table
> > Turn on the ReportServer service
> > See if row disappears
> > Send me the latest reportserverservice<date>.log file
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:79C1481E-78A5-4594-8758-8AECD43776A6@.microsoft.com...
> > > Daniel,
> > >
> > > I checked Event table in report server database on that machine and
there
> > is
> > > currently no row in that table. The value for PollingInterval is 10.
> > >
> > > Thanks
> > >
> > >
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > When you manually start the job a row should be placed in the Event
> > table in
> > > > the report server database. Is this happening? Also can you tell
me
> > the
> > > > value for the element PollingInterval in the rsreportserver.config
file.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> > > > > I just manually started the job 10 minutes ago and the SQL job was
> > running
> > > > > successfully. But there was no event fired around that time for
this
> > job
> > > > when
> > > > > I checked the report server log file and also there was no email
> > coming in
> > > > to
> > > > > the mailbox so far.
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > What happens if you run the job manually. Right click on the
Sql
> > Agent
> > > > job
> > > > > > and choose start job. This should cause the job to execute.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > > > > > Daniel,
> > > > > > >
> > > > > > > One thing I want to mention is that I changed the schedule to
the
> > new
> > > > > > > schedule last week for the report to be sent out on every
Monday
> > 4pm
> > > > with
> > > > > > > which the latest running time was on 8/09 at 4pm. I checked
the
> > > > history
> > > > > > of
> > > > > > > the job and it was running at 8/09/2004 4pm. Then I checked
the
> > log
> > > > file
> > > > > > > around that time. There is no any event for this job on 8/09
at
> > 4pm,
> > > > but I
> > > > > > > found the event for this job on the log file dated at
8/10/2004
> > 2:02am
> > > > > > which
> > > > > > > was the actual time this report was sent out this morning. I
cut
> > that
> > > > part
> > > > > > of
> > > > > > > the log file for this job and paste it here:
> > > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56::
Schedule
> > > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004
2:02:56
> > AM.
> > > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56::
Schedule
> > > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed at
> > 8/10/2004
> > > > > > 2:02:56
> > > > > > > AM.
> > > > > > >
> > > > > > > Thanks
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > Ok, I am assuming that is what you expect. The next thing
to
> > check
> > > > > > would be
> > > > > > > > to check the history of the job. Make sure that it is
firing
> > when
> > > > you
> > > > > > > > expect. If they are then look in the
> > ReportServerService<date>.log
> > > > > > file.
> > > > > > > > Around the time the schedule is fired an event should be
picked
> > up
> > > > from
> > > > > > the
> > > > > > > > Event table, and this should be logged.
> > > > > > > >
> > > > > > > > Can you verify that all of this is happening.
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > > > > > Daniel,
> > > > > > > > >
> > > > > > > > > The SQL job is scheduled to fire on Every week on Tuesday
4pm.
> > > > > > > > >
> > > > > > > > > Thanks
> > > > > > > > >
> > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > >
> > > > > > > > > > Can you look at the SQL job that was created to see when
it
> > is
> > > > > > scheduled
> > > > > > > > to
> > > > > > > > > > fire.
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > -Daniel
> > > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > confers
> > > > no
> > > > > > > > rights.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > >
news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > > > > > Daniel,
> > > > > > > > > > >
> > > > > > > > > > > Thank you for your response. Sql Server is on the same
> > box,
> > > > and
> > > > > > the
> > > > > > > > clock
> > > > > > > > > > on
> > > > > > > > > > > that machine is fine. The report was sent out on time
> > before I
> > > > > > > > installed
> > > > > > > > > > SP1.
> > > > > > > > > > > Any idea about why this could happen?
> > > > > > > > > > >
> > > > > > > > > > > Thanks.
> > > > > > > > > > >
> > > > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Is you Sql Server on the same box? Is it possible
the
> > clock
> > > > on
> > > > > > the
> > > > > > > > > > machine
> > > > > > > > > > > > that has SQL is 12 hours off?
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > -Daniel
> > > > > > > > > > > > This posting is provided "AS IS" with no warranties,
and
> > > > confers
> > > > > > no
> > > > > > > > > > rights.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in
message
> > > > > > > > > > > >
> > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > > > > > I have a report which is scheduled to be sent out
by
> > > > > > every
> > > > > > > > > > Tuesday
> > > > > > > > > > > > at
> > > > > > > > > > > > > 4pm. It used to run and be sent out on time. Then
I
> > > > changed
> > > > > > the
> > > > > > > > report
> > > > > > > > > > a
> > > > > > > > > > > > > little adding a couple more subreports, the report
> > being
> > > > sent
> > > > > > out
> > > > > > > > that
> > > > > > > > > > > > week
> > > > > > > > > > > > > was a few minutes delayed but it was ok. Then I
> > installed
> > > > > > > > Reporting
> > > > > > > > > > > > Services
> > > > > > > > > > > > > SP1 and from that week the report was delayed over
12
> > > > hours to
> > > > > > be
> > > > > > > > sent
> > > > > > > > > > out
> > > > > > > > > > > > > and it is like this since then. I dropped the old
> > shared
> > > > > > schedule
> > > > > > > > and
> > > > > > > > > > > > added a
> > > > > > > > > > > > > new shaed schedule but the report still can't be
sent
> > out
> > > > on
> > > > > > time.
> > > > > > > > > > Does
> > > > > > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Mary
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||My guess is the service you are turning on and off is actually pointing to
the other DB. You should run rsconfig to make sure it is pointing to the
database you think it is.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Mary" <Mary@.discussions.microsoft.com> wrote in message
news:363E5281-4099-447F-81DB-AED237198B5B@.microsoft.com...
> Daniel,
> WhenI tried to run the command the job runs, I realized I was wrong at
some
> point. There are actually two report server database on the same machine
with
> another one is called ReporterverII (I guess it resulted from two times of
> the initial installations). So the job command is actually using
> ReportServerII database but all I checked yesterday was another
ReportServer
> database. Here is what I did today: I turned off ReporServer service and
> manully started the SQL job with the job successfully ran at 12:13pm, then
I
> found there was a row added to the Event table with this job ID but with
> TimeEntered was 16:13pm. Then I truned on the ReportServer service, that
row
> is still in the Event table. I checked log file around that time stamp,
and I
> didn't find anything for this job. Also there is no email coming in so
far.
> Hope I'm not cofussing you.
> Thanks
> "Daniel Reib [MSFT]" wrote:
> > Ok, now we are getting somewhere. The fact that there was no row in the
> > event table after the job was fired is a problem. All the job does is
call
> > a stored procedure which should enter a row in the event table. You say
the
> > job fires successfully? There are no errors reported? Who is the job
> > owner?
> >
> > Can you try running the command that the job runs from Query Analyzer?
Run
> > it as the same user as the job. Does that add a row. If not was there
an
> > error? You might also try running just the SQL in the stored proc that
is
> > called, does that succeed? Do these with the reportServer service
turned
> > off, otherwise if the row does get in then it will pick it up and delete
the
> > row.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > news:778ADD45-9F76-4EAE-A58E-071B2DBC2AFA@.microsoft.com...
> > > I turned off reportServe service and ran the job manually, there was
no
> > row
> > > in Event table. Then I turned on the service and there is still no row
in
> > > that table. We have some jobs scheduled to run every 10 minutes, so
the
> > log
> > > file is big. I don't see anywhere I can send attachment, so I'm
sending
> > you
> > > the part aroud 3:24pm when the job was last run. Again, I don't see
> > anything
> > > in the log file for this job around 3:24pm.
> > >
> > > ReportingServicesService!library!d98!08/11/2004-15:23:52:: i INFO:
> > > Initializing EnableExecutionLogging to 'True' as specified in Server
> > system
> > > properties.
> > > ReportingServicesService!library!230!8/11/2004-15:23:52:: i INFO:
> > > Initializing EnableExecutionLogging to 'True' as specified in Server
> > system
> > > properties.
> > > ReportingServicesService!library!cf0!8/11/2004-15:23:52:: i INFO:
> > > Initializing EnableExecutionLogging to 'True' as specified in Server
> > system
> > > properties.
> > > ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
> > > 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004
> > 3:23:52
> > > PM.
> > > ReportingServicesService!library!cf0!8/11/2004-15:23:52:: Schedule
> > > 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 8/11/2004
> > 3:23:52
> > > PM.
> > > ReportingServicesService!dbpolling!230!8/11/2004-15:23:52::
EventPolling
> > > finished processing item 4cd4644b-8a15-43fd-baf1-c2ca8cbcd0d9
> > > ReportingServicesService!dbpolling!d44!8/11/2004-15:23:52::
EventPolling
> > > processing 1 more items. 4 Total items in internal queue.
> > > ReportingServicesService!dbpolling!230!8/11/2004-15:23:52::
EventPolling
> > > processing item a2ff2ad5-dc41-442b-ba91-d3a9e1d76a47
> > > ReportingServicesService!dbpolling!cf0!8/11/2004-15:23:52::
EventPolling
> > > finished processing item ec3f0cbd-0ec0-44bd-b714-6af044c06ba0
> > > ReportingServicesService!library!d98!08/11/2004-15:23:52:: Schedule
> > > 87d27b74-96a1-4f41-9df0-c451424665cf execution completed at 08/11/2004
> > > 15:23:52.
> > > ReportingServicesService!dbpolling!d98!08/11/2004-15:23:52::
EventPolling
> > > finished processing item b98d78ad-15dd-48ce-8c32-8db9fc716d61
> > > ReportingServicesService!library!230!8/11/2004-15:23:52:: Schedule
> > > 87d27b74-96a1-4f41-9df0-c451424665cf executed at 8/11/2004 3:23:52 PM.
> > > ReportingServicesService!schedule!230!8/11/2004-15:23:52:: Updating
report
> > > execution snapshot for report /Summary Open Order Reports/OOCByDateFDR
> > > ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
EventPolling
> > > polling service stopped
> > > ReportingServicesService!dbpolling!8c0!8/11/2004-15:23:54::
EventPolling
> > > heartbeat thread exiting for stop.
> > > ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
> > > NotificationPolling polling service stopped
> > > ReportingServicesService!dbpolling!c48!8/11/2004-15:23:54::
> > > NotificationPolling heartbeat thread exiting for stop.
> > > ReportingServicesService!dbpolling!9e8!8/11/2004-15:23:54::
> > SchedulePolling
> > > polling service stopped
> > > ReportingServicesService!servicecontroller!9e8!8/11/2004-15:23:54::
> > Service
> > > controller exiting.
> > > ReportingServicesService!processing!bc8!8/11/2004-15:23:54:: e ERROR:
> > > Throwing
> > >
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> > Query
> > > execution failed for data set 'GMS'., ;
> > > Info:
> > >
Microsoft.ReportingServices.ReportProcessing.ReportProcessingException:
> > Query
> > > execution failed for data set 'GMS'. -->
> > > System.Threading.ThreadAbortException: Thread was being aborted.
> > > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> > > cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> > > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> > behavior)
> > > at
> > >
> >
System.Data.SqlClient.SqlCommand.System.Data.IDbCommand.ExecuteReader(Comman
> > dBehavior behavior)
> > > at
> > >
> >
Microsoft.ReportingServices.DataExtensions.CommandWrapper.ExecuteReader(Comm
> > andBehavior behavior)
> > > at Microsoft.ReportingServices.ReportProcessing.a0.v()
> > > -- End of inner exception stack trace --
> > >
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > So try this:
> > > >
> > > > Turn off the reportServer service
> > > > Run the job manually
> > > > See if a row is in the events table
> > > > Turn on the ReportServer service
> > > > See if row disappears
> > > > Send me the latest reportserverservice<date>.log file
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > news:79C1481E-78A5-4594-8758-8AECD43776A6@.microsoft.com...
> > > > > Daniel,
> > > > >
> > > > > I checked Event table in report server database on that machine
and
> > there
> > > > is
> > > > > currently no row in that table. The value for PollingInterval is
10.
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > When you manually start the job a row should be placed in the
Event
> > > > table in
> > > > > > the report server database. Is this happening? Also can you
tell
> > me
> > > > the
> > > > > > value for the element PollingInterval in the
rsreportserver.config
> > file.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > news:4A142D53-7729-4FA2-AB95-F610CA049DB0@.microsoft.com...
> > > > > > > I just manually started the job 10 minutes ago and the SQL job
was
> > > > running
> > > > > > > successfully. But there was no event fired around that time
for
> > this
> > > > job
> > > > > > when
> > > > > > > I checked the report server log file and also there was no
> > > > coming in
> > > > > > to
> > > > > > > the mailbox so far.
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > What happens if you run the job manually. Right click on
the
> > Sql
> > > > Agent
> > > > > > job
> > > > > > > > and choose start job. This should cause the job to execute.
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > news:3DF5F4E2-AEC5-4DA1-B495-B2B821F319E9@.microsoft.com...
> > > > > > > > > Daniel,
> > > > > > > > >
> > > > > > > > > One thing I want to mention is that I changed the schedule
to
> > the
> > > > new
> > > > > > > > > schedule last week for the report to be sent out on every
> > Monday
> > > > 4pm
> > > > > > with
> > > > > > > > > which the latest running time was on 8/09 at 4pm. I
checked
> > the
> > > > > > history
> > > > > > > > of
> > > > > > > > > the job and it was running at 8/09/2004 4pm. Then I
checked
> > the
> > > > log
> > > > > > file
> > > > > > > > > around that time. There is no any event for this job on
8/09
> > at
> > > > 4pm,
> > > > > > but I
> > > > > > > > > found the event for this job on the log file dated at
> > 8/10/2004
> > > > 2:02am
> > > > > > > > which
> > > > > > > > > was the actual time this report was sent out this morning.
I
> > cut
> > > > that
> > > > > > part
> > > > > > > > of
> > > > > > > > > the log file for this job and paste it here:
> > > > > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56::
> > Schedule
> > > > > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d executed at 8/10/2004
> > 2:02:56
> > > > AM.
> > > > > > > > > ReportingServicesService!library!de8!8/10/2004-02:02:56::
> > Schedule
> > > > > > > > > 0c6ad482-0b44-405e-a1cc-c15b0f1b238d execution completed
at
> > > > 8/10/2004
> > > > > > > > 2:02:56
> > > > > > > > > AM.
> > > > > > > > >
> > > > > > > > > Thanks
> > > > > > > > >
> > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > >
> > > > > > > > > > Ok, I am assuming that is what you expect. The next
thing
> > to
> > > > check
> > > > > > > > would be
> > > > > > > > > > to check the history of the job. Make sure that it is
> > firing
> > > > when
> > > > > > you
> > > > > > > > > > expect. If they are then look in the
> > > > ReportServerService<date>.log
> > > > > > > > file.
> > > > > > > > > > Around the time the schedule is fired an event should be
> > picked
> > > > up
> > > > > > from
> > > > > > > > the
> > > > > > > > > > Event table, and this should be logged.
> > > > > > > > > >
> > > > > > > > > > Can you verify that all of this is happening.
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > -Daniel
> > > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > confers
> > > > no
> > > > > > > > rights.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in message
> > > > > > > > > >
news:00B85A4A-D50E-40BC-8B85-F3BA129515CD@.microsoft.com...
> > > > > > > > > > > Daniel,
> > > > > > > > > > >
> > > > > > > > > > > The SQL job is scheduled to fire on Every week on
Tuesday
> > 4pm.
> > > > > > > > > > >
> > > > > > > > > > > Thanks
> > > > > > > > > > >
> > > > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Can you look at the SQL job that was created to see
when
> > it
> > > > is
> > > > > > > > scheduled
> > > > > > > > > > to
> > > > > > > > > > > > fire.
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > -Daniel
> > > > > > > > > > > > This posting is provided "AS IS" with no warranties,
and
> > > > confers
> > > > > > no
> > > > > > > > > > rights.
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in
message
> > > > > > > > > > > >
> > news:241C68BF-31FC-4A20-8371-216B270AB697@.microsoft.com...
> > > > > > > > > > > > > Daniel,
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thank you for your response. Sql Server is on the
same
> > > > box,
> > > > > > and
> > > > > > > > the
> > > > > > > > > > clock
> > > > > > > > > > > > on
> > > > > > > > > > > > > that machine is fine. The report was sent out on
time
> > > > before I
> > > > > > > > > > installed
> > > > > > > > > > > > SP1.
> > > > > > > > > > > > > Any idea about why this could happen?
> > > > > > > > > > > > >
> > > > > > > > > > > > > Thanks.
> > > > > > > > > > > > >
> > > > > > > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Is you Sql Server on the same box? Is it
possible
> > the
> > > > clock
> > > > > > on
> > > > > > > > the
> > > > > > > > > > > > machine
> > > > > > > > > > > > > > that has SQL is 12 hours off?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > -Daniel
> > > > > > > > > > > > > > This posting is provided "AS IS" with no
warranties,
> > and
> > > > > > confers
> > > > > > > > no
> > > > > > > > > > > > rights.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > "Mary" <Mary@.discussions.microsoft.com> wrote in
> > message
> > > > > > > > > > > > > >
> > > > news:6DAB515D-B442-47BB-88DA-BFA95E9F08D3@.microsoft.com...
> > > > > > > > > > > > > > > I have a report which is scheduled to be sent
out
> > by
> > > > > > > > every
> > > > > > > > > > > > Tuesday
> > > > > > > > > > > > > > at
> > > > > > > > > > > > > > > 4pm. It used to run and be sent out on time.
Then
> > I
> > > > > > changed
> > > > > > > > the
> > > > > > > > > > report
> > > > > > > > > > > > a
> > > > > > > > > > > > > > > little adding a couple more subreports, the
report
> > > > being
> > > > > > sent
> > > > > > > > out
> > > > > > > > > > that
> > > > > > > > > > > > > > week
> > > > > > > > > > > > > > > was a few minutes delayed but it was ok. Then
I
> > > > installed
> > > > > > > > > > Reporting
> > > > > > > > > > > > > > Services
> > > > > > > > > > > > > > > SP1 and from that week the report was delayed
over
> > 12
> > > > > > hours to
> > > > > > > > be
> > > > > > > > > > sent
> > > > > > > > > > > > out
> > > > > > > > > > > > > > > and it is like this since then. I dropped the
old
> > > > shared
> > > > > > > > schedule
> > > > > > > > > > and
> > > > > > > > > > > > > > added a
> > > > > > > > > > > > > > > new shaed schedule but the report still can't
be
> > sent
> > > > out
> > > > > > on
> > > > > > > > time.
> > > > > > > > > > > > Does
> > > > > > > > > > > > > > > anybody have any idea how to fix it?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Thanks,
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Mary
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
Subscribe to:
Posts (Atom)