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 SRA: Component processes are not longer visible - SAXParseException; lineNumber: 52; columnNumber: 4353; Character reference "&#
Caused by: org.xml.sax.SAXParseException ; lineNumber : 52; columnNumber : 4353; Character reference "&#
CMS-XML Multi-threaded ZMF web service requests failing with SAXParseException errors
A customer has been experiencing several production problems where requests executed in their multithreaded, ZMF web services application are failing with the following error: org.xml.sax.SAXParseException ; lineNumber : 1 ; columnNumber : 1 ; Premature end of file. No errors can be seen in the usual log files related to this error and rerunning the same services invariably runs successfully.
CMS-XML After upgrade SBM 11.4.1, unable to log into Repository or connect via Composer
Caused by: org.xml.sax.SAXParseException ; lineNumber : 5; columnNumber : 74; cvc-elt. 1 .a: Cannot find the declaration of element 'hibernate-mapping'.
CMS-XML After upgrade SBM 11.4.1, unable to log into Repository or connect via Composer (HTTP 500 or HTTP 403)
Caused by: org.xml.sax.SAXParseException ; lineNumber : 5; columnNumber : 74; cvc-elt. 1 .a: Cannot find the declaration of element 'hibernate-mapping'.
CMS-XML RLM to ZMF integration gives "We did not find any matches for your request (404)" and alm.log gives "Invalid byte 1 of 1-byte UTF-8 sequence"
We did not find any matches for your request (404) The ALM.log (by default located in C:\Program Files\Common\tomcat\6.0\logs), maybe give the following error: 02-19@19:42:26 [http-8080-2] DEBUG [ZMFClientException.java:34] [admin] : ZMFClientException thrown : org.xml.sax.SAXParseException : Invalid byte 1 of 1 -byte UTF-8 sequence.
CMS-XML BrowseComponent web service fails and crashes tomcat accessing specific component
" org.xml.sax.SAXParseException ; lineNumber : 2; columnNumber : 18783; El nombre de atributo "AC" asociado a un tipo de elemento "m:C" debe ir seguido del carácter ' = '." The customer is blaming repeated attempts to browse this component as the issue that leads to a memory leak in the application server that requires a restart of Tomcat to resolve: ...
CMS-XML org.xml.sax.SAXParseException at package create time.
When a customer clicks finish when creating a new package in ZMF4ECL they get the following exception, see below: !ENTRY com.serena.eclipse.zmf.core 1 0 2017-06-14 08:48:13.072 !MESSAGE Exception in ZmfServer: ; nested exception is:
CMS-XML How to troubleshoot the Rest Grid widget when you get "We did not find any matches for your request" instead of results.
ERROR 4: Invalid byte 1 of 1-byte UTF-8 sequence. The complete error from the log is: 02-19@19:42:26 [http-8080-2] DEBUG [ZMFClientException.java:34] [admin] : ZMFClientException thrown : org.xml.sax.SAXParseException : Invalid byte 1 of 1 -byte UTF-8 sequence.
CMS-XML SBM: Logging into Repository gives error: "org.xml.sax.SAXParseException; Premature end of file."
SBM: Logging into Repository gives error: " org.xml.sax.SAXParseException ; Premature end of file."
CMS-XML ARM-ZMF Web Services issuing invalid error when incorrect userid specified
When a non-existent TSO userid is specified in an ARM-ZMF Web Services request the following error message is returned: org.xml.sax.SAXParseException : Premature end of file.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs