SEPM with SQL Express database certificate has expired
Article ID: 381108
Updated On:
Products
Issue/Introduction
The certificate for SEPM and SQL has expired and needs to be updated.
Unable to log into the SEPM Console, error: An unexpected Server error has occurred
You may also see the error: Request could not be authorized.
Error in the system log (scm-server-0.log):
java.sql.SQLException: Cannot create PoolableConnectionFactory (The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "NotAfter: Fri Jan 03 16:35:27 CET 2025"
(time will depend on when the SQL certificate expired).
Environment
SEPM versions 14.3 RU1 (14.3.3385.1000) and higher, (the embedded database was updated to the Microsoft SQL Express database in the SEPM 14.3 RU1 release).
SQL Express "embedded" database
Resolution
- Move the date of the system back before the certificate expired.
- Login to the SEPM Console
NOTE: Errors may appear, but it will login eventually - Go to Settings - Servers - Select the SEPM in the site list - select Manage Server Certificates.
- Choose the option to create a new self-signed certificate and uncheck the option to create new keys.
NOTE: If the checkbox for create new keys is checked, the clients will not be able to reconnect to the SEPM - When complete, close down the console.
- Restart the 3 services:
Symantec Endpoint Protection Manager
Symantec Endpoint Protection Manager API Service
Symantec Endpoint Protection Manager Webserver - Launch the Management Server Configuration Wizard.
- On the first page to Reconfigure the server, uncheck the option to restore keys.
- Go through the rest of the wizard (defaults are fine).
- When complete, set the date of the system back to today's date.
- Reboot the system.
- Confirm you can log back into the console with the current date.
If the above doesn't work, please check this article:
You received an email from your SEPM stating the SEPM certificate is expiring or has expired.
Feedback
