Endpoint Protection

Hi all,

i having a problem with my sepm, the system can't start. error.log is;

08/22 07:56:19. Database cannot be started -- sem5.log is an invalid transaction log
08/22 08:24:39. Database cannot be started -- sem5.log is an invalid transaction log
08/22 08:36:46. Database cannot be started -- sem5.log is an invalid transaction log
08/22 09:05:59. Database cannot be started -- sem5.log is an invalid transaction log
08/22 09:15:48. Database cannot be started -- sem5.log is an invalid transaction log
08/23 07:50:46. Database cannot be started -- sem5.log is an invalid transaction log
08/24 02:10:33. Database cannot be started -- sem5.log is an invalid transaction log
08/24 04:14:04. Database cannot be started -- sem5.log is an invalid transaction log
08/24 08:14:32. Database cannot be started -- sem5.log is an invalid transaction log
08/24 08:18:09. Database cannot be started -- sem5.log is an invalid transaction log
08/24 08:20:08. Database cannot be started -- sem5.log is an invalid transaction log
08/24 15:22:04. Database cannot be started -- sem5.log is an invalid transaction log
08/26 17:19:47. Database cannot be started -- sem5.log is an invalid transaction log
08/26 17:24:04. Database cannot be started -- sem5.log is an invalid transaction log
08/26 17:24:10. Database cannot be started -- sem5.log is an invalid transaction log

and from out.log file
.
.
.
I. 08/26 17:24:08. Copyright © 1989-2007 Sybase, Inc.
I. 08/26 17:24:08. Portions Copyright © 2002-2007, iAnywhere Solutions, Inc.
I. 08/26 17:24:08. All rights reserved. All unpublished rights reserved.
I. 08/26 17:24:08. 
I. 08/26 17:24:08. This software contains confidential and trade secret information of
I. 08/26 17:24:08. iAnywhere Solutions, Inc.
I. 08/26 17:24:08. Use, duplication or disclosure of the software and documentation
I. 08/26 17:24:08. by the U.S. Government is subject to restrictions set forth in a license
I. 08/26 17:24:08. agreement between the Government and iAnywhere Solutions, Inc. or
I. 08/26 17:24:08. other written agreement specifying the Government's rights to use the
I. 08/26 17:24:08. software and any applicable FAR provisions, for example, FAR 52.227-19.
I. 08/26 17:24:08. 
I. 08/26 17:24:08. iAnywhere Solutions, Inc., One Sybase Drive, Dublin, CA 94568, USA
I. 08/26 17:24:08. Adaptive Server Anywhere Developer Edition
I. 08/26 17:24:08.
I. 08/26 17:24:08. 2 logical processor(s) on 1 physical processor(s) detected.
I. 08/26 17:24:08. Networked Seat (per-seat) model. Access to the server is limited to 3 seat(s).
I. 08/26 17:24:08. This server is licensed to:
I. 08/26 17:24:08.     Developer Edition
I. 08/26 17:24:08.     Restricted Use
I. 08/26 17:24:08. Running on Windows 2000 Build 2195 Service Pack 4
I. 08/26 17:24:08. 65536K of memory used for caching
I. 08/26 17:24:08. Minimum cache size: 65536K, maximum cache size: 65536K
I. 08/26 17:24:08. Using a maximum page size of 8192 bytes
I. 08/26 17:24:08. Starting database "sem5" (C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db) at Wed Aug 26 2009 17:24
I. 08/26 17:24:08. Database recovery in progress
I. 08/26 17:24:08.     Last checkpoint at Sat Aug 22 2009 04:21
I. 08/26 17:24:08.     Checkpoint log...
I. 08/26 17:24:08. Performance warning: Database file "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" consists of 3874 disk fragments
I. 08/26 17:24:09.     Transaction log: sem5.log...
E. 08/26 17:24:09. Error: Database cannot be started -- sem5.log is an invalid transaction log
I. 08/26 17:24:09. Error: Database cannot be started -- sem5.log is an invalid transaction log
I. 08/26 17:24:09.
E. 08/26 17:24:10. Database cannot be started -- sem5.log is an invalid transaction log
I. 08/26 17:24:10. Database server stopped at Wed Aug 26 2009 17:24
 

pls help me..

Hay,

Are you recovering the database from a backed up version. It looks like the restore is not able to complete.

Did the setup end in the meantime?

Cheers,
Aniket

Try to rename sem5.log file to sem5.old
Then start the service it should start...

Try running a repair install, it will tell you whether the schema got Corrupted or not

stop all the SEPm service database and SEPM service.
Then rename sem5.log to something else like sem5.baklog
Then start the SEPM services it wil create a new log and the service should also stay started.

Hi,

If the issue gets resolved by this suggestion, we should definitely think of making a KB for it, if it does not exist!

Cheers,
Aniket

This issue occurs when the transcation log is corrupt.

The steps that we need to follow:

1. STOP symantec embedded service

2. navigate to Program files/ symantec /symantec endpoint protection manger /db/sem5.log and rename it to anything sem5.old

3.Now start the services ..the new sem5.log is created.



If this resolves the issue it will well and good or else we have to uninstall and reinstall SEPM.

 Well...I remember resolving issues with this step back in symantec as well as lately i have resolved one of issues in the forum with this step.

Thanks for reply. I still cannot solve the problem, I already rename sem5.log file, stop the service and restart again still same.

error from microsoft management console pop up is;

"Could not start Symantec Embedded  Database service on local computer. The service did not return an error."

Will it be possible for you to reboot the server and see if the service is getting started or not.

If it works well and good..else as per my last post you need to Uninstall and Reinstall SEPM.

Once the SEPM is installed you can run Sylink Replacer or Sylink Remote to bring all the clients back into SEPM. You don't need to uninstall and reinstall the Clients again

https://www-secure.symantec.com/connect/downloads/sylink-remote

 

Verify if there is any running instance of dbsrv9 in the Task Manager > Processes tab. If yes, then end that process

Start the Embedded database service. ( If this does not resolve the issue, then follow the steps listed below )

Go to "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\" and rename sem5.log to sem5.log.old

Click Start, click on Run and Type "CMD" then click OK

In the Command Prompt type: "CD C:\Program Files\Symantec\Symantec Endpoint Protection Manager\ASA\win32\" and press Enter this will change directories to the folder containing dbsrv9.exe.

To force the recreation of sem5.log. Type: "dbsrv9 -f "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db\sem5.db" and press Enter

Click Start, click on Run and Type "services.msc" then click OK and start the Symantec Embedded Database Service

Start the Symantec Endpoint Protection Manager service

 

Our SEP server crashed last week, now we are having a problem with our sem5.db, services are not starting. Tried what is suggested on this site and others but no luck. 

I kept the db folder with the sem5.db, i have no backup though: C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db

I uninstalled SEPM, then reinstalled selected Advanced, for 1000+ clients and pointed it to new directory C:\Program Files\Symantec\SEPM
Then in the Management Server Configuration Wizard, what option do i choose?
1. Install my first site
2. Install an additional management server to existing site
3. Install an additional site

I'm not installing it for the first time, i didn't find anything online that specified what to do in this case.

Since i need to run the synlinkreplacer, i'm not sure how to proceed from here.