cancel
Showing results for 
Search instead for 
Did you mean: 

TREX NameServer exits with code 128 on system start

Former Member
0 Kudos

Installed a new TREX server on Windows 2003 x64 server, using standard settings for a stand-alone TREX server. Installed as Local (not domain) and install completed successfully. After the install (or after any reboot), all the regular TREX services start up correctly except for TREXNameServer.exe.

Looking at the trace file for TREX Daemon, here is an excerpt:

[4084] 2008-11-06 12:01:18.093 i Daemon TrexDaemon.cpp(07478) : start TREXDaemon

[4084] 2008-11-06 12:01:18.274 i Daemon TrexDaemon.cpp(01969) : created shared-memory for NameServer (shm: Handle=0x268, size=16690888, mtx: Handle=0x230)

[4084] 2008-11-06 12:01:18.349 i Daemon TrexDaemon.cpp(05496) : start 'TREXNameServer.exe -port 30001' as process 2152

[4084] 2008-11-06 12:01:18.545 i Daemon TrexDaemon.cpp(06789) : process TREXNameServer.exe with pid 2152 exited with code 128

[4084] 2008-11-06 12:01:19.553 i Daemon TrexDaemon.cpp(05460) : child <TREXNameServer.exe> terminates too soon -> disabled

[4084] 2008-11-06 12:01:22.367 i Daemon TrexDaemon.cpp(05496) : start 'TREXPreprocessor.exe -port 30002' as process 2256

[4084] 2008-11-06 12:01:24.383 i Daemon TrexDaemon.cpp(05496) : start 'TREXIndexServer.exe -port 30003' as process 2296

[4084] 2008-11-06 12:01:29.363 i Daemon TrexDaemon.cpp(05496) : start 'TREXQueueServer.exe -port 30004' as process 4132

[4084] 2008-11-06 12:01:34.284 e Daemon TrexDaemon.cpp(04782) : creation of process '"python" alertserver.py' failed: The system cannot find the file specified.

[4084] 2008-11-06 12:01:34.284 i Daemon TrexDaemon.cpp(05498) : start 'python alertserver.py' failed

[4084] 2008-11-06 12:01:34.389 i Daemon TrexDaemon.cpp(05496) : start 'TREXCruiser.exe' as process 4176

If I log into the server as <sid>adm, run TREXConsole and then start TREXNameServer, it starts up fine and works without a problem. However, that doesn't start the Name Server as a service, preventing the unattended operation that one would hope for.

Has anyone encountered this before? I've searched all over, but have not located anything that is not allowing the Name Server to start. I would appreciate any suggestions to help track down this problem. Thanks.

TREX Version: 7.10.14.147693

Windows 2003 Server x64 SP2 with vcredist64, JRE installed

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Issue was related to security settings on the Windows drive in question. Discovered by systematically examining all TREX installs in the company until we found the few that were working properly.

Former Member
0 Kudos

Hi Jones,

It turns out my issue was related to security on the Windows drive in question. I installed the TREX main directory on the E drive of the server and simply added the "Users" group to that drive to fix my problem. I'm pretty sure that the service user SAPService<SID> was having access permission issues until I added the group to the security settings of the drive.

Former Member
0 Kudos

Hi,

I have same problem. Did you solve this?

-Jones