AppFabric beta 2 error connecting to database

Question

I've installed beta 2 of the AppFabric.  I did this just after installing Visual studio 2010 RC, no earlier versions of 2010 or AppFabric were installed.

I have not been able to get the Persistence mechanism to work

when I open up the AppFabric dashboard, I get the following error (displayed in the top right corder of the dashboard).

Data Source=QUIET\SQLEXPRESS,Initial Catalog=AppFabricPersistence;IntegratedSecurity=False;User ID=sa;Password=!!!!!!" is not a valid monitoring database or is not available

I've tried using both integrated and not integrated security, I did this by re running the AppFabric configuration, and recreating the database, I've also tried just re attaching to the existing database, the configuration utility gives no errors, but the dashboard won't connect.

I'm not sure if it is related, but I'm not getting any values in the "WF Instance History" fields.  I've created a simple workflow service, when I execute methods on that test service an instance does show up in the "Persisted WF Instances", which makes me thing that indeed something is able to connect to the persistence DB, however nothing ever shows up in the instance history.

I am running SQLExpress 2008, and noticed that there are entries in the jobs table of but not in the WFEvents table.

I also noticed the following event in the event viewer.

Unable to connect to the database used by the following application(s) (Default Web Site/DeclarativeServiceLibrary2). Dropping event with event ID 209. This event has occurred 1 times.

Local Service is a sysadmin on the database.

I also noticed the following error

Unable to open database connection for the following application(s) (Default Web Site/DeclarativeServiceLibrary2). Received exception. Message: Invalid object name 'ASStagingTable'.. This event has occurred 157 times.

Any ideas would be very helpful.

thanks

Answer 1

Judging by your error message

"Data Source=QUIET\SQLEXPRESS,Initial Catalog=AppFabricPersistence;IntegratedSecurity=False;User ID=sa;Password=!!!!!!" is not a valid monitoring database or is not available"

it looks like you may be pointing the monitoring system at a persistence database, which will not work.  Can you send a snapshot of your <Microsoft.ApplicationServer><Monitoring> configuration?  If you're using the defaults for monitoring then this section should be in the machine's root web.config file.  If you've made app specific changes then there will be a corresponding section in your application's web.config file.

Thanks.
Adam

Answer 2

it looks like you may be pointing the monitoring system at a persistence database, which will not work.  Can you send a snapshot of your <Microsoft.ApplicationServer><Monitoring> configuration?  If you're using thedefaults for monitoring then this section should be in the machine's root web.config file.  If you've made app specific changes then there will be a corresponding section in your application's web.config file.

Thanks.
Adam

Agree with Adam. I met the similar problem before. Later I found that I was pointing the monitoring system at a persistence database .