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 VM: SSO Login gives error "First Element must contain the local name, Envelope , but found html"
VM: SSO Login gives error " First Element must contain the local name , Envelope , but found html"
CMS-XML Promote or Deploy gets aborted with error in Activity log - ERROR -- An error happened during the import to Application Engine: First Element must contain the local name, Envelope , but found Fault
Promote or Deploy gets aborted with error in Activity log - ERROR -- An error happened during the import to Application Engine: First Element must contain the local name , Envelope , but found Fault
CMS-XML Cannot deploy orchestration - org.apache.axis2.AxisFault: First Element must contain the local name, Envelope , but found html - com.serena.core.runtime.CoreException: Failed to deploy event map
Under specific circumstances Process apps containing orchestrations may not deploy. In such cases the below messages are to be found in the logging infrastructure of SBM. mashupmgr.log throws the following :
CMS-XML Null Pointer Exception Error in RemoteUserFilter when turning on TRACE log level
2014-11-04 08:38:35,920 TRACE f: g: RemoteUserPrincipalFilter.getRemoteUser(114): remote user is null2014-11-04 08:38:35,952 DEBUG FS 172.25.76.148 f:877F249C8382BD184F14151119145141 g:11C2F47D6F2A1C467B14151118531051 RSTCallProxy.internalGenericInvoke(485): Axis Fault: First Element must contain the local name , Envelope , but found html
CMS-XML Values Removed from Working Data Elements when a Working Data Element with a Similar Name is Deleted
Array records, default values, and mappings are removed from a working data element and its child elements when another working data element at the same level as the containing working data element is deleted. This only happens when the two working data elements have the same name or start with the same letters.
CMS-XML Snapshot promotion failed with parser error if contain calendar or calendar feed report with reference name Custom Form
ERROR -- Parser Error at file E:/EXTuserAppl/serena/SBM/Application Engine/mst56027/teamtrack/6344862c-0a2a-44f6-a77c-518c4940fb7b/instance.xml, line 2574, char 10 Message: element 'ReferenceName' is not allowed for content model
CMS-XML Wrong part name specified accessing Web Service variable
If a WSDL contains multiple elements using the same name , even if they are in different operations, when a service operation from this WSDL is included in an orchestration workflow, the Composer deployment fails.
CMS-XML SBM not correctly creating request when WSDL contains a " simpleContent " tag in angle brackets.
</complexType> This should result in an element like <myElementName name ="myAttribute">1</myElementName>. However, the outgoing web service call when the BPEL is generated and run turns it into <myElementName name="myAttribute"><simpleContentValue>1</simpleContentValue></myElementName>.
CMS-XML SSO/CAC can use PIV Cards in addition/instead of CAC Cards. Identity Transform
.1401513392" // Expects that cnTokens[n-1] & keys contain data like "1401513392" // where n is the last element of the CN username = keys.get(cnTokens[cnTokens.length - 1]); if (username != null) { return username; } if (PIV) { // PIV Expects that first two tokens are first name & surname
CMS-XML Error when delete items from the repository in the web client 12.2.2.x Dimensions
Found a problem in version 12.2.2.X Dimensions Web client when deleted (from the repository, not from project) any element contained in a project which name contains the letter "Ñ" (or any other umlaut characters), this problem did not occur in Dimensions 2009.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs