Change of Service Account gets 669 Error

PDinCA · December 14, 2015 4:59PM

When the service account is changed, via the Services Management Console, the registry permissions should be checked at that time, and failure used to prevent the change.

We just changed from the trial windows user account to use the SQLService account, which was accepted, but the backups all fail with a 669 error.

Please enhance the service itself to detect a login change and fire off the necessary validations.

version 7.7.0.18

petey · December 15, 2015 8:23PM

Changing account credentials via the Services Management Console is independent of the SQL Backup service application, in that SQL Backup is not notified that a change has been made, and thus cannot prevent the change if the new account does not have the required permissions,.

PDinCA · December 15, 2015 9:19PM

So I guess that the SQL Service is too dumb to check any login change for itself?

Is any kind of an enhancement request worth the time to add in Uservoice?

What is the actual best-practice to achieve the goal of changing the service account, if the Management Console is a faux pas!?

Assistance would be appreciated as this isn't the only server affected...

petey · December 16, 2015 1:21AM

When SQL Backup encounters error 669, it would have been recorded in the SQL Backup error log, which is then visible in the SQL Backup GUI. If so configured, an email would also have been sent to the user notifying them of the error when SQL Backup failed to back up or restore a database.

PDinCA · December 16, 2015 1:46PM

Hi Peter,

With due respect, you failed to answer the most important question, "What is the actual best-practice to achieve the goal of changing the service account, if the Management Console is a faux pas!?"

Neither did you comment on whether requesting the means of changing the account, with registry and folder permission checks, intercepted via a login change made by Management Console, would be a waste of effort.

The documentation at https://documentation.red-gate.com/display/SBU7/Permissions under "Changing the SQL Backup Agent service startup account", in fact, actually states that the Management Console snap-in for Services is precisely what to use!

Isn't it time that the "Server Property" known as the Service Account was changeable via the UI, not by some manual method that isn't entirely covered in the documentation under the "Changing the SQL Backup Agent service startup account" heading? That section, at the very least, needs to reference the preceding sections, (that someone looking for precisely the title of the heading would have homed in on, skipping the rest)to ensure that the reader knows that Registry and Folder permissions must be revisited for a successful change to occur... If the UI were to handle it, all the checks that the installer ensured were in place, would be run, and those missing would be automatically set. Eases the pain quite a bit.

PDinCA · December 16, 2015 1:46PM

Duplicate deleted.

Change of Service Account gets 669 Error

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk