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 simple cdosys email task does not work

I currently have a simple cdosys email task that has been scheduled to send a simple email from ssis. The email is sent using an activex script in a "SQL 2000 DTS Package Task". When executed manually, the email is sent ok. When scheduled (and run under our SQL agent account), it fails. Can anyone point me in the right direction? Is this a permissions issue?

'-- this script seems to cause problems, but only when scheduled --
dim mailer
set mailer = CreateObject("CDO.Message")
dim cdoconfig
const cdoDispositionNotificationTo = "urn:schemas:mailheader:disposition-notification-to"
const cdoReturnReceiptTo = "urn:schemas:mailheader:return-receipt-to"
set cdoconfig = CreateObject("CDO.Configuration")

with mailer
set .Configuration = cdoconfig
.BodyPart.charset = "unicode-1-1-utf-8"
.BodyPart.ContentTransferEncoding = "quoted-printable"
.Fields("urn:schemas:httpmail:importance").Value = 2
.Fields.Update

.Subject = "Notification"
.From = "donotreply@.test.com"
.TextBody = "TEST"
.Bcc = "someone@.test.com"
.Send
end with
'-

Also, since I have several DTS packages that are similar, I'd like to keep these packages in the SQL 2000 dts format, instead of converting them into SSIS format and using database mail.

Any help would be appreciated.

Almost certainly permissions. Here's the KB article on this subject:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;918760

Is your SMTP server configured to allow anonymous sending, or to allow the account being used by Agent?

-Doug

|||

Thanks for the article.
We did try method 1 (SQL Agent proxy account). We also set method 2 for serverstorage protection level. We don't have any sensitive information so we skipped method 3 (Encrypt Sensitive with password). As for method 4, we do have package configuration files that have been set as well.

Also, our SMTP server allows anonymous connections.

However, since we are trying to execute activex script tasks using CDOSYS, we're assuming perhaps there is some security permissions issue we overlooked with "component services" perhaps? We also tried adding our SQL agent account (as well as proxy account) into our local admins group, but without any luck. It still runs only manually, but fails for CDOSYS when scheduled.

Scheduling simple cdosys email task does not work

I currently have a simple cdosys email task that has been scheduled to send a simple email from ssis. The email is sent using an activex script in a "SQL 2000 DTS Package Task". When executed manually, the email is sent ok. When scheduled (and run under our SQL agent account), it fails. Can anyone point me in the right direction? Is this a permissions issue?

'-- this script seems to cause problems, but only when scheduled --
dim mailer
set mailer = CreateObject("CDO.Message")
dim cdoconfig
const cdoDispositionNotificationTo = "urn:schemas:mailheader:disposition-notification-to"
const cdoReturnReceiptTo = "urn:schemas:mailheader:return-receipt-to"
set cdoconfig = CreateObject("CDO.Configuration")

with mailer
set .Configuration = cdoconfig
.BodyPart.charset = "unicode-1-1-utf-8"
.BodyPart.ContentTransferEncoding = "quoted-printable"
.Fields("urn:schemas:httpmail:importance").Value = 2
.Fields.Update

.Subject = "Notification"
.From = "donotreply@.test.com"
.TextBody = "TEST"
.Bcc = "someone@.test.com"
.Send
end with
'-

Also, since I have several DTS packages that are similar, I'd like to keep these packages in the SQL 2000 dts format, instead of converting them into SSIS format and using database mail.

Any help would be appreciated.

Almost certainly permissions. Here's the KB article on this subject:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;918760

Is your SMTP server configured to allow anonymous sending, or to allow the account being used by Agent?

-Doug

|||

Thanks for the article.
We did try method 1 (SQL Agent proxy account). We also set method 2 for serverstorage protection level. We don't have any sensitive information so we skipped method 3 (Encrypt Sensitive with password). As for method 4, we do have package configuration files that have been set as well.

Also, our SMTP server allows anonymous connections.

However, since we are trying to execute activex script tasks using CDOSYS, we're assuming perhaps there is some security permissions issue we overlooked with "component services" perhaps? We also tried adding our SQL agent account (as well as proxy account) into our local admins group, but without any luck. It still runs only manually, but fails for CDOSYS when scheduled.

Scheduling Reports

How are reporting services reports scheduled to run and email? I don't see
any links in the SQL Server Business Intelligence Development Studio. Are
there plug ins or something else from microsoft that could be missing? I have
SQL Server 2005 SP1 running on my PC (windows 2003). Any step by step
documentation?Reports are scheduled through Report Manager... Go to
http://<yourserver>/reports
Then select a report.
You should see a subscriptions tab, where you can schedule.
To schedule a report, the data source MUST use Credentials Stored Securely
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
I support the Professional Association for SQL Server ( PASS) and it''s
community of SQL Professionals.
"dbach" wrote:
> How are reporting services reports scheduled to run and email? I don't see
> any links in the SQL Server Business Intelligence Development Studio. Are
> there plug ins or something else from microsoft that could be missing? I have
> SQL Server 2005 SP1 running on my PC (windows 2003). Any step by step
> documentation?
>

Scheduling not working

I have an Active Task in a DTS which uses CDONTS to send an email. When I
execute the package manually it works. The schedule doesn't. It says in the
job list that it has been successful. The email does not, however, get sent.
The job, server agent and task scheduler are all enabled. I have even tried
setting up the job/dts package on the server in case there was some kind of
permissions issue. Any ideas? Regards, Chris.
The solution was specify a user name that belonged to sysadmin when creating
the package and schedule.
"Chris Kennedy" <chrisknospam@.cybase.co.uk> wrote in message
news:enmaP4%23REHA.3444@.TK2MSFTNGP12.phx.gbl...
> I have an Active Task in a DTS which uses CDONTS to send an email. When I
> execute the package manually it works. The schedule doesn't. It says in
the
> job list that it has been successful. The email does not, however, get
sent.
> The job, server agent and task scheduler are all enabled. I have even
tried
> setting up the job/dts package on the server in case there was some kind
of
> permissions issue. Any ideas? Regards, Chris.
>

Scheduling not working

I have an Active Task in a DTS which uses CDONTS to send an email. When I
execute the package manually it works. The schedule doesn't. It says in the
job list that it has been successful. The email does not, however, get sent.
The job, server agent and task scheduler are all enabled. I have even tried
setting up the job/dts package on the server in case there was some kind of
permissions issue. Any ideas? Regards, Chris.The solution was specify a user name that belonged to sysadmin when creating
the package and schedule.
"Chris Kennedy" <chrisknospam@.cybase.co.uk> wrote in message
news:enmaP4%23REHA.3444@.TK2MSFTNGP12.phx.gbl...
> I have an Active Task in a DTS which uses CDONTS to send an email. When I
> execute the package manually it works. The schedule doesn't. It says in
the
> job list that it has been successful. The email does not, however, get
sent.
> The job, server agent and task scheduler are all enabled. I have even
tried
> setting up the job/dts package on the server in case there was some kind
of
> permissions issue. Any ideas? Regards, Chris.
>

Scheduling not working

I have an Active Task in a DTS which uses CDONTS to send an email. When I
execute the package manually it works. The schedule doesn't. It says in the
job list that it has been successful. The email does not, however, get sent.
The job, server agent and task scheduler are all enabled. I have even tried
setting up the job/dts package on the server in case there was some kind of
permissions issue. Any ideas? Regards, Chris.The solution was specify a user name that belonged to sysadmin when creating
the package and schedule.
"Chris Kennedy" <chrisknospam@.cybase.co.uk> wrote in message
news:enmaP4%23REHA.3444@.TK2MSFTNGP12.phx.gbl...
> I have an Active Task in a DTS which uses CDONTS to send an email. When I
> execute the package manually it works. The schedule doesn't. It says in
the
> job list that it has been successful. The email does not, however, get
sent.
> The job, server agent and task scheduler are all enabled. I have even
tried
> setting up the job/dts package on the server in case there was some kind
of
> permissions issue. Any ideas? Regards, Chris.
>

Scheduling Job sending email if datefield = today

Hi there,
I am wondering if the following is possible.

I would like to have a scheduled job that would check every day a date field of every record (on a specific table). If that date correspond to today then I would like to send an email with the information of that record.

Is this possible?

Btw if I mentionned Job Scheduling it's because I don't know if there is other ways available for such purpose, so if you think of an other way please let me know.The way I'd do it would be to have a SQL Agent job that is scheduled to run nightly. That agent would run a stored procedure to select today's records, like this:

DECLARE @.currentdate char(8)
DECLARE @.startdatetime varchar(21)
DECLARE @.enddatetime varchar(21)
SELECT @.currentdate = CONVERT(char(8),GETDATE(),112)
SELECT @.startdatetime = @.currentdate + ' 00:00:00'
SELECT @.enddatetime = @.currentdate + ' 23:59:59.999'
SELECT
 *
FROM
 myTable
WHERE
 myDate BETWEEN @.startdatetime AND @.enddatetime

Terri|||

Is there a way to do this with out SQLAgent because tiscali's SQL Agent is not running and thy don't want to run it.
I need to call a webmethod in a webservice every 10 min. any help would be appreciated

|||Sorry, I have no idea. It's not possible through SQL withoutusing the SQL Agent AFAIK. It looks like you've asked thisquestionelsewhere so hopefully you'll get the answer you are looking for.
|||

Thanx

If you had to write a website withreminders so that the users can say I want a reminder on this day and thistime. What would you do to see if a reminder is due and send it?

I desperately have to find a way to do this.

|||Sorry, I'd use SQL Agent. :-( Where I work we host both thewebsite and SQL Server so I have all possible methods available to me.
FWIW There are several threads going on in the Getting Started forum right now related to this topic

http://forums.asp.net/944623/ShowPost.aspx
http://forums.asp.net/494136/ShowPost.aspx
http://forums.asp.net/945255/ShowPost.aspx (sort of)

Also, check out these articles:

Combine Web and Windows Services to Run Your ASP.NET Code at Scheduled Intervals
The Code Project - A New Task Scheduler Class Library for .NET

They both rely on a Windows Service to work, and it sounds like in your situation you do not have that option.


|||

Thank you for your help. I think I have toconvince my company to go to another hosting company where I can use a windowsservice.

Thank you

|||I agree with you. I chatted with a pal about this and another suggestion he had wasPaul Wilson's Keep-Alive hack.Keep in mind this is indeed a hack and is prone to failure but it couldbe better than nothing as you try to implement a more robust solution.
|||

Thank you,you are a life saver

|||All the credit goes toSomeNewKid; he is one smart cookie. I'm glad this suggestion got you over the hump.

Scheduling Issue...need help please.

I have a report that has to be delivered via email on the last day of each
month. I am using a last_day function to capture the last day of each month.
Can I store this in a table and have RS2000 email based on the value in the
table? If so, how?
Thanks in advance
OSIs there any way you can upgrade to SQL 2005? The reporting services is SO
MUCH BETTER... and you can EASILY create a report subscription that will send
on the last day of the month.
--
~lb
"OriginalStealth" wrote:
> I have a report that has to be delivered via email on the last day of each
> month. I am using a last_day function to capture the last day of each month.
> Can I store this in a table and have RS2000 email based on the value in the
> table? If so, how?
> Thanks in advance
> OS

scheduling delivery

i would like to ask how to execute the email delivery setting? can it be done
in the report server homepage'it is a must to get it work through web
service programming?
thanks in advanceIts form the report MANAGER home page http://servername/reports. Go to
whtever report you want the set the subscription on, and when you view the
report, you have a tab saying new subscription, click on tht and give the
parameter info and the schedule info.
"Jasonymk" wrote:
> i would like to ask how to execute the email delivery setting? can it be done
> in the report server homepage'it is a must to get it work through web
> service programming?
> thanks in advancesql

Scheduled weekly reports

I am trying to create a Job that will run a stored procedure i have scripted
and the email the the results to certain managers in my company for analysis
purposes. The procedure is fine i was just wondering how i would get the
results formatted and into an email. Do i use the SQL Mail?hi
did u see xp_sendmail
best Regards,
Chandra
http://chanduas.blogspot.com/
http://www.SQLResource.com/
---
"A.B." wrote:

> I am trying to create a Job that will run a stored procedure i have script
ed
> and the email the the results to certain managers in my company for analys
is
> purposes. The procedure is fine i was just wondering how i would get the
> results formatted and into an email. Do i use the SQL Mail?|||"A.B." <AB@.discussions.microsoft.com> wrote in message
news:4C34B83A-C86E-4031-ACEF-05B4F02B0326@.microsoft.com...
>I am trying to create a Job that will run a stored procedure i have
>scripted
> and the email the the results to certain managers in my company for
> analysis
> purposes. The procedure is fine i was just wondering how i would get the
> results formatted and into an email. Do i use the SQL Mail?
No, you use reporting services.|||Do both: use SQL Mail to send a message that the report is ready, but use SQ
L
Reporting Services for the actual report.
Why would you need to send a large amount of data through e-mail? Don't they
get enough spam anyway? ;)
ML|||"ML" <ML@.discussions.microsoft.com> wrote in message
news:7303024C-CB3B-4273-9D76-24D9C962D9BC@.microsoft.com...
> Do both: use SQL Mail to send a message that the report is ready, but use
> SQL
> Reporting Services for the actual report.
Or you could use Reporting Services to both render and send notification via
email.

Scheduled task alerts in 6.5

Is it possible to setup SQL server 6.5 to automatically inform me via email
when a scheduled task fails? Im told that this is possible in 2000, but not
in 6.5.
Is there any work around? some scripts or a 3rd party util ?
olly
--
________________________________________________
Macinley.co.uk
http://www.macinley.co.ukHi,
Yes, You can do an Email alert in SQL 6.5
1. Enterprise manager -- Select Server menu -- choose Alerts / Operators
2. Click in the Operator tab -- New OPerator -- Mention a operator ID and
give the email address
3. CLick OK
4. Go to ALerts tab -- CReate new alert
5. Mention and id and in the respose definition select the "Scheduled Task
to fire"
6. Mention the Alert Notification message and click ok
So when ever there is a error raised an Email alert will be send.
Thanks
Hari
MCDBA
"Harry Hudini" <harry.hudini@.nospam@.simplicity.co.uk> wrote in message
news:#dzjybIcEHA.3016@.tk2msftngp13.phx.gbl...
> Is it possible to setup SQL server 6.5 to automatically inform me via
email
> when a scheduled task fails? Im told that this is possible in 2000, but
not
> in 6.5.
> Is there any work around? some scripts or a 3rd party util ?
> olly
> --
> ________________________________________________
> Macinley.co.uk
> http://www.macinley.co.uk
>|||Harry,
As a side note, you should be aware that SQL Server 6.5 is no longer
supported by Microsoft. I do not recommend you use it in production (or
anywhere else). Upgrade to SQL Server 2000 as soon as you can.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Harry Hudini wrote:
> Is it possible to setup SQL server 6.5 to automatically inform me via email
> when a scheduled task fails? Im told that this is possible in 2000, but not
> in 6.5.
> Is there any work around? some scripts or a 3rd party util ?
> olly
>

Scheduled report by email with attached report fails

Can anyone offer any help with this?

Error maesage:
Status:
Failure sending mail: The Report Server has encountered a configuration error; more details in the log files

Windows 200 Server: SP4
RS 2000: SP2
SQL Server 2000, on the same server as RS.

We

get this error whenever we try to run a report with the report

attached. However, the email sends fine if the report is not attached.

Reports can also be exported into different formats without problem when viewing the report through report manager.
I received a email telling me there had been a reply to this thread, but I see nothing.

Can anyone help with this?|||Did you check the log files to see what the error is?|||Bringing this topic back from the dead a little I know, but I've finally had chance to get back to trying to use this since being switched onto other projects.

Which log would likely contain the information needed.
The logs located at: C:\Program Files\Microsoft SQL Server\MSSQL\LOG
called: SQLAGENT.OUT ?|||I am having the same problem. The report service log file only re-iterates the message, and does not provide any further details.
I checked the Report Server configuration file and it looks okay, nothing unusual.
Does anyone have any idea what may be causing the problem?|||

The RS log files are located here:

%Program Files%\Microsft SQL Server\MSSQL.2\Reporting Services\LogFiles

The Windows Service log file (which processes subscription events) should have a name like this:

ReportServerService__03_19_2007_00_01_09.log

|||

No entry is made in that folder when it fails the job.

However, we have noticed that if my colleague creates the subscription then it works fine without the error. So I suspect it might be related to permissions in sql server or on the win 2000 server box. So far I've been unable to determine which permission is causing it. Despite ensuring I am in the same permission groups as he is, my subscriptions still fail.

Scheduled report by email with attached report fails

Can anyone offer any help with this?

Error maesage:
Status:
Failure sending mail: The Report Server has encountered a configuration error; more details in the log files

Windows 200 Server: SP4
RS 2000: SP2
SQL Server 2000, on the same server as RS.

We

get this error whenever we try to run a report with the report

attached. However, the email sends fine if the report is not attached.

Reports can also be exported into different formats without problem when viewing the report through report manager.
I received a email telling me there had been a reply to this thread, but I see nothing.

Can anyone help with this?|||Did you check the log files to see what the error is?|||Bringing this topic back from the dead a little I know, but I've finally had chance to get back to trying to use this since being switched onto other projects.

Which log would likely contain the information needed.
The logs located at: C:\Program Files\Microsoft SQL Server\MSSQL\LOG
called: SQLAGENT.OUT ?|||I am having the same problem. The report service log file only re-iterates the message, and does not provide any further details.
I checked the Report Server configuration file and it looks okay, nothing unusual.
Does anyone have any idea what may be causing the problem?|||

The RS log files are located here:

%Program Files%\Microsft SQL Server\MSSQL.2\Reporting Services\LogFiles

The Windows Service log file (which processes subscription events) should have a name like this:

ReportServerService__03_19_2007_00_01_09.log

|||

No entry is made in that folder when it fails the job.

However, we have noticed that if my colleague creates the subscription then it works fine without the error. So I suspect it might be related to permissions in sql server or on the win 2000 server box. So far I've been unable to determine which permission is causing it. Despite ensuring I am in the same permission groups as he is, my subscriptions still fail.

Scheduled report by email with attached report fails

Can anyone offer any help with this?

Error maesage:
Status:
Failure sending mail: The Report Server has encountered a configuration error; more details in the log files

Windows 200 Server: SP4
RS 2000: SP2
SQL Server 2000, on the same server as RS.

We get this error whenever we try to run a report with the report attached. However, the email sends fine if the report is not attached.

Reports can also be exported into different formats without problem when viewing the report through report manager.
I received a email telling me there had been a reply to this thread, but I see nothing.

Can anyone help with this?
|||Did you check the log files to see what the error is?|||Bringing this topic back from the dead a little I know, but I've finally had chance to get back to trying to use this since being switched onto other projects.

Which log would likely contain the information needed.
The logs located at: C:\Program Files\Microsoft SQL Server\MSSQL\LOG
called: SQLAGENT.OUT ?
|||I am having the same problem. The report service log file only re-iterates the message, and does not provide any further details.
I checked the Report Server configuration file and it looks okay, nothing unusual.
Does anyone have any idea what may be causing the problem?|||

The RS log files are located here:

%Program Files%\Microsft SQL Server\MSSQL.2\Reporting Services\LogFiles

The Windows Service log file (which processes subscription events) should have a name like this:

ReportServerService__03_19_2007_00_01_09.log

|||

No entry is made in that folder when it fails the job.

However, we have noticed that if my colleague creates the subscription then it works fine without the error. So I suspect it might be related to permissions in sql server or on the win 2000 server box. So far I've been unable to determine which permission is causing it. Despite ensuring I am in the same permission groups as he is, my subscriptions still fail.

Scheduled Jobs & Failed Notifications

Periodically on jobs scheduled in the SQL Server Management, a scheduled job will execute successfully, but fail to email the notification to the operator that the job completed successfully.....anyone have any thoughts as to the cause
I welcome any input ! :)Make sure your windows application log is not full, if it is, you will not
get notified.
--
Ray Higdon MCSE, MCDBA, CCNA
--
"David Moe" <dmoe@.coorstek.com> wrote in message
news:BCDD08D7-A9D6-4717-93D0-100DBBF38C98@.microsoft.com...
> Periodically on jobs scheduled in the SQL Server Management, a scheduled
job will execute successfully, but fail to email the notification to the
operator that the job completed successfully.....anyone have any thoughts
as to the cause ?
> I welcome any input ! :)|||if you never get email notification work, that means
maybe you havn't configure the sql mail utility.
>--Original Message--
>Periodically on jobs scheduled in the SQL Server
Management, a scheduled job will execute successfully,
but fail to email the notification to the operator that
the job completed successfully.....anyone have any
thoughts as to the cause ?
>I welcome any input ! :)
>.
>|||This thread is on a server which has other working alerts, typically including the one that failed
All other alerts executed with no problems...just this one fails periodically....haven't been able to coorelate any problems with server or database(s) on said server
It simply states in both the job history and the application event log that the notification failed. (Event log is set to overwrite
This same operator is used in all of the alerts coming from this particular server
-- David Moe wrote: --
Periodically on jobs scheduled in the SQL Server Management, a scheduled job will execute successfully, but fail to email the notification to the operator that the job completed successfully.....anyone have any thoughts as to the cause
I welcome any input ! :)

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
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >