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 Orchestrations failing to get called with "The requested resource (/OEGatewayService/oegs) is not available." and "Xml Parser Exception : unexpected type" errors
and " Xml Parser Exception : unexpected type" There may also be the following error in the server.log:
CMS-XML Get error "couldn't parse jbpm configuration from resource 'jbpm.cfg.xml'" in server.log file. Also orchestrations don't run and you can't deploy an application that has an orchestration in it.
In order to fix this open the following file in notepad. C:\Program Files\Serena\SBM\Common\jboss405\server\default\conf\jboss-service. xml Search for "8083"
CMS-XML After Upgrade, user is unable to login because resource ... sp-metadata.xml does not exist.
After Upgrade, user is unable to login because resource ... sp-metadata. xml does not exist.
CMS-XML Incident Management: unexpected xml document type error on Chrome
page error: Unexpected XML document type Uncaught TypeError: Cannot read property 'totalCount' of undefined /tmtrack/solutions/javascript/jquery-1.5.1.min.js:16 Resource interpreted as Document but transferred with MIME type image/gif: "http://sbmserver/tmtrack/images/jsblank.gif"
CMS-XML The XML page cannot be displayed. Cannot view XML input using style sheet.
The system cannot locate the object specified. Error processing resource 'http://stal-azaplluzha/tmtrack/DTD/xhtml1-strict....
CMS-XML Restarting Serena Business Mashups fails after the import of a language XML file
In certain configurations there can be a problem with the conversion of the imported strings into resource files. This problem can be solved by replacing one of the XSL templates that ship with Serena Business Mashups.
CMS-XML RLC gives HTTP 404 with "The origin server did not find a current representation for the target resource or is not willing to disclose that one exists."
a call has succeeded An Xml Parsing exception occurred while parsing the response : HTTP Status 404 - Not Found
CMS-XML Examples of setting up XML Services security with ACF2 and Top Secret
**** / CLASMAP.XMLSERV ENTITYLN(0) MUSID() RESOURCE ($XMLSERV) RSRCTYPE(SER) You will then need the following 2 keys added to the "class" resource setup in the CLASMAP action.
CMS-XML MCLG: Dreamweaver: WebDAV: Error ''The desired action could not be completed because access to the desired resource was denied by the server. (HTTP Error 401)''
If for any reason you need to change the port number that Collage uses for the HTTP 1.0 connection, complete the following steps, in addition to setting the correct port number in Dreamweaver: Open the following file in a text or XML editor: install location/tomcat/conf/server.xml
CMS-XML Logging in gives error "The proxy server isn’t responding" and server.log gives "Error creating bean with name 'liquibase' defined in class path resource"
Initialization of bean failed; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [rlc-liquibase-context. xml ]: Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire change log lock.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs