Comments
1 comment
-
Support pointed me toward the solution:
Starting with 7.0.6, the account under which the IIS Application Pool for the SQL Monitor website is running must have direct access to SQL Monitor's database. In my case, I had the SQL Monitor application pool set at its default identity "ApplicationPoolIdentity". I changed it to use the same AD credentials that SQL Monitor uses to connect to its database, and everything immediately started working.
Add comment
Please sign in to leave a comment.
We're running it on Windows Server 2008 R2 with IIS 7.5. It was running perfectly fine with version 7.0.4. I verified the IIS settings against the SQL Monitor documentation, and nothing appears to have changed. IISReset and rebooting the server seemed to make no difference, nor did uninstalling and reinstalling the SQL Monitor Web application.