search cancel

Catalog is not starting and view.log file grows to a massive size in a very short timeframe.


Article ID: 212576


Updated On:


CA Service Catalog


After restarting CA Service Catalog, the view.log grows to a massive size (several GB's).  The following errors are observed in the view.log

2021/01/01 ERROR [https-jsse-nio-8443-exec-11] [DomProcessor] Error Generating Document

javax.xml.transform.TransformerException: org.apache.xalan.xsltc.TransletException: org.apache.xml.utils.WrappedRuntimeException: Invalid byte 1 of 1-byte UTF-8 sequence.


Release : 17.2 and higher



The key is the "Invalid byte 1 of 1-byte UTF-8 sequence." error, which signifies a bad XML file.

In this case, under the filestore location, specific location custom/locale/icusen, file "includes_shared.xml" was found to have additional text added which contained a special character inserted that was disrupting Catalog startup.  

The following screencap depicts the "includes_shared.xml" file opened in Notepad and the offending character highlighted.


Affected entry contains banner text that is used in PAM.  Removal of the banner text special character corrected the issue.  In this case, the file was modified with text that was pasted from a source that contained the anomalous character.

The above illustrates one example of such an issue taking place.  The specific XML file that is causing the problem may vary depending on circumstances.  One should examine all such XML and XSL files within the Catalog installation that had been modified recently to determine which is causing the issue to occur.

Additional Information

This tech article discusses how to locate the filestore location as stored in the MDB database:

Location of the Filestore