Symantec manager not updating
For example, change the name to “sem5” Next, regenerate a new sem5file by opening a command prompt and changing to the “C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\” directory (again, using the correct path if you have a 64-bit machine).
steps for how an administrator can automate backups and perform recommended maintenance procedures for Enterprise Vault (EV), Compliance Accelerator (CA), and Discovery Accelerator (DA) SQL databases using SQL Server maintenance plans.A shrink operation increases the fragmentation of table indexes; therefore, a shrink operation must be followed by the index maintenance operation of reorganizing or rebuilding the indexes.Note: If an index maintenance operation does not reduce fragmentation levels, even after multiple runs with the EV/CA/DA services stopped, and there is a large amount of free space in the database, a shrink operation with the option to return file space back to the operating system may need to be run, followed by the index maintenance operation to rebuild the indexes.The Symantec Endpoint Protection Manager console may fail to start on the local machine after a software update or a forced shutdown of the server.This is a known issue, and is documented on the Symantec site as first occurring in deployments of version 12.1 of the SEPM application.The most recent report was posted in January of 2014.
The issue has been documented on both Windows 2003 and Windows 2008 servers.
SQL Database Administrators (DBAs) often have their own preferred method to perform backups and maintenance.
Those methods should take precedence over these suggested steps as long as the basic recommended functions are performed.
Those basic functions are, in order: Whilst SQL Server 2005 and higher allow for online index operations, i.e., running index rebuilds and maintenance without stopping any EV, CA or DA services, this is not the recommended method as there are certain restrictions to running online operations.
First, online index operations are typically only available in the Enterprise version of SQL Server.
If you still cannot launch the SEPM console after regenerating the log file, you may be able to perform administrative tasks temporarily by logging in to the host remotely.