Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

The Issue

I recently deployed SAP BusinessObjects 4.1 across several environments at a client site and ran into the following error message when saving a Web Intelligence report to the platform from the Webi Rich Client, Java Panel and HTML Panel.


The document's serialization version is too recent (Error: WIS 30915)


Scheduling a Web Intelligence report to Webi format also resulted in the above error.

The Web Intelligence processing server logs left the following trace:

**ERROR:SRM:An internal error occured while dgSerializeManagerImpl is calling ibo_idgSrmStore->PublishToCorporate [kdgSerializeManager.cpp;2533]

  • No issues were logged in the setupengine.log
  • Running a repair on the deployment didn't resolve the issue

Root Cause

Query Builder reveals what would appear to be an incorrect version number for the Web Intelligence application

SELECT SI_ID, SI_NAME, SI_FILENAME, SI_WEBI_SERIALIZATION_VERSION FROM CI_APPOBJECTS WHERE SI_KIND = 'WebIntelligence'



Solution

  • Note the dfo filename above - BusinessObjects_WebIntelligence_dfo.xml.
  • Stop all SIA nodes
  • Backup the CMS database
  • Copy the file from the <InstallDir>\SAP BusinessObjects Enterprise XI 4.0\dfo directory to <InstallDir>\SAP BusinessObjects Enterprise XI 4.0\packages directory
  • Start the SIA Node containing the CMS
  • Confirm the file has been removed from the <InstallDir>\SAP BusinessObjects Enterprise XI 4.0\packages directory
  • Confirm the update via Query Builder

  • Run earlier tests.......All working :grin:

Side Notes

I ran into this issue on an upgrade from BI4.0 SP5 FP4. I wasn't able to replicate this issue (as expected) on an environment that had a clean build i.e. no upgrade

I'll report the issue through the correct channels in due course but I felt it was best to get this information out there as I burnt several hours troubleshooting this and no doubt someone else might run into the same problem.

17 Comments
Labels in this area