Troubleshooting the Data Warehouse connection
Dashboard Server displays performance metrics as graphs, sparklines and bar charts by connecting to the SCOM Data Warehouse using the Dashboard Server application pool identity.
If Dashboard Server is unable to connect to the Data Warehouse you will not see graphs anywhere is Dashboard Server, for example when browsing to the Performance perspective for a server.
If no graphs are showing anywhere in Dashboard Server or Dashboard Server is particularly slow, follow the troubleshooting steps below.
If you are having problems with some Performance graphs see .
Symptoms
No performance graphs shown in Dashboard Server. Performance tiles may be blank or you may see one of the following errors:
connection-failed-blocking: Timeout expired. The timeout period elapsed prior to obtaining a connection from the pool. This may have occurred because all pooled connections were in use and max pool size was reached.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
connection-failed-no-sql-server: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
access-denied-table: Cannot open database "PerformanceDataContext" requested by the login. The login failed. Login failed for user '<application pool identity>'
access-denied-user: Login failed for user 'Application Pool Identity'
Troubleshooting
Is the Data Warehouse connection configured correctly?
Ensure that the Data Warehouse connection is properly configured
There are two parts to the Data Warehouse connection: The Data Warehouse connection string in Dashboard Server, and the permissions to the Data Warehouse database.
Connection
You can check that the Data Warehouse connection string specified is correct for the specified SCOM server by going to the right-hand menu in Dashboard Server ☰ > system > Connections.
Permissions
You should also check that the Dashboard Server application pool account has the OpsMgrReader role for the Data Warehouse database.
For more information on checking both the connection and permissions see How to check and reconfigure the Data Warehouse connection.
If you have migrated the Data Warehouse to a different server, you will need to reconfigure Dashboard Server to use the new location. See How to reconfigure Dashboard Server after moving the Data Warehouse or SCOM server.
Login failed for user
If you see Login failed for user
on a Performance tile this indicates that a SQL login has not been created for the Dashboard Server application pool identity.
access-denied-table: Cannot open database "database" requested by the login. The login failed. Login failed for user 'application pool identity'
access-denied-user: Login failed for user 'Application Pool Identity'
For example, this happens if the Dashboard Server application pool identity has been changed, but not given the OpsMgrReader role for the Data Warehouse database.
To resolve this issue see How to check and reconfigure the Data Warehouse connection or Manually creating the Data Warehouse permissions.
If you see Login failed for user
when running through the setup wizard configuring the Data Warehouse then this means that there is a problem with the SQL login for the user you are logged in with. See "Login failed for user" when configuring the Data Warehouse.
Some graphs are blank or show an error
If you are seeing some graphs in Dashboard Server, this means the Data Warehouse connection is configured correctly. If some Performance tiles show blank or show an error you should troubleshoot these tiles individually.
For example:
timeout-command: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
No values found for the given metric for the last 12 hours at the resolution 'raw/hourly/daily'.
See .
Further Issues
Please contact SquaredUp Support if you experience any problems and reply to the automatic response with the output of the Dashboard Server Diagnostics (see Collecting diagnostic information) and, if possible, a screenshot of the problem.