cancel
Showing results for 
Search instead for 
Did you mean: 

WebIntelligenceProcessingServer stopped unexpectedly

Former Member
0 Kudos

Hi,

We are noticing WebIntelligenceProcessing Server restart automatically and throws the following error in the Windows Event Viewer

[Node Name: <Server_Name>]

[User Name: SYSTEM]

Server Intelligence Agent: server <Server_Name>.WebIntelligenceProcessingServer3 stopped unexpectedly.

The webiProcessingServeru2019s Timeout Before Recycling is set to 1200 and Maximum Documents Before Recycling is set to 1000.

We also get a Transport Error in the Event Viewer which is more often (multiple times a day).

Transport error: Invalid object reference.

Environment Information:

BOE R3.1 SP2

OS: Windows Server 2003 (64bit)

DB: Oracle 11g

Thanks,

Srihari.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hello, Srihari

I'm facing the same problem. How did you solve it? Did Dell's suggestion work?

Former Member
0 Kudos

I've heard there are some memory leaks in the WebI servers in 3.1 that cause this kind of issue - I've seen it on a regular basis since upgrading to 3.1, but I'm not sure whether that's the reason for it or not. Here's what we've done that has alleviated some of the problems:

1. Add an additional WebI Processing Server to the CMS. This provides fail-over in case one goes down.

2. Go into the CMC and check the servers at least once a day (probably more often for you since you're seeing multiple failures a day). If any of them are stopped, start them.

3. If the servers won't start, there is a way to take care of it without rebooting the report server, but you have to have access to the server (I use Remote Desktop.)

a. Open the Task Manager on the server.

b. Go to the "Processes" tab and sort on Image Name. If the "PID" is not showing, go to the View Menu and add it to the selected columns.

c. Find the exe name for the server you're trying to start. WebI Processing I believe is WIReportServer.exe.

d. For each instance of the Image Name, check the PID against what's showing in the PID column of the server list in the CMC. If you find one that is not listed, stop it.

e. You should now be able to start the server in the CMC.

4. Reboot the server at least once a week. We have ours on a scheduled reboot on Saturday evenings when there are no reports scheduled.

I hope this helps!

-Dell