Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have installed AppFabric onto Windows Server 2012. I checked the prerequisites were installed first and have installed accumulative update 3. I have an instance of SQL Server 2012 installed to SP1 and the OS indicates that all updates have been installed.

When viewing the dashboard I am receiving the error:

Unable to cast object to type 'System.Management.Automation.PSCustomObject' to type 'Microsoft.ApplicationServer.Management.Data.Group...'

I've found minimal information during my Google searches, none of which are providing a solution to the problem.

Can anyone help with this?

share|improve this question
did you ever find a solution to this? – user170556 Apr 21 '13 at 20:17
Unfortunately not. In the end it didn't seem to be getting in the way of the monitoring I was looking at, so I'm just living with the error. – tim_barber_7BB Apr 22 '13 at 9:19

The reason for this error is that the underlying PowerShell cmdlet expects to read AT LEAST ONE record from the AppFabric Persistence DB's table [System.Activities.DurableInstancing].[InstancesTable] , that is related to the WF Service(s) that the current AppFabric Dashboard is shown for.

Once you have at least one record there, the error will stop showing up (in the Dashboard of the current WF Service(s) )

Furthermore, in case you have WF Service in a WOW64 mode ("Enable 32-bit Applications"=TRUE on the Thread Pool of the WF Service) , then AppFabric Dashboard has another issue which is: it ignores the fact that WF Service process is in WOW64 mode and does not read the Persistence connection string from the 32-bit Framework root web.config (as it should be) , but instead reads it (wrongly) from the 64-bit Framework root web.config. Thus if you want workaround this issue, you have to manually edit the 64-bit Framework root web.config in order to substitute the Persistence connection string there with the one from the 32-bit... This will cause that the AppFabric Dashboard of any 64-bit WF Services will now stop showing the Instances info.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.