Category Archives: Bugs & Fixes

BinaryFormatter Version incompatibility. Expected Version 1.0. Received Version 1634552164.1866884455

I have a three tiered WinForm application that uses Microsoft .NET Remoting Framework via a HTTP channel formatted in binary to communicate commands from the client to the server. Every so often when I am making changes to the system I will received the following error:

BinaryFormatter Version incompatibility. Expected Version 1.0. Received Version 1634552164.1866884455

I can't begin to tell you how much I hate this error. It is completely useless. I would rather the error message said "Unknown error" instead of miss leading you into thinking there is something more meaningful or helpful in the message. This message simply tells you that there is a problem that needs to be fixed. After many battles with this particular error message I came across a useful trick. I use the following XML in an configuration file the .Net remoting:

<configuration>
  <system.runtime.remoting>
    <application>
      <channels>
        <channel ref="http" useDefaultCredentials="true">
          <clientProviders>
            <formatter ref="binary" />
          </clientProviders>
        </channel>
      </channels>
    </application>
  </system.runtime.remoting>
</configuration>

To receive a meaningful error message I change the binary format to soap by changing <formatter ref="binary" /> to <formatter ref="soap" />. SOAP error messages are descriptive and can tell you what is going on with the connection. Once I resolve the issue, I switch the formatter back to binary and my application magically works again.

For more information about .Net remoting visit http://msdn.microsoft.com/en-us/library/ms973864.aspx.

Microsoft.Office.Server.UserProfiles.UserProfileException Request Channel Timed Out

I was installing SharePoint 2010 Beta in a Windows 7 Hyper-V image the other day when I encountered the following error message when I ran the configuration wizard:

Configuration Wizard Failed

An exception of type Microsoft.Office.Server.UserProfiles.UserProfileException was thrown. Additional exception information: The request channel timed out while waiting for a reply after 00:00:59.9980468. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.

Microsoft.Office.Server.UserProfiles.UserProfileException: The request channel timed out while waiting for a reply after 00:00:59.9980468. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The request channel timed out while waiting for a reply after 00:00:59.9980468. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout. ---> System.TimeoutException: The HTTP request to 'https://localhost:32844/SecurityTokenServiceApplication/securitytoken.svc' has exceeded the allotted timeout of 00:01:00. The time allotted to this operation may have been a portion of a longer timeout. ---> System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)

The problem was that the UserProfiles service web service call was timing out during configuration. SharePoint was unable stay connected to the web service to finish what it needed to do. To correct this issue you need to modify the client.config file which can be found under "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\". In the client.config file, you will notice all the timeout settings are set to 20 seconds. Below is an example of one of the xml binding element that can be found in the client.config file:

<binding name="ProfileServiceHttpsBinding"
            receiveTimeout="00:00:20"
            sendTimeout="00:00:20"
            openTimeout="00:00:20"
            closeTimeout="00:00:20">

I changed the all timeout values from "00:00:20" to "00:02:00" and saved the file. After the modifications to the client.config file were complete, I reran the configuration wizard and it was able to finish smoothly.

System.Configuration.ConfigurationErrorsException: Unrecognized attribute ‘allowInsecureTransport’

If you have already begun installing the SharePoint Server 2010 Beta on Microsoft Windows Server 2008 R2 or Microsoft Windows 7 you may have already encountered the following error when provisioning Service Applications or when accessing pages that make service calls:

"System.Configuration.ConfigurationErrorsException: Unrecognized attribute 'allowInsecureTransport'. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\<Service Area>\client.config line <Line Number>)"

To resolve this issue you will need to download the KB976462 hotfix which can be found at http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=23806.