Symptom
- TREX start failure
- Following error information is shown in TREX nameserver alert trace.
[268] 2013-08-12 02:46:19.290 e topology Topology.cpp(00185) : line 32: excepted < or > , got .sap.com.local
[268] 2013-08-12 02:46:19.306 e NameServer TREXNameServer.cpp(09209) : loading topology failed. trying c:\usr\sap\XXX\TRX00\sap123\\topology.ini
[268] 2013-08-12 02:46:19.306 e topology Topology.cpp(00185) : line 32: excepted < or > , got .sap.com.local
[268] 2013-08-12 02:46:19.306 f NameServer TREXNameServer.cpp(01308) : An error occured, while loading the topology file -> Stopping TREX !
[268] 2013-08-12 02:46:19.306 f NameServer TREXNameServer.cpp(02058) : Stopping instance...
Read more...
Environment
TREX all revision.
Keywords
TREX, start failure, unexpected, excepted < or >, topology corrupt, IP address, hostname, FQDN, separate line, split into two lines, can't open topology file, topology.ini, trexserver, nslookup, TREX start failure due to unexpected line in topology regarding separated FQDN , KBA , BC-TRX , TREX , How To
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.