2010-10-28 15:51:24.054 SEVERE: scm.server.version = 11.0.5002.333
2010-10-28 15:51:27.211 SEVERE: ================== StartClientTransport ===================
2010-10-28 15:51:27.726 SEVERE: Schedule is started!
2010-10-28 18:14:32.310 SEVERE: Unknown Exception
java.sql.SQLException: Violation of PRIMARY KEY constraint 'PK_PATTERN'. Cannot insert duplicate key in object 'dbo.PATTERN'.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:364)
I'd migrate up to RU6a then to RU6 MP1. If you're going to open a case I can almost guarantee the first thing you're going to be asked to do is migrate up.
You weren't specific about whether or not you used replication in your environment with another SEPM. I found this in the KB noted as a fix included in RU6 MP1.
Replication failure due to Primary Key Violation
Fix ID: 1958237
Symptom: The Symantec Endpoint Protection Manager logs display an error "java.sql.BatchUpdateException: Violation of PRIMARY KEY constraint 'PK_SEM_COMPUTER'. Cannot insert duplicate key in object 'dbo.SEM_COMPUTER'".
Solution: If the insert statement batch fails, Symantec Endpoint Protection Manager now catches the primary key violation exception and executes the statements one by one to make sure all data is inserted or updated to the database.
Then it appears to have connection problems with the database.
2010-10-29 07:21:54.660 SEVERE: Unexpected server error.
com.sygate.scm.server.metadata.MetadataException: I/O Error: Connection reset
sandra
edit: Ha ha, great minds think alike Rafeeq...