An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below
[FormatException: Input string was not in a correct format.]
System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +7476535
System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +119
System.Convert.ToInt32(String value) +63
Infragistics.WebUI.UltraWebListbar.UltraWebListbar.PreRenderLBar(Object sender, EventArgs e) +20
System.Web.UI.Control.OnPreRender(EventArgs e) +8766646
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +842
Hello Allan Albetski,
Thank you for posting in our forums!
Did you upgrade your project to use the Infragistics v6.2 assemblies? To me, it sounds like the v6.2 assemblies were copied into your project's bin folder or GAC and are still there after uninstalling (which is expected).
The project is likely still referencing the v6.2 assemblies, you just need to find where they are and change the references back to v5.2. What version is your project currently referencing? You should make sure it is referencing the v5.2 DLLs.
If you need further assistance with this, please let me know.
It is referencing version 5.2 . This is the header from the aspx page
<%@ Register TagPrefix="iglbar" Namespace="Infragistics.WebUI.UltraWebListbar" Assembly="Infragistics.WebUI.UltraWebListbar.v5.3, Version=5.3.20053.50, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" %>
The version 6.2 is not in the project's bin folder and after uninstalling 6.2 I do not have anything left in the GAC besides the dll in the Temporary ASP.NET Files.
I believe the exception you are seeing has to do with logic that parses the browser version and was fixed in a later version of the toolset for firefox 10 which was released in early 2012 so you will need to get the latest service release of 2011 Volume 1 to get the fix for this. The bug would impact any browser that has a version of 10 or greater.
I was actually able to get the controls loaded in the compatibility mode in IE, but when I remove the compatibility mode the error re appears. We have the same version working fine in our prod environment I am not sure why it would do that in the test environment.
In compatibility mode, IE is probably sending a user agent string that is reporting a version of version of IE that is less than 10 so the exception doesn't occur when in compatibility mode. If this doesn't happen in production and only in staging then for some reason based on browser settings your production site is probably also running under compatibility mode. I recommend reviewing your compatibility view settings to see what sites run in compatibility view and note that there is an option to run intranet sites in compatibility view..
Let me know if you have any questions with this matter.