I have a Windows server 2003 standard SP2. Had a problem about a month ago with the SEPM console not opening up. I was able to fix it by re-installing iiS 6 and SEPM.
I removed some files the other day from my AV server because i was running out of space. After that I could not open the SPEM console. I can connect to the builtin database (ODBC test okay) When I attempt to repair or re-install the SEPM program the message below appears at the end of the attempted installation.
"The wizard was interrupted before Symantec Endpoint Protection Manager could be completely installed. Your system has not been modified. To complete installation at another time, please run setup again. "
I tried everything on from this webpage -> Unable to install the Symantec Endpoint Protection Manager ("The wizard was interrupted...")
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008070714555148
Here's the last lines of the install file:
Property(C): DBFILE = C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db
Property(C): DBNAME = sem5
Property(C): DBSERVER = sav-app-2
Property(C): DBPORT = 2638
Property(C): DBUSER = DBA
Property(C): REINSTALLMODE = omus
=== Logging stopped: 1/27/2010 16:02:13 ===
MSI (c) (C0:A0) [16:02:13:556]: Note: 1: 1729
MSI (c) (C0:A0) [16:02:13:556]: Product: Symantec Endpoint Protection Manager -- Configuration failed.
MSI (c) (C0:A0) [16:02:13:556]: Windows Installer reconfigured the product. Product Name: Symantec Endpoint Protection Manager. Product Version: 11.0.5002.333. Product Language: 1033. Reconfiguration success or error status: 1603.
MSI (c) (C0:A0) [16:02:13:572]: Grabbed execution mutex.
MSI (c) (C0:A0) [16:02:13:572]: Cleaning up uninstalled install packages, if any exist
MSI (c) (C0:A0) [16:02:13:572]: MainEngineThread is returning 1603
=== Verbose logging stopped: 1/27/2010 16:02:13 ===
I defragged, checked disked, brought the server back on the domain, used another administrator account.
Is there some file I'm missing or registry key missing or stuck? I'm able to connect to the database okay using the ODBC test. Dbvalidator tested good also.
Yes, I have a Support ticket in on this but I need some help from other minds.
Any suggestions?