Registry Start Scheduled Report Manager (sys-start-sschdldrprtmngr)


This registry entry addresses a sporadic problem that some users have encountered with ReportAnywhere. Occasionally ReportAnyway gets in a mode where it isn't actually doing anything but it gives no indication of any problems.  This registry entry is designed to alert the appropriate individual of the situation, so that the ReportAnyway service can be shutdown and restarted.

Testing Your Registry Entries
The system does not verify the validity of registry entries. Be sure to test your registry entries after completing them to verify that they are functioning correctly.

Setting Values are Uppercase-Lowercase Sensitive:
The Setting Value is case-sensitive: be sure that you enter the value exactly as specified in the documentation. If the documentation specifies a value of true, do NOT enter True or TRUE.

Batch Files:

Typically, the Scheduled Report Manager as an agent-type user, and started via a batch file. See Suppressing Messages Boxes for Agent Type Users for an important batch file command.

Important Fields:



Enable Timeout Alarm Option

With this option enabled, an alarm-type event is created whenever ReportAnywhere is launched.  As long as ReportAnywhere continues to function normally, it continually reschedules the alarm event to prevent it from triggering.  When ReportAnywhere is shutdown properly, it cancels the timeout event to prevent a false alarm.  However, when terminated abnormally (this includes stopping due to an unexpected error), the alarm event will eventually trigger and someone will be advised that a problem exists. 

Setting Key: TimeoutAlarmEnabled Setting Value: true (default = false)

This entry is required for the timeout alarm.

Specify Timeout Interval

Setting Key: TimeoutAlarmDays Setting Value: anInteger (default = 0)

Setting Key: TimeOutAlarmHours Setting Value: anInteger (default = 0)

Setting Key: TimeOutAlarmMinutes Setting Value: anInteger (default = 30)

Replace anInteger with an appropriate number. You may implement one of these entries to set the timeout interval. The registry entry should use only one of the Days, Hours or Minutes entries.

Alarm Message Options

Setting Key: TimeoutAlarmEmailFrom Setting Value: anEmailAddress (default user's email)       
Setting Key: TimeoutAlarmEmailTo Setting Value:anEmailAddress (default TimeAlarmEmailFrom)       
Setting Key: TimeoutAlarmEmailSubject Setting Value: aSubject
(default = ReportAnywhere service appears to have stopped.)
Setting Key: TimeoutAlarmEmailMessage Setting Value: aMessage (default= blank)

These entries control who the timeout alarm is sent to, as well as the contents of the subject line and message text.

WARNING:  if a single instance of SAMPRO is used to run both the Scheduled Event Manager and ReportAnywhere, this option is useless since they would both stop simultaneously.  Generally, I would suggest that Scheduled Event Manager run independently in its own instance of SAMPRO.

 Log File

An optional log file can be maintained by each running instance of ReportAnywhere.  The idea is to use the log to determine what ReportAnywhere has been doing when it gets into the aforementioned mode.  The entry to implement this option is:

Setting Key: LogFileEnabled Setting Value: true (default = false)

The log file is named ReportAnywhere_<UserId>_<AlarmEventId>.log  It is created in the same directory as the running V.EXE.


This release includes simpler options to set the amount of time ReportAnywhere goes to sleep between checking for new reports to run.  The entries to implement this option are as follows:

Setting Key: TimerMinutes Setting Value: anInteger (default = 0)
Setting Key: TimerSeconds Setting Value: anInteger (default = 0)
Setting Key: TimerMilliseconds Setting Value: anInteger (default = 60000 = 1 minute)

Only one of these entries should be made.  

Scheduled Downtime

This option enables you to specify Scheduled Downtime for Scheduled Event and Report Managers under SQL Server. It lets you temporarily suspend operation of the event managers, including Scheduled Events, Report Events, and TechAnywhere Events. These registry settings are needed so that certain SQL server maintenance tasks can be completed in SQL Server. These tasks include Reorganizing and Rebuilding Indexes. We recommend discussing this option with your support representative.

Setting Key: Downtime Setting Value: start_end

The downtime is specified in military time (e.g., 12:30 AM = 0030, 11:15 PM = 2315) and should last for at least an hour. The downtime that you specify needs to be in sync with the time the SQL Server is firing the Reorganizing and Rebuilding Indexes. The Scheduled Events manager needs to be started 10 minutes after the Report and TechAnywhere managers so that there are no conflicts.

All of the managers must be suspended individually as shown in following examples.


For these examples, we will assume that SQL maintenance runs from midnight until about one in the morning. Since we are not sure exactly when maintenance will end, we have given ourselves an extra ½ hour of downtime. Note that the Scheduled Event Manager restarts 10 minutes later.

Techanywhere Event Manager (if applicable):

Id: sys-start-stchanywhreevntmngr  Setting Key: Downtime Setting Value: 0000_0130

ReportAnywhere Scheduled Report Manager:

Id: sys-start-sschdldrprtmngr   Setting Key: Downtime Setting Value: 0000_0130

Scheduled Event Manager: (notice downtime is 10 minutes longer)

Id: sys-start-sschdldevntmngr  Setting Key: Downtime Setting Value: 0000_0140