How can we help you today? How can we help you today?
ClearView
Thanks for the response Eddie.  I am still trouble shooting this issue but I think the problem is more involved. This server has a default SQL2008R2 Developer instance which has had SQL Backup Pro installed and running for a couple of years.  I recently (2 weeks) installed an instance of SQL2017 Developer and moved the dev databases to that instance (Detach/Attach) in SQL2008 compatibility.  I used the same service account when I set up SQL Backup Pro on the new instance.  I can still edit Backup Pro Server Options for the default instance but I cannot edit the options on the new instance.  Notably, some of the server option settings I made during installation did take effect and some did not. I have found this error in the System Event Log.  It occurs each time I try to update the Server Options on the SQL2017 Instance. Component: Software Version Agent  Error: Could not read from the registry sub-key.  Cause: This error can be caused by a corrupt registry or a low memory condition.  Rebooting the server may correct this error. I am still checking the registry permissions and will update the thread when I complete that. I am considering "uninstalling" and reinstalling the server components on the SQL2017 instance.  Do you think that would help or hurt? <Update 2019-08-30 13:00 CDT> I explicitly added the domain service account to the three registry keys for the named instance with Full Control.  I restarted the service and refreshed the connection in the GUI.  I still cannot modify "Server Options" through the GUI. BTW, The default instance Still works fine, even though the Service Account is not explicitly granted permissions on the registry keys. / comments
Thanks for the response Eddie.  I am still trouble shooting this issue but I think the problem is more involved.This server has a default SQL2008R2 Developer instance which has had SQL Backup Pro i...
0 votes