Input string was not in a correct format.

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

I had an application in Win server 2008 that had a reference to Infragistics 5.2 dll but Infragistics was not installed in the machine, I installed Infragistics v6.2 in the same machine and I started getting that error, I even uninstalled Infragistics but still get the same error. I tried installing version 5.2 in the machine but error doesn't go away. I believe the machine did not had infragistics but installing it in that machine introduced the error now it doesn't go away.Can anyone please help me I have been stuck on this issue for last 3 days.

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.

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..