There was a problem loading the comments.

Installing Report Runner Web Portal on Windows Server 2012, 2016, 2019, 2022 (or Later)

Support Portal  »  Knowledgebase  »  Viewing Article

  Print

PREREQUISITES - MUST READ:

The first prerequisite is you or someone at your company must have a basic knowledge of IIS to be able to install this application on a web server. If you do not know IIS, this is not something we can teach. Get with your IIS administrator to install the application. Once installed, anyone that is familiar with Crystal Reports will understand how to configure the reports for Web Portal. 

You can install Web Portal on Windows Server 2012, 2016, 2019, 2022 or later. We do not support installing or running Web Portal on a desktop PC. This defeats the purpose of running a server application.

While we can't support the installation of IIS, we DID outline the steps we took installing IIS on Windows Server 2019 (these instructions also work for 2016 or 2022). If you're starting with a fresh server (like one just "spun up" on AWS), do the following:

 

https://help.reportrunner.com/knowledgebase/article/basic-configuration-of-a-new-windows-server-to-run-report-runner-web-portal-asp-net-application

 

User Requirements and System Requirements to Install Report Runner Web Portal (and other Report Runner Products)

 

---

Web Portal is not an overly complicated application, but it is important you use this installation guide and follow each step. There are a lot of parts that work together beautifully, but each piece must be there. There is more to do than simply run the installers and type in a URL.

 

Do the following FIRST, before installing Web Portal:

  • Print Installation Check List (Click to Open PDF) - This is a high level overview of major steps.
  • Install Report Runner Batch First; Note, when you install Report Runner Batch, go in and configure it. For the Web Portal server, you MUST configure your MAIL settings (Global Options, Settings, Mail settings tab) to be able to email a report in Web Portal. Be sure and configure you mail settings in Report Runner Batch before proceeding (and be sure and TEST them, too, in Report Runner Batch).
  • Install Report Runner Event Server Second

 

---

UPGRADING FROM A PREVIOUS RELEASE?

Backup your entire Web Portal install files and directories in C:\inetpub\www\YourWebPortalDirectory; if you've made custom CSS changes, those will normally need to be re-done. If you have any issues re-doing your CSS changes, if you have a backup, we can easily help you merge old settings with new settings.

 

---

 

LOOKING FOR RELEASE NOTES?

 


---

I. INSTALLING WEB PORTAL:


Have you installed Report Runner Batch and Report Runner Event Server on the same machine yet? If not, go back to PREREQUISITES.

Important! If you are a network administrator installing Web Portal for someone else in your company who will be administrating it, it is HIGHLY recommended they sit with you while you install the application. There are NUMEROUS directories that the Web Portal administrator needs to know about and USE. These directories must be written down so the Web Portal administrator knows where to find them later.

Installation of Report Runner Web Portal 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 via the link sent to you in email (it's not publicly posted on our website)

2) Run the setup executable name Report_Runner_Web_Portal_Setup.exe

Note: If running in an environment where your machine is "locked down", you will need to use the "Run As Administrator" function or if on a Terminal Server (RDP), use "Install Terminal Server Application" from the Control Panel.



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



4) Next, read the Happiness Disclaimer, and click Next



5) Enter your IIS website directory (do not use spaces within this folder), and click Next



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

Note: This directory MUST ALREADY EXIST (because you previously installed Report Runner Batch and Report Runner Event Server). You will not be able to continue unless the directory is there. Within the existing Report Runner Batch\AppData\Event Server directory, this installer will add a WebTemplates directory. This is where your report Web Templates will need to be moved/saved from Report Runner Batch or where they are auto-generated when you add RPTs to the Input queue of Event Server (more on this later). These "Batch" XML templates are used to configure your web reports.

NOTE: Reread previous note (a common question is "Where do I put my web templates?") -- You will also be reminded again later.



7) Select the Portal skin/color you would like to start off with initially (this can be changed later). Most customers go with "Modern" or "Microsoft" to start out with. As noted on the installation screenshot below, we are happy to help you customize your Web Portal's customer-facing interface to match your company's branding.



8) Enter your company name.



9) Configure your mail settings. In the user-facing application, the user can change their login password. These mail settings are only used to send these emails (when login password is changed).

 

NOTE: The Web Portal report emails are sent using the Report Runner Batch mail settings (not the settings below).



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



11) This is what you will see while the files are installing



12) Once the installation is complete (after the main files are copied), you will see a message about setting and configuring IIS. The application should be set up as an .NET 4 application (which is the default application pool for modern servers). 

NOTE: The ADMIN interface/the jnAdmin folder (which has all the ASP pages for creating/editing reports and users) is not protected by default. You can easily configure a web portal administrator password in the web.config file (AdminPassword). It times out after 30 minutes (and you can configure that).

 

Additional pop-up reminder of what has to be done after the installer completes.


note-remember.png

13) Installation is complete, and click Finish

Note: Write down the Picklist and Web Templates directories listed below. The Web Portal Administrator needs to know where these directories are located.

Note: Write down the Picklist and Web Templates directories listed below. The Web Portal Administrator needs to know where these directories are located. 

Note: Write down the Picklist and Web Templates directories listed below. The Web Portal Administrator needs to know where these directories are located. 


note-remember.png


14. SET FULL PERMISSIONS ON FOR ALL USERS. Go to the main Web Portal directory (C:\inetpubs\ReportRunnerWebPortal by default). Right click on this directory. Make sure no files are flagged Read Only, and turn on FULL CONTROL permission for all users; Properties, Security, Edit; click on all groups and user names and check/select Full Control and Apply. Do NOT proceed until you have done this.











15. Start IIS (Start, Windows Administrative Tools, IIS Manager)



- Expand Machine, Sites, expand Default Web Site, and you'll see ReportRunnerWebPortal listed
- Right-Click on ReportRunnerWebPortal, Convert to Application (default application pool should be .Net 4 which is what you want); Click OK to confirm





16. If you are on Windows 2016, 2019, 2022, or later, edit the web.config file in the main Web Portal directory. There is a line in it you need to delete/remove. If you do not do this, the formatting of the portal will not look correct.

 

DELETE THE MIMEMAP LINE SHOWN:

 

 

 

Save your changes to the web.config file.

---

IMPORTANT DIRECTORIES TO BE AWARE OF:

1) Free category icons directory. We've made over 150 free category icons available. You can create custom report categories and select any of these perfectly designed and matching icons.



2) Picklists directory. This directory is where you place any custom picklists you create to assign to parameters. The Web Portal is unable to load the SQL-based dynamic parameters directly your Crystal Reports, so we allow you to create picklists external to Web Portal and assign them to parameters. Picklists can be static, single value or show one value but set another, cascading, or SQL-based. Our Cascading parameters can fully duplicate all of the functionality within Crystal Reports parameters. There are a number of pre-defined picklists in this directory, and you'll figure out the syntax of these picklists quickly. Also note, the beginning names of the picklists matter, too. The names are used to determine how Web Portal reads the picklist format. This text-based picklist technique is simple and elegant all-in-one. Picklist configuration is discussed more below in the "Configuring Web Portal" section.



3) "New" Report templates directory. This directory is where you can place any NEW reports that you want to run in the Web Portal. This will allow you to browse to these reports when you're ready to add a new report.

 

Please note, alternatively (and our recommended technique), you can "throw" all RPT files for Web Portal into the Input queue of Event Server, and Event Server will automatically create Web Portal templates for each report. As a bonus, when these RPTs are processed, any static parameter selections found in the report will be used to create auto-picklist text files to be used within Web Portal (more on this later).

 

The login ID/password assigned to the reports in this "Input Queue" process will be the Global ID/password from Report Runner Batch. If your reports do not require an ID/password, you can either leave the Global ID/Password blank or literally set them both to "jnnothing" (without quotes). Any other kind of custom login information will require you editing the XML files (Web Templates) manually from Report Runner Batch.



---

MODIFYING WEB.CONFIG SETTINGS:

All of your Web Portal-specific settings are stored in the web.config file, found in c:\inetpub\www\YourWebPortalDirectory. Towards the top, you will see various paths defined, which the installer takes care of setting. There are some additional settings that you can toggle features on or off by editing the web.config file manually. Most of the settings in web.config have comments/notes above them that explain how to modify them.

 

Here are a few examples of modifications for key features:

1) Turn on Active Directory support (optionally). Simply change the 0 to a 1 to enable. Set your LDAP/AD directory or you can comment out that line to tell Web Portal to use default AD directory. Turning on AD support will DISABLE the Groups and Users tabs within the ADMIN interface. Your report groups will now list your AD groups, and you can assign them to the reports. And of course, when your end users log in to the application, they will use their AD credentials.



2) Modify the parameter date format (optionally). Do not change this just for the fun of it, to see it displayed a different way. Change it only if the date format we are passing to the report needs to be formatted another way.



3) Modify mail settings. When you ran the installer, you entered your mail settings for sending password notifications. The installer created these settings in web.config. If you need to change these settings later, you can change them here. Note, THESE mail settings are ONLY for sending password resets. It is NOT the mail settings for sending report output to user (that is done within the Report Runner Batch engine and you configure the mail server there).



---

OTHER NOTEWORTHY OPTIONAL WEB.CONFIG SETTINGS:

Note: These settings are normally NOT modified or changed from their default settings. We are simply explaining how to use them if you choose to.

1) ShowPasswordInBrowseList - By default, password settings are hidden in the ADMIN interface. Use this setting to show them.

2) InstanceNamingFormat - Use this setting to set the default instance naming format

3) UseWPLoginForDatabaseLogin - By default, report login information for database access is stored in the Web Portal (Batch) XML template. Enable this setting to use the same Web Portal login ID and password for report database access, too.

4) WebPortalURL - If you plan on using the command line feature of Web Portal (calling URLs to run reports without user interaction), there is a key called "webportalurl" that you need to set. We do not automatically set it, because you may want to use a different URL for external display. When you generate a command line to call a report, this URL will be used.

---

STARTING AND VERIFYING YOUR WEB PORTAL INSTALLATION:

1) Start your ADMIN interface:

http://localhost/ReportRunnerWebPortal/JNAdmin/ReportList.aspx

or

http://YourServerURL/YourWebPortalDirectory/JNAdmin/ReportList.aspx



Note: Sample ADMIN interface from our Web Portal demo server can be seen here -- http://admin.reportrunner.com

2) Start your END USER interface:

http://localhost/ReportRunnerWebPortal/Login.aspx

or

http://YourServerURL/YourWebPortalDirectory/login.aspx



Note: Sample END USER interface from our Web Portal demo server can be seen here -- http://reports.reportrunner.com

 

Does your Web Portal load (look) correct?


Does it look like this? If the portal looks wrong/broken (like below)...

 

...do the following:

Edit the web.config (using Notepad) in the main Web Portal directory (C:\inetpub\wwwroot\ReportRunnerWebPortal) and DELETE this line:
 

<mimeMap fileExtension=".less" mimeType="text/css" />


 

 

NOTE: On some older servers like 2012 and previous, this mimeMap setting is normally needed and should not be deleted.

Refresh the previously "broken" Web Portal URLs and they should now display correctly. 

3. If using the default installation, you can go to ADMIN interface. We're now going to configure a quick test report and make sure everything is "hooked up" correctly.

 

Add Report (click New Report), drop-down template should show TEST.XML; choose this template, name the new report "TEST", set/select group permissions (to Demo and Everyone) and SAVE it. This TEST.XML uses our batch message Crystal RPT report which will simply run a test report and allow you to enter a parameter.

 

Select the TEST.XML template


 

Name the new report "TEST"


 

Select the Groups (we are setting Group permissions)

 

Save the new "TEST" report



Did the report save correctly and go back to the main "Reports" menu tab?

Note, if you SAVE and it does nothing (it should save and exit), then you did not set FULL PERMISSIONS for all users on the Web Portal folder correctly.

 

Go BACK to the permissions step and set FULL permissions for the Web Portal directory for ALL users.

 



4. Congrats! You've created your first Web Portal report. Now let's test it...

Go to END USER interface, log in with demo/demo, run TEST report (whatever you named it). It should have one parameter, enter whatever you want (like "Hello World!"), run it to Screen. It should show a PDF (via popping up to a new tab) with whatever you typed. If you don't see PDF, make sure pop-ups are allowed for localhost.

Remember: You will not able to email a report from Web Portal until you configure the email settings within Report Runner Batch. Once email tests correctly there, email should work just fine from Web Portal.

Login with demo/demo

 

Select TEST report

 

Enter/answer the parameter "Hello World!" (or anything else you want to type)

 

Click Submit to run the report

 

Web Portal now makes a copy of the TEST.XML template, edits it with your parameter value, sets a unique output file name, and "throws" it into the Input Queue for Event Server to see it and run it

 

Did you get an error? If so, find the log file in the Report Runner Batch log file directory or open the Report Runner Event Server monitor (right-click in system tray on Event Server icon -- this is the Event Server Controller). When monitor opens, you'll see a RED line in the Error queue. You can double-click it to open the log file that goes with it.

 

Is it just spinning and spinning for minutes without completing? If so, then the Report Runner Event Server service has not been started. You can either start it from the Event Server Controller or go directly to your Windows Services interface and start it there.

 

If it worked, then you should see a tab open up and show the PDF file!

 

Back to the Web Portal tab, you should see a "Report Complete" message. You can click Return to go back to your report list.

 

If you see the "Report Complete" message, but the report did not open up, then your browser is blocking pop-ups. Just click the "blocked pop-up" icon and select to Always Allow pop-ups (or some other similar message).





That's it! Web Portal is installed!

---

--- USER MANUAL ---

QUICK CUSTOMIZATION OF WEB PORTAL:

Customizing Web Portal is super easy. From your ADMIN interface, click on SETTINGS. You can change the upper right logo and background easily (see screenshots below). You can also easily make CSS changes to modify colors and fonts. The footer displayed on the END USER interface can be modified to show your company name and important links. This footer will show on all forms after the user logs in. Want to change text or messages displayed on the a form? You can do that by editing the data dictionary. All columns are sortable. It's easiest to sort the definitions and look for the string you want to change. Just EDIT, UPDATE, and click the orange REFRESH button to reload the dictionary into memory. Please note, in some browsers, you may need to do a Ctrl-F5 to reload cached text in browsers and/or CSS changes. Lastly, we've added a simple Widget setting to allow for implementing the left or right "floating" prompts that you can generate with various web-based helpdesk and feedback applications like Zendesk or UserVoice, or GetSatisfaction, just to name a few.




---

CONFIGURING WEB PORTAL AND SETTING UP REPORTS:

Once installed and customized, using and configuring Web Portal is really straightforward. There are two types of interfaces. The ADMIN interface and the END USER interface (start-up links given previously). Start the ADMIN interface. You have 5 tabs to choose from, which you can use to configure 99% of everything in Web Portal. We recommend configuring in the following order:

  • Configure base SETTINGS: As discussed in prior topic, you can customize the look-and-feel of the END USER interface here. You can do this at any time, but we recommend doing it first.
  • Configure base CATEGORIES: Set up names and icons for all of report categories. We've installed over 150 32x32 sized icons to use within the application. When you add a report, you will have a list of your categories to choose from to assign the report to. End users only see categories for reports they have been assigned. If you have a Management category and an end user has no Management reports assigned to them, they will not see this category. So, set up an unlimited number of categories. We've created a number of default ones for you.
  • Configure GROUPS: If you are using the Active Directory integration, their is nothing to do here (all groups would be loaded from Active Directory). Otherwise, set up your user groups here. You can be as specific as creating groups like Sales, Support, Administrative, Employees, Customers, etc... or as generic as Everyone (which we include by default). If you have already created some users or reports, you can assign these items here, too. Reports are assigned to groups, not users. Users are assigned to groups. Users can be assigned to multiple groups. Note, we have a unique feature where, if you do not want to create specific user IDs for everyone, you can give them the group ID and password, and they can simply log in as a group.
  • o Configure USERS: If you are using the Active Directory integration, their is nothing to do here (all users would be loaded from Active Directory). Otherwise, set up your user users here. A user can be anything from an in-house employee to an external customer. One of the neatest features in Web Portal is the ability to assign up to three (3) *hidden*, user-based, parameter values. Why is this neat? This allows you to use one report for everyone, and everyone sees something different because of these values. The end user does not see these hidden values, but you, the administrator, can assign them as "answers" to parameter prompts (and hide the parameter prompts). For example, you may have a sales report that has a salesman ID parameter. You could set up the report to use parameter value one. The salesmen would never see the prompt; it would simply filter the data in the report based on their hidden user value. You could do the same with customer invoices. You could post an invoice report, assign to all customers, and have a parameter that filters the report based on a hidden customer ID. The customers never see this parameter. They simply enter their invoice number and it allows them to see it, because the record selection also filters based on this hidden customer value. The "wrong" customer would never see another customers invoice, because they would have different user values assigned. Note, you could always make the user ID the same as the customers actual account ID (or for salesmen, their actual salesman ID), because one other option for parameters is to assign the "login ID" to the parameter value, too.
  • Configure REPORTS: Lastly, you create your reports. You have two types of Web Portal reports (really three)... 1) Live 2) Static Crystal Reports (pre-run reports using Report Runner Batch) 3) Static URLs (http-based links to pages and/or documents). We're going to discuss live Crystal Reports-based reports first.

    Web Portal depends on an XML "config" file to be created for every live report. These XML config files are the exact same format as a Report Runner Batch XML file with one batch job in it. Previous to 2013 of Web Portal, you had to manually create these single-job XML files using Report Runner Batch. In 2013, this is no longer necessary. While you can still do this manually in Report Runner Batch, you have two other options. One, you can place all of your RPT files that you want to create XML templates for into the INPUT directory of Event Server (this KB assumes you know what Event Server is). Event Server will AUTOMATICALLY process the RPT files (and also auto-create your static picklists from values stored in RPT files), creating one XML template per RPT file (using same name as report), and placing that new XML template into the Event Server's Web Templates directory (this is the same directory used in previous version of Web Portal). Since these XML templates are now in the Web Templates directory, when you go to add a new report, your XML templates will load and show for all of these reports. There is no limit to the number of reports you place in the INPUT queue either. You can place 10, 50, 100, or 500. It will create the web templates for each one. Alternatively, your second option is to place all of your RPT files into the Web Portal directory called "NewRPTFilesDirectory". This will allow you to (from the new report interface), browse to that directory and pick the RPT file. Once you select the RPT file, Event Server will process the RPT file on-the-fly, and create a new web template for you. Some users may prefer doing reports one-at-a-time like this so they don't have to choose from a large number of XML templates in the drop-down. Note, this automated web template creation process will assign the Global ID and Password from Report Runner Batch to be used to run Web Portal reports. If you need to configure some other ID/password, you will need to edit the XML web template manually using Report Runner Batch and configure the data connection information.

    Ok, so you've selected your web template. Next, name your reports, assign a category, configure your output options (PDF only or allow user to choose), configure usage of report instances, and configure your parameters.

    Report instances allow Web Portal to retain previously run reports. This allows users to easily access a report they ran previously. You determine how many to keep, and Web Portal does the rest. The biggest benefit of report instances is it saves report processing time on the server, because users aren't re-running the same report over-and-over. For example, a salesman might run a report every morning at 8am. Let's say it take 5 minutes to run. If he wants to look at that same data later in the say, he doesn't need to rerun the report and wait 5 minutes; he can click the previous report instance and it opens immediately.

    You have numerous options to configure parameters and picklists. You can change parameter prompting text (uses Crystal Reports prompt by default), assign a picklist, enter a default value, assign a user-based value, allow for manual values, and show/hide (display) the parameter. Most of this falls right-in-line with how you would expect the report to work. Assuming you know Crystal Reports, configuring the parameters should make sense and work as you would expect it to work.

    Picklists are text files stored in the PicklistDirectory. These picklist text files have multiple ways to be configured, and we use text files so you can configure them with a text editor like Notepad. Picklists can be static (values listed per line in text file) or dynamic (values are fetched when report is run by executing a SQL Select query). Picklists can also be cascading (choosing one value shows another limited set of values to choose from). Cascading picklists are only static at this time (you can't create cascading picklists with a SQL Select query). Cascading picklist files MUST start with the words "CascadingPicklist". All other picklists MUST start with "Picklist". The rest of the filename can be anything, but we recommend being as descriptive as possible.

    Static Picklists: We have a number of default static picklists already defined in the PicklistDirectory folder. You can manually create a picklist simply by adding values to a text file, one line at a time. If you need to show one value, but assign a different value, add the pipe symbol "|" between each value. Click here to see a sample static picklist. In this sample, Yes or No is picked by user, but 1 or 0 is assigned to the parameter.

    Cascading Picklists: Cascading picklists must be configured manually or you can create formulas in a Crystal Reports template and export values from a database to text using Report Runner Batch. Click here for an example of our cascading picklist format. The greater than sign is used to indicate a cascading value. Use the Header line to assign cascading headers/descriptions, too. In this example, users can pick a state in the US, then a region, then a city, and via the pipe symbol "|", a city code is passed instead of the city name.

    For the 2nd and 3rd types of Web Portal reports, static reports, you need to check the "Static" option. This will change the form to allow you to browse and select a static report (from the StaticReports directory) or enter a specific URL. The specific URL option makes sense to most users, but we do get the question of why the static Crystal Reports option? This allows you to pre-run long running reports (imagine large sales or accounting reports that take an hour or longer to run) using Report Runner Batch. You could refresh these static reports at whatever interval you like and any time the user selects this type of report, it opens it immediately. There iss, of course, no need to set up parameters or output options, because they are already run and saved to a specific format.

    The final thing you will do is assign the report to the groups that are allowed to access it. You can assign a report to more than one group. Users only see reports their groups have been assigned. If you have 1000 reports created, but a user group has access to 20 of them, those users see ONLY those 20 reports, not all 1000.

    Here are some examples of the "canned" picklists we include upon installation:



  • Cascading Picklists: Cascading picklists (as shown above) must be configured manually or you can create formulas in a Crystal Reports template and export values from a database to text using Report Runner Batch. Click here for an example of our cascading picklist format. The greater than sign is used to indicate a cascading value. Use the Header line to assign cascading headers/descriptions, too. In this example, users can pick a state in the US, then a region, then a city, and via the pipe symbol "|", a city code is passed instead of the city name.

    For the 2nd and 3rd types of Web Portal reports, static reports, you need to check the "Static" option. This will change the form to allow you to browse and select a static report (from the StaticReports directory) or enter a specific URL. The specific URL option makes sense to most users, but we do get the question of why the static Crystal Reports option? This allows you to pre-run long running reports (imagine large sales or accounting reports that take an hour or longer to run) using Report Runner Batch. You could refresh these static reports at whatever interval you like and any time the user selects this type of report, it opens it immediately. There iss, of course, no need to set up parameters or output options, because they are already run and saved to a specific format.

    The final thing you will do is assign the report to the groups that are allowed to access it. You can assign a report to more than one group. Users only see reports their groups have been assigned. If you have 1000 reports created, but a user group has access to 20 of them, those users see ONLY those 20 reports, not all 1000.

    Auto-Created Picklists: When your RPT is processed via Event Server, static parameter values stored in your RPT file will be extracted to auto-create static picklist files for you. These auto-created picklists are stored in your Event Server data folder (where your WebTemplates directory is located --- installation step #12) in a folder called AutoPicklists. The picklists are named based on the report name and the parameter name, so you know what it should be assigned to. You will need to MOVE any auto-created picklists from the Event Server AutoPicklists folder to the PicklistDirectory folder in Web Portal. We do not automatically store all picklists in the PicklistDirectory folder, because a number of reports (can) utilize the same picklist, and it's better to use one picklist for maintenance purposes. If you need to add a code to a picklist, and the picklist is used by 100 reports, it's much easier to add a code to one file than 100 files. Make sense?



    Dynamic SQL-based Picklists: As of Web Portal 2013.5g, dynamic, SQL-based picklists are now available. It's as simple as configuring a connection string and writing a select statement. The SQL-based picklists can be a direct connection to SQL Server or, for any other datasource type, be based on a DSN. Click here for an example of a SQL Server connection. Click here for an example of a DSN connection. Note, the format of the file must be as shown. The *SQL* at the top is a keyword to tell Web Portal this is a SQL-based picklist. The number 1 you see on the second line can be a 1 or a 2. 1 indicates one value is being returned. 2 indicates two values are being returned. If two values are returned, the 1st value is shown to use in picklist, and based on users choice, the 2nd value is assigned to the parameter.




---

FINAL QUESTIONS:

Q: How many users can access Web Portal?
A: It's unlimited. You can set up an unlimited number of named users. They can all access the Web Portal at once. We do not limit users in any way.

Q: How many users can be logged in at one time running reports?
A: It's unlimited. Live reports will run in the order the reports were submitted. Event Server processes report requests in the background. You can configure Event Server to run up to twenty (20) reports at a time. How many you set this to depends completely on your server power and configuration. End users will never get a messages stating "too many report requests" or "licenses exceeded". We simply queue up the reports and run them one-by-one.

Q: Are static-type report requests or instances "queued up" in the order received?
A: No, they are processed/opened immediately. Event Server does not need to do anything with these types of requests. They are already processed.

Q: The reports seem to be running, but they are not displaying afterwards. It shows "Report Complete". What's the problem?
A: You have pop-ups blocked. You must instruct any users to enable pop-ups in their browser. Please note, many (all?) browsers have a pop-up blocker AND many devices have additional pop-up blocking software. If the report is not displaying after completing, it is your pop-up blocker.

Q: Reports will not finish (the gears just keep turning) or I get an error message. How can I fix this?
A: https://help.reportrunner.com/knowledgebase/article/how-to-debug-web-portal-report-runner-errors-and-issues

Q: Where's the User Manual? I can't figure how to use Web Portal.
A: THIS DOCUMENT IS THE MANUAL. Scroll back up a bit to the previous sections. Those sections really do explain all you need to know to get started and do most anything with Web Portal.

 

---  

 

That's it! Please let us know if you have any additional questions. We are always here to help!

 


Share via

Related Articles

© Report Runner Support