Fix – Error while accessing SCOM Application Advisor & Diagnostics console
Recently one of our clients enabled .NET application monitoring through their SCOM environment and configured it as per their requirement so they can get alerts for application down, application slowness, etc.
After configuration, when they did the testing, they found that they are getting alerts for the application as expected however the Application Advisor/Diagnostics links provided under alert description to investigate the alerts were not working.
You can get the detailed information about Application Advisor and Application Diagnostics following below links:
Below is the error message they were getting while accessing both the Application Advisor and Application Diagnostics console.
After clicking Retry button, below was the error message:
When I checked the Application Event on SCOM Web Console server, I found Event ID: 1309 with Event Description Cannot open database “OperationsManagerDW” requested by the login. The login failed.
While checking other Application Event logs, I found exception for OperationsManager DB as well.
Cannot open database “OperationsManager” requested by the login. The login failed.
If the web console does not have sufficient access to the operational database or the data warehouse database, we get this exception while accessing Application Advisor and Diagnostics console.
To resolve this issue, you can have your database administrator run the following SQL Server statement on both the operational database and data warehouse database:
EXEC [apm].GrantRWPermissionsToComputer N'[LOGIN]’
The local and remote parameters are as follows:
- For local installation (Single Server Deployment), the LOGIN is: IIS APPPOOL\OperationsManagerAppMonitoring
- For remote installation (Distributed Environment), the LOGIN is: Domain\MachineName$
Since in our scenario, SCOM DB and DW were installed on a separate machine, we would be choosing second option and will run below query:
EXEC [apm].GrantRWPermissionsToComputer N’ Domain\MachineName$‘
MachineName = Web Console Server hostname.
Run the same query for OperationsManagerDW database as well.
Once the query execution done on the both the databases, open the account login properties and make sure apm_datareader, apm_datawriter and Public roles are selected for both the OperationsManager and OperationsMangerDW databases.
Also, make sure same roles are selected for Data Access Service Account as well.
Now, it’s time to access the Application Advisor and Diagnostics console.
Application Advisor started working as expected.
Application Diagnostics also started working perfectly fine.
Hope this helps.