LiteSpeed

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

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!

  • 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-

  • 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-

  • The service account I am referring to is the one that you are prompted to supply during configuration. I provide DOMAIN\dsvc_litespeed. The one I get the prompt about is dsvc_sa_servername, and this is also the service account the jobs attempt to "run as." I'm not sure where this one comes from, as I have not supplied that anywhere.

    I feel like I'm missing or not understanding something correctly during setup; my personal user account has all the admin rights necessary to install, but I do want litespeed to run using dsvc_litespeed. Our enviornment can be quirky (we're going through some security changes/upgrades/confusion), and occasionally things happen like accidentally disabling wrong user accounts...

    I will definitely check on the files and access as you suggested here and below, and then open a support case as necessary/with whatever information I find.

    Thank you!!
  • No problem always happy to help!

    As a FYI....

     

    You most likely are talking about this section seen during instance configuration.

     

     

     

     

     

     

    This is the account used to run the Litespeed activity service (below screenshot) and it's only job is to replicate data between the Local and central repositories.

     

    The other accounts you could supply, but are not really prompted for, during instance configuration would be used to build the repositories and install the extended stored procedures.  Please note there is no Litespeed service the Litespeed jobs run either as the user starting them, as in the case of a Litespeed command line operation, or the SQL server startup account.

    This "dsvc_sa_servername" sounds like your SQL server startup account which will need sysadmin rights for many Litespeed functions. Because of its importance the installer (Instance configuration) will check if the service account has that role and warn if it does not.

    If it already has that role the message can be ignored as in some older versions of Litespeed this was a false message.

    We can go over this with you during a support call and check your configuration.

    Hope that helps,

    -Ben-