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 Promote error if distribution report has values selected for "Show only Column Field Values" you may get an error containing ".... element 'LiteralValue' "
If you have a custom distribution report with "Show only Column Field Values" selected then when you try to promote you will get an error similar to one of the below: Parser Error at file C:/Program Files/Serena/SBM/Application Engine/mst49684/teamtrack/f618284c-5d37-4a1b-8ae5-2c843312f56f/instance.xml, line 1999, char 58 Message: no declaration found for element ' LiteralValue '
CMS-XML ZMF Connector gives error "Invalid element" or "Content is not allowed in prolog" or "Unexpected subelement hostAddress"
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source) ~[na:1.6.0_12] 04-04@20:27:21 [http-8080-2] ERROR [CheckConnectionController.java:243] [] : org.xml.sax.SAXException: Invalid element in com.serena.zmf.webservices.client.internal.DeveloperEnvironmentAdmin.GetApplParmsResultsResult - enableDisplayOrderLibtype
CMS-XML SBM 10.x database upgrade to SBM 11.x: ZMFPackageServices.wsdl gives error "s4s-att-not-allowed: Attribute 'defaut' cannot appear in element 'element' "
SBM 10.x database upgrade to SBM 11.x: ZMFPackageServices.wsdl gives error "s4s-att-not- allowed : Attribute 'defaut' cannot appear in element ' element ' "
CMS-XML Composer: Load attempt failed for design element. You do not have permission to perform the requested operation.
Composer: Load attempt failed for design element . You do not have permission to perform the requested operation.
CMS-XML Array index cannot have an external element reference error when using ForEach in an Orchestration.
Composer does not allow to go through internal array using ForEach step due to "Array index cannot have an external element reference" error.
CMS-XML After upgrade to 11.4 opening a labeled version of a process app throws errors: Attempt to resolve label ... failed. ... The design element could not be retrieved from the Repository.
The design element could not be retrieved from the Repository. Please ensure that you have permission to view the process app and application/orchestration and that it still contains the Visual Styles. PartDoesNotExistException: Design element does not exist
CMS-XML In SBM 11.1 if a user doesn't have permission to see any fields in a privilege section the Expander control will still show on a custom form.
return Replace with this one, which will check against a duplicate element with all scripts removed (leaving the original untouched): // remove orphan refresh functions before checking text contents
CMS-XML PDS#309S A matching name element was not found in this copybook member
PDS#309S A matching name element was not found in this copybook member
CMS-XML TT661 The Web service import function is not expanding elements with a reference attribute.
TT661 The Web service import function is not expanding elements with a reference attribute.
CMS-XML Transistions are not correctly updated in Mashup Composer if element is deleted
Having deleted an element from a mashup, you may get an error like the following: WARN -- Import: Invalid Data 'e89d46ae-060e-41ab-b9b5-d9c4041c493d' in node 'SelectionID'. Context: Object type 'Workflow', name '<Workflow Name>', UUID 'fb8527ee-aaf4-4e9b-b9df-cb064cc2a731'
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs