Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 1 subscriber
  • Views 16459 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

Changing database account from local to domain issues

asester

All,

I'm trying to change the account that runs the database from the original local account that was used when the server was first built to a domain account (I didn't do that btw....).  Everything I've read is that in order to change it, you must re-run the installer for SEC, select the Database option and Modify the install.  However, when I do this I get the error:  "The logon user cannot access the database created during a previous installation."  Obviously I cannot proceed from here.

I have tried changing the account and password that run the services for SEC....no go.  SEC essentially crashes at that point.  Any other suggestions?  I don't believe the original accounts password has changed since the initial install, so I'm not sure why I'm getting this error.

With that being said, it's server 2008 R2 and I was contemplating moving forward to server 2012 R2....as long as I keep the same name and IP address, import all policies etc, would there be any issues with endpoints communicating back to the console?  Or am I going to have to re-deploy?  I do have 1 relay server setup too....

Regards,

Adam

:54041


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

    Hello Adam,

    thanks ... now the only suspect lines are the ones with Checking for presence of database: SOPHOSENCxx as they don't name an instance. Everything else seems correct. I'm still on 5.2.1 so I can't verify that the 5.2.2 setup.exe "normally" inserts an instance (and the correct one). I'm reluctant to assume that the 5.2.2 Modify workflow is broken - but then I don't have a better explanation. I'm not in the mood to upgrade right now to answer this question :smileywink:.

    Guess unless someone who's modified a 5.2.2 installation comes forward you better call Support (I'd check the bootstrapper log of the initial install or upgrade to make sure that an instance is named on the Checking for lines - but that's purely academic interest).   

    Christian

    :54387
Reply
  • 0

    Hello Adam,

    thanks ... now the only suspect lines are the ones with Checking for presence of database: SOPHOSENCxx as they don't name an instance. Everything else seems correct. I'm still on 5.2.1 so I can't verify that the 5.2.2 setup.exe "normally" inserts an instance (and the correct one). I'm reluctant to assume that the 5.2.2 Modify workflow is broken - but then I don't have a better explanation. I'm not in the mood to upgrade right now to answer this question :smileywink:.

    Guess unless someone who's modified a 5.2.2 installation comes forward you better call Support (I'd check the bootstrapper log of the initial install or upgrade to make sure that an instance is named on the Checking for lines - but that's purely academic interest).   

    Christian

    :54387
Children
No Data