Description / Remarks

Run Report SYNC

• Click on Repository tab 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’

Entries in Ginapps.config for Report configurationNote 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 servers

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

IMPORTANT: If different URL is mentioned as ReportUI ReportURI and/or ReportAPI, DO NOT proceed tochange thatthe URL immediately. Check accessing those URL for verification and consult with technical team if required.

Verify ReportAPI application

Access ReportAPI URL directly entering in browser. The format of ReportAPI URL is mentioned, change the server name or IP appropriatelyfirst (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://<Server name or IP>/GinesysReportAPI/Api.asmx

Verify ReportUI application

Access ReportUI GinesysReportUI/Admin.aspx

• 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 is mentioned, change the server name or IP appropriatelyshould 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://<Server name or IP>/GinesysReportUI/Admin.aspxGinesysReportAPI/Api.asmx

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) >

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

• 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

Report path test connection under Server tab.

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

Test the Report Path using the Icon.

GinesysWebReprts.xml file is present or not

Find the file from the below path.

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

Verify the physical path of ReportAPI folder and its AppPool from IIS Manager.

Verify the folder Security of ReportAPI folder. Standard set of security should be like :

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)

Physical path & App pool is mentiond in the Advance settings of each Web application ( ReportAPI, ReportUI etc.)

Select any Web Application > At the right side pane we see the Advance settings > Enter into it & check the physical path of folder of that web application along with app pool.

Physical Path , AppPool , Standard Folder Security set of ReportUI folder.

Verify the physical path of ReportUI folder and its AppPool from IIS Manager. See in the description column.

Right click on any folder ( ReportAPI , ReportUI etc. ) > Properties > Security tab > Check the below Set of Security.

lightning Icon at the end of the Report Path field.

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)

Physical path & App pool is mentiond in the Advance settings of each Web application ( ReportAPI, ReportUI etc.)

Select any Web Application > At the right side pane we see the Advance settings > Enter into it & check the physical path of folder of that web application along with app pool.

Add Full permission for IIS_IUSRS if found missing.

Check presence of GinesysWebReprts.xml file is present or not.

Find the file from the below path. available at following mentioned path

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

If missing, forward to technical team.

Folder Security set of ReportUI & ReportAPI.

Right click on any folder ( ReportAPI , ReportUI etc. ) > Properties > Security tab > Check the below Set of Security.

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 GinesysReportScheduler.

Go to > RUN > Services.msc >
Find the Report scheduler service > Check is it stopped or not installed. If Service is not installed , see in the description section link.service GinesysReportScheduler service.
Ensure service is running

If GinesysReportScheduler service is not installed found in service list, then you need to install it. Please follow the below reference for Report Scheduler Service installationrefer Report Scheduler installation section in the Report installation guide.

Ginesys Reports Installation Guide

If service is found in stopped state, try to start the service.

Check presence of eWebReportsScheduler.exe file is present or not

Find the file from in the below pathfollowing location.

\GinesysReport\ReportScheduler\eWebReportsScheduler.exe

If missing copy the file from Report kit.

Check presence of eWebReportsScheduler.xml file

Find the file from in the below pathfollowing location.

\GinesysReport\ReportScheduler\eWebReportsScheduler.xml

If the XML is not present in the expected name, look for named as eWebReportsScheduler<Kit Version>.xml.
Rename the file to eWebReportsScheduler.xml.

Test connection of Schedule Remoting Host

Go to Ginesys Web > Report > Server > General > Main Settings > Scheduler Settings > (left side menu) > Scheduler Settings (double click)
Find Schedule Remoting host > Test the connection.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.

eWebReportsScheduler.xml , eWebReportsScheduler.exe , eWebReportsScheduler.exe.config – this files along with all DLL files under Ginesys Report folder needs to be unblock.

Open CMD with Admin privilege and run the below command.

Type Powershell ( press Enter )

Type below command.

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

If Report Server or Report Installation folder location is different then change the mentioned path accordingly in How to check section.

GinesysReportScheduler Service state

RUN > Services.msc > Find the Report scheduler service > Check the service it stopped or not installed.

If Service is not installed , see in the description section link.

If GinesysReportScheduler service is not installed then you need to install it. Please follow the below reference for Report Scheduler Service installation.

Ginesys Reports Installation Guide

Test mail credentials in SMTP mailer from Launchpad.

Open Launchpad > SMTP Mailer > Click on Stop Service > Click on Pencil t button for editing > Put your credentials & test the smtp details. ( Do not save any details after checking on this window ) .

eWebReportsScheduler.exe file

Find the file from the below path.

\GinesysReport\ReportScheduler\eWebReportsScheduler.exe

SMTP Mail settings in eWebReportsScheduler.xml file

Find the file from the below path and verify the SMTP details.

\GinesysReport\ReportScheduler\eWebReportsScheduler.xml

SMTP SSL settings in eWebReportsScheduler.xml file.

The common known SMTP ports are used in mail configuration i.e. 587,465,25.

SSL ports : 587 , 465

Non SSL ports : 25

If found SSL ports are associated with SMTP server name. then SSL tag should be set as true accordingly.

eWebReportsScheduler.exe.config file settings under Runtime tag for mail attachment failure.

Below xml tag needs to be add under <Runtime> tag from the the following path.

<loadFromRemoteSources enabled="true"/>

path : \GinesysReport\ReportScheduler\eWebReportsScheduler.exe.config

eWebReportsScheduler.xml , eWebReportsScheduler.exe , eWebReportsScheduler.exe.config – this files along with all DLL files under Ginesys Report folder needs to be unblock.

Open CMD with Admin privilege and run the below command.

Type Powershell ( press Enter )

Type below command.

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

If Report Server or Report Installation folder location is different then change the mentioned path accordingly in How to check section.