Video Screencast Help

Can't Start "Symantec Embedded Database" service.

Created: 29 Jan 2010 • Updated: 03 Aug 2010 | 26 comments
Kui's picture

Can't Start "Symantec Embedded Database" service.

I get this in my event viewer:

"The description for Event ID ( 1 ) in Source ( ASA 9.0 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: ASANYs_sem5, Could not start server."

On trying to start the service in Services I get a message that says:

"The Symantec Embedded Database service started then stopped. Some services stop automatically if they have no work to do."

How do I fix this? None of the fixes I have read up on have worked. I have tried a repair too but to no avail. Please someone sort me out!

Urgent.

Comments 26 CommentsJump to latest comment

postechgeek's picture

@Kui

I have experienced this same error before.
What I did to fix the issue is rename the sem5.log to sem5.old file in "\Symantec Endpoint Protection Manager\db". See if that helps.

Mike

Kui's picture

Strangely..I can't locate sem5.log.

All that's there is sem5.db and sem5.txt.

postechgeek's picture

That's probably because you have done a repair on the install. Do you have a backup of the database?
The backup zips are usually stored here: \Symantec Endpoint Protection Manager\data\backup

Try unzipping the backup, and copying it to the the db folder "\Symantec Endpoint Protection Manager\db". Try starting the service.

Most likely, the database is damaged. You might have to do a clean install.

Mike

Visu310's picture

As was told, it might happen due to a broken database too ... Unfortunately you can't even check if the db is broken or not coz the dbvalidator needs DB service to be running... Okay, try this..

* Check if you have any process called dbsrv9.exe running.( It won' be there, check it anyway)

* Run dbsrv9.exe from SEPM\ASA\Win32 \

* Provide the server name and point the app to the sem5.db .. It ill try to initiate a connection with database.... If that's successfully started, the problem is with the service...

* Paste the output of running that file, Lets check what it says :)

Cheers,
Visu.

I came, I saw, I err ;)

Kui's picture

2 logical processor(s) on 1 physical processor(s) detected.
Per-processor licensing model. The server is limited to use 16 processor(s).
This server is licensed to:
    Symantec
    Symantec
Running on Windows 2003 Build 3790 Service Pack 1
2048K of memory used for caching
Minimum cache size: 2048K, maximum cache size: 262144K
Using a maximum page size of 8192 bytes
Starting database "sem5" (C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\sem5.db) at Sat Jan 30 2010 09:20
Performance warning: Database file "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\sem5.db" consists of 51 disk fragments
Transaction log: sem5.log
Starting checkpoint of "sem5" (sem5.db) at Sat Jan 30 2010 09:20
Finished checkpoint of "sem5" (sem5.db) at Sat Jan 30 2010 09:20
Database "sem5" (sem5.db) started at Sat Jan 30 2010 09:20
Database server started at Sat Jan 30 2010 09:20
Trying to start SharedMemory link ...

    SharedMemory link started successfully

Trying to start NamedPipes link ...

    NamedPipes link started successfully

Trying to start TCPIP link ...

Starting on port 2638
    TCPIP link started successfully

Trying to start SPX link ...

SPX communication link not started

Now accepting requests

Visu310's picture

In the ODBC properties, uncheck SPX commmunication in the 'Network' Tab...  and try to runthis application again... If its started succesfully, it wil minimize itself to system tray ..

* Run dbvalidator.bat and check the log under tomcat\logs\dbvalidator.log

* Run management server config wizard and reconfigure the server.

Lets see what happens :)

Cheers,
Visu.

I came, I saw, I err ;)

Kui's picture

Thanks ALOT for helping me out.

SPX Comm was not checked in ODBC properties. Left it as is.

After running dbsrv9 again: It minimises....*good thing*

Log from dbvalidator:

2010-01-30 10:45:58.106 INFO: logger initialized ...
2010-01-30 10:45:58.106 INFO: SEPM Server Home:[C:\Program Files\Symantec\Symantec Endpoint Protection Manager\Tools\..\tomcat]
2010-01-30 10:46:01.700 SEVERE: ERROR: can't init database. exit.

That does not look good.

Running management server config wizard doesn't work: error is Failed to connect to database (which would make sense coz it's not starting up.

Please don't tell me I have to do a clean install.

P_K_'s picture

Reboot the machine and see if the database service is getting started or not.

if that does not work in that and to case you have to uinsstall and reinstall the SEPM and use the sylink replacer to bring back all the cleint in SEPM

else if you have a back up of the SEPM database then you can restore it in the new SEPM and you can get all your settings back

MCT MCSE-2012 Symantec Technical Specialist (SCTS)

Visu310's picture

As long as you have this DB folder and as long as its not corrupted,we can easily rebuild the system.. But lets check few things before we go with the ultimate solution :)

* Change the registry key :

- HKLM\System\CurrentControlSet\Services\ASANY_sem5
- Edit the parameters key
- Scroll to he right end and you can find the db port, change it to 2639(Something different from the usual 2638)
- Close down the registry and try to start the service.

* If we still have the problem, run dbsrv9.exe and let it connect over 2639(or the new port)

* Now run mgmt server wizard and change the db por to 2639 and proceed.

Note: Symantec Embedded service is nothing but the dbsrv9.exe , so we are basically trying to launch it as a process than as a service.

Cheers,
Visu.

I came, I saw, I err ;)

Kui's picture

Changed the port number to 2639, the service still did not start.

When I run dbsrv9.exe it still tries to connect over 2638 instead of 2639. Restarted the server and it's still doing that.

Can't change port number in mgmt server wizard because it still sees 2638 as the port number. Is there somewhere else I need to change the port number so that dbsrv9 recognises it?

What would the ultimate solution be?

Visu310's picture

Kindly check in the properties file for the db port...

SEPM \ Tomcat \ etc \ conf.properties

Ultimate solutions, unfortunately, happens to be a rebuild! .. (If we are helpless!! :( )

Cheers,
Visu.

I came, I saw, I err ;)

Kui's picture

Thanks again.Below is my conf.properties file.

#Mon Feb 01 10:10:29 GMT+03:00 2010
scm.server.version=11.0.4014.26
scm.timer.lu_delta=2
scm.server.type=master
scm.db.client.bin=C\:\\Program Files\\Symantec\\Symantec Endpoint Protection Manager\\ASA\\win32
scm.timer.agentstatus=60
scm.timer.activedirectory=86400
scm.companysize=3
scm.timer.logcollection=20
scm.liveupdateclient.path=C\:\\Program Files\\Symantec\\LiveUpdate
scm.agent.root=C\:\\Program Files\\Symantec\\Symantec Endpoint Protection Manager\\data
scm.server.port=8443
scm.iis.http.defaultsite=0
scm.timer.iiscache=10
scm.agent.groupcreation=false
scm.agent.kcs=A9259ED1A4AE2927E8CBB3F33EC9948E
scm.db.datasource=jdbc/metadatabase
scm.timer.appcollection=20
scm.timer.packagebuilder=60
scm.iis.http.port=8014
scm.http.port=9090
scm.extlog.deli=,
scm.server.backup=C\:\\Program Files\\Symantec\\Symantec Endpoint Protection Manager\\Server Private Key Backup\\
scm.console.log=true
scm.server.name="x"
scm.server.id=6D23BC90C0A800030087C80196F6C98E

Can't find the db port in it. Not a good thing. Is there a way to insert it?

AravindKM's picture

Symantec Endpoint Protection: Why and how is the port changed on an embedded database?
http://service1.symantec.com/SUPPORT/ent-security....

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Kui's picture

Enbedded db service is not running so I can't do this. It's the problem I'm having in the first place.

AravindKM's picture

Are you able to start the reconfiguration wizard?
If yes jst try to reconfigure it after changing the port no in registry..

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Kui's picture

I can start the wizard, but won't get past the page that you specify port number and password. Tried to change the port number but it won't recognise the new one.

AravindKM's picture

Do you have any database backup? 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Kui's picture

None. Was a new install. Barely two months old.

AravindKM's picture

Then I think it is better to reinstall the SEPM and connect the clients back by using any of one method
How to point Symantec Endpoint Protection(SEP) clients to a new Symantec Endpoint Protection Manager after you have either uninstalled, are going to decommission or replace the Existing Primary Symantec Endpoint Protection Manager (SEPM).

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

P_K_'s picture

It seems that you have tried alomost all the steps , in this senario you have to uinsstall and reinstall the SEPM and use the sylink replacer to bring back all the cleint in SEPM

else if you have a back up of the SEPM database then you can restore it in the new SEPM and you can get all your settings back

MCT MCSE-2012 Symantec Technical Specialist (SCTS)

AravindKM's picture

To obtain "SylinkReplacer", contact Symantec Technical support at:
http://www.symantec.com/business/support/index.jsp
 

Please don't forget to mark your thread solved with whatever answer helped you : ) Thanks & Regards Aravind

Kui's picture

Not available in my country. An email address i could send an email to to request it?

Kui's picture

Got it.

Thanks alot.

Quick confirmation. I run it before uninstalling the SEPM right?

Rafeeq's picture

you run that after u install new sepm.
take sylink from new sepm and run the tool
there is a pdf, go through it , well explained :)