cancel
Showing results for 
Search instead for 
Did you mean: 
Create Post
Level 12

MSSQL Auditor - Won't start with domain user

Jump to solution

Hello,

I'm fairly new to the MSSQL Auditor and I'm trying to get it working.  I had it working with just a single server and I wanted to expand that server to monitor others.  I added the other servers and told the service to run as a specific account that has Sysadmin on the servers.  When I try to start, I get the error message:

"Unable to start MSSQL Auditor. Verify that the user has the proper credentials to do database auditing by using the AuditorConfig Test Button."

I run the test and get the following:

01-13-16 09:34:53.12 User 'domain\user' authenticated

01-13-16 09:34:53.12 

01-13-16 09:34:53.13 connecting to SQL Server...connected

01-13-16 09:34:53.13 checking for auditing capability...verified

01-13-16 09:34:53.13 sqlserver1.fqdn: Tests succeeded

01-13-16 09:34:53.13 

01-13-16 09:34:53.15 connecting to SQL Server...connected

01-13-16 09:34:53.15 checking for auditing capability...verified

01-13-16 09:34:53.15 sqlserver2.fqdn: Tests succeeded

01-13-16 09:34:53.15 

01-13-16 09:34:53.17 connecting to SQL Server...connected

01-13-16 09:34:53.17 checking for auditing capability...verified

01-13-16 09:34:53.17 sqlserver3.fqdn: Tests succeeded

01-13-16 09:34:53.17 

01-13-16 09:34:53.17 Testing completed

(Anything italicized has been changed from the values on the screen.)

The tests are passing but the service still won't start, any thoughts?

Thanks!

0 Kudos
1 Solution

Thanks for the help, it lead me in the correct direction!   Turns out the user account I was trying to use didn't have the "logon a service" right on the server it was installed on.  I gave it that right and it started right up!

View solution in original post

2 Replies
Level 15

I just fought this for a couple days.  Part of my issue was that I broke the Local Profile Service in Windows, so if you've got users getting logged into TEMP profiles, that seems to break things.

Second, I found that the Windows Service Manager could start/stop the MSSQL Auditor service, and I would see logs and data getting created.  You may see if that works.

Third, does domain/user have rights to the C:\Program Files (x86)\SolarWinds Log and Event Manager MSSQL Auditor\logs directory?  If you start the Service in Windows, do you see logs in this directory?

Fourth, in that MSSQL Auditor folder is MSSQLAuditor.config.  Are your servers and all getting saved to that file?  (I had to manually edit mine with Notepad++ to get things to stick)

Thanks for the help, it lead me in the correct direction!   Turns out the user account I was trying to use didn't have the "logon a service" right on the server it was installed on.  I gave it that right and it started right up!

View solution in original post