Symantec DLP Enforce web console fails to start

[Migration User]

Hello,

I know that there were few forum discussions here on Connect regarding the similar problem, but I have not found the same symptoms.

Problem description: Symantec DLP web console fails to start. The message in browser says: "HTTP Status 404 - /ProtectManager/enforce/navigate" and then "the requested resource is not available" (Apache Tomcat/7.0.23).

Additional information

• SDLP version: 11.6
• Installation: single-tier
• Restarting services doesn't help. The Vontu Monitor Controller suddenly stops.

[yang_zhang]

If the Vontu Monitor Controller failed to start, please check the log of the VontuMonitorController for the error message.

[stephane.fichet]

hi

 

did you check database connection between enforce and DB ?

check vontu manager and vontu controller log files, and if there is no information switch log level to FINEST instead of INFO then restart Vontu services.

 

 regards

[Migration User]

Thank you for your replies. I will check the documentation to see where the Vontu services logs are being written.

[stephane.fichet]

logs are stored in Protect/logs directory on your enforce server. there is also some logs in Protect/logs/debug directory.

if you cannot connect to enforce server, you can retrieve them via DLP UI, in system/logs.

[Migration User]

Checked the DB connection (listener status).

Here is the result:

C:\>lsnrctl services

LSNRCTL for 64-bit Windows: Version 11.2.0.2.0 - Production on 08-OCT-2013 18:04
:46

Copyright (c) 1991, 2010, Oracle.  All rights reserved.

Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=srv03)(PORT=1521)))
Services Summary...
Service "CLRExtProc" has 1 instance(s).
  Instance "CLRExtProc", status UNKNOWN, has 3 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0
         LOCAL SERVER
      "ORACLE SERVER" established:0 refused:0 current:0 max:25 state:ready
         CLRExtProc
         (ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\NTN_1270_28D84D55_AB57.ORA))
      "ORACLE SERVER" established:0 refused:0 current:0 max:25 state:ready
         CLRExtProc
         (ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\NTN_1270_28D84D55_A9B0.ORA))
Service "protect" has 1 instance(s).
  Instance "protect", status BLOCKED, has 1 handler(s) for this service...
    Handler(s):
      "DEDICATED" established:0 refused:0 state:ready
         LOCAL SERVER
The command completed successfully

 The BLOCKED status is not good I think. How to unblock?

 

 

[stephane.fichet]

seems that during last database stop, something went wrong. so did you try restarting oracle server ?

 

or try to do:

lsnrctl

LSNRCTL> status

LSNRCTL> stop

LSNRCTL> start

connect to database using sysdba privilege :

SQL> startup

 

[Migration User]

Restarting Oracle failed. Somehow the sysdba password didn't work...

 

[stephane.fichet]

oups, i dont have anymore ideas for your issue. did you ask your dba to have a look at enforce database ? or if it is a test platform, may be you can reinstall database or install a new one, i know it is not a solution to your issue cause you will never know why it is just a workaround but it can allow you to go on with DLP.

[Migration User]

Hi

There are few things to check:

1.Check Vontu Services are running properly.Make it sure restart it.
2.Check the DB connection.Tomcat log file can help to identify the  status/problem.
3.Check the Network/Firewall changes happened recently.Incase of your enforce server in diff/secure network.
4.Verify the port connection with enforce server.

the above steps can help the existing environment.(Built & worked early). For new build need to check few more.

 

[m@ntec]

hi,

i think database does not mount to your enforce

please follow this:

 

 Please run “lsnrctl status” to check the status of TNS Listener

 

Run “SQLPlus /nolog”

Login to Oracle database as “sys” user

Run “select status from v$instance ;” to check the status of instance

Run “select open_mode from v$database ;” to check the status of Oracle database.

 

[Migration User]

Reinstalled. No way to fix the DB.