Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML About integrating PPM/Mariner and SBM
About integrating PPM/Mariner and SBM
CMS-XML After upgrading PPM, the integration with SBM no longer works
After upgrading PPM, the integration with SBM no longer works
CMS-XML Mariner integration with SBM fails due to authentication error
Mariner integration with SBM fails due to authentication error
CMS-XML When I go to the SBM login screen there are no images, the background is white and the page looks way out of alignment.
When I go to the SBM login screen there are no images, the background is white and the page looks way out of alignment.
CMS-XML Mariner web services fault can't be caught in Business Mashups
Mariner web services fault can't be caught in Business Mashups
CMS-XML Would like to be able to update existing Mashup Tool Event Mapping
The Mariner release number is being passed to SBM as the "Product Version". Therefore, with each release of Mariner, the version number changes and the Mashup Tool Event Map must be recreated. "Product Version" is not really a good name for this field.
CMS-XML "Object reference not set to an instance of an object" when navigating in Mariner
After successfully logging in to Mariner, error messages like the following appear when trying to browse the Mariner interface. These errors occur when Mariner and Serena Business Mashups are installed on the same IIS web server. Mariner 2008 and SBM on the same IIS web server
CMS-XML On Update notifications shouldn't get sent for changes not in Attribute History
In other words if the fact that an attribute changed wasn't deemed important enough to show in the attribute history tab then an on update notification shouldn't fire either. Another side effect of this issue is that when the nightly post job runs it causes all the investments in the system to get an update which in turns causes notifications to be sent for on update and each one firing to the sbm server. During this time the scheduler service is using around 4gb of ram and throwing out of memory errors.
CMS-XML Mariner 2008 R3.04 Patch Release
DEF167105 ‘onbeforesave’ javascript event is not firing DEF167238 Mariner integration with SBM fails due to authentication error DEF167633 Rich text fields should keep line breaks on custom reports
CMS-XML Mariner 2008 R3.06 Patch Release
DEF175141 Upgrading Mariner requires updating existing SBM Mashup event definitions. In previous versions, Mariner was sending the Mariner version number to the SBM Mashup. The SMB Mashup was expecting a configuration version number rather than a product version number.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs