Getting error message "[Fatal Error] :1:1: Premature end of file" on the Engine Sub Components.
search cancel

Getting error message "[Fatal Error] :1:1: Premature end of file" on the Engine Sub Components.


Article ID: 48942


Updated On:


CA Mediation Manager



Suddenly receiving the following error message on the Engine Sub Components log "STD-ERROR-<timestamp>.log:

"[Fatal Error] :1:1: Premature end of file."

And since then Mediation Manager could not process any data to the Presenter LC and push them to eHealth.

The Engine Sub-Component logs will show messages like the following:

com.torokina.common.tinyutil.ToroXmlHelper getDocument
SCHWERWIEGEND: Premature end of file. - 1 : 1 process
SCHWERWIEGEND: Process DeliveryStoreFunction Failed
org.xml.sax.SAXParseException: Premature end of file.


The root cause of this error is due to having an invalid PresenterDeviceIndex.xml file in the $CAMM_HOME/COMPONENTS/ENGINE_<device pack>/repository/work directory of the Engine.

One would notice that the file PresenterDeviceIndex.xml has a size of 0 byte and is not in a proper xml file format. For example, normally the hex dump of this xml fileshould show "3C 3F 78 6D 6C 20" (standing for <?xml). If this is missing from the file on the problematic Engine, then the PresenterDeviceIndex.xml is considered as badly formatted xml file.

And this is the reason for the "Premature end of file" error.

To solve the problem follow these steps:

  1. Remove PresenterDeviceIndex.xml from the $CAMM_HOME/COMPONENTS/ENGINE_<device pack>/repository/work directory.
  2. Trigger a new Inventory Poll.
  3. Once the Inventory Poll will be completed, a new and well structured PresenterDeviceIndex.xml file will be recreated in the same

    $CAMM_HOME/COMPONENTS/ENGINE_<device pack>/repository/work directory.


Component: MEDMGR