Endpoint Protection

I created an addition site as replication partner to my main site in SEP. but when I open the SEPM console on the addition site top three links don't work and gives an error as unable to communicate with the reporting component.

what could be the problem other tabs are working fine.

OS:- Windows2k3sp2
SEPM ver- SEP11RU5
RAM-2GB
Server-XEON dual processor server

The exact message is as below

HI,

Please check the scm-server-0.log and let us know if you find any errors there.

And refer to the following documentation:

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/beb4238fecda37a588257433006db633?OpenDocument

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/32a9ac7fc1ff64b8882574fa007a946b?OpenDocumenthttp://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/32a9ac7fc1ff64b8882574fa007a946b?OpenDocument

http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/cf4efe8c7640f1074925743500612666?OpenDocument


http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/c338203f13f7f420802575d6002a798e?OpenDocument

https://www-secure.symantec.com/connect/articles/how-create-new-reporting-virtual-directory-iis-manager-troubleshooting-unable-communicate-r

Aniket

Below is the scm-server-0.log



2009-11-06 17:04:06.703 SEVERE: ================== Server Environment ===================
2009-11-06 17:04:06.703 SEVERE: os.name = Windows 2003
2009-11-06 17:04:06.703 SEVERE: os.version = 5.2
2009-11-06 17:04:06.703 SEVERE: os.arch = x86
2009-11-06 17:04:06.703 SEVERE: java.version = 1.6.0_14
2009-11-06 17:04:06.718 SEVERE: java.vendor = Sun Microsystems Inc.
2009-11-06 17:04:06.718 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2009-11-06 17:04:06.718 SEVERE: java.vm.version = 14.0-b16
2009-11-06 17:04:06.718 SEVERE: java.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
2009-11-06 17:04:06.718 SEVERE: catalina.home = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
2009-11-06 17:04:06.718 SEVERE: java.user = null
2009-11-06 17:04:06.718 SEVERE: user.language = en
2009-11-06 17:04:06.718 SEVERE: user.country = US
2009-11-06 17:04:06.718 SEVERE: scm.server.version = 11.0.5002.333
2009-11-06 17:04:17.390 SEVERE: ================== StartClientTransport ===================
2009-11-06 17:04:18.562 SEVERE: Schedule is started!
2009-11-06 17:05:39.781 SEVERE: com.sygate.scm.server.util.securitydata.ThreatData: Signature verification failed for Security Response outbreak information.
2009-11-06 17:20:15.718 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.io.IOException: There is not enough space on the disk
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:260)
 at com.sygate.scm.server.task.PackageTask.checkLiveUpdateDirectory(PackageTask.java:1512)
 at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:271)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:21:15.796 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.io.IOException: There is not enough space on the disk
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:260)
 at com.sygate.scm.server.task.PackageTask.checkLiveUpdateDirectory(PackageTask.java:1512)
 at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:271)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:22:01.609 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.io.IOException: There is not enough space on the disk
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:260)
 at com.sygate.scm.server.task.PackageTask.checkLiveUpdateDirectory(PackageTask.java:1512)
 at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:271)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:23:37.843 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.io.IOException: There is not enough space on the disk
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:260)
 at com.sygate.scm.server.task.PackageTask.checkLiveUpdateDirectory(PackageTask.java:1512)
 at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:271)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:24:23.812 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.io.IOException: There is not enough space on the disk
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:260)
 at com.sygate.scm.server.task.PackageTask.checkLiveUpdateDirectory(PackageTask.java:1512)
 at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:271)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:25:13.468 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.io.IOException: There is not enough space on the disk
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:260)
 at com.sygate.scm.server.task.PackageTask.checkLiveUpdateDirectory(PackageTask.java:1512)
 at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:271)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:25:58.718 SEVERE: Unknown Exception in: com.sygate.scm.server.task.PackageTask
java.io.IOException: There is not enough space on the disk
 at java.io.FileOutputStream.writeBytes(Native Method)
 at java.io.FileOutputStream.write(FileOutputStream.java:260)
 at com.sygate.scm.server.task.PackageTask.checkLiveUpdateDirectory(PackageTask.java:1512)
 at com.sygate.scm.server.task.PackageTask.run(PackageTask.java:271)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:26:19.765 SEVERE: Unknown Exception
java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0EM: End of data.
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:611)
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:913)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3963)
 at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:2325)
 at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69)
 at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:220)
 at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:203)
 at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1720)
 at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate(SybStatement.java:1703)
 at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java:115)
 at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
 at com.sygate.scm.server.metadata.StateMetadataCollection.updateMetadata(StateMetadataCollection.java:103)
 at com.sygate.scm.server.metadata.MetadataManager.updateMetadata(MetadataManager.java:387)
 at com.sygate.scm.server.configmanager.ConfigManager.updateStateObject(ConfigManager.java:1004)
 at com.sygate.scm.server.configmanager.ConfigManager.updateSemServerStateObject(ConfigManager.java:2950)
 at com.sygate.scm.server.task.StateCheckpointTask.run(StateCheckpointTask.java:65)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:26:19.937 SEVERE: Unexpected server error. in: com.sygate.scm.server.task.StateCheckpointTask
com.sygate.scm.server.metadata.MetadataException: JZ006: Caught IOException: java.io.IOException: JZ0EM: End of data.
 at com.sygate.scm.server.metadata.MetadataManager.updateMetadata(MetadataManager.java:390)
 at com.sygate.scm.server.configmanager.ConfigManager.updateStateObject(ConfigManager.java:1004)
 at com.sygate.scm.server.configmanager.ConfigManager.updateSemServerStateObject(ConfigManager.java:2950)
 at com.sygate.scm.server.task.StateCheckpointTask.run(StateCheckpointTask.java:65)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
Caused by: java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0EM: End of data.
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:611)
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:913)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3963)
 at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:2325)
 at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69)
 at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:220)
 at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:203)
 at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1720)
 at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate(SybStatement.java:1703)
 at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java:115)
 at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
 at com.sygate.scm.server.metadata.StateMetadataCollection.updateMetadata(StateMetadataCollection.java:103)
 at com.sygate.scm.server.metadata.MetadataManager.updateMetadata(MetadataManager.java:387)
 ... 5 more
com.sygate.scm.server.util.ServerException: Unexpected server error.
 at com.sygate.scm.server.configmanager.ConfigManager.updateStateObject(ConfigManager.java:1006)
 at com.sygate.scm.server.configmanager.ConfigManager.updateSemServerStateObject(ConfigManager.java:2950)
 at com.sygate.scm.server.task.StateCheckpointTask.run(StateCheckpointTask.java:65)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
Caused by: com.sygate.scm.server.metadata.MetadataException: JZ006: Caught IOException: java.io.IOException: JZ0EM: End of data.
 at com.sygate.scm.server.metadata.MetadataManager.updateMetadata(MetadataManager.java:390)
 at com.sygate.scm.server.configmanager.ConfigManager.updateStateObject(ConfigManager.java:1004)
 ... 4 more
Caused by: java.sql.SQLException: JZ006: Caught IOException: java.io.IOException: JZ0EM: End of data.
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:611)
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:913)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3963)
 at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:2325)
 at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69)
 at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:220)
 at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:203)
 at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1720)
 at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate(SybStatement.java:1703)
 at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java:115)
 at org.apache.commons.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:102)
 at com.sygate.scm.server.metadata.StateMetadataCollection.updateMetadata(StateMetadataCollection.java:103)
 at com.sygate.scm.server.metadata.MetadataManager.updateMetadata(MetadataManager.java:387)
 ... 5 more
2009-11-06 17:26:20.890 SEVERE: Unknown Exception in: com.sygate.scm.server.task.AgentLogCollector
java.lang.NullPointerException
 at com.sygate.scm.server.task.AgentLogCollector.run(AgentLogCollector.java:89)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:26:20.890 SEVERE: DomainId: null
SiteId: 903BB02C0A21011A0179A09C65E5D535
ServerId: A0FB3FA20A21011A00707ACA1C6A18FC
SystemEventId: 1281
EventDesc: null
MessageId: -1
ErrorCode: -1
java.lang.NullPointerException
 at com.sygate.scm.server.task.AgentLogCollector.run(AgentLogCollector.java:89)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:26:26.906 SEVERE: db is not connected! try agagin.
2009-11-06 17:26:28.875 SEVERE: db is not connected! try agagin.
2009-11-06 17:26:28.875 SEVERE: Unknown Exception in: com.sygate.scm.server.task.ApplicationCollector
java.lang.NullPointerException
 at com.sygate.scm.server.task.ApplicationCollector.run(ApplicationCollector.java:56)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-06 17:26:30.843 SEVERE: db is not connected! try agagin.
2009-11-06 17:26:28.875 SEVERE: DomainId: null
SiteId: 903BB02C0A21011A0179A09C65E5D535
ServerId: A0FB3FA20A21011A00707ACA1C6A18FC
SystemEventId: 1281
EventDesc: null
MessageId: -1
ErrorCode: -1
java.lang.NullPointerException
 at com.sygate.scm.server.task.ApplicationCollector.run(ApplicationCollector.java:56)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-07 00:20:39.250 SEVERE: Unknown Exception
java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:557)
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:861)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3967)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3912)
 at com.sybase.jdbc2.tds.Tds.login(Tds.java:440)
 at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:254)
 at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:230)
 at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:200)
 at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:134)
 at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
 at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
 at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
 at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
 at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
 at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:285)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:276)
 at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:74)
 at java.util.logging.Logger.log(Logger.java:458)
 at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:394)
 at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:373)
 at com.sygate.scm.server.task.ApplicationCollector.run(ApplicationCollector.java:186)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-07 00:20:37.062 SEVERE: DomainId: null
SiteId: 903BB02C0A21011A0179A09C65E5D535
ServerId: A0FB3FA20A21011A00707ACA1C6A18FC
SystemEventId: 1281
EventDesc: null
MessageId: -1
ErrorCode: -1
java.lang.NullPointerException
 at com.sygate.scm.server.task.ApplicationCollector.run(ApplicationCollector.java:56)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-07 00:20:39.250 SEVERE: Unknown Exception during logging
java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:557)
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:861)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3967)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3912)
 at com.sybase.jdbc2.tds.Tds.login(Tds.java:440)
 at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:254)
 at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:230)
 at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:200)
 at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:134)
 at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
 at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
 at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
 at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
 at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
 at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:285)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:276)
 at com.sygate.scm.server.util.logging.DbLogHandler.publish(DbLogHandler.java:74)
 at java.util.logging.Logger.log(Logger.java:458)
 at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:394)
 at com.sygate.scm.server.util.ServerLogger.log(ServerLogger.java:373)
 at com.sygate.scm.server.task.ApplicationCollector.run(ApplicationCollector.java:186)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)
2009-11-07 00:20:40.234 SEVERE: Unknown Exception
java.sql.SQLException: JZ006: Caught IOException: java.net.ConnectException: Connection refused: connect
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseError(ErrorMessage.java:557)
 at com.sybase.jdbc2.jdbc.ErrorMessage.raiseErrorCheckDead(ErrorMessage.java:861)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3967)
 at com.sybase.jdbc2.tds.Tds.handleIOE(Tds.java:3912)
 at com.sybase.jdbc2.tds.Tds.login(Tds.java:440)
 at com.sybase.jdbc2.jdbc.SybConnection.tryLogin(SybConnection.java:254)
 at com.sybase.jdbc2.jdbc.SybConnection.regularConnect(SybConnection.java:230)
 at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:200)
 at com.sybase.jdbc2.jdbc.SybConnection.<init>(SybConnection.java:134)
 at com.sybase.jdbc2.jdbc.SybDriver.connect(SybDriver.java:179)
 at org.apache.commons.dbcp.DriverConnectionFactory.createConnection(DriverConnectionFactory.java:38)
 at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
 at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:974)
 at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
 at org.apache.commons.dbcp.BasicDataSource.getConnection(BasicDataSource.java:880)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:285)
 at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:276)
 at com.sygate.scm.server.metadata.MetadataManager.getConnectionNoCheckRequireTransactionId(MetadataManager.java:831)
 at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:804)
 at com.sygate.scm.server.metadata.MetadataManager.getConnection(MetadataManager.java:839)
 at com.sygate.scm.server.metadata.MetadataManager.getMetadata(MetadataManager.java:866)
 at com.sygate.scm.server.metadata.MetadataManager.getMetadataAttributes(MetadataManager.java:249)
 at com.sygate.scm.server.configmanager.ConfigManager.getTopLevelObject(ConfigManager.java:287)
 at com.sygate.scm.server.configmanager.ConfigManager.getSemSiteObject(ConfigManager.java:1439)
 at com.sygate.scm.server.task.BackupSchedulerTask.readBackupSchedule(BackupSchedulerTask.java:95)
 at com.sygate.scm.server.task.BackupSchedulerTask.run(BackupSchedulerTask.java:37)
 at java.util.TimerThread.mainLoop(Timer.java:512)
 at java.util.TimerThread.run(Timer.java:462)

Do you have enough space ?

I see this in log..


java.io.IOException: There is not enough space on the disk

checked ODBC connection ,its complaining about that too.

2009-11-06 17:26:26.906 SEVERE: db is not connected! try agagin.
2009-11-06 17:26:28.875 SEVERE: db is not connected! try agagin.
 

 A lot of There is not enough space on the disk message present in your log file
Check your hard Drive frees pace availability.

Yes I don't have space .I saw that and freeing some space on my server. after that I will let you know

After making some free space of 6GB. when I opened the console still the same error appears.

This error is appearing on my replication site which I installed yesterday.
my main site is working ok with same configuration

have you fixed the ODBC ?

How to fix it.

PLease make sure that the ODBC connection is successful, using the steps below:
In the Windows Control Panel, open Data Sources (ODBC).
On the System DSN tab click Symantec Endpoint Security DSN.
Click Configure.
On the Login tab, enter the User ID DBA and the Symantec Endpoint Protection database password configured during installation (this is the same as the Endpoint Protection Manager login password by default).
On the Database tab enter the name of the computer that runs Symantec Endpoint Protection Manager into the "Server name:" field.
Under Database Name, enter the following: sem5
On the ODBC tab, click Test.
If the test is successful Click OK to save the changes.
 

How to Create a new "Reporting" Virtual Directory in IIS Manager for troubleshooting "Unable to Communicate with Reporting Component" issue

I removed SEPM on that server and aslo removed embeded databse and reinstalled but still same issue. what to do ?
Now I think I should open a case for this but already 4 cases are still open which are due to new  virus.

Database replication is working successfully  it means no problem in db connectivity .

what should I do now .I don't want to create a new virtual directory in IIS.

Yes it is a good idea..
Also check that whether you are having sufficient resources in that server...
May be a high memory usge is causing the problem......

NO I have 2gb  memory and 23gb free hdd space . so no problem in that.

when I try to login from IIS reporting virtual directory it shows no error and comes as blank page nothing is displayed.

One thing I forgot to mention is that on my main server I have installed fastcgi but on my second(replication) server I havn't installed fastcgi. could this be a problem.

Logoff button is also not working I am manually closing  the console.

in the folder program files\symantec\symantec endpoint protection manager\ php.ini

put these lines in ON :

display_errors = Off

display_startup_errors = Off

login in the reporting site by IIS manager and see any error you are getting?
if getting tell me what is the error

Hi Arindam After following your method below is the error msg


Fatal error: Uncaught exception 'com_exception' with message 'Failed to create COM object `pmem2.MachineInfo2.1': Invalid syntax ' in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Login\curl_funcs.php:53 Stack trace: #0 C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Login\curl_funcs.php(53): com->com('pmem2.MachineIn...', NULL, 65001) #1 C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Login\Login_verify.php(21): doLogin('0172f944006390e...', 'e0f70e87f4076ae...', '', '') #2 {main} thrown in C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub\Reporting\Login\curl_funcs.php on line 53

Try giving permission for Authenticated users in
 C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Inetpub
C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection Manager

permission given but still the same problem.

my main server is working fine but its the other server which i configured as replication server is giving this problem.

Rename the curl_funcs.php &Login_verify.php in new server and copy the same from old server and see what is the error you are getting?

ok will try 2morrow and let you know

I copied the two files curl_funcs.php &Login_verify.php .but same thing when i open the sepm console . but from iis it gives different error

FastCgi error

http error 500

Enable fast cgi and see any difference?
Below article cab help you in this
Installing the FastCGI Extension for Internet Information Services 6.0

Also compare the files in the reporting directory with your main server and see any file is missing in this...

Have already installed fastcgi but still problem remains the same.

u done every thing then why u ask u Q.

To adjust the Symantec Endpoint Protection Manager heap size:
Click Start> Run.
In the Run dialog box, type regedit
Press Enter.
Locate the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\semsrv\Parameters\
Locate the following keys:
JVM Option Number 0
JVM Option Number 1
Adjust the key values upward, and for optimal performance, match the key values.
For example, to create a 1 GB static heap, set: "JVM Option Number 0" to "-Xms512m", and set "JVM Option Number 1" to "-Xmx1024m".
Close Regedit.
Click Start> Settings> Control Panel> Administrative Tools
In the Services dialog box, right-click Symantec Endpoint Protection Manager, and then click Restart.


 

After doing so many things the problem is not solved yet .thats why I am asking for help?
If you can't help then pls don't comment like this.
we are here to help other and ask for help also. atleast I think so.

I just wanted to know what you get when you try this.

open IIS on the problamatic SEPM server
right click on reporting
click on browse, what do u get ? access denied or Page cannot be displayed? 
 fix the permission issue using iisdiag tool from MS

 http://www.microsoft.com/downloads/details.aspx?familyid=9BFA49BC-376B-4A54-95AA-73C9156706E7&displaylang=en

when you do browse through reporting or when you do Http://localhost:8014/reporting do you get a blue login page?

 Http://localhost:8014/reporting giving FastCgi error
error no 2
the system can't find the file specified.

http error 500

what else I can try. still the problem exits.
should i try a repair of sepm

pls suggest.I am going to log a case for this.

First assure you are having all req. files in reporting directory
specially
reporter.php & reporter2.php

If this not works try with SEPM repair..

I tried repairing but still same problem. no improvement.

any other suggestion.