SEPM Configuration Wizard Problem

[Migration User]

Hi everyone

I have a server that was running SEPM, but I had to change the database port as another product needed that port. I switch from 2638 to 2639.

The database port change went well, but somehow the network identify of my server changed, as the encrypted password seem to no longer work. The SEPM login throw me a Unknow server error.

 

In db_connection-0.log I now see that; (Part in french, but it mean bad username or password)

Caused by: java.sql.SQLException: [Sybase][JDBC Driver][SQL Anywhere]Le mot de passe ou l'ID utilisateur est incorrect
 at sybase.jdbc4.sqlanywhere.IDriver.makeODBCConnection(Native Method)

 

I went in my ODBC32 to re-entered the password, and the test worked good, but the error persist.

Tested with dbisqlc.exe and It work with my ODBC connector & my password too, but the error still persist.

 

My guess was, in ROOT.xml, the password is not good, aka in that line (... password="{V01}ENCRYPTEDTEXT" ...)

 

So my next step was to try to run the Configuration Wizard to regenerate all that stuff, but, at my surprise I can't, it still detect old port... See image

 

 

I looked around on my server to find that the other tool use a SQLANY's database like SEPM, an old version, but that seem to block the wizard.. Someone know how to force the port in that wizard ? or can help me to bypass that bad password error.

 

btw, tired to repair, but no good, the wizard still stop at the same place after the repair.

 

Thanks a lot

 

 

 

 

Phillip

 

[ℬrίαη]

Can you try running the symhelp tool on it to see if it throws any errors?

About Symantec Help (SymHelp)

[Migration User]

I assume you used this article to change your database port?

Please check if all necessary services are running (embedded database, SEPM, SEPM Web Server and so on).

Do I understand you correctly that the connection to database works fine, but you cannot enter the SEPM console?

If you even have problems to connect to the database: Did you ever change the admin's password? Be aware that the password of the embedded database is the initial password of the SEPM admin. So if you have changed the admin's password in the meantime, the current admin's password won't work for the database, you have to use the first admin's password you ever created.

I would not touch the encrypted password in root.xml.

[Rafeeq]

You first need to change the value in the registry only then you will see that in the congifugration wizard , follow this document

How to use a custom port for the Embedded database on Symantec Endpoint Protection 12.1

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

[Migration User]

Brian, Thanks for the link !

There is the error I see. The new error that show me is the one with port 8014.

For the process dbsrv12.exe that use the por 2638, it's the other product, as the port 2639 is listening for SEPM.

 

 

 

greg12, Yes, you assume corrcetly. I did not change the password. Strangley when I use the tool from symantec dbislqc.exe the password enter just fine. I validated, and the server was changed of domain. Thus a reason I was wondering if that change did broke something too. (as in the tomcat/log/db_connection I really see only a lot of bad password error)

Refeeq, I did that first. Netstat -ano list the database process under the new port and the odbc test connect just fine .

 

 

Thanks! Let me know if you need more log

 

 

 

Phillip

 

[Migration User]

Hi, found the issue, in the wizard I stop the dbservice and I had to replace the DB with the default's one from the install media. (even if it's the setup that created the one on disk). the bad password prompt did not occured after.