We have some PowerShell scripts that we start from a Windows service. This produces some unpredictable behaviours. By default the service runs with the "Local System" account. Mostly this works well. Sometimes we get the following message:
- Code: Select all
Get-VBRServer : Microsoft SQL server hosting the configuration database is
currently unavailable. Possible reasons are heavy load, networking issue,
server reboot, or hot backup.
Please wait, and try again later.
When then changing the account to e.g. a local administrator account. The "Get-VBRServer" runs fine again. The Veeam server is running fine all the time. I suspect the error message is due to some account right problems. Unfortunally I cannot figure out which rights this might be. So if some might give me I hint I would do some further researching.