Jeremy Wadsworth's Blog

Active Directory - The directory service cannot perform the requested operation on the RDN attribute of an object

Wed, 30 Sep 2009 04:35:55 GMT

This error cropped up while writing some Methods to modify existing Active Directory user accounts. This error occurs if you try to use DirectoryEntry.CommitChanges to update the CN attribute of an entry object. If you search around a little you'll find the short answer is to use the DirectoryEntry.Rename method for changing the name. However, it's important to note that the Rename method needs the format "CN=Joe Smith". For example.
objEntry.Rename("CN=" & strFirstName & " " & strLastName)

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

Thu, 18 Dec 2008 21:27:54 GMT

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>

ASP.NET 2.0 - Compiler Error Message: BC30560: 'Login_ascx' is ambiguous in the namespace 'ASP'

Thu, 28 Aug 2008 20:36:03 GMT

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.

Adobe Reader 8 - Adobe Reader won't print

Fri, 22 Aug 2008 17:35:52 GMT

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.

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

Fri, 22 Aug 2008 03:00:25 GMT

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.