There was a problem loading the comments.

Installing Event Server 2030

Support Portal  »  Knowledgebase  »  Viewing Article





Installation of Report Runner Event Server is simple and straightforward. Following is a list of steps, one-by-one, that will take you from beginning to end:

1) Download the software

2) Run the setup executable name Report_Runner_Event_Server_Setup.exe (right-click on it, and Run As Administrator).

3) This is the first window you will see (after initialization process).

4) Select the type of install to run, and click Next

5) Enter your Program Files directory.

Note: This directory MUST ALREADY EXIST with Report Runner Batch installed there. You will not be able to continue unless this has been done. It's required that you've already installed Report Runner Batch previously. 

Note: If you have an older release installed, you will see a screen like this to let you know the installer needs to uninstall the previous version first.

6) Enter your Report Runner data folder (default should normally be used), and click Next.

Note: This directory MUST ALREADY EXIST as well since it's required that you've already installed Report Runner Batch. Within the existing Report Runner Batch\AppData directory, the installer will add an Event Server folder (along with the Input, Processed, and Error directories).

7) Enter your existing short-cut folder (default should normally be used), and click Next

8) Select your installation options, and click Next.


Event Server "watches" for multiple events to happen.


By default, one of the possible events is watching for when a Batch XML file "hits" the Input queue. The first option below sets the amount of time between checking the Input queue for existing batches. The default setting of 5 seconds is more than adequate.


The second option tells Event Server how many Batch XML files to process at one time. There is a maximum of 20 batches at a time. It's important to understand you must make sure the computer/server you are installing Event Server on is capable of processing 20 batches at a time. Event Server does NOT monitor the power or capability of your server. It will simply try to run 20 batches at once if you instruct it to.


The third and fourth options are separate time settings (like option 1) for the 3 add-ons to Event Server (Mail Rules, File Rules, and SQL Rules). These 3 add-ons are included with any Event Server license. The rules default to 0, because you do not want these rules activated if you are not using them. 0 means the rules are disabled (not run). 

9) You are ready to INSTALL; this is your final confirmation before files start being copied; click >>INSTALL>> to begin

10) This is what it looks like while installing

11) Installation is complete, and click Finish

12) Once the installation is complete (after the main files are copied), you will see a message about setting and configuring the Report Runner Event Server Service (Start, Control Panel, Administrative Tools, Services, Report Runner Event Server Service).

NOTE: If you are running reports from UNC path or exporting reports to a UNC path, it's important that you change the "Run As" permissions on the Event Server service itself. Otherwise, the batches will NOT work. By default, a Windows service uses the System account to run, and the System account does NOT have access to network resources. You may also need to modify the "Run As" permissions for various database security settings, too.

13) Now, let's verify the Report Runner Event Server service, know where it is, and it works.


Go to your Control Panel, Administrative Tools, open up Services, and find Report Runner Event Server.


Right-click on Report Runner Event Server Service, bring up the Properties, and look at the Logon tab

Important: By default, as mentioned previously, services run as the Local System Account. Sometimes this Local System account has access to do everything it needs on your server, sometimes it doesn't. You may need to modify it to use "This account", and specify a specific Windows ID and password (like your own). This ensures the service can access DSNs, databases, the mail server, and file locations that your batches require to run successfully.

14) You may be thinking, "How can I know the service is running?" Let's look at the log files that the service generates. Go back to your Control Panel, Administrative Tools, and open Event Viewer.


Expand "Application and Services Logs" and find "JNRRB_ES Log"

The JNRRB_ES log is the log that the service writes to constantly (if the service is running). It writes to it every few seconds. The service will write to this log file upon starting and stopping, and every time it is processing batch XML files or rule packs.

All of this writing can generate large log files. These log files need to be maintained. Make sure you have set the log files to overwrite as needed. If you do not, and the log file fills up, it will crash the service.

Make sure you have set the log files to overwrite as needed. Again, if you do not, and the log file fills up, it will crash the service.

Important: Make sure the log file is configured to overwrite as needed!
15) Last, but not least, let's take a look at the Report Runner Event Server Controller. Look for an [E] icon in your system tray , in the lower right-hand corner of your monitor. If you right-click on the [E] icon, you'll see options to control/Start/Stop the Event Server service and to Display Event Server Monitor. Click to START the Event Server service.


Note: If you haven't rebooted after installing (it's part of Start up settings), it can be manually started. Go to your Report Runner apps in the Program Files and find the Controller installed there, and start it. After starting, look for [E] icon and try starting the Event Server service.

When you start the Event Server service, you may see the following error. This means you are not running the controller with proper Administrator permissions. Did you use the "Run As" Administrator to install? If not, you will need to go back and re-install it. For now, to get past the error, right-click on the controller and exit it, and restart it using the right-click option to run the controller as Administrator. Once you get the controller running again, re-try starting the Event Server service. 

Next, let's look at the Event Server Monitor. Right-click on the [E] icon and click to start monitor.

This option displays a really cool utility to monitor your various Event Server queues (Input, Error, and Processed). It also give you a neat way to monitor active batches and system resources. 

The Event Server Monitor looks like this (except a bigger window). 


There is a LOT of information on this window:


a. Input queue - you'll see any XML files waiting to run here

b. Error queue - you'll see any XML files that failed here

c. Processed queue - you'll see any successfully processed XML files here


With any XML files you see, you can double-click on them and see the log file!


The Processed queue will only show the most recent 100 XML files. This makes the window work faster, because some users have 1000's of XML files in the processed queue. There is an option to Pause Monitor should it even not be responsive enough for you to open an XML file.


From here, you can also Open Services (to tweak Report Runner Event Server service). And you can open the Event Viewer to look at the JNRRB_ES Log file.


In the lower middle, you can see the words "File/SQL" and "Mail". If these are greyed out, the rules are NOT enabled. If they are GREEN, then that rule pack is enabled and running.


Lastly, if you have Report Runner Monitor and Debugger installed, you can click the big button to start it and see various CPU usage of any Report Runner process. 

This is what the Report Runner Monitor and Debugger window looks like (except it's bigger). Other than seeing tasks running, there are multiple tabs across the top. For Event Server, there is a tab which will allow you to see various logs related to Event Server processes (that are stored in the Report Runner Batch log file directory). These logs are DIFFERENT from the messages in the JNRRB_ES Log file. The JNRRB_ES Log file shows you SERVICE messages. The logs in the Batch log file directory will show you specifics as to what Event Server has run and why.

That's it! 



Common Installation Errors/Issues:

  1. If service will not start from controller, check your Run As permissions (or reinstall using Run As Administrator).
  2. If service will not start or it starts and crashes quickly (won't stay running), check your log file settings as discussed previously. Make sure it's set to overwrite. 
  3. If you are wanting to use the rule packs and they are not running or if they are not editable within Report Runner Batch (Tools menu), you have set the scan time for the rules to zero (0) when you were installing Event Server. Rerun the Event Server installer and modify the settings. 
  4. If your system seems overloaded running batches (CPU pegged at 100%), try reducing the maximum XML batches that can be processed. Rerun the Event Server installer and modify the settings.



KB article regarding the Mail, File, and/or SQL Rule Add-Ons for Event Server:

KB article regarding the Event Server AutoPrint feature (print PDFs automatically):



Share via

Related Articles

© Report Runner Support