"The Web Intelligence Server is down or unreachable"

[Former Member]

Hello All,

We have sporadic issues where everyone that is using Webi will receive the error “The Web Intelligence Server is down or unreachable” and it promptly kicks them out and they have to log back in again.

We are running:

SAP BusinessObjects BI Platform 4.1 Support Pack 3 – (Processing tier is running on a physical server w/ Windows 2008 R2 – Fully Patched)

Webi is running on VM w/ 2012 R2 Fully Patched

DI is running on aVM w/ 2012 R2 Fully Patched

HTML only for the web client x 100 users

Rich Client x 6 power users

Our end users are in Minneapolis while the Servers/iSeries/Netezza are all in Charlotte.

We have a 20/20mb dedicated line running less than 50% usage on average directly to our Corp Office

Ping times to the processing tier server average around 120ms. There is near zero packet loss.

We use Data Integrator to move the data from Oracle JD Edwards One World 9.1 to our IBM Netezza Appliance.

Any ideas? Let me know if you need more information.

[Former Member]

Thank you both for your replies. We will update to the latest patch. We've also turned on tracing (wasn't on). No scheduled reports are being used, but we do have some larger reports.

I'm not sure what our architect meant by processing is happening on a physical server and webi is on a VM. Asking for clarification.

[denis_konovalov]

you'll need to check to wee if your webi processing server is crashing (most likely) or not when the users get that error (see if server pid changes) maybe enable trace on it and see if it shows why it goes down.
You can also use auditing to see what has been running during the crash - maybe its a badly designed or a huge report that's crashing it.

Or this might be a simple sizing issue. You have 106 users, but how many of them are concurrent and how many schedules and sizes of reports are you dealing with ?

Also, what do you mean processing is on real hardware, but webi is on VM ?
How do you define your tiers ?

[kumar_kesireddy]

What patch are you on? Looks like this has been fixed on patch 8 according to 2031139.