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 Users unable to get into Work Center due errors "Unable to validate user" and "Error: Not Found" and "Error static Top : Not Found"
Start ONLY Serena Common JBoss. Wait until you are able to open the SBM Application Repository login page (URL: http://MyServer: 8085/mashupmgr / ) Start IIS.
CMS-XML Error on deploy: The endpoint reference (EPR) for the Operation not found is /mashupmgr/services/sbmimportcallback72 and the WSA Action = null or Invoking import callback failed: End of file or no input: The handle is invalid.
callback.web.context=http://Server Name: 8085/mashupmgr /
CMS-XML Importing Release Control solution gives "Failed to extract the solution. You do not have permission to delete the obsolete snapshot"
Log into the Application Repository ( http://server: 8085/mashupmgr ). Switch to the Privileges view. Select your user, and verify that you have all privileges, including Delete Process App, Delete App/Orch, and Break Lock.
CMS-XML RLM 6.0.1: "All Packages" view does not show any Release Packages
When promoting the process apps, the Release Train process app must be promoted before the Release Package process app. To fix the view, you must re-promote the Release Package process app. Log into the Repository ( http://server: 8085/mashupmgr / ) Go under Snapshots, and choose Release Package.
CMS-XML Deploys are failing with result=12 in the import log and errors in the Event Viewer C:/Program Files/Serena/SBM/Application Engine/bin/design/a5cc553c-f6f4-4fb6-9316-e5acfbf319f0/c2ee0d3e-c3e8-4349-bbc8-daa15913ebd9.xml contains an incorrect path.
07/10/2014 12:52:57: Invoking import callback: uuid=dd272508-f071-4eef-949c-d88bfd4058d1, endpoint=http://sbmenginedev.testweb.bp.com: 8085/mashupmgr /services/sbmimportcallback72, result=12 07/10/2014 12:52:57: Invoking import callback failed: unknown and in the Windows Event Log:
CMS-XML How to rename or move a server hosting SBM
Log into the SBM Application Repository (by default, http://serverName: 8085/mashupmgr ). On the Environments screen, open the Default Environment (for example).
CMS-XML Deploys are timing out, Invoking import callback, result=12
06/29/2009 11:05:26: Invoking import callback: uuid=ec09c2d9-84e3-4be6-a701-6c59b9c8cfc8, endpoint=http://wlm1w810: 8085/mashupmgr /services/aeimportcallback71, result=12 06/29/2009 11:05:26: Invoking import callback failed: unknown.
CMS-XML New Endpoints Created After Deploying Process Apps
and click Publish Open SBM Application Administrator (enter http://localhost: 8085/mashupmgr / in a browser).
CMS-XML Deploy / promote gets stuck on "waiting" status
Edit the file "Program Files\Serena\SBM\Common\jboss405\server\default\deploy\mashupmgr.war\WEB-INF\mashupmgr.cfg" on the Application Engine server to which you are trying to deploy. Uncomment out the "callback.web.context" section, and put in the Repository ( Mashup Manager ) URL ( i.e. http://server: 8085/mashupmgr ). Restart the Serena Common JBoss service.
CMS-XML Deploying a process app from Composer gives error "Authentication Failed: Unable to contact Authentication Service"
Log into the Application Repository ( http://servername: 8085/mashupmgr ) Under Environment, click on the environment to which you are trying to deploy. Go to the Endpoints tab.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs