The service application proxy “User Profile Service Application” could not be provisioned because of the following error: Unrecognized attribute ‘allowInsecureTransport’.

So, here I am, going through my installation of the SharePoint 2010, and received my first error! The error (full text below), came while configuring the services via the Initial Farm Configuration Wizard

Errors occured.

The service application proxy "User Profile Service Application" could not be provisioned because of the following error: Unrecognized attribute ‘allowInsecureTransport’. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\client.config line 56)

Corelation Id: bf7f0c8a-97f2-4250-b4e5-04c4d74eff3e

DOH! In addition to this error, not only is this halting my forward progress, and not this has anything really to do with anything, but, hopefully they run a spell check before this gets to RTM. There are two spelling mistakes in the message above (bolded and underlined). Anyways, I did a bit of searching on the interwebs for this, and it appears that it is a known issue on both Windows 7, and, Server 2008 R2, the latter of which I am running.

It appears that there is a fix coming down the pipe from Microsoft, according to this post on the SharePoint TechNet Forums: http://social.msdn.microsoft.com/Forums/en-US/sharepoint2010general/thread/041ddc78-8d18-4753-b7be-8d8113e26e62, as there is an issue with WCF on the two aforementioned platforms, as they share the same core.

There are also workarounds posted (like here: http://mphacker.spaces.live.com/Blog/cns!8040CC624DDC5404!790.entry), however, these come in the form of modifying a file within the “SharePoint Root” [14 Hive] (the file mentioned in the error). This is unsupported, but, guess what, so is the Beta copy of SharePoint 2010. However, in the article above, some issues have arisen by modifying the file directly.

There is no release date that I am aware of for the patch, however, a search on Google nets the following

It appears it was there at some point, however, it has since been removed (“Sorry, but we couldn’t find the page that you requested.”). I’ll make another post as soon as I see it comes out. In the meantime, I am holding off on my installation until the fix comes out so I can have a “clean” fresh install.

UPDATE: Hotfix has been released! WCF Hotfix (KB976462) for Windows Server 2008 R2