How to regain access to the ePolicy Orchestrator SQL Server database engine as a system administrator
Last Modified: 2023-07-20 08:59:08 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
How to regain access to the ePolicy Orchestrator SQL Server database engine as a system administrator
Technical Articles ID:
KB87571
Last Modified: 2023-07-20 08:59:08 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.x All supported SQL Server versions For details of ePO- and SQL-supported environments, see KB51569 - Supported platforms for ePolicy Orchestrator. SummaryThis article describes the process for reconnecting to an SQL Server database using SQL Server Management Studio.
ProblemYou're unable to access the ePO database using SQL Server Management Studio (SSMS) with an administrator account that doesn't have the
The following error is displayed: An administrator is unable to make any changes or browse the ePO database. System ChangeA system administrator can lose access to an instance of the SQL Server because of one of the following reasons:
SolutionOption 1: Attach all databases to the new instance.
One way in which you can regain access is to reinstall the SQL Server and attach all databases to the new instance. This solution is time-consuming, and to recover the logons, it might require restoring the master database from a backup. If the backup of the master database is older, it might not have all information. If the backup of the master database is recent, it might have the same logons as the previous instance; so, administrators are still locked out.Option 2: Complete the Microsoft procedure on how to connect to the SQL Server when System Administrators are locked out. For details, see this Microsoft article to give the To perform the steps above, you must be logged on to Windows as a member of the local administrators group and you must have SSMS already installed on the system. After you perform the procedure, you can connect normally with the new account that's now a member of the Affected ProductsLanguages:This article is available in the following languages: |
|