I've recently deployed Appfabric on a web farm whereby the Appfabic hosts (win 2008 R2) connect*"There was a error executing the instance query. See inner exception for details.... The specified database is not a valid Monitoring database or is not avaialble.
to a Sql server 2008 R2 instance on another host via a user in the <Mydomain\AppFabricAdmins> group. However,
on each dashboard load, the "Error(s) encountered"* status is displayed on the dashboard AFTER the query stats have been displayed. Clicking on the Errors Encountered renders the following:
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
Trying to troubleshoot the problem, Sql profiling on the loading of AppFabric showed various select statements around AsEvents view with ASEventSources, AsWcfEvents, WfEvents, ASWfInstances from the Monitoring DB and [System.Activities.DurableInstancing].[Instances] from the Persistence DB. I reran all the t-sql commands captured in the trace in SSMS on the AppFabric host as the same user loading the dashboard, successfully. I also increased the Connect timeout on the persisitence and monitoring connection strings, and there's nothing being logged into event viewer by AppFabric regarding the error either or the Sql log on the DB server.
SO my question is, has anyone encountered the "specifed database is not a valid monitoring database" error when loading AppFabric and resolved it? Perhaps if I could capture the exact query/store procedures invoked by AppFabric dashboard when first loaded (in case I havnt captured them all), I could try and reproduce the querie(s). I suspect its a premissions issue accessing part of the schema or alike.
- 編集済み BrianBoru 2012年5月3日 2:15
Persistance and Monitoring require 2 different schemas , and can reside on the same or different databases.
IS the monitoring schema database actually configured with the right permissions?
1)check if Both these schemas are configured with the right permissions using App Fabric Configuration Tool.
2) check if the windows services AppFabricEventCollectionService and AppFabricWorkflowManagementService are configured to run using accounts that are members of the AS_Admin
3) Additional error infomation would be available in the event log under Application and Services-->MIcrosoft--> Windows-->Appliction Server - System Services --> Admin
For additional App Fabric Architecture info, see
- 編集済み A.ELan 2012年5月9日 23:29