Troubleshooting: Uninstalling the Symantec Endpoint Encryption Management Server
search cancel

Troubleshooting: Uninstalling the Symantec Endpoint Encryption Management Server

book

Article ID: 161273

calendar_today

Updated On:

Products

Endpoint Encryption

Issue/Introduction

This article provides troubleshooting solutions when uninstalling the Symantec Endpoint Encryption Management Server.

Resolution

Problem

You receive a prompt for SQL Server Logon on the Communication policy page while creating the Management Agent package.

Solution

Enter the appropriate server name, database name, and credentials to authenticate to the SQL Server. If the authentication fails, ensure the SEEMSDb database exists on the SQL Server. It is possible the Endpoint Encryption Management Server was uninstalled and the remaining Management Agent and other installation components were left on the system. If the database was deleted as part of the uninstallation process, it will need to be restored by restoring the database on the SQL Server from a backup.

Also, the Symantec Endpoint Encryption Management Server installation will need to be executed again and the option should be selected to use an existing Endpoint Encryption database. If a new database is selected instead, clients fail to communicate. This will require that all clients be manually decrypted, the Endpoint Encryption software uninstalled, and any new client packages be reinstalled on the client.
 


 

Problem

After uninstalling the Symantec Endpoint Encryption Management Server and other components, the SEEMSDb (database) remains in Microsoft SQL Server and should have been deleted.

Solution

Back up the database and delete it from SQL Server. This error occurs when the option to delete the database during the Management Server uninstall process is not selected.

 


Attachments