Server Version: XIR3
It is quite often WebIntelligence Processing Server crashed for unknown reasons.
If the BO application is setup in Windows server, the error is logged in Event Viewer. For example, you may find below error message.
It is quite often WebIntelligence Processing Server crashed for unknown reasons.
If the BO application is setup in Windows server, the error is logged in Event Viewer. For example, you may find below error message.
The server would restart to resume operation automatically. However, any process during the down time may be lost. For instance, the following problems were found in my past experience.
- Failed to run scheduled WEBI reports.
- Failed to send scheduled WEBI reports to clients.
- Publication generated reports with incorrect figures. However, reports were compressed into zip file and sent to clients.
Here are several suggestions (http://scn.sap.com/thread/1744967) to minimize the impact.
Add additional WEBI Processing Server(s) to CMC
It is allowed to setup multiple WEBI processing servers. If one server goes down, the system choose select other available servers for operations. This provides fail over in case one instance goes down. The maximum number of WEBI processing servers allowed depends on CPU and server memory.
One WEBI processing server occupies 1 CPU core. That means if there are 16 CPU cores in server, 16 processing servers are allowed. The maximum memory for each processing server is 2 GB as it is a 32-bit application. For example, server with 16 GB memory allows at most 8 WEBI processing servers.
Health Checking on servers periodically
Login CMC and check server status once a day. Restart any server if they are stopped. During start up, the servers may not be able to start. There is a way to take care of it without rebooting the report server.
Reboot the Windows server once a week
Create scheduled task to reboot on weekend when there are no reports scheduled. Server reboot usually solve lots of issues due to bugs in BO applications.
Applying actions mentioned above reduce server downtime and hence provide higher availability.
Add additional WEBI Processing Server(s) to CMC
It is allowed to setup multiple WEBI processing servers. If one server goes down, the system choose select other available servers for operations. This provides fail over in case one instance goes down. The maximum number of WEBI processing servers allowed depends on CPU and server memory.
One WEBI processing server occupies 1 CPU core. That means if there are 16 CPU cores in server, 16 processing servers are allowed. The maximum memory for each processing server is 2 GB as it is a 32-bit application. For example, server with 16 GB memory allows at most 8 WEBI processing servers.
Health Checking on servers periodically
Login CMC and check server status once a day. Restart any server if they are stopped. During start up, the servers may not be able to start. There is a way to take care of it without rebooting the report server.
- Access to BO server.
- Open the Task Manager on the server.
- Go to the "Processes" tab and sort on Image Name.
- Find the exe name "WIReportServer.exe" for the server you're trying to start.
- For each instance, check the PID against what's showing in the PID column of the server list in the CMC. If the "PID" is not showing on the Task Manager, go to the View Menu and add it to the selected columns.
- If you find one that is not listed, stop it.
- Start the server in the CMC.
Reboot the Windows server once a week
Create scheduled task to reboot on weekend when there are no reports scheduled. Server reboot usually solve lots of issues due to bugs in BO applications.
Applying actions mentioned above reduce server downtime and hence provide higher availability.