.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Post New Web Links

Strange "Input string was not in a correct format" after upgrading to .net 4.0 (VS 2010)

Posted By:      Posted Date: October 22, 2010    Points: 0   Category :ASP.Net

Hi guys, I am at a loss here.  I have a gridview that was displaying and handling postbacks correctly, that is, until I upgraded to .net 4.0 (vs 2010) from .net 3.5. Now I am getting the classic (and in this context meaningless) "Input string was not in a correct format" error upon postback. The postback is initiated by a command button and the row command event handles everything nicely.

The trace shows internal grid postback handling and nothing else:

[FormatException: Input string was not in a correct format.]
   System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +9594283
   System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) +119
   System.Convert.ToInt32(String value, IFormatProvider provider) +48
   System.Web.UI.WebControls.GridView.HandleEvent(EventArgs e, Boolean causesValidation, String validationGroup) +1047
   System.Web.UI.WebControls.GridView.RaisePostBackEvent(String eventArgument) +210
   System.Web.UI.WebControls.GridView.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +13
   System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13

View Complete Post

More Related Resource Links

Upgrading to 2010

Is there any problem with running VS2008 and VS2010 Web Developer express on the same machine?  

Upgrading to SharePoint 2010 Foundation on SBS Server 2008

Hi all, I've just tried to install SharePoint Foundation on 2010 on Windows Small Business Server 2008 and whilst the literature I've found suggests that this is supported, I receive the following error: SharePoint 2010 Products cannot be installed in Stand-alone mode on a Domain Controller.  For more information on upgrading, see http://support.microsoft.com/?kbid=975805. What's funny about the KB ID, is that it doesn't exist.  The pre-requisites for SharePoint 2010 Foundation installed OK and the SharePoint installer has detected that it will perform an in-place upgrade.  the STSADM -o preupgradecheck output is below. Any idea's?  It would be really great if we could start using the shared workspace and ribbon features that are inherent with SPF2010. Jason.  

Strange Problems in 2010

Hello, we have just upgraded to sharepoint 2010 from 2007, on the whole the upgrade went well, but we seem to be having problems accessing Manage Content and Structure or browsing for an Image or Link, I have turned on debugging in web.config to see what the error is, there are several different errors including this one:   Object reference not set to an instance of an object. body {font-family:"Verdana";font-weight:normal;font-size: .7em;color:black;} p {font-family:"Verdana";font-weight:normal;color:black;margin-top: -5px} b {font-family:"Verdana";font-weight:bold;color:black;margin-top: -5px} H1 { font-family:"Verdana";font-weight:normal;font-size:18pt;color:red } H2 { font-family:"Verdana";font-weight:normal;font-size:14pt;color:maroon } pre {font-family:"Lucida Console";font-size: .9em} .marker {font-weight: bold; color: black;text-decoration: none;} .version {color: gray;} .error {margin-bottom: 10px;} .expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; } Server Error in '/' Application. Object reference not set to an instance of an object. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.NullRe

Reg Upgrading List of MOSS 2007 to InfoPath 2010

Hi, Actually right now there is Newform.aspx of the list in MOSS 2007 through which we are collecting the data from the user.Now our customer is planning to migrate the application to SharePoint 2010 so i just want to know so that can we get a easy support to implement in InfoPath 2010 compared to the list of MOSS 2007 Thanks & Regards, Sudheer

Upgrading from WSS 3.0 to Sharepoint 2010

We currently have WSS 3.0 but at this time haven't decided on whether we will upgrade or do a fresh install on new servers for Sharepoint 2010. If we do a fresh install of Sharepoint 2010 on it's own servers, is there any way to migrate existing sites (blogs, wiki's, document libraries) from WSS 3.0? I don't even know if that is possible, if so, is there any information out there on this can be done? What could we loose in the process? Regards, Lisa  

Upgrading Foundation 2010 to Search Server Express


Hi there,

I can't find any conclusive articles/technet references on what the correct (best) way to get to a Search Server Express 2010 built on top of Foundation actually is.

I know I can install Search Server directly, but does this then limit the features of the resulting "foundation" aspects? Is it better to do a full install of Foundation and then an 'upgrade' to search server 2010 express?

Any links to an actual reference would be great!


Upgrading SharePoint 2010 from Beta 2 to RC or RTM

Microsoft have stated that they cannot gaurentee that there will be no more database schema changes between Beta 2 and RTM and as such there is no upgrade path from Beta 2 to RTM.  This leave the TAP and the PEP participants in a bit of a hole in that they have signed up to having sites live by the time SharePoint 2010 goes RTM.

Jie Li on his blog has stated that

If you are exporting/importing content that means you are "migrating". It would be fine. However attach a beta content database to RTM will not work.

So can it be confirmed that I can use the deployment API to export content from say a Beta 2 site and again using the deployment API can import that content into a RTM site.

In reality  I would use Chris O'Brien's SharePoint Deployment Wizard which uses the deployment API.



SharePoint 2010 without upgrading to Office 2010?


We planned on upgrading our SharePoint server from 2007 to 2010 before rolling out Office 2010 by about 6 months. We were just told yesterday that this is a bad idea due to incompatabilities with Infopath and SharePoint Designer. We realize we have to run SPD 2010 with SharePoint 2010, but are the other Office applications really that big of a deal? We only have a handful of SPD users, out of thousands of everyday users. All of our Infopath forms are designed to be browser based, and not opened in the client.

If this is a really an issue, what types of problems will we see running the Enterprise version of SharePoint 2010 while our users will be on Office 2007? For Infopath developement, can we not just upgrade those developers to Office 2010, and leave the rest of our users on 2007 for a while longer? The only real issue I can find would be some of the Office Web Applications would have features disabled if the user didn't have a full Office 2010 Suite installed.

Upgrading content databases from 2007 to 2010


Hi all

So I'm doing the database attach upgrade method, which involves building a new SharePoint 2010 environment on new servers and then migrating the content databases over to the new SQL server and attaching the databases to the new farm.  I've followed all steps in the Microsoft guides (http://technet.microsoft.com/en-us/library/cc263026.aspx).  I'm at the point where I'm ready to attach the databases to the new farm.  As the guide recommends, I used the Test-SPContentDatabase cmdlet to see if there was anything missing from the farm that is required by the content.  Here's the error it's spitting out:

PS C:\> Test-SPContentDatabase -Name SharePoint_WSSContent -WebApplication https://url

Category        : MissingSetupFile
Error           : True
UpgradeBlocking : False
Message         : File [Features\ExcelServerSite\Microsoft.Office.Excel.WebUI.dwp] is referenced [3] times in the database [SharePoint_WSSContent], but is not installed on the current farm.  Please install any feature/solution which contains this file.
Remedy          : One or more setup files are referenced in the database [SharePoint_WS

Getting User related issues when Upgrading Classic based 2010 web application to claim based 2010 we



I have upgraded Classic based to claim based . I used these Power-Shell scripts :

$w = Get-SPWebApplication " http://<server>/ "

$w.UseClaimsAuthentication = 1




It upgraded fine. But I am getting a problem when users are trying to log in, they are not able to log in to sharepoint. When I remove existing user and add the same user again then that user can log in.

One thing I also noticed that If User "ABC" is already in Share Point and If I add same user again then it shows both users. But there is only one user.

I am using Share Point 2010 RTM.

What is wrong with my share point 2010?

Can you please help me ?

G. Goyal

Will my customization on SharePoint 2007 be retained after upgrading my solution to SharePoint 2010

I have implemented lot of custom features, branding , themes for my custom sharepoint solution. I have also included lot of file system changes in 12 hives.
Will my customization on SharePoint 2007 be retained after upgrading my solution to SharePoint 2010.
-Puneet Mishra

Error upgrading MOSS 2007 publishing site to 2010 - Exception: Column 'PublishingStartDate' does n


We are in the process of testing a database attach upgrade from MOSS 2007 to SharePoint Server 2010. We are running into an issue when we attach the database with the main portal site collection which has the publishing features enabled. In the upgrade error log, we are receiving the following errors:

[powershell] [CmsImageLibrarySiteAction (] [INFO] [10/21/2010 3:40:37 PM]: SPSite Url=http://<WEBAPP>.<COMPANY>.com
[powershell] [CmsImageLibrarySiteAction (] [ERROR] [10/21/2010 3:40:37 PM]: Failed to upgrade site collection images library on site http://<WEBAPP>.<COMPANY>.com.
[powershell] [CmsImageLibrarySiteAction (] [INFO] [10/21/2010 3:40:37 PM]: SPSite Url=http://<WEBAPP>.<COMPANY>.com
[powershell] [CmsImageLibrarySiteAction (] [ERROR] [10/21/2010 3:40:37 PM]: Exception: Column 'PublishingStartDate' does not exist. It may have been deleted by another user.
[powershell] [CmsImageLibrarySiteAction (] [INFO] [10/21/2010 3:40:38 PM]: SPSite Url=http://<WEBAPP>.<COMPANY>.com
[powershell] [CmsImageLibrarySiteAction (] [ERROR] [10/21/2010 3:40:38 PM]:    at Microsoft.SharePoint.SPFieldCollection.GetField(String strName, Boolean bThrowException)
   at Microsoft.SharePoint.SPViewFieldCollection.Add(String

Error upgrading MOSS 2007 SSP database/user profiles to 2010


I am trying to use the new-spprofileserviceapplication powershell script to do a db attach/upgrade of my 2007 SSP to upgrade the user profiles.

New-SPProfileServiceApplication -applicationpool User_profile_service_app_pool -Name "User Profile Application" -Profiledbname prodsspconfig2 -Profiledbserver dbname\int

It gets a certain way and then errors out with the following error:

[powershell] [ProfileDatabaseSequence] [ERROR] [10/22/2010 12:13:56 PM]: Action of Microsoft.Office.Server.Upgrade.ProfileDatabaseSequence failed.
[powershell] [ProfileDatabaseSequence] [INFO] [10/22/2010 12:13:56 PM]: ProfileDatabase Name=prodsspconfig2
[powershell] [ProfileDatabaseSequence] [ERROR] [10/22/2010 12:13:56 PM]: Exception: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_ProfileTypePropertyAttributes_PropertyList". The conflict occurred in database "ProdSSPConfig2", table "dbo.PropertyList".
The statement has been terminated.
[powershell] [ProfileDatabaseSequence] [INFO] [10/22/2010 12:13:56 PM]: ProfileDatabase Name=prodsspconfig2
[powershell] [ProfileDatabaseSequence] [ERROR] [10/22/2010 12:13:56 PM]:    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowE

Error in adding new link in summary link webpart after upgrading to sharepoint 2010



I have a weird error after upgrading my portal from sharepoint 2007 to sharepoint 2010 using attach database approach.

The error occurs when creating a new link in the summary link web part, so a pop up screen will show up, then if I click on Browse Button to link for an item an error occur, on the other hand if i click Browse Button to link an image then everything is working normally.

I checked the event viewer and here what I got, any Ideas?

Event code: 3005

Event message: An unhandled exception has occurred.

Event time: 23/10/2010 3:44:56 PM

Event time (UTC): 23/10/2010 12:44:56 PM Event ID: b74e380e0f6c4d3499feae1176557bcd Event sequence: 403 Event occurrence: 5 Event detail code: 0


Application information:

Office 2010 required before upgrading or installing SharePoint Foundation 2010??


Is it required now to upgrade to SharePoint 2010 Foundation etc. first before using Office 2010 with SharePoint??

Or can Office 2010 work in even a limited manner with WSS 3.0??

Thank you, Tom

Strange behaviour of VS 2010 in ASP.NET Dynamic data web App


I noticed this while i was working on asp.net dynamic data web app. It made me go crazy as I struggled quite a lot of time why this error was coming.

Basically, I have some of the custom page templates added to my application. I observed that if I keep these custom pages say /DynamicData/CustomPages/Employees/Details.aspx opened in the designer, I always get following error when i try to run the app.

Server Error in '/' Application.

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.

Requested URL: /DynamicData/CustomPages/Employees/Details.aspx

I did not understand the logic behind this. In order to confirm, i created a simple web app with dynamic data and still this error occurs. In fact, the same error also occurs if you keep any of the default page templates opened in your designer.


Question on retaining workflow data after upgrading to SP 2010



After upgrading from SP 2007 to SP 2010, will the workflow data be retained? I mean, if there are any workflows that are started but are yet to be completed, will there be any issues with those after upgrade? I tried finding about this in the Internet, but couldn't find any.

ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend