Video Screencast Help

DB has been moved and cannot open the SEPM anymore

Created: 14 May 2013 | 4 comments

I am really hoping someone can help me out.  Yesterday our SQL team took it upon themselves to move my SEPM DB to VM ware.  Now I cannot open the SEPM - getting a "cannot access the DB" error message.  It there anyway to fix this?

 

thanks

 

 

Operating Systems:

Comments 4 CommentsJump to latest comment

.Brian's picture

Run the Management Server Configuration Wizard

Follow steps here

How to move the Symantec Endpoint Protection Manager SQL database to a new SQL Server

Article:TECH174821  |  Created: 2011-11-18  |  Updated: 2012-01-06  |  Article URL http://www.symantec.com/docs/TECH174821

 

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Chetan Savade's picture

Hi,

Repair the SEPM through add/remove programs.

 

Chetan Savade
Sr Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

Mithun Sanghavi's picture

Hello,

Here are the steps:

  • Detach the Database in question from the current Instance; in SQL 2000 this is done via the "SQL 2000 Enterprise Manager", whereas if using SQL 2005 or 2008 this would be accomplished through the "SQL Server Management Studio".
  • After the Database is detached, navigate to the appropriate data folder where the existing SQL server data files are stored.

Example:

C:\Program Files\Microsoft SQL Server\MSSQL\xxxx\DATA 

OR 

C:\Program Files\Microsoft SQL Server\MSSQL\DATA.

  • Copy the following database files to the data folder on the new server you plan to house this SQL database:

<db_name.MDF>

<db_name.NDF>

<db_name.LDF>

  • On the new SQL server, Right click on the Database instance, and click on Tasks > All Tasks> Attach Database.  This will again be done through the SQL Enterprise Manager or Management Studio. 
  • Type the path to the <db_name.MDF> file, and the wizard will automatically pick up the other files. (.NDF and .LDF)
  • Click OK. The wizard will automatically collate and attach the SEPM SQL Database to the chosen SQL Instance on the new server.
  • Once complete, Run the "Management Server Configuration Wizard" on the SEPM to point it to the new server housing its SQL Database.
  • In the Database Server name tab, type in the <HostName>\<InstanceName> of the new SQL server, fill in the remaining required details and complete the configuration wizard.

  • Once the wizard has completed, log in to the SEPM console and confirm that the previously configured Policies and Client groups appear as expected.

Here are the perfect articles for your issue:

Migrating to Microsoft SQL 2008 from a previous version

http://www.symantec.com/docs/HOWTO17917

How to move the Symantec Endpoint Protection Manager SQL database to a new SQL Server

http://www.symantec.com/docs/TECH174821

Best Practices guide to moving the Symantec Endpoint Protection Manager SQL Server database from an existing SQL Server database to a new SQL Server database

http://www.symantec.com/docs/TECH104723

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Chetan Savade's picture

Hi,

Symantec Endpoint Protection Manager need to be Synch with SQL database loaction.

Refer this article: http://www.symantec.com/docs/TECH104723

Info is taken from above shared article:

Problem

How can I move the Symantec Endpoint Protection Manager SQL Server database from an existing SQL Server database to a new SQL Server database?

Solution

In order to move the Symantec Endpoint Protection Manager SQL Database (DB), please follow the steps as outlined below:

  1. Detach the Database in question from the Existing Database in SQL 2000 via the "SQL 2000 Enterprise Manager."
    Note: If using SQL 2005, the "SQL Server Management Studio".
     
  2. After the Database is detached, navigate to the appropriate data folder where the existing SQL server data files are stored.

    Example:
    C:\Program Files\Microsoft SQL Server\MSSQL\xxxx\DATA

    OR

    C:\Program Files\Microsoft SQL Server\MSSQL\DATA.
     

  3. Copy the following database files to the data folder for the new server housing the new SQL DB
    • <db_name.MDF>
    • <db_name.NDF >
    • <db_name.LDF >
       
  4. On the server where you want to move the existing SQL DB to, Right click on the Database instance, and click on Tasks>All Tasks> Attach Database.
     
  5. Type the path to the < db_name .MDF > file, and the wizard will automatically pick up the other files. (. NDF and . LDF )
     
  6. Click OK. The wizard would automatically collate and attach the Symantec Endpoint Protection Manager console database to the new SQL Database.
     
  7. Once complete, Run the "Management Server Configuration Wizard" and point the Symantec Endpoint Protection Manager to the new server housing the newly attached Database.
    • In the Database Server name tab, type in the <HostName> /<ComputerName> of the new server, fill in the remaining required details and complete the configuration wizard.
       
  8. Once the wizard has completed its task, log into the Symantec Endpoint Protection Manager Console and the configured Policies and Clients will appear as in the previous installation.

Chetan Savade
Sr Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<