Job not running daily with events

[junction123]

For several weeks I have been unsuccessful in trying to get my report to run. I have scheduled two instances one to run at 12:05 AM(before the event runs) the next day and one to run at 7:00 AM the next day after the event runs.

When I run the job manually it is fine and sends the report via e-mail.

I have scheduled jobs that run outside the Crystal server mainly one that deletes the old file from the root directory on the Crystal server and another that puts a new flag file in the root directory on the Crystal server, an indication for the event on the Crystal server to kick off. These jobs run fine. Assuming the event kicked off successfully, what else could be the cause?

I am using Crystal Management Console.

The crystal admin support has been helpless.

I looked at the Crystal knowledge base but that does not explain anything very clearly.

http://support.crystaldecisions.com/library/kbase/articles/c2013051.asp

Can anyone help me on this and put an end to my frustration?

Thanks in advance!
junction123

 

[rhinok]

General Troubleshooting

The first report, the one that runs prior to the event, is irrelevent to the event itself. The one we're concerned about is the second report, which should be based on the file event, correct? I have a couple of questions for you:[ol][li]Under 'Filename' did you key in the full UNC to the file, including the extension (c:\filename.txt or \\server\folder\filename.txt, for example)?[/li]

[li]Have you tested whether or not you can access the file--using the path and filename from the 'filename' event field--directly from the machine that houses the Event Server?[/li]

[li]Is the event server enabled? It may be running, but disabled.[/li][/ol]Assuming the Event Server is enabled and the file is accessible by the server:

The article you linked to basically states that the report referenced was incorrectly scheduled from the start, which hosed all subsequent recurrences ('hosed' being a technical term). Technically, an event-based report doesn't kick off at the time you specify. It stays in a pending status until the event actually occurs. When you schedule a report to run daily at 7 am based on a file event, Crystal Enterprise will start polling the file location for the creation of the file after 7 am.[ul][li]If the file is created at 7:05 am then the report will generate, because CE will recognize that the file was created after it started looking for it.[/li]

[li]If the file is generated at 6:59 then the report won't generate, because the file will already exist by the time CE starts looking for it. [/li][/ul]I think this is what's happening in your situation.

My suggestion is to delete your recurring, file event-based schedule and recreate it so that CE starts polling for the file prior to its next generation. If you expect the next file to be created at ~7 am, tomorrow then create the schedule so that it starts looking for the file on 12/04/2003 06:50 AM.

~Kurt

 

[Reebo99]

Under Schedule, select Daily.

Using the drop down list, select :

Every X hour(s), N minute(s), with events

Set Where X is: to 0 and Where Y is: to 1

Leave the start and end dates as the default.

Select the event from the Events to wait for.

This will give you a report which will run every time the event is triggered, assuming the event isn't triggered twice in 1 minute.

Reebo
UK

 

[mdwyer]

And could people scream at Crystal Decisions to enable a persistent file-based event?

Using the times in RhinoK's message as an example, I have reports that cannot run before 7am because of server scheduling. But the event file is typically created around 6am, although it might be delayed as late as 8am. Also, adhoc instances scheduled during the day get tied to the file-based event. My definition of a file-based event (developed in Seagate Info before the downgrade to CE) is "does the file exist?"

 

[junction123]

Thanks all for your help! I had found out that the crystal admin had entered the wrong path under filename.

Kurt, you were right, though I have read your reply only today.