Intersoft Community - WebGrid Enterprise - WebGrid server crash every month

WebGrid server crash every month

Eric — Wed, 22 Feb 2012 03:22:14 GMT

Hi Frank! No, it never got resolved. But we moved away from that Windows 2000 server to a "new" platform (IIS6) a few months ago and there I don't remember having any problems with this. The new environment has other issues, but not this one.

WebGrid server crash every month

qafrank1 — Tue, 21 Feb 2012 17:31:40 GMT

Did this bug ever get resolved?

WebGrid server crash every month

Eric — Fri, 10 Jun 2011 03:43:25 GMT

You know that you can never test on a production system. And reproducing this is also not possible right now as you know.

So the only thing we can do is to add some logging to find out more details (which might lead to a reproduction scenario or whatever). But you never told me what you need.

I understand that this bug is not very important for you, as this happens currently only for us and only randomly every few weeks and on an old server - together with your limited resources. But it is still a very drastic bug and might still exist on any newer server for any client you have.

So please let me know how to go on. If you don't want to fix it, please tell us this clearly too. Just letting us wait and telling things about reproduction is no option.

WebGrid server crash every month

handy@intersoftpt.com — Fri, 10 Jun 2011 02:04:21 GMT

Hello,

Unfortunately, the resources are not enough. First, the log does not lead us to further investigation.
The information is not enough. Last, even we can debug it, we need to debug at the time the error/crash happened. If not, we don't have the information what is exactly cause the error.
If we are able to replicate the issue and know what cause the issue, we will fix it.

Regards,
Handy

WebGrid server crash every month

Eric — Thu, 09 Jun 2011 08:35:32 GMT

I don't understand what you mean.

We both know you won't be able to reproduce the issue - ever. (That's why I offered help to debug / log.)

So does this mean you won't fix it?

WebGrid server crash every month

handy@intersoftpt.com — Fri, 03 Jun 2011 07:19:33 GMT

Hi,

I do understand about that. But as you said, the issue is randomly happened. There is no guarantee if I login, I can see the issue. If it still runs well when I login, I still could not do any progress about that.

Also, We never said that we refuse to fix it. It's just we need to replicate the issue first.

Regards,
Handy

WebGrid server crash every month

Eric — Wed, 01 Jun 2011 09:49:00 GMT

I fully understand that it's difficult. That's why I offered to add logging or whatever.

But what I understood is that under current circumstances you are not interested in getting this fixed. Can you confirm that you won't fix this issue?

WebGrid server crash every month

handy@intersoftpt.com — Mon, 30 May 2011 06:25:09 GMT

Hello Eric,

We don't have any update or progress in this situation. I hope your understand that it's very hard to investigate without replicate the issue.

Regards,
Handy

WebGrid server crash every month

Eric — Fri, 27 May 2011 03:42:06 GMT

So how will it go on with this bug? As you cannot replicate it yet, does this mean you will not try any longer to investigate and just not fix it?

WebGrid server crash every month

handy@intersoftpt.com — Mon, 23 May 2011 06:50:51 GMT

Hi Eric,

Yes, but currently we are also stuck because we still unsucessful to replicate the issue.

Regards,
Handy

WebGrid server crash every month

Eric — Wed, 09 Feb 2011 09:57:50 GMT

Hi,

This is the same question as our initial support request [IS-C4A66AE8-3423-4C20-A164-35B59B3FE656] {83029} via mail which is from February 2009. The issue still happens, although we upgraded Webgrid in the meantime from version 5 to version 6. We use Framework 2.0, IIS5 on an old Windows 2000 Advanced Server.

The problem is that we have in all WebGrids the code <ClientSideEvents OnUnhandledError="GridUnhandledError" with the JavaScript redirecting to a new page (or something similar).

This code gets triggered and it happens about once a month. Sometimes it "repairs itself" after about half an hour or so, but sometimes it doesn't. Closing the client web browser, clearing its cache etc. doesn't help. Restarting the web server (services) also doesn't help or only during a few minutes. The only thing that helps is to reboot the whole server. We have to raise critical tickets and wake up people. This lets us look bad, especially because everything else works, only the WebGrid interactions don't work. All pages that don't use a WebGrid work fine. All pages with the WebGrid initially also load, but any interaction that causes a FlyPostback results in a crash showing our general error page or something similar.

In the meantime I have Fiddler installed, so I can trace the HTTP traffic. This clearly shows the problem (just an example here):

POST /xxxxx.aspx HTTP/1.1
Accept: */*
Accept-Language: en-us,de-ch;q=0.5
Referer: http://server/xxxxx.aspx
Content-Type: application/x-www-form-urlencoded
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E; MS-RTC LM 8)
Host: server
Content-Length: 10101
Connection: Keep-Alive
Pragma: no-cache
Cookie: WT_FPC=id=123.123.123.123-1234123412.12341234:lv=1234123412345:ss=1234123412345; lazy_tnummer=username; ASP.NET_SessionId=3yz3iv452f2ivcn2clp2wz46

WebGridRequest=¢WebGrid>¢request id="grdSearch" action="Custom"/>¢/WebGrid>
&__VIEWSTATE=/abc[...]def/k1
&grdSearch=
&grdSearch$grdSearch_h=¢
WebGrid ServerUniqueID="grdSearch" UseDefaultStyle="True" IsPreviewMode="False" UseWebResourcesForClient="True" UseWebResourcesForScript="True" TotalLoadedRows="26" TotalRows="26" GBBLabelClass="WG5-GBBL" RowClass="ISGridItemStyleHt11">¢
ChartSettings/>¢
FlyPostBackSettings PostHiddenFields="False"/>¢
LayoutSettings AllowContextMenu="False" TreeLines="False" InProgressUIBehavior="ChangeCursorToHourGlass" RowHeaders="No" Culture="en-US" SelectedRowClass="ISGridSelectedRowStyle" CheckedRowClass="WG5-CR" LostFocusClass="WG5-LFR" EditFocusClass="WG5-EFC" TextBoxClass="WG5-ET">¢
StatusBarCommandStyle Active="WG5-SBC-A" Over="WG5-SBC-O" Normal="WG5-SBC-N"/>¢
ClientSideEvents çUnhandledError="alert('Session timeout or other error. Please close all windows and try again.');window.close();" ç
RowSelect="DoBlaBla"/>¢
/LayoutSettings>¢
RootTable TableLevel="0" Name="" IsRootTable="True" Position="0" IsUseColumnSet="False" HasMultiPrimaryKey="False">¢
FocusCellStyle BorderColor=""/>¢
ChildTables/>¢
FilteredColumns/>¢
SortedColumns/>¢
ColumnSets/>¢
GroupedColumns/>¢
Columns>¢
WebGridColumn Name="Item_ID" Visible="False" DataType="System.Int32" DataMember="Item_ID" Caption="Item_ID"/>¢
WebGridColumn ColumnType="Custom" Width="100%" Name="Item_Name" DataMember="Item_Name" Position="1" Caption="Item_Name"/>¢
WebGridColumn Name="SPID" Visible="False" DataMember="SPID" Position="2" Caption="SPID"/>¢
WebGridColumn Name="CRR" Visible="False" DataMember="CRR" Position="3" Caption="CRR"/>¢
WebGridColumn Name="HD" Visible="False" DataType="System.DateTime" DataMember="HD" Position="4" Caption="HD"/>¢
WebGridColumn Name="HC" Visible="False" DataType="System.Int32" DataMember="HC" Position="5" Caption="HC"/>¢
/Columns>¢
/RootTable>¢
ChartInteractiveUI/>¢
ChartCategoryCollection/>¢
UtilizedCustomEditors/>¢
ChartFilterCollection/>¢
ChartDataCollection/>¢
ChartSeriesCollection/>¢
WebCombos/>¢
selectedObject tblName="" type="Row" rowIndex="12" cellIndex="0" parentIndex="">¢
keyValue>¢
![CDATA[1234]]>¢
/keyValue>¢
/selectedObject>¢
/WebGrid>
&WebGridID=grdSearch&PID=1234
&__EVENTTARGET=ISControl
&__EVENTARGUMENT=PostBack
&__FLYPOSTBACK=true
&__FLYPOSTBACKID=grdSearch


HTTP/1.1 200 OK
Server: Microsoft-IIS/5.0
Date: Wed, 09 Feb 2011 11:10:39 GMT
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Length: 0

(added some additional line breaks and anonymized)
(ç = char 0x02)
(¢ = char 0x03)

As you can see, the FlyPostback POST request is answered by the server with a 200 OK, but without any data. The client interprets this as an error and runs the client-side event OnUnhandledError.

As this only happens for WebGrid's FlyPostback HTTP POST requests, I have no idea of what else I should check.

Also I think updating to WebGrid 7, upgrading the server's operating system or the .NET Framework will probably not help, as long as you haven't fixed this specific problem.

So what should we do now? Get rid of WebGrid? Any other ideas?

Thanks,

Eric