Video Screencast Help

How to reset password on embedded database?

Created: 15 May 2008 • Updated: 02 Mar 2009 | 8 comments
Is it possible to reset the password on the embedded database?  I'm using the dba login, but the password I thought I used did not work on my test server.  I'm having issues upgrading to MR2 and need to unload the database and clean it up.

Comments 8 CommentsJump to latest comment

ryan_w's picture
After searching everywhere I finally figured out my password.  It was stored in the sem5.log file in the  %installationdirectory%\db. (another reason to use different passwords for all systems)  It ended up being a typo on the password!  I'm not sure how I accomplished that.
Anyhow I think it would still be nice to know if it is possible to reset the password.  I could not find it anywhere on the Internet for this DB engine.  Now hopefully I can get MR2 working.
Brett_F's picture

 Where exatly did you see that? I have a copy of the file, I don't reckongize any password...


Abhishek Pradhan's picture

This will help -


 Symantec Endpoint Protection: How to change the database password to a non complex password for use with the Management Server Reconfiguration Wizard 


Let me know if this sorts out the issue.


Abhishek Pradhan, PMP, MCT
Blog: | SIG Lead - Pune IT Pro (Microsoft Pune User Group) |

Brett_F's picture

 Thanks I had looked at that. Problem is we don't have the dB pwd documented, we do not knwo the original. We're usualyy quite detailed in documenting such things, we don't know why this has escaped us. We need a method to reset or discover the original password. Only other article was related to DR which seemed a little drastic to reset a password (uninstall reinstall etc).

Sandeep Cheema's picture

Brett_F , Try this hack at your own risk though I can tell you it's going to work.


1) Go to ODBC, enter the user name and password as blah blah.


2) In the database server name, enter the server name as blah.


3) Goto %programfiles%\symantec\symantec endpoint protection manager\php


4) Change the attributes for php.ini to remove the read only.


5) Open the php.ini file and search for "off", make this to be "on" , for all the errorlog and give the path for error_log = syslog to say c:\test\test.txt but not the root of any drive like c:\test.txt as this will not generate a log, I dont know but this could be a bug with php.


6) Login to SEPM and you should get, "unable to communicate with reporting component"


7) The log file generated will have your username as DBA and the good working password set in originally.


*Edited : Dont forget to make php.ini back to read only once done with the editing.



Message Edited by Sandeep_Cheema on 10-29-2008 10:27 AM

De facto when AV does something, it starts jumping up and down, waving its arms, and shouting...

"Hey!  I found a virus!  Look at me!  I'm soooo goooood!"

Brett_F's picture

 Yes that did the trick, it was what we thought it was, why the special character article mentioned didn't resolve, thats another issue thoguh, at least we've confirmed the issue and can fix.


 Yes, all reset back to normal and can log in no errors, worked great.


Mike.Rhodes's picture

Not sure if this is a bug that Symantec has since fixed, but this did not work for me :(