Jeremy Wadsworth | ASP.NET Web Development blog and resources. Free Enhanced Personal Site Starter Kit download.

Welcome

Welcome to my personal website. Here you will find blog posts related to web development as well as personal related interests. If you're here for the source code to my Personal Web Site Kit, please register and you'll receive an email when your account has been approved.

Latest Blog Entries

Thursday, December 18, 2008

Sys.WebForms. PageRequestManager TimeoutException: The server request timed out.

I got the exact message: Sys.WebForms.PageRequestManagerTimeoutException: The server request timed out.

There's a real simple fix to this annoying message that pops up. I was getting this in Visual Web Developer while stopped at breakpoints during debugging. Find your <ScriptManager code and modify it to include the AsyncPostBackTimeOut property. Then set the property value in seconds. I set mine to 4 minutes like so.

<asp:ScriptManager ID="MyScriptManager" runat="server"
AsyncPostBackTimeout="240">
</asp:ScriptManager>

jeremy at 4:27 PM | (0) Comments | Add a comment | Permalink

Thursday, August 28, 2008

Compiler Error Message: BC30560: 'Login_ascx' is ambiguous in the namespace 'ASP'

I've been getting this error intermittently for a while now and finally got tired of seeing it, so I started looking for causes and solutions. The exact error I was getting is shown below. Note that it could appear with the same error 'BC30560', but have a different class name and different namespace.

Compiler Error Message: BC30560: 'Login_ascx' is ambiguous in the namespace 'ASP'

I couldn't really find a clear answer as it seems it can be caused by different scenarios, some of which may be a result of a bug in the framework. In my case it was a simple fix, although I don't know why this fixed it.

I had a page named Login.aspx and a User Control that resided on that page named Login.ascx. Why did I do it this way? Because I used the Login.aspx page as the primary login page, but there were other scenarios where I wanted to show a login without redirecting to the login page. So I created a User Control that I could put anywhere I wanted.

It seems as though there is a bug in the asp.net framework since my page and my control have different file extensions and different class names. Yet as soon as I changed my User Control to be named LoginCtrl.ascx, the error stopped appearing.

jeremy at 3:36 PM | (3) Comments | Add a comment | Permalink

Friday, August 22, 2008

Adobe Reader won't print

I pulled up a PDF on my computer running Vista and tried to print. I got this message about not having a printer installed. Well I have a Network printer installed and have used it from this computer. After choosing File>Print Setup, I can see that my printer is selected, yet Adobe Reader isn't seeing it. Come to find out, if you don't have a printer set as the default printer in Vista, Adobe Reader doesn't seem to want to print even though it sees it in the Print Setup. I set the Default Printer and was able to print.

jeremy at 12:35 PM | (0) Comments | Add a comment | Permalink

Thursday, August 21, 2008

Unable to start debugging on the web server. Debugging failed because integrated windows authentication is not enabled.

I've been developing using Visual Web Developer 2008 and Visual Studio 2008 exclusivily for the last 6 months. I've also been using Windows Vista for the same amount of time. I needed to work with a third party control that apparently could only be designed in Visual Studio 2005. So I loaded the project into VS 2005 and hit run, and received the following error.

"Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled."

This was my first time to run VS 2005 in Windows Vista. After fittling around with IIS7 settings for a while, I found that this issue is easily fixed with the following Microsoft Hotfix.

http://support.microsoft.com/kb/937523

Once I ran this hotfix, the error was gone and I could debug as expected.

jeremy at 10:00 PM | (2) Comments | Add a comment | Permalink

Thursday, August 14, 2008

Attach database failed for Server computername\SQLEXPRESS

The error I received.

Attach database failed for Server 'COMPUTERNAME\SQLEXPRESS'. (Microsoft.SqlServer.Smo)
------------------------------
ADDITIONAL INFORMATION:

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Directory lookup for the file "C:\Data\WebHelp\help_log.ldf" failed with the operating system error 2 (The system cannot find the file specified.). (Microsoft SQL Server, Error: 5133)

This error occurred for me when I tried to attach and SQL Server was looking for an existing log file (.ldf). I was able to get around this by doing the following.

Opened up SQL Server Management Studio Express. Browsed to my database (.mdf) file. Once I set the file name to attach I selected the log file that was listed below the database file, and clicked the Remove button located just above the Cancel button.

jeremy at 11:32 PM | (4) Comments | Add a comment | Permalink