I may be missing something obvious here, but at the moment I'm not sure what it is. It may be all one issue, or three separate ones.
I have a windows litespeed service account set up, but when I go to configure remote servers, they are attempting to use a completely different account and saying it does not have sysadmin privileges. Any ideas why, and how to fix it?
After configuring remote servers with local repositories, the central console still says that it does not have a local repository configured. Is that due to the service account being incorrect?
I need to use a network location for backups. The backup jobs appear to run successfully, but no backups appear in the specified location. I would assume the jobs would fail in the case of not enough permissions?
Perhaps I've just been staring at this too long, and as I said, missing something ridiculously obvious. But any suggestions would be appreciated!
Also for this issue... “After configuring remote servers with local repositories, the central console still says that it does not have a local repository configured. Is that due to the service account being incorrect?” Check the Litespeedsettings.ini file located here C:\ProgramData\Quest Software\LiteSpeed\SQL Server For a section like the below [activity <your SQL instance name>] serverauthentication =0 serverusername = serverpassword =YMVbtJPOsgyu localdatabase=LiteSpeedLocal localauthentication=0 localusername= localpassword=YMVbtJpHTYSTR statsenabled=true pushenabled=true pushjobstatsenabled=true If its not there then the message is correct there is no Litespeed local for that SQL instance. If the section is there, and populated correctly, then most likely the problem is the access rights to the file (as mentioned in my prior post) Hope that helps, -Ben-