AppFabric 1.1 Monitoring not working on workgroup server? (netlogon dependency)

Question

Hi there,

I'm almost pulling my hair out. I'm trying to install Windows Server AppFabric 1.1 for our developer staff on a web server that's going to be housed externally - therefore it is workgroup only, no domain membership. OS is Windows Server 2008 R2 SP1 German.

AppFabric 1.1 installed fine, Persistence configuration works - but Event Collection Monitoring cannot be set up using the wizard:

System.InvalidOperationException: Der Dienst AppFabricEventCollectionService kann nicht auf dem Computer . gestartet werden. ---> System.ComponentModel.Win32Exception: Der Abhängigkeitsdienst oder die Abhängigkeitsgruppe konnte nicht gestartet werden
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei System.ServiceProcess.ServiceController.Start(String[] args)
   bei Microsoft.ApplicationServer.Configuration.Utilities.ServiceControllerHelper.StartWindowsService(String serviceName)
   bei Microsoft.ApplicationServer.Configuration.WorkerPage.OnBackgroundWorkerDoWork(Object sender, DoWorkEventArgs e)

When trying to start AppFabricEventCollectionService manually, I get an 1068 dependency error pointing to the Netlogon service in Eventlog ("Der Dienst "AppFabric-Ereignisauflistungsdienst" ist vom Dienst "Anmeldedienst" abhängig, der aufgrund folgenden Fehlers nicht gestartet wurde: Der Vorgang wurde erfolgreich beendet.").

The Netlogon service, however, cannot start because it is a workgroup server :-) (or to be more exact, it starts but terminates itself immediately with the known 3095 error that it is a workgroup computer and Netlogon's not needed)

I looked at the installation guide, searched the net and forums but couldn't find anyone having this issue or a statement that workgroup environments are not supported. Is this an AppFabric bug or am I blindfolded and missing something?

Thanks in advance,

Markus

Answer 1

I have setup AppFabric 1.0 in workgroup mode fine. I had not heard that 1.1 requires a domain so I am pretty sure this is not required. My AppFabric Event Collection service is running as Local Service.

If you setup a local account for the service, does this work?

It sounds like there is a service dependency. You might try removing the service dependency (http://kb2.adobe.com/cps/400/kb400112.html) on the NetLogon service.

Thanks,

---

If this answers your question, please use the "Answer" button to say so | Ben Cline

Answer 2

Here is a good article on doing this for AppFabric 1.1: http://msdn.microsoft.com/en-us/library/hh351385.aspx.

It looks like workgroup mode is still possible.

Thanks,

---

If this answers your question, please use the "Answer" button to say so | Ben Cline

Answer 3

Thank you but I checked dependencies beforehand and neither in UI (services.msc) nor Registry there are any "DependOn.." Registry values for neither AppFabric service.

It seems to me like a kind of internal dependency that is coded into the AppFabric sevices.

Answer 4

Thanks a lot, I've tried the guide from "Preparing" to "Installing" but I fail on step 14. - instead of a successful pop-up I still get the Win32Exception error. This time now, following the guide closely, with local Accounts instead of the default AS_* groups (which, in my view, shouldn't make any difference for a standalone server not interacting with other workgroup AppFabric computers).

So I guess my next best take would be to try out the older AppFabric 1.0 version.

Answer 5

I can now confirm that AppFabric 1.0 configuration works flawlessly. It seems to be something specific to 1.1.

With 1.0 I can even use the default internal AS_* groups since it is a standalone server. No need to create and manage any separate user accounts. I also don't need the caching share since I don't use caching; and it's a secured system having SMB sharing disabled.

I could mark this as my own answer but that probably won't help others running into this problem with AppFabric 1.1 in the future.

Answer 6

Interesting, it must be something incorrect with AppFabric 1.1. So it must be something with the security differences between 1.0 and 1.1. I can pass along your issue to the AppFabric team. It sounds like they will need to look into your issues.

Thanks,

---

If this answers your question, please use the "Answer" button to say so | Ben Cline