KB Article #176568

Sentinel 4.0.1 TemplateServer does not start up because it is unable to load Sentinel configuration file, trkserver.xml

Problem

After upgrading to Sentinel 4.0.1 from 3.6.0, TemplateServer fails to start up and following error and fatal messages are recorded in sentinel.log

[TemplateServer ] ERROR L111  XmlDataBinderErrorHandler.error - SAXParseException: parser state = 'currentElement'='Services', 'lastEntity'='file:///C:/Axway/Sentinel/RmiRegistryConfig.xsd', line=170, column=56, SystemID=null, publicID=null: cvc-complex-type.4: Attribute 'id' must appear on element 'Service'.

[TemplateServer ] FATAL L128  TemplateServerConfig.<init> - Unable to load Sentinel configuration file 'C:\\Axway\\Sentinel\\conf\\trkserver.xml' !

[TemplateServer ] FATAL L129  TemplateServerConfig.<init> - Parsing error, reason:  Error during : << reason = Document parsing failed>>
Exception source message = 'SAXParseException: parser state = 'currentElement'='Services', 'lastEntity'='file:///C:/Axway/Sentinel/RmiRegistryConfig.xsd', line=170, column=56, SystemID=null, publicID=null: cvc-complex-type.4: Attribute 'id' must appear on element 'Service'.'
Exception source type = 'org.xml.sax.SAXParseException'
root Object = 'TemplateServerConfig'
root Node = 'SentinelServerConfiguration'

[TemplateServer ] FATAL L130  TemplateServerConfig.<init> - Program abort.



Resolution

Add the missing IDs to trkserver.xml

1) Make sure all the Sentinel Servers are stopped.

2) Take a backup copy of trkserver.xml in <SentinelFileDriveHome>\Sentinel\conf\

3) Add the following IDs to the Services as shown below (highlighted in yellow) to the trkserver.xml

<Service activate="true" port="1301" id="HTTP-XML" poolSize="10">
<Description>HTTP server tracker for XML data type</Description>
<SrvImpl protocol="HTTP" class="SocketEventReceiver" package="com.axway.sentinel.frontend.server.services.socketevent" />
</Service>
<Service activate="true" port="1302" id="QLT-XNTF" poolSize="10" >
<Des cription>QLT server tracker for XNTF data type</Description>
<SrvImpl protocol="QLT" class="SocketEventReceiver" package="com.axway.sentinel.frontend.server.services.socketevent" />
</Service>

<Service activate="true" port="1303" id="QLT-XML" poolSize="10" >
<Description>QLT server tracker for XML datas type</Description>
<SrvImpl protocol="QLT" class="SocketEventReceiver" package="com.axway.sentinel.frontend.server.services.socketevent" />
</Service>

<Service activate="true" port="1304" id="HTTP-XNTF" poolSize="10" >
<Description>HTTP server tracker for XNTF data type</Description>
<SrvImpl protocol="HTTP" class="SocketEventReceiver" package="com.axway.sentinel.frontend.server.services.socketevent" />
</Service>

<Service activate="true" port="1305" id="AUTO" poolSize="50" >
<Description>HTTP/QLT server tracker for XNTF/XML data type</Description>
<SrvImpl protocol="AUTO" class="SocketEventReceiver" package="com.axway.sentinel.frontend.server.services.socketevent" />
</Service>
                
<Service activate="true" port="1306" id="AUTO-UTF8" poolSize="20"  >
<Description>HTTP/QLT/UTF8 server tracker for XNTF/XML data type</Description>
<SrvImpl protocol="AUTO" class="SocketEventReceiver" package="com.axway.sentinel.fronten d.server.services.socketevent" />
</Service>

4) Starting up the Sentinel servers