Endpoint Protection

connecting to DB failed, can you try repairing the SEPM using add/remove program.

ok will try it and let you know

I tried to repair SEPM but the issue still persist, please HELP

Is this an embedded database or a SQL Server?

There is different troubleshooting steps for each one.  Your error is pointing at a problem connecting to the database. 

IF this is an embedded database, make sure the database service is running.  If it is stopped, you'll get this error.

If its a SQL server:

After that, go to Administrative Tools --> ODBC --> System DSN

You'll see a Symantec connection string.  Configure that and click next on through.  You'll have to enter the username/password of the account that connects to the database.  When you get to finish, you'll get a pop-up, click Test Connection.  If this succeeds, we can proceed with other troubleshooting steps, but if it fails or you can't get past the login/pw then there is a problem with the database connection. 

Run the management server configuration wizard.

Hi

Repair and run Management Server Wizard

Regards

HI all,

yes it is an embedded database, is that the symantec protection management services you are talking about? i checked it is started but when i tried to logging in the console its stop.

i also run repair  and run management server wizard all setting as default issue still persist?

please check attached file.

the DB services is stopped. can you start and verify?

when i start it and then tried to log in the console, it STOPS automatically.

these two services embedded databas and symantec enpoint management service

whats the SEPM version?

whats the size of db.log?

do you have backup of working DB? can you restore?

The DB service should start immediately after you have run the management server config wizard.

seems like you are running 64 bit OS, can you check the odbc connection as per this document

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

SEPM 12.1

the db.log file is it the sem5.db? if so it is 3GB nad unfortunately i have a very small experience in SEPM, there are no BACKUP :(

yes its a 64 bit OS, i followed your instructions, but waht should i configure and how?

Can you guide me? i have run a test in the mean time chek attachment

Have you run the Server configuration wizard?

Path  Start --> Programs--> Symantec --> Symantec Endpoint Protection Manager --> Select Management server configuration wizard.

After that apply above Rafeeq steps

1. • Name: SymantecEndpointSecurityDSN
   • Description:<Anything><anything></anything>
   • Server: Servername\InstanceName (Can be blank as it is localized, otherwise specify default "sem5")
   • Login ID: dba
   • Password: <password></password><password>
     
      
2. Leave the default settings for the remaining items and click Finish
3. Click Test Data Source, and verify that it states "Success"
4. Click OK
5. You should get the result as DB connection as  Success

Hi,

Try to reconfigure your SEPM with ip address instead of host name.

Hi Stephane,

As you mentioned the Symantec Embedded Database service stops straight away when you try to start it, have a look on the db folder. You should have sem5.db, sem5.log, out.log and probably an err.log as you're facing SEPM Database connection issue. This log file may contain further details in order to point out the root cause of your connection issue.

How is the size of your sem5.log so far ? It might need to be recreated in order to maintain the SEPM database service started.

Did you have a disk space issue recently before your SEPM connection issue occur ? If so it might be fair to have a look if your conf.properties file is ok. It might have been truncated as side effect from a previous disk space issue.

Located by default on %\Symantec\Symantec Endpoint Protection Manager\tomcat\etc\

You should have the following lines on your conf.properties file.

scm.agent.root=C\:\\Program Files\\Symantec\\Symantec Endpoint Protection Manager\\data
scm.timer.lu_delta=2
scm.group.lan.sensor.cleanup.threshold.days=30
scm.db.client.bin=C\:\\Program Files\\Symantec\\Symantec Endpoint Protection Manager\\ASA\\win32
scm.timer.group.lan.sensor.minutes=1
scm.exe.dir=C\:\\Program Files\\Symantec\\Symantec Endpoint Protection Manager\\tomcat\\bin
scm.externallog.retryinterval=1000
scm.server.type=master
scm.timer.appcollection=20
scm.shutdown.port=8765
scm.companysize=0
scm.console.log=true
scm.email.package.lifetime.days=45
scm.externallog.retrycount=30
scm.site.name=(there you basically have the Site name you mentioned when you installed your SEPM. It can be customized by running the Wizard server configuration).
scm.securityalertnotifytask.notification.interval=10
scm.webservices.port=8444
scm.log.loglevel= (there by default set on WARNING or INFO, you could set FINEST in order to have further debug info)
scm.extlog.deli=,
scm.server.name=(There the hostname of your SEPM server).
scm.liveupdateclient.path=C\:\\Program Files\\Symantec\\LiveUpdate
scm.timer.logcollection=20
com.symantec.crypto.fips140mode=false
scm.guplistupdatefrequency.seconds=60
scm.http.port=9090
scm.timer.iiscache=10
scm.license.producttype=SEPE (it can be different is you're using Small Business Edition).
scm.server.id=(there an ID corresponding to your SEPM site)
scm.include.legacy.netscanpassword=true
scm.rmmwebservices.port=8446
scm.agent.kcs= (there you should have your SEPM encrypted certificate)
scm.console.reporting.https.port=8445
scm.timer.packagebuilder=60
scm.webserver.http.port=8014 (default communication port used by SEPM/SEP client communication).
scm.db.datasource=jdbc/metadatabase (If this line is not there, you will not be able to connect to your SEPM as it will not know where to look at for your DB).
scm.agent.groupcreation=false
scm.server.port=8443
scm.server.version=(there you will have the entire product version built like for example 12.1 RTM which is 12.1.671.4971, etc ...).
scm.timer.agentstatus=20

If you notice your conf.properties is way shorter than that, log a ticket with the support to get some help to fill the minimum information required in order to re-run the Wizard Server Configuration sucessfully and be able to start all the services without any issue so you'll be able to connect back to your SEPM.

Kind regards,

A. Wesker

Hi Stephane,

Any update so far about your issue ?

Kind regards,

A. Wesker