Provisioning a secondary server using Web Farm Framework 2

Question

We have 3 new instances (all Windows 2008 R2 Datacenter) running on EC2, one to run as a controller for the web farm, and the other two as web servers (all running IIS 7.5).

Installed WFF via Web Platform Installer, we've got the controller provisioning the primary server just fine, but when we add the secondary server we get the following errors:

1. Deleting filePath (C:\inetpub\temp\appPools\APC3226.tmp).
2. An error was encountered when processing operation 'Delete File' on 'APC3226.tmp'.
   Retrying operation 'Delete' on object filePath (C:\inetpub\temp\appPools\APC3226.tmp). Attempt 1 of 5.
3. Failed to run operation 'RunRemote'. Failed to run method 'Microsoft.Web.Farm.SyncApplicationsRemoteMethod' on server...
4. Failed to run operation 'ProvisionApplications'. Failed to run method 'Microsoft.Web.Farm.SyncApplicationsRemoteMethod' on server...
5. Failed to run operation 'Repair'. Failed to run method 'Microsoft.Web.Farm.SyncApplicationsRemoteMethod' on server...
6. Failed to run operation 'AutoRepair'. Failed to run method 'Microsoft.Web.Farm.SyncApplicationsRemoteMethod' on server...
7. Server marked 'Unhealthy' due to failure to run operation 'AutoRepair'

I've tried creating new instances of the controller, primary and secondary server but it makes no difference - I get the same sequence of errors.

Seems like a similar issue posted here: Issue provisioning IIS 7.5 server using Web Farm Framework 2 but as yet I can't find a resolution. Has anyone else encountered this?

Answer 1

In step # 2

...An error was encountered when processing operation 'Delete File' on 'APC3226.tmp'. Retrying operation 'Delete' on object filePath (C:\inetpub\temp\appPools\APC3226.tmp)...

it sounds like either 1) a permission issue or 2) some other process has locked the file preventing its deletion.

Perhaps try to manually delete the file using the same administrator account that WFF is running under. Or try creating and then running a server operation to execute a delete on the file remotely from the controller server and see if it works.

Also, try checking to see if and what process is locking the file. You might need to determine if that process is needed and maybe temporarily stopping that process whenever provisioning is executing (by creating a custom workflow provider to run before and after the provisioning).