Replies: 1 comment
-
Hi, I think the service could not start due to a login failure is likely down to one of these issues:
Note: A group managed service account can be a good option. It avoids the need to rotate passwords manually and/or set them never to expire. The service will work fine as a normal domain account though. The service account needs permissions to write to the C:\DBADash folder to create the log folder and log files. The service account also needs permissions to connect to your monitored instances and repository database. See here for more info. I don't think either of these issues will cause the login failure - it's likely to be one of the issues above. To troubleshoot you could try:
The above all works and you still get the logon failure it could be down to the logon as a service right. Hope this helps |
Beta Was this translation helpful? Give feedback.
-
Hello, thank you for your efforts in developing DBADash. I've come across an error during the setup process. In my environment, a domain user account is used to install the DBADash Agent as a Windows server service. Although the installation completes successfully, I encounter an issue when attempting to start the service Logon failure and failing to create logs folder
'Cannot strat service "DBADashService' on the computer The service did not start due to logon failure.'
'Log floder does not exist c:DBADash\Logs . This is created when the service is started'
Beta Was this translation helpful? Give feedback.
All reactions