top of page
Writer's pictureChris Hickman

Repairing a Corrupted BI Services Installation

After working with a client on a dashboarding project in SAP BusinessObjects 4, we encountered an error with SAP BusinessObjects Web Intelligence when we were trying to connect to BI Services.  We could neither connect nor could we publish.  After some investigation, it seems that we needed to redeploy dswsbobje.  Here’s a bit of information that we gathered and the resolution that we discovered.

Symptoms:

Connecting to BI services in Webi in launch pad or rich client will throw random XML parser errors such as XML reader error: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[1089,5]Message: XML document structures must restart and end within the same entity.

You cannot see existing web services nor publish new web services.

Opening the URL http://<servername:port>/dswsbobje/services/Session?wsdl goes into an infinite loop and will crash your browser.  Ensure that wsdl is lowercase.

Cause:

From time to time, BI Service can become corrupt and cause the symptoms that are shown above.

Resolution:

Redeploy the dswsbobje application. To redeploy, follow these steps on the BI4 server:

  1. Stop Tomcat and the SIA using the CCM

  2. Open a command prompt

  3. Go to the directory: C:\Program Files (x86)\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\wdeploy

  4. Run the command: wdeploy tomcat6 -DAPP=dswsbobje deploy

  5. Look for Build Successful at the bottom of the resulting output.  If you do not see Build Successful, rerun the wdeploy command

  6. Start Tomcat and the SIA using the CCM

Go to the URL http:// <servername:port>/dswsbobje/services/Session?wsdl.  The browser should not crash.

Try to connect to BI Services in Webi (launch pad or rich client).  The issue should be resolved.

19 views0 comments

Recent Posts

See All

Comments


bottom of page