Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 9806 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrade SEC 5.2.1 to 5.2.1 R2 - Password not know for DB User

dluneau

Trying to upgrade SEC 5.2.1 to 5.2.1 R2 but don't know the DB user password.  Support says to change password on domain account then reinstall 5.2.1 on top of itself using the new password.

All three components are installed on the same server.  I did setup a test server under this same scenario and changing the password on a domain account then upgrading from 5.2.1 to 5.2.1 R2 seemed to work just fine.

I also read this article below and wondered if this would be an option. Deleting the reg key for DB user.

SEC reinstall over to change db un and pw failing

Thanks for taking time to read.

:50282


This thread was automatically locked due to age.
Parents
  • 0

    Christian,

    Appreciate the reply and apologies about murky details.  I running these dev environments to figure out what breaks if I change DB user password before upgrading to v5.2.1.  I've told that everything will break if I change password on DB user account (domain account) proceeded by upgrading to v5.2.1 R2. 

    Do you know what breaks?  Is there a particular setup that is prone to breaking if password is changed?

    :50360
Reply
  • 0

    Christian,

    Appreciate the reply and apologies about murky details.  I running these dev environments to figure out what breaks if I change DB user password before upgrading to v5.2.1.  I've told that everything will break if I change password on DB user account (domain account) proceeded by upgrading to v5.2.1 R2. 

    Do you know what breaks?  Is there a particular setup that is prone to breaking if password is changed?

    :50360
Children
No Data