Sentinel: On Windows, if the PATH env variable contains quotes or ends in a semi-colon, the eSecurity Communication Service won't start.

  • Document ID:3513328
  • Creation Date:14-Aug-2006
  • Modified Date:26-Apr-2012
    • Micro Focus Products:
      Sentinel

Environment

Microsoft Windows Server 2003 Standard Edition
Microsoft Windows 2000 Server

Situation

Why does my eSecurity Communication Service fail to start?

Resolution

This is a known issue. In a case where eSecurity Communication Service will not start, it maybe due to a PATH issue in the Windows environment.

If the PATH environment variable contains quotes or ends in a semi-colon, the eSecurity Communication Service won't start.

For example, the following PATH will cause the problem:

C:\Program Files\esecurity5.1.1.0\wizard\dlls;C:\Program Files\esecurity5.1.1.0\Sun-1.4.2\bin\server;C:\Program Files\esecurity5.1.1.0\Sun-1.4.2\bin;C:\Program Files\esecurity5.1.1.0\wizard;C:\Program Files\esecurity5.1.1.0\lib;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\Perl\bin\;C:\Program Files\Common Files\NetSarang;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Microsoft SQL Server\80\Tools\BINN;"C:\Program Files\Symantec\Norton Ghost 2003\";C:\Program Files\esecurity5.1.1.0\3rdparty\SonicMQ\MQ6.1\bin


In particular, Norton Ghost 2003 may cause this issue.