Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

SEP content monitoring tool is displaying blank while running it

Created: 11 Sep 2013 | 6 comments

Hi,

I downloaded the latest SEP content monitoring tool and try to exexute it.

While running, it is showing blank, only white screen, no information is dispalyed. What can be caused for it.

 

SEPM Version : SEP 12.1.2015.2015

OS: Windows Server 2008

 

Regards

KK

Operating Systems:

Comments 6 CommentsJump to latest comment

.Brian's picture

And your running from the SEPM tools directory?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

.Brian's picture

Can you show a screenshot?

You also configured the logging per the readme?

You downloaded the correct version for 12.1? I believe there is also one for 11.x

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Kumar K's picture

Hi Brian,

Please find the screenshot below.

90px_Capture1.PNG

Yes, it is the correct version for 12.1 i.e. SEPM Content Dist Monitor - BETA v1.3

 

No, I didn't configured the logging.

 

Kumar K's picture

Hi,

 

I have configured the logging as per the readme file.

Still it is showing as blank.

Thanks & Regards

KK

Kumar K's picture

Hi,

 

Below are the logs from sepmmonitor.log file

 

2013-09-12 09:32:19.807 THREAD 1 INFO: logger initialized ...
2013-09-12 09:32:20.049 THREAD 1 INFO: SEPM Server Home:[E:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Tools\..\tomcat]
2013-09-12 09:32:20.105 THREAD 1 INFO: Initialized the database.
2013-09-12 09:32:20.535 THREAD 1 INFO: com.sygate.scm.server.metadata.MetadataException:
    at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:965)
    at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:931)
    at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:971)
    at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:997)
    at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:254)
    at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:362)
    at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:275)
    at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:336)
    at com.sygate.scm.server.configmanager.ConfigManager.getSemLocalSettings(ConfigManager.java:2725)
    at com.sygate.scm.tools.monitor.SepmMonitor.initializeSepmMonitor(SepmMonitor.java:499)
    at com.sygate.scm.tools.monitor.SepmMonitor.main(SepmMonitor.java:337)
Caused by: java.sql.SQLException: SEM: Connect to database failed
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:341)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:270)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:260)
    at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:963)
    ... 10 more
Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:344)
    at javax.naming.InitialContext.lookup(InitialContext.java:411)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSource(DatabaseUtilities.java:155)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:392)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:285)
    ... 13 more
com.sygate.scm.server.util.ServerException: Unexpected server error.
    at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:379)
    at com.sygate.scm.server.configmanager.ConfigManagerCache.getTopLevelObject(ConfigManagerCache.java:275)
    at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:336)
    at com.sygate.scm.server.configmanager.ConfigManager.getSemLocalSettings(ConfigManager.java:2725)
    at com.sygate.scm.tools.monitor.SepmMonitor.initializeSepmMonitor(SepmMonitor.java:499)
    at com.sygate.scm.tools.monitor.SepmMonitor.main(SepmMonitor.java:337)
Caused by: com.sygate.scm.server.metadata.MetadataException:
    at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:965)
    at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:931)
    at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:971)
    at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:997)
    at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:254)
    at com.sygate.scm.server.configmanager.ConfigManagerCache.prepareTopLevelObject(ConfigManagerCache.java:362)
    ... 5 more
Caused by: java.sql.SQLException: SEM: Connect to database failed
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:341)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:270)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:260)
    at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:963)
    ... 10 more
Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:344)
    at javax.naming.InitialContext.lookup(InitialContext.java:411)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSource(DatabaseUtilities.java:155)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:392)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:285)
    ... 13 more

2013-09-12 09:32:24.858 THREAD 18 INFO: Refreshing of SEPM Monitor...