I am encountering a strange issue that is occurring on random PC's. When a user does a search on one of our web pages, the results are then displayed in an UltraWebGrid on that page. However, on some PC's, when the user does a search, instead of the results being displayed in the grid, the text "Table control" will appear in place of the UltraWebGrid.
This does not happen on all the user's PC's, so I am stumped to what is causing it. Some of the users are running IE8, the rest are running IE6. It happens with both IE6 and IE8.
It seems that this text is being returned from the UltraWebGrid control, because I cannot locate it anywhere in the project's code. Does anyone know what could be causing this?
UltraWebGrid v7.1 / ASP.NET 2.0 / IE6 & IE8
Update:
This issue is occurring on random PC's because the User-Agent string that is being passed from these clients to the ASP.NET servers (.NET 1.1 & .NET 2.0) is too long. When this string exceeds the maximum default length of 256 characters, the remaining characters in the string are chopped off. This in return can cause the web server to not handle the request properly.
Microsoft has documented this issue at:
ASP.NET 1.1: http://support.microsoft.com/kb/974762/en-us
ASP.NET 2.0: http://support.microsoft.com/kb/962204/en-us
Microsoft posted some documentation on resolving this issue for ASP.NET 1.1 and ASP.NET 2.0 at:
http://blogs.msdn.com/b/dougste/archive/2010/02/16/asp-net-user-agent-limitation-expanded-from-256-to-512-characters.aspx
Hello,
Thank you for your feedback and for sharing this with us. We believe that the other community members could benefit from such threads.
Please feel free to let me know if a question about our tool set comes up on your mind.
Having same issue...were you able to fix?
For what it's worth, I am experiencing this as well. Unfortunately though, my User-Agent string is only about 110 characters long, so theoretically I shouldn't be hitting this limit.
After doing what feels like endless searching, I can't seem to find any more information on why this is going on. Is it perhaps a specific version of IIS? I'm targeting .NET 2.0, but changing that to 4.5 doesn't seem to do anything either.
Any help would be greatly appreciated.