I have a big problem,  A few days ago am not able to lo ggin to symantec endpoint 12.1 manager console, giving message " failed to connect to the server, make sure that the server is running and your session has not timed out.  if you can reach the server but cannot logon, make sure that you provided the correct parameters,

i thought i forgot the password thus reset it by clicking on resetpass on windows C, program files (X86), symantec, symantec endpoint protection manager, tools, resetpass but am getting message, cannot connect to database.

after searching on net, i found that the embedded database, sem5 is the problem, i have tried every solution on the forums but it cannot access the database.  I tried to correct the parameters of "Asanys" in regedit but i can't even find the registry key.

Can someone plz help me as i don't want to reinsall the manager, i got 15 pcs connected to the symantec server.

btw, i have win7 64 bit OS

regards

AMIIRAH

Considering the time. I would suggest you to uninstall SEPM, reinstall a new sepm.

use this option to push the communication setting  so that your clients will communicate with new SEPM

http://www.symantec.com/business/support/index?page=content&id=TECH199124

Or Try this

http://www.symantec.com/business/support/index?page=content&pmv=print&impressions&viewlocale&id=TECH134782

Have you tried repairiing SEPM from add/remove programs.?

Hi,

Please check below threads for the same.

http://www.symantec.com/business/support/index?page=content&id=TECH134782

https://www-secure.symantec.com/connect/forums/sep-manager-failed-connect-server

https://www-secure.symantec.com/connect/forums/failed-connect-server-make-sure-server-running-and-your-session-has-not-timed-out

http://www.symantec.com/business/support/index?page=content&id=TECH104931

https://www-secure.symantec.com/connect/forums/failed-connect-server-25

Just to clarify then, you are currently unable to start the Symantec Embedded database service, correct?

What's gettong logged in the err.log file in the below folder?

C:\Program Files\Symantec\Symantec Endpoint Protection Manager\db

Hi

Repair and Run Management Wizard

Regards

Hi Amiirah,

Step 1: Check if all your symantec services are started in services.msc

Symantec embedded database

Symantec endpoint protection manager 

Symantec endpoint protection webserver

If they are not started, make sure all three process are started.

Step 2:  If issue still presists run a management server configuration wizard

To reconfigure an embedded database

1. Stop the Symantec Endpoint Protection Manager service by selectingStart > Programs > Administrative Tools > Services.
2. Locate Symantec Endpoint Protection Manager and then right-click to select Stop.
3. Click Start > Programs > Symantec Endpoint Protection Manager > Management Server Configuration Wizard.
4. In the Welcome to the Management Server Configuration Wizard screen, click Reconfigure the management server.
5. Click Next to begin the reconfiguration.
6. Edit the name of the computer on which the management server is installed in the Server name box.
7. Edit the HTTPS port number that the management server listens on in the Server port box.

The default port number is 8443.

8. Edit the location of the server data folder or browse to the root folder where data files are located.

The root folder includes backups, replication, and other management server files.

The default pathname is C:\​Program Files\​Symantec\Symantec Endpoint Protection Manager\data)

9. Click Next.
10. Click Embedded database.
11. Click Next.
12. Type the number of the server port in the Database server port box.

The default port number is 2638.

13. Type the password in the Password box.

This field cannot be blank.

14. Type the password again the Confirm Password box.
15. Click Next.

The database creation takes a few minutes. A database message appears during that period of time if the management server service is still running.

16. You can choose to Start Symantec Endpoint Protection Manager and Start Management Console.

These options are selected by default.

17. Click Finish.

You completed the reconfiguration of the database. If you kept the start options selected, the console logon appears.

Referred article http://www.symantec.com/docs/HOWTO27478

Step 3: if issue still presists

Open the driver in which you had installed SEPM and locate to symantec endpoint protection manager folder-> tomcat-> logs-> scm-server-0.log

post the log in this thread for us to analyze it.

Hope this helps thanks you

Hi Amirrah

Do you need any more help

Regards

hi jeshrel,

i followed the steps, i get the message " embedded database is not started"

please find attached log file2014-03-09 23:08:15.132 THREAD 1 SEVERE: ================== Server Environment ===================
2014-03-09 23:08:15.195 THREAD 1 SEVERE: os.name = Windows 7
2014-03-09 23:08:15.195 THREAD 1 SEVERE: os.version = 6.1
2014-03-09 23:08:15.195 THREAD 1 SEVERE: os.arch = x86
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.version = 1.6.0_24
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.vm.version = 19.1-b02
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
2014-03-09 23:08:15.210 THREAD 1 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Tools\..\tomcat
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.user = null
2014-03-09 23:08:15.210 THREAD 1 SEVERE: user.language = en
2014-03-09 23:08:15.210 THREAD 1 SEVERE: user.country = US
2014-03-09 23:08:15.210 THREAD 1 SEVERE: scm.server.version = 12.1.671.4971
2014-03-09 23:09:37.329 THREAD 1 SEVERE:
java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Database server not found
    at ianywhere.ml.jdbcodbc.jdbc3.IDriver.makeODBCConnection(Native Method)
    at ianywhere.ml.jdbcodbc.jdbc3.IDriver.connect(IDriver.java:769)
    at java.sql.DriverManager.getConnection(DriverManager.java:582)
    at java.sql.DriverManager.getConnection(DriverManager.java:207)
    at ianywhere.ml.jdbcodbc.jdbc3.ASADataSource.getConnection(ASADataSource.java:313)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:520)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:417)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:402)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:392)
    at com.sygate.scm.server.db.util.DatabaseUtilities.testDBConnection(DatabaseUtilities.java:2849)
    at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2829)
    at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2655)
    at com.sygate.scm.tools.DatabaseFrame.main(DatabaseFrame.java:1201)

this log

01/09 21:26:01. Database cannot be started -- sem5.log is an invalid transaction log
01/12 21:18:37. Database cannot be started -- sem5.log is an invalid transaction log
01/19 21:21:50. Database cannot be started -- sem5.log is an invalid transaction log
01/20 03:19:54. Database cannot be started -- sem5.log is an invalid transaction log
02/13 03:02:48. Database cannot be started -- sem5.log is an invalid transaction log
02/20 03:44:13. Database cannot be started -- sem5.log is an invalid transaction log
03/03 02:18:32. Database cannot be started -- sem5.log is an invalid transaction log
03/09 23:05:47. Database cannot be started -- sem5.log is an invalid transaction log
03/09 23:20:05. Database cannot be started -- sem5.log is an invalid transaction log
03/10 01:49:20. Database cannot be started -- sem5.log is an invalid transaction log
03/10 02:09:54. Database cannot be started -- sem5.log is an invalid transaction log
03/10 02:10:17. Database cannot be started -- sem5.log is an invalid transaction log
03/10 02:40:04. Database cannot be started -- sem5.log is an invalid transaction log
03/10 02:40:58. Cannot access "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db": file does not exist
03/10 02:41:07. Cannot access "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db": file does not exist
03/10 02:41:27. Cannot access "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db": file does not exist
03/10 02:41:54. Database cannot be started -- sem5.log is an invalid transaction log
03/10 02:43:07. Database cannot be started -- sem5.log is an invalid transaction log
03/10 02:45:27. Database cannot be started -- sem5.log is an invalid transaction log
03/10 02:45:57. Database cannot be started -- sem5.log is an invalid transaction log
03/10 23:50:57. Database cannot be started -- sem5.log is an invalid transaction log
03/10 23:51:48. Cannot access "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db": file does not exist
03/11 00:16:40. Database cannot be started -- sem5.log is an invalid transaction log
03/11 00:18:56. Database cannot be started -- sem5.log is an invalid transaction log
03/11 00:19:24. Database cannot be started -- sem5.log is an invalid transaction log
03/11 00:20:07. Database cannot be started -- sem5.log is an invalid transaction log
03/11 01:00:28. Database cannot be started -- sem5.log is an invalid transaction log
03/12 22:01:10. Cannot access "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db": file does not exist
03/12 22:01:18. Cannot access "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db": file does not exist
03/12 22:14:31. Cannot access "C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\db\sem5.db": file does not exist
 

hi sameer,

try to repair but getting message "fatal error during installation"

It's best bet you can perfrom Disaster Recovery method,You can also raised support ticket for your issue regarding.

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

You can follow disaster recovery process to sort out your issue.

http://www.symantec.com/business/support/index?page=content&id=TECH160736

Hi Amiirah,

Thats why I told you to unisntall / reinstall rather than wasting time to fix the db, it will be good learnign but hard to repair corrupt DB. 

Download the latest SEPM from fileconnect

https://fileconnect.symantec.com 

put the serial number, download 12.1.4 Ru4a,

Uninstall SEPM, 

Install new version

use this option to connect your previous systems to report to new sepm

http://www.symantec.com/business/support/index?page=content&id=TECH199124

the entire process will not take more than 2 hours, all the best, check back in if you need any help

hi Jeshrel cyril,

it says " embedded database is not started"

and the log file message is below:

2014-03-09 23:08:15.132 THREAD 1 SEVERE: ================== Server Environment ===================
2014-03-09 23:08:15.195 THREAD 1 SEVERE: os.name = Windows 7
2014-03-09 23:08:15.195 THREAD 1 SEVERE: os.version = 6.1
2014-03-09 23:08:15.195 THREAD 1 SEVERE: os.arch = x86
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.version = 1.6.0_24
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.vendor = Sun Microsystems Inc.
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.vm.name = Java HotSpot(TM) Client VM
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.vm.version = 19.1-b02
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\jre
2014-03-09 23:08:15.210 THREAD 1 SEVERE: catalina.home = C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\Tools\..\tomcat
2014-03-09 23:08:15.210 THREAD 1 SEVERE: java.user = null
2014-03-09 23:08:15.210 THREAD 1 SEVERE: user.language = en
2014-03-09 23:08:15.210 THREAD 1 SEVERE: user.country = US
2014-03-09 23:08:15.210 THREAD 1 SEVERE: scm.server.version = 12.1.671.4971
2014-03-09 23:09:37.329 THREAD 1 SEVERE:
java.sql.SQLException: [Sybase][ODBC Driver][SQL Anywhere]Database server not found
    at ianywhere.ml.jdbcodbc.jdbc3.IDriver.makeODBCConnection(Native Method)
    at ianywhere.ml.jdbcodbc.jdbc3.IDriver.connect(IDriver.java:769)
    at java.sql.DriverManager.getConnection(DriverManager.java:582)
    at java.sql.DriverManager.getConnection(DriverManager.java:207)
    at ianywhere.ml.jdbcodbc.jdbc3.ASADataSource.getConnection(ASADataSource.java:313)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDataSourceDBConnection(DatabaseUtilities.java:520)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:417)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:402)
    at com.sygate.scm.server.db.util.DatabaseUtilities.getDefaultDatabaseConnection(DatabaseUtilities.java:392)
    at com.sygate.scm.server.db.util.DatabaseUtilities.testDBConnection(DatabaseUtilities.java:2849)
    at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2829)
    at com.sygate.scm.server.db.util.DatabaseUtilities.initDataSource(DatabaseUtilities.java:2655)
    at com.sygate.scm.tools.DatabaseFrame.main(DatabaseFrame.java:1201)

Hi

Please follow the disaster recovery  for SEP 12.1

http://www.symantec.com/business/support/index?page=content&id=TECH160736

Regards

hey guys,

am going to the last solution, will reinstall sep.

clients pcs are not getting update since many days, can't wait longer.

thanks very much to all of you.

regards

amiirah

Hi

Please mark as a solution which ever you feel is right

Regards