March 2005 - Posts

Path Helland is leaving Microsoft.

It must be a big loss for Microsoft when Path Helland starts working for Amazone March 7th. Path, how you keep up the brilliant work at Amazone.com and keep on blogging.

http://blogs.msdn.com/pathelland/archive/2005/03/03/384636.aspx

Calling the postback function of the parent form a child window. (ASP.NET)

I needed a way to refresh a ASP.NET page from a child window, without loosing the current state of server controls. I used the child window to retrieve som values from an ASP page, who posted the values back to an ASP.NET page, who stored them in session state on page load. Then I wanted to refresh the parent form to load the selected values into the form and close the child window. I wrote this magic javascript code inside the form tag of the aspx page after storing the values in session state..

window.opener.execScript("__doPostBack('someButton','')","JavaScript");
window.close();
It works..

SqlException: General network error. Check your network documentation.

There is a lot of people out there complaining about SQL Server returning a General network error while executing a command form ADO.NET version 1.1 or 1.0. Since it is a General network error, it seems to me that there are as many reasons for this error as there are people having it. I found several postings and articles about this strange error message, and finnaly I also found a workaround that fixed the problem for me...

What i did was to append: max pool size = 7500, to my connection string.
This fixed the problem, but didn't explain why the problem occured in the first place.. What I discovered later on was that Norton Internet Security was blocking requests to my SQL server, causing some strange errors while pooling connections. When disabling Norton Internet Security, SQL Server works perfect again.. Even without the max pool size setting in the connection string.