• State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 12 subscribers
  • Views 7661 views
  • Users 0 members are here
Options
Related
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

Windows service accounts, litespeed local repository not configured, network backup location

kmanni
over 6 years ago

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!

Parents
  • 0 over 6 years ago

    Hello,

     

    When you say "litespeed service account" to what service are your referring to? (the only Litespeed "service" is the activity manager)

     Please note that the message "does not have sysadmin privileges" is referring to the SQL server startup account.  If your SQL server startup account has those rights the message can be ignored.

     

     “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?”

     

    The only service account that matters here is the SQL server startup account for the server in question.

    I would check it has “full access” to the following directory, “C:\ProgramData\Quest Software\LiteSpeed\SQL Server” and file “litespeedsettings.ini”. If this does not help we will need to review your installer log. So please open a support case.

     

    "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?"

    I would open a support case for this issue. There can be many causes (not all are errors) and a log file will need to be reviewed to see what is causing the issue. But you are correct a “failed to write” problem, no matter the cause, would produce a failed job.

     

    Hope that helps some,

    -Ben-

Reply
  • 0 over 6 years ago

    Hello,

     

    When you say "litespeed service account" to what service are your referring to? (the only Litespeed "service" is the activity manager)

     Please note that the message "does not have sysadmin privileges" is referring to the SQL server startup account.  If your SQL server startup account has those rights the message can be ignored.

     

     “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?”

     

    The only service account that matters here is the SQL server startup account for the server in question.

    I would check it has “full access” to the following directory, “C:\ProgramData\Quest Software\LiteSpeed\SQL Server” and file “litespeedsettings.ini”. If this does not help we will need to review your installer log. So please open a support case.

     

    "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?"

    I would open a support case for this issue. There can be many causes (not all are errors) and a log file will need to be reviewed to see what is causing the issue. But you are correct a “failed to write” problem, no matter the cause, would produce a failed job.

     

    Hope that helps some,

    -Ben-

Children
No Data