Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

What to check / Basic actions

How to check ( Quick Guide )

Recommended action

1

Run Report SYNC

  • Go to Ginesys Web > Report > Repository and then run SYNC.

  • Restart IIS (Follow either step)

    • Open CMD ( in Run as admin privilege), type >IISRESET > Press Enter.

    • Open Windows Services (services.msc), restart the service ‘World Wide Web Publishing Service’

Note the error message appeared if any for tech team investigation.

2

Verify Report configuration entries in GinApps.config

Ensure the following standard entries are present in Ginapps.config file.
Path: \GSL\GINESYS12\Shared\Ginapps.config

Deployment 1: Ginesys and Report on same server

<add key="ReportURI" value="/GinesysReportUI/" />
<add key="CustomPort" value="" />

Deployment 2: Ginesys and Report on different serversserver

<add key="ReportURI" value="htphttp://<Report Server host IP>/GinesysReportUI/" />
<add key="ReportAPI" value="htphttp://<Report Server host IP>/GinesysReportAPI/API.asmx" />
<add key="CustomPort" value="" />

IMPORTANT: If different URL is mentioned as ReportURI and/or ReportAPI, DO NOT proceed tochange the URL immediately. Check accessing those URL for verification first (Check 4 & 5). If applications are accessible then do not change the URLs.

Correct the the URL if inappropriately mentioned.

3

Check presence of GinesysWebReprts.xml file

Find the file available at following mentioned path

\GSL\GINESYS12\GinesysReport\ReportUI\Config\GinesysWebReports.xml

If missing, forward to technical team.

4

Verify access to GinesysReportUI application
Test GinesysWebReprts.xml

  • Open the Exago Admin page accessing GinesysReportUI application directly from web browser. The URL of GinesysReportUI is as mentioned in GinApps.Config. If host name or IP is not mentioned in URL then add application server name or IP in following mentioned format.
    Ideally the Exago Admin page should be loaded.

http://<IP>/GinesysReportUI/Admin.aspx

*Note: Ensure the server IP is being used while testing the access.

  • Once Exago Admin page opens, then verify Ginesys Report configuration XML. In top left corner, under the Exago logo, load the file GinesysWebReports.xml from drop down. All configuration should be loaded.

Note the error message appeared if any for tech team investigation.

5

Verify access to GinesysReportAPI application

Access GinesysReportAPI URL directly entering in browser. The format of GinesysReportAPI URL should similar to Ginesys ReportUI URL. Replace application same and page name as mentioned in following format.
Ideally a list of supported API operations should be loaded.

http://<IP>/GinesysReportAPI/Api.asmx

*Note: Ensure the server IP is being used while testing the access.

Note the error message appeared if any for tech team investigation.

6

Test Data Source connection string under Server tab

Go to Ginesys Web > Report > Server > Data (left side menu) > Source (Expand)

  • Test database connection: Double click on GINESYS. In right side test Connection String using the lightning Icon at the end of the connection string.

  • Test Assemblies: Double click on GinesysAssemby. In right side test Connection String using the lightning Icon at the end of the connection string.

In case of unsuccessful connection, verify Oracle connection string and assembly path mentioned GinesysAssembly connection string

7

Test Report Path under Server tab

Go to Ginesys Web > Report > Server > General (left side menu) > Main Settings (double click to load)

Test the Report Path using the lightning Icon at the end of the Report Path field.

In case of unsuccessful test, verify assembly path mentioned Report Path connection string

8

Properties of Report web applications: GinesysReportUI, GinesysReportAPI

Verify Physical path and Application Pool

Open inetmgr and expand to the application list.

Right click on GinesysReportUI, select Manage Application > Advance Settings
Verify the Application Pool. Must be GinesysReportAppPool.
Verify the path mentioned for Physical Path.

Right click on GinesysReportAPI, select Manage Application > Advance Settings
Verify the Application Pool. Must be GinesysReportAppPool.
Verify the path mentioned for Physical Path.

Select the correct AppPool.
Refer Report installation guide if GinesysReportAppPool is not present in list.
Ginesys Reports Installation Guide

Mention correct path for Physical Path if found wrong.

9

Folder Security of Report directories: \GinesysReport\ReportUI, \GinesysReport\ReportAPI

Go to directory \GSL\GINESYS12\GinesysReport
Verify folder Security entries for both the directories, ReportUI and ReportAPI

Following permissions must be present in a healthy configuration.

  1. SYSTEM : Full Permission

  2. Creator Owner : Special Permission

  3. Administrators : Full permission

  4. Users : Read& Execute , List of Folders , Read , Special Permission

  5. IIS_IUSRS : Full Permission

Add Full permission for IIS_IUSRS if found missing.

...