Page Comparison

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.

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.

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.

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.

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.

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

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

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.

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.

Check status of service GinesysReportScheduler, should be in running.

Go to Services.msc
Find the service GinesysReportScheduler service.
Ensure service is running

If GinesysReportScheduler service is not found in service list, then you need to install it. Please refer Report Scheduler installation section in the Report installation guide.

Ginesys Reports Installation Guide

“Error occurred The service failed to start within 30 seconds.” - This message may appear while installing Report Scheduler service using InstallReportSchedulerSerrvice

Solution:
Unblock the scheduler executable \GinesysReport\ReportScheduler\eWebReportsScheduler.exe. See, check 4 below.

If service is found in stopped state, try to start the service. Unblock the scheduler executable \GinesysReport\ReportScheduler\eWebReportsScheduler.exe. See, check 4 below. If still service doesn’t start, note the error message appeared for further troubleshooting.

Check presence of eWebReportsScheduler.exe file

Find the file in the following location.

\GinesysReport\ReportScheduler\eWebReportsScheduler.exe

If missing, copy the file from Report kit.

Check presence of eWebReportsScheduler.xml file

Find the file in the following location.

\GinesysReport\ReportScheduler\eWebReportsScheduler.xml

If the XML is not present in the expected name, then

• Look for named as eWebReportsScheduler<Kit Version>.xml.

• Rename the file to eWebReportsScheduler.xml.

NOTE: Since the Ginesys Report file set is separately downloaded, Windows Smart Screen Filter marks most of the files as BLOCKED to execute.

• Go to file property of Report Scheduler executable file, GinesysReport\ReportScheduler\eWebReportsScheduler.exe.

• Observe, in the General tab at lower side, is there a check box or button to UNBLOCK.

• If the button or check box is found, then that means the files are in blocked state.

• Open CMD with Admin privilege and run the below command.

• Type powershell ( press Enter )

• Type following command. Mention the correct drive letter and verifypath verify path of Ginesys Report before execution.

• dir <Drive><Drive Letter>:\GSL\GINESYS12\GinesysReport\ -Recurse | Unblock -File

Test connection of Schedule Remoting Host

Go to Ginesys Web > Report > Server > General (left side menu) > Scheduler Settings (double click)
Find Schedule Remoting Host
Test the connection using the lightning Icon at the end of the URL field.

If find the field blank, mention following.
http://<Report Server IP>:2001 or tcp://<Report Server IP>:2001
Alter the protocol between tcp and http if connection is not successful.

Enable Report Scheduling Option is True

Server > General > Main Settings > Scheduler Settings > Find Enable Report scheduling > It should be set as True.