Hi,

I'm trying to install SEPM 12.1.2 on a W2K8 R2 server with an embedded database.

During the creation of the embedded database via the wizard I get a "failed to connect to the database. Please make sure your login and password are correct".

I don't understand that message as the database's just been created.

I also found this in the install_log file:

hello,

As per error you have put wrong user name and password.

Can you share error snap shot

Did the Embedded database services are starting mode ?

Hi Manish,

Thanks for your answer.

 I understand the message but as it's a fresh install with a new password created during the installation, how could it be a "wrong" password ?

 Regards,

Eric

Read it

Migration from SEP 11 to SEP 12.1 wizard terminates without warning. In install_log.err "Creating database failed. SEPM's error code is [-2000]"

Check the Embedded database services are starting or not in services.msc

How much disk space avaialbe in your system drive where you install SEPM?

Yep, all the services are started.

I can't find any MSIxxxx.log file

I have 48 GB available on the drive where I'm installing SEPM.

Check the comment of iman D from the below thread

https://www-secure.symantec.com/connect/forums/failed-connect-sql-database-during-sepm-instalation

Iman Comment

hello,

Can you post catalina.out and scm-server-0.log

Don't have any catalina.out nor scm-server-0.log :-(

hello,

Try to repair SEPM console for add remove programe

Have you check my attach above comment?

I checked it but it seems that it's more about SQL database. Mine is embedded one.

Check the scm-server-0.log in Program Files\Symantec\Symantec Endpoint Protection Manager\Tomcat\Logs

also try to repair SEPM

Hello,

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

It might be a stupid question as SEPM uses apache but: I realize there's a wsus server with Windows Internal database (service) on the same server.

Could it be a problem ?

Thanks.

OK. So I think I found out what was wrong. I edited the hosts file and realize that the loopback entry 

127.0.0.1 locahost   was commented (#). I got rid of the # and the installation went fine !

No idea why it was like that though.

Thanks everybody for your help !

Hello,

There would be no issues affecting WSUS.

Infact, you are doing a good job of Migrating to the Latest version of SEP 12.1.

WSUS uses IIS and SEP 12.1 does not use IIS, it uses Apache.

There is no inherent incompatability.  I do, however, recommend monitoring for performance. 

Both SEPM and WSUS will be competing for the same resources (network ports, bandwidth, CPU cycles, hard drive space) while keeping your environment up-to-date. 

If you have a very large environment and there are any signs that WSUS or SEPM is struggling to keep up with its job, it would be a good idea to move each to a dedicated server.  The best admins take stability and security very seriously, and ensure that the tools which look after that (SEPM and WSUS) have plenty of resources to do their job right.

Hope that helps!!

Hello,

Thanks for updating all of us with the solution.

Nice to hear the issue is resolved.

Thanks Mithun !