cancel
Showing results for 
Search instead for 
Did you mean: 

can't open webi documents

Former Member
0 Kudos

Hi,

We can't open webi documents on BO XI 3.0. We have the following error message :

com.businessobjects.wp.om.OMReportElementContainer

(Error: INF)

But we can open deski documents through infoview.

Any ideas ?

View Entire Topic
Former Member
0 Kudos

Hi Frederic,

that's funny. Our WebI on BO XI 3.0 was running fine until yesterday we were suddenly facing the exact same problem as described in your post. We were able to solve the problem by restarting our Windows server on which BO XI R3 is installed.

Hopefully, this also works for you.

Best wishes, Marc.

Former Member
0 Kudos

Same problem and a server bounce fixed it as well. Very strange

Former Member
0 Kudos

I just want to let you know the fix is the same for 3.1 - full server restart fixed it.

SadiqManji
Product and Topic Expert
Product and Topic Expert
0 Kudos

We just ran into this issue on XI 3.1 FP 1.3 and what fixed it was restarting Tomcat.

We have a distributed system, 3 servers: 1 Tomcat, 1 Management server (CMS, FRS, etc...), and 1 Webi server (job and processing).

We tried restarting all the Webi services via the CMC, restarted the SIA on the Webi box, and then even restarted the entire Windows server hosting Webi services but we were still seeing the issue. Then we stopped the Webi services on the Webi box and created a new Webi service on the management server; same issue!

Once we restarted Tomcat (via the CCM) the issue subsided. The Tomcat logs revealed a java.lang.NoClassDefFoundError: com.businessobjects.wp.om.OMReportElementContainer

Not sure what instigated this issue but hopefully it doesn't continue to occur...

Former Member
0 Kudos

We also ran into this issue last friday. Our installation is XI 3.1, no FP's on Windows 2003 server.

It was the first time we had the issue. As confirmed in previous messages, restarting Tomcat solved the issue.

What caused it? Only change we can think of we did closely before the first issue was raised: cloning of our WebIntelligenceProcessingServer. We restarted the SIA for this, not Tomcat.

No idea if this could be the cause(?)

Former Member
0 Kudos

Yes. Restarting Apache Tomcat solves the problem. The problem occurred after we installed polestar to Edge Series 3.1. The Server Intelligence Agent restarted automatically but didn't realize that we have to restart tomcat as well.