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 Certain scripts may validate in Composer yet still fail
It is possible that Validation in Composer does not catch all errors
CMS-XML Import of MSD (blueprint) to Composer fails with Object reference not set to an instance of an object.
Import of MSD (blueprint) to Composer fails with Object reference not set to an instance of an object.
CMS-XML Composer reports 'Load attempt failed' for report without any columns
Composer reports 'Load attempt failed ' for report without any columns
CMS-XML Process App validation passes even when "Validate AppScript" fails in Composer
AppScripts are validated using the "Validate AppScript" option in the "AppScript" tab in Composer . However, even when validation fails there, validation for the Process App still passes without errors, and deployment will also complete successfully.
CMS-XML Composer: Load attempt failed for design element. You do not have permission to perform the requested operation.
You can get the following error when opening a Process App in Composer if you do not have privileges to all the applications or orchestrations. However there is a defect such that when a new application or orchestration is added that it may not be visible in the Application Repository "privileges" section.
CMS-XML Composer does not fail validation if the owner or secondary owner field is "not used" or "deleted"
Composer does not fail validation if the owner or secondary owner field is "not used" or "deleted"
CMS-XML Temp files not being deleted when deploy from Composer - error: ... Failed to delete the temp log file: ...
.... mashupmgr.Deploy -- Failed to delete the temp log file: C:\Program Files\Serena\SBM\Common\jboss405\server\default\work\jboss.web\localhost\mashupmgr\DeployHistory_ .....
CMS-XML Deployment fails for database field name of TS_ID or TS_TS_ID
Deployment fails if the database name of a field in the table editor in SBM Composer is TS_ID, or if the database name of a field in a blueprint file is TS_TS_ID.
CMS-XML "Failed to compare two elements in the array" error
In some cases with very long lists of selection values in a selection field, adding or renaming selection values in Composer will produce an error that says, " Failed to compare two elements in the array." To work around this issue until it is resolved in a future release, the "End user display order" setting can be changed to "User defined" before adding and renaming the selection value and then changed back to the desired "End user display order" option.
CMS-XML Web service call TransitionItem with TranId = 0 fails in 10.1.1.3
To handle the SOAP fault, you can place the Service step that calls the Web service inside a Scope step and catch the fault in a Catch branch of the FaultHandler. For more information about SOAP faults and how to handle them, see the orchestrations section of the Serena Mashup Composer Guide. The fault is: This transition is not currently valid
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs