Web Farm Framework 2.2 does not provision through Web Platform Installer 3.0

When you set up a Microsoft Web Farm Framework (WFF) 2.2 provision through Microsoft Web Platform Installer (WPI) 3.0, you may receive the following "Invalid URI" error messages about the feed for WPI 3.0.

These errors occur because WFF 2.2 depends on the components of WPI 3.0. However, support for the main feed for WPI 3.0 has recently ended.

The WPI 3.0 feed is deployed to a new URL. Therefore, to fix this problem, you must include the new platformProvision feed URL in the ApplicationHost.config file, and then change the file manually by using Internet Information Services (IIS) Manager GUI or by running an AppCmd command.

To update the ApplicationHost.config file, use one of the following methods.

Method 1: Use the IIS Manager GUI

1. Locate your Controller server, and then start IIS Manager.
2. Click the server node, and then click the Configuration Editor module.
3. Click the Section menu, and then select Web Farms.
4. Click the Collection row, and then click the ellipsis icon on the right end of this row.
5. Highlight the Web Farms row, and then expand platformProvision.
6. Change the feed URL to the following:
   
   <https://webpifeed.blob.core.windows.net/webpifeed/3.0/webproductlist.xml>
7. If the WFF service does not receive the change automatically, restart WFF and IIS. To verify that the change took effect, open the ApplicationHost.config file and search for an updated platformProvision element.
8. To verify that the change is working as expected, click Servers under Server Farm. You should see no errors reported.
    

Method 2: Use AppCmd

At a command prompt, run the following AppCmd command:

%systemroot%\system32\inetsrv\appcmd.exe set config -section:webFarms /[name='MMAIISfarm-DEV'].platformProvision.feedUrl:"https://webpifeed.blob.core.windows.net/webpifeed/3.0/webproductlist.xml" /commit:apphost

Note To avoid configuration conflicts, we recommend that you do not change the ApplicationHost.config file manually.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Learn about the terminology that Microsoft uses to describe software updates.