Got an interesting scenario unfolding here. Last week user's couldn't authenticate to the web. I wanted to look at accounts table in Database Manager but couldn't run Database Manager as it could not connect. Error message stated that the account involved ('solarwinds') was expired and locked. We unlocked and unexpired and a Windows dialog forced us to change password. We did so and gave Config Wizard new credentials. Took a few attempts as Windows detected the password wasn't complex enough. We ultimately had one work (complex enough). Config wizard ran without issue and users logged in...for a few hours until issue presented again. Ran through the same exercise and then fixed (temporarily with the same steps). I noticed at the time the config mgmt jobs were running unsuccessfully using the same account during a time when web access still worked (same account name 'solarwinds'). Account locked another time and I decided to create a new account (name not 'solarwinds'). Ran through config wizard and used those new credentials for DB connectivity. No issues since last week with user authentication. However since that time NCM jobs won't run. They fail silently. Logs for jobs indicate that a database migration is in progress. If this was a new install of 7.3, I would expect that, but we upgraded last year and I remember the database migration very clearly.
Something somewhere has NCM unable to run jobs or for that matter run the NCM Win32 application. When trying to launch NCM, seeing error message 'The SolarWinds NCM software was unable to get data from SQL server. Original exception details: (Login failed for user 'solarwinds').
Interestingly the account NCM is trying to use for communicating with the SQL server is not the new one I created and then updated via config wizard. But at least it's not locking out the new account due to different name. There is nowhere in config wizard to tell NCM about new credentials, and it doesn't seem to learn them from the database portion of config wizard that completes without issue.
I have opened a support case and generated a diagnostic file. I'm reviewing the NCM portions to determine what (if anything) I would be allowed to provide. With support, I copied an earlier job and made it download configs from only one node. That job fails in the same way--unable to start due to database migration in progress.
Anyone seen this before?