[SerializationException: BinaryFormatter Version incompatibility. Expected Version 1.0 Received Version 1835627630.1699884645.]
What it really means . . . .
When you set up a remoting client to use the Binary Formatter over HTTP, it's expecting a binary answer. If the response from the server component contains HTML (like an IIS Server 500 error) then the deserializer tries to interpret it as binary and ends up turning some random HTML where the version number should be into a garble of numbers.
This one's a little better . . .
Could not create Windows user token from the credentials specified in the config file. Error from the operating system 'A required privilege is not held by the client'
If the web.config file has impersonation specified, like so:
<identity impersonate="true" userName="username" password="password"/>
Then the ASPNet account needs to have the 'Act as part of the Operating System' privilege in order to call the Win32API LogonUser() function.
Update - here's the KB article for this one. It was surprisingly difficult to hunt down, so I thought I'd make a note of it here as well. It says Windows 2000, but I'm pretty sure I've seen this on 2003 as well.
PRB: Per Request Impersonation Does Not Work on Windows 2000 with ASP.NET
File Under: Technology,