Introduction
...
In this article we have described the basic understanding and trouble shooting steps for Web Report module , those will help to understand the cause of the problem & its basic understanding to prevent such problem in future. Also it will help to avoid the unnecessary delay of tickets forwarding.
Check List of various common problems and its quick resolution guide are listed in table format below.
Issue Type / Problem Type | What to check / Basic actions | How to check ( Quick Guide ) | Remarks |
Report is Not opening | Run Report SYNC |
| |
Entries in Ginapps.config for Report configuration | Ensure the following standard entries are present in Ginapps.config file.
IMPORTANT: If different URL is mentioned as ReportUI and ReportAPI, DO NOT change that. Check accessing those URL to verify 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 appropriately
| ||
Verify ReportUI application | Access ReportUI URL directly entering in browser. The format of ReportAPI URL is mentioned, change the server name or IP appropriately
| ||
Test Admin Configuration: Data Sources |
| ||
Report path test connection under Server tab. | Server tab > General > Main Settings > We can find the Report Path line > Test the Report path. | ||
GinesysWebReprts.xml file is present or not |
| ||
Physical Path , AppPool , Standard Folder Security permission of ReportAPI folder. | 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 :
| ||
Physical Path , AppPool , Standard Folder Security permission of ReportUI folder. | Verify the physical path of ReportUI folder and its AppPool from IIS Manager. Verify the folder Security of ReportUI folder. Standard set of security should be like :
| ||
Report SYNC is not happening | GinesysWebReprts.xml file is present or not. |
| |
Folder Security permission of ReportUI & ReportAPI. | Verify the standard Folder security permission.
| ||
Report Scheduler service is working | GinesysReportScheduler Service state. | RUN > Services.msc > Find the Report scheduler service > Check is it stopped or not installed. | If GinesysReportScheduler service is not installed then you need to install it. Please follow the below reference for Report Service installation. |
eWebReportsScheduler.exe file | Find the below file is present or not from the following path.
| ||
eWebReportsScheduler.xml file | Find the below file is present or not from the following path.
| ||
Schedule Remoting Host test connection ? | Server > General > Main Settings > Scheduler Settings > Find Schedule Remoting host > test the connection. | ||
Enable Report Scheduling Option is True | Server > General > Main Settings > Scheduler Settings > Find Enable Report scheduling > It should be set as True. | ||
Open CMD with Admin privilege and run the below command. Type Powershell ( press Enter ) Type below command.
| |||
Report Scheduler Mail is not happening / Schedule Report goes to Abend State. | GinesysReportScheduler Service state | RUN > Services.msc > Find the Report scheduler service > Check is it stopped or not installed. | |
Test mail credentials in SMTP mailer from Launchpad. | Open Launchpad > SMTP Mailer > Click on Stop Service > Click Edit button > Put your credentials & test the smtp details. ( Do not save anything on this window ) . | ||
eWebReportsScheduler.exe file | Find the below file is present or not from the following path.
| ||
Check mail settings in eWebReportsScheduler.xml file | Find the below file & check the settings from the following path.
| ||
Check SSL settings in eWebReportsScheduler.xml file set as true or false. | The common known ports are used in mail configuration i.e. 587,465,25,995 etc. SSL ports : 587 , 465 No Non SSL ports : 25 If found SSL ports are attached associated under SMTP server name. SSL tag should be set as true. | NOTE : In Exceptional cases, private mail domain might be configured with 587 port with Non SSL configuration. So ,here we have to set false under SSL tag after testing with settings. It will be act like No Non SSL 25 port general SMTP port. | |
Failed to attach mail attachment for Report Scheduler. Then we need to eWebReportsScheduler.exe.config file settings under Runtime tag. | Following tag needs to add under Runtime tag.from the the following path. <loadFromRemoteSources enabled="true"/> <Ginesys Installation_drive> | ||
Mail got Report Scheduler Abended under Report Scheduler Page. | Open CMD with Admin privilege and run the below command. Type Powershell ( press Enter ) Type below command.
|
This Article is applicable for all those cases where No Web report is running or Web Report module is not opening or Some specific report menu is not running.
Area of Troubleshooting :
Ginesys Report server or Ginesys Report Folder path identify or Location identify.
Ginapps config file checking.
Standard folder permission checking.
Report applications checking using IIS Manager.
Log searching for Advance troubleshooting.
- Basic Task
Basic steps to be performed at preliminary stage when any issue occurs ,
1.Run SYNC first from Repository tab.
2.Then reset IIS server in Ginesys HO server / Report Server system using IISRESET option in Command Prompt or CMD.
- Basic Troubleshooting steps
1.Check the Server tab settings of Ginesys Report Module :
a. Test the connection of Data source (Ginesys).
b. Check report path in Main Setting under Server tab.
c. Check the Remoting scheduler host path setting. ( protocol : http or tcp , server hostname or IP , Port : 2001 ).
d. Check the Report Scheduler service is running or not.
e. Check Ginapps.config file from <\GSL\GINESYS12\Shared> location and find the below rows.
<add key="ReportURI" value="/GinesysReportUI/" />
<add key="CustomPort" value="" />
2.Check the basic configuration from IIS manager :
a.Check standard Permission is enabled or not in each report application ( Report UI , Report API ):
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)
b. Check the Report Applications ( Report UI , Report API ) path :
Example: Physical path of Report UI folder and Path of GinesysReportUI set in IIS server is same or not.
Ex : C : \ GSL\GINESYS12\GinesysReport\ReportUI = below picture.
...
c. Check the Application Pool:
a.Check Report Applications GinesysReportUI, GinesysReportAPI , which must be run from GinesysReportAppPool.
d. Check the Application Pool identity :
a. Click on Application Pool at Left hand side , there must be a list view of AppPool at Right hand side , check GinesysReportAppPool is set to Application Pool Identity or not.
e. Check the Binding settings of default Web Site :
a. Click on Default Web Site , at the right hand side there is an option Binding. Click on that observe the binding details if any.
3. Procedure of advance Error findings :
In such cases after performing if the above basic checks fails and still problem exists, then you have to find out actual error from various logs.
1.log path for General Web Report related error : C : \ GSL\GINESYS12\WebUI\logs\log.txt
2.For Report scheduling related error : C : \ GSL\GINESYS12\GinesysReport\Report Scheduler\eWebReportScheduler.txt ( as per latest date & time)
| Tip |
|---|
In this section we will briefly describe that how to use IIS Manager to check various web report related parameters : |
First to Open IIS Manager :
Go to RUN and type inetmgr or Go to Start Button type IIS server Manager. Find & enter into it.
At the Left side you will find IIS server name , below that you will see the Application Pool , just a little below you will find the Default Web Site along with its web applications or web sites. Like as below.
Star Page
Server Name (Domain\username)
Application Pools
Sites
Default Web Site
GINESYSReportUI
GINESYSReportAPI
- To check Application Pool & its Identity
Just click on Application Pool , at the middle of the window you will see all Application Pool & its identity. For Web report Application Pool is GinesysReportAppPool and its Identity is ApplicationPoolIdentity .
- To check Default Web Site along with its Binding
Click on Default Web Site , at left hand side , you will see the Binding Option , click on that one small window will open and you can see all binding & Certificate details if any exists.
- To check Basic settings of any Web Report Application ( Ex. GinesysReportUI , GinesysReportAPI )
Click on any application , at left hand side you will find the Basic Settings option & click on it. Post that you can see the Alias Name , Application pool , Physical Path of that application.
- To check Permission of any Application ( Ex. GinesysReportUI , GinesysReportAPI ) ,
Click on the application and at the left hand side you will see Edit Permission option. Then click on it and you can find the Security tab. On that tab you can check & verify the Standard permission settings which is mentioned below section.
Check standard Permission is enabled or not in each report application ( Report UI , Report API ):
SYSTEM ( Full Permission)
Creator Owner (Special Permission)
Administrators (Full permission)
Users (Read& Execute , List of Folders , Read , Special Permission)
IIS_IUSRS (Full Permission)
For more details regarding Web Report Installation including its configuration you can go through the below link : Ginesys Reports Installation Guide
...