Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 5 replies
  • Subscribers 1 subscriber
  • Views 9804 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.
  • 0

    Hello dluneau,

    what worked on the test server should work on the production server as well. Your post gets murky though (no insult intended) after the I also read this article - it's not clear which article(s) you are referring to and what the SEC reinstall [...] failing means.  You did not yet change the password of the production DB User and try the reinstall, did you?

    Christian

    :50332
  • 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
  • 0

    Just to be clear, I'm upgrading from v5.2.1 to v5.2.1 R2.

    :50362
  • 0

    This is what I ended up doing and it worked for my scenario.

    Changed password for win\sophossql
    -          Took snapshot of SEC VM
    -          Proceeded reinstall on top of current v5.2.1
    -          Checked database option
    -          Installation failed – Unable to install Database (a custom action failed)
    -          Reverted VM to earlier snapshot
    -          Ran osql -E -S .\Sophos -Q "exec sp_detach_db 'Sophos521' " from command prompt
    -          Received an error that the database was in use and could not detach.
    -          I opened SQL Management Studio and stopped the running instance
    -          Moved databases to backup directory
    -          Ran SEC installer v5.2.1
    -          Received error (the logged on user cannot connect to SQL instance SOPHOS)
    -          Tried to start instance from SQL Management Studio – failed
    -          Reverted VM to earlier snapshot
    -          Updated password on 5 services running as win\sophossql
    -          Detached the following DBs SOPHOS521, SOPHOSENC52, SOPHOSPATCH52, SophosSecurity
    -          Backed up and moved those DBs from current location
    -          Ran SEC installer (selecting all 3 components to install)
    -          Detach new DBs created and moved to different location
    -          Moved original DBs back to correct location and attached to Sophos instance
    -          Started console and it worked
    -          Ran SEC installer to upgrade to v5.2.1 R2 (selecting all 3 components to install)
    -          Upgraded to v5.2.1 R2 successfully

    The only strange thing is all of my connected endpoints that have been running v10.3 for some time now have the warning status to reboot.  I'm not sure what took place there.

    :50398
  • 0

    10.3.1 was upgraded to 10.3.7 which does require a reboot.

    :50406