Video Screencast Help

Migrate From Embedded DB To SQL Server DB

Created: 17 Feb 2010 • Updated: 21 May 2010 | 10 comments
This issue has been solved. See solution.

Hello:

We are currently running SEPM 11.0.5 using the embedded database. We have been having problems with the database not starting and continually shutting down. I have gone thru the repair of SEPM and still have not had any success. We are getting the following errors:

The Symantec Embedded Database service on Local Computer started and then stopped. SOme services stop automatically if they are not in use by other services or programs.

Event ID: 1
Source: ASA 9.0
The description for Event ID 1 from source ASA 9.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

ASANYs_sem5
Could not start server

Running the dbvalidator returns:

2010-02-17 09:47:53.235 INFO: logger initialized ...
2010-02-17 09:47:53.235 INFO: SEPM Server Home:[C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Tools\..\tomcat]
2010-02-17 09:48:01.768 SEVERE: ERROR: can't init database. exit.

Running dbsrvr9 returns against the sem5.db returns:

Internal database error ***ERROR*** Assertion failed: 201501 (9.0.2.3654)
Page for requested record not a table page or record not present on page--transaction rolled back

This is the second time this has occured. After the first instance, I did a complete reinstall and the issue returned after about a month.

I would like to reinstall using the local SQL Server 2005 database instead of the embedded database (the server is WIndows Server 2008-R2). We have about 30 clients and I would appreciate instruction on how to:

1) Reinstall and use SQL 2005.
2) Reconnect the existing clients without having to do a reinstall on each client.

Thank you in advance for any suggestions or comments.

Comments 10 CommentsJump to latest comment

Rafeeq's picture

you can follow this document

Symantec Endpoint Protection Manager: Moving from the Sybase Embedded Database to Microsoft SQL Server

http://service1.symantec.com/support/ent-security.nsf/docid/2007092722095248

since you have 30 clients, it would be better if you could do a fresh install of SEPM with SQL and use sylink remote tool to get connect your old clients to new manager 
  https://www-secure.symantec.com/connect/downloads/sylink-replacer

Akebono's picture

Thank you. From the first link, since I will be doing a complete reinstall am I correct in assuming that I can skip backing up the embedded databse (which I can't access anyway) and skip backing up the server certificate? I will be reinstalling using the same server name and IP address.

Rafeeq's picture

if you are installing fresh ( which i think wil save lot of time)
skip everything
install fresh SEPM with sql 
use the sylink remote to connect your clients. plain and simple 

Akebono's picture

OK. I have uninstalled SEPM using Add/Remove Programs/Change. I have rebooted the server. However, when I go to reinstall SEPM I receive:

Symantec Endpoint Protection Manager has detected that there are pending system changes that require a reboot. Please reboot the system and rerun the installation.

I have rebooted twice and the message still comes up during the install.

Is there a registry change I need to make to proceed?

Thank you!

Vikram Kumar-SAV to SEP's picture

 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\

highlight Session Manager then on the right hand side delete

PendingFileRenameOperations

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search button..do use it.

Rafeeq's picture

the pending key will be on the right side of session manager, hight light session and then look for pending in right hand side.
lets us know about the progress..
 

Akebono's picture

Ended up reinstalling and using the SQL Server DB instead of the embedded DB. No issues since.

SOLUTION