ASP.NET 2.0 ... VB.NET ... AJAX 1.0... the whole thing is an itty bitty usercontrol that implements the IWebPart interface.
I started getting the same error, without really understanding what happened. The weird thing is that I thought I picked the most benign and insignifigant place to put an update panel. I also get these errors in the event log:
>EventType clr20r3, P1 w3wp.exe, P2 6.0.3790.1830, P3 42435be1, P4 system.web.services, P5 2.0.0.0, P6 4333af0f, P7 273, P8 36b, P9 ybv1uwyoq5jwn2acoifmkgc11cxoj3gf, P10 NIL.
And this wonderful one:
An unhandled exception ('System.Web.Services.Protocols.SoapException') occurred in w3wp.exe [2120]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on. Check the documentation index for 'Just-in-time debugging, errors' for more information.
Here's my amazingly complex source code:
1 <asp:UpdatePanel ID="UpdatePanel1" runat="server" UpdateMode="conditional">
2 <ContentTemplate>
3 <table style="width:100%">
4 <tr>
5 <td>Have you met <asp:HyperLink runat="server" ID="hlDisplayName" CssClass="link"></asp:HyperLink>?
6 <asp:Label runat="server" ID="lblBrief"></asp:Label>
7 </td>
8 </tr>
9 <tr>
10 <td>
11 <br />
12 <div style="text-align:center;">
13 <asp:HyperLink runat="server" ID="hlEmployee">
14 <asp:Image runat="server" ID="iEp" BorderWidth="0" />
15 </asp:HyperLink>
16 </div>
17 </td>
18 </tr>
19 </table>
20 </ContentTemplate>
21 <Triggers>
22 <asp:AsyncPostBackTrigger ControlID="Timer1" EventName="Tick" />
23 </Triggers>
24 </asp:UpdatePanel>
25 <asp:Timer ID="Timer1" Interval="10000" runat="server">
26 </asp:Timer>
Basically this displays a new employee, and some information about them. It updates every ten seconds, and looked pretty cool. Right up until the point that I started getting that error. I have to do an iisreset, and then it works for another few minutes, and then it barfs out on me again.
I'm wondering... maybe.. if it has to do with the fact that it's in debug mode? I'm really not sure what's causing this error, and I'm pretty damn happy that I didn't implement this in production yet. I mean throwing a fatal exception because of AJAX? That's just plain crazy.