Server Error in ‘/’ Application.

A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 – Error Locating Server/Instance Specified)

I recently migrated my dedicated server from the worthless company AIT to the cloud computing division of RackSpace. As a result I had to move my SQL database. No Problem I thought. I’ll just edit my web.config and go about my merry business. Well that is when the above error appeared.  This peticular site is dynamically compiled VB site with code in the aspx pages. (no code behind).

The data access layer is handled by some dataset files with XSD extentions. I found that when the files were created the web config connections strings were coppied but not dynamically linked. Each table adpter’s connection sting needed pointed at the web config again. The process was slow due to the now-remote database.

Now that the table adapters have updated their connection strings all is well.

The jist is this: the formview was trying to use an empty string for an int field instead of Nothing.
Here is the error I saw, helpful huh?

Failed to set one or more properties on type xxxxxxx  Ensure that the input values are valid and can be converted to the corresponding property types.

The fields are allowed to be null but the formview just isn’t smart enough to use nothing instead of “”.

My workaround was simple and flexible enough to be re-used so I figured I would post it here.
I simply hijack the formview’s onInserting and replaced “” with Nothing for each field.

Protected Sub formView1_ItemInserting(ByVal sender As Object, ByVal e As System.Web.UI.WebControls.FormViewInsertEventArgs)

For Each o As DictionaryEntry In e.Values
If o.Value = “” Then e.Values(o.Key) = Nothing
Next

End Sub

This same snipit can be put on any page as is and forces certain pages to be https. The nice thing about it is that the user can not edit the url back to http on a page that has this. All I did was put it on the login page and payment page.

On page load the server examines the Request.IsSecureConnection flag and redirects if not secure. It’s that simple. To make it a re-useble snipit I get the page name dynamically.

Be sure not to include the slash after your top level domain.

If Not Page.IsPostBack Then

If Not Request.IsSecureConnection Then

Response.Redirect(“https://www.yourhostname.com” & Request.Url.PathAndQuery.ToString)

End If

End If