Scheduling Reports in 8.5

[oshlonger]

I schedule my reports through Crystal Management Console to run daily. It seems that every so often, a day is skipped and the report isn't run. By skipped, I mean the there is no instance of the report run, not that it fails. The days that are skipped do not fit any pattern, just random days.

Has anyone else encountered this problem?

 

[khartman]

When you look at the history for your report does it show failed instances or just that they are not appearing? Are you running your APS on an NT/2000 machine? If so check the Event Log and make sure that the APS hasn't been shut down during those periods. Maybe your systems people are doing maintenance on those servers and are performing system reboots during the period in which your report is scheduled to run.

 

[oshlonger]

The history of my report has no instance for a particular date. The report is not failing, its not running. For example, there will be a success for 1/9, 1/10, and 1/12. There will be nothing listed for 1/11.

I'm running Crystal 8 on a windows 2000 machine. As far as I know, there was no maintenance or system reboots during the period that my reports are scheduled to run.

 

[lyanch]

Depending on the level of logging you have turned on, you may be able to get information from your logs:

In the crystal aps log look for something like:

Agent(6518) loaded to Runnable Map...

That is the agent that is running that scheduled report.

There might be some failure info in there for your report.

Lisa

 

[oshlonger]

How exactly do I go about checking my Crystal APS logs?

 

[lyanch]

There is a log directory on the server. Depending on what (if any) level of logging you are using, logs will show up.

Crystal aps logs look like "crystalaps_" + timestamp.log. If you don't have any then you don't have logs turned on. Check the support site for turning logs on and off.

Warning: Having all logs on max can eat up a LOT of disc space in no time at all (mine eat about a gig a week).

Lisa

 

[oshlonger]

Ok, I was able to find the log files. I have been keeping track of the days that my report has skipped and they sort of relate to the log files. Each time a log file is generated, the next day the report doesn't run. I don't know how to interpret these log files nor do I know what my next step is. Any help would be appreciated.

 

[lyanch]

I can only interpret some things in the logs. If you don't have a log that covers the time the report is scheduled to run then the service (or server) is probably not running. The logs start a new one for three reasons: either the log is full (489kb) or the service is stopped and restarted (files less than 489 kb when stopped) or midnight is reached (again files less than 489 kb). I have never experienced the problem that you are looking at. If your schedule is to run at midnight exactly, you might want to change the schedule to start a couple minutes after midnight.. just because the system seems to do a cleanup then.

Lisa

 

[oshlonger]

There are no "crystalaps_" + timestamp.log for the exact time that the report isn't run. I have several reports that are scheduled to run at different times during the morning(between 7-9am). All of these reports skip for the particular day.

The info in one of the logs reads:
Assert Failure (y:\silib\cosnaming\nameserver\ncontext.cpp212). (false: cserverNamingContext::dobindageserverageserver not responding).

I appreciate your help