I needed to rewrite the URLs for DotNetNuke for SEO purposes. Here's how to do it.

1. Open the SiteURLs.config file located in the root directory. Optionally, use the Friendly URL settings interface in Host Settings.

2. Figure out what you want the URL to be and how to write the URL with Querystrings. Add an entry in the SiteURLs.config file like below. Regular expressions can be used, but because I want each page to show up a particular way, I have to explicitly specify each one. Lookfor is the one you want to show up, and Sendto is the real URL with querystring.

   
     <RewriterRule>
      <LookFor>.*/HorsebackRiding/MendesRanch.htm</LookFor>
      <SendTo>~/Default.aspx?tabid=78&a ...

I decided to try my custom dotnetnuke shopping cart module on a different version of DNN to see how it fared - a common practice among dotnetnuke module developers. I installed a new DNN instance and then used a template to set everything up. The version test went great, but the second I tried to add a new text module to the home page, the installation became corrupted and I couldn't recover it. After retracing my steps, I figured out that the cause was a some difference in the portal export feature. Lesson learned - only use create new portals from templates made in the same version of DNN.

I recently experienced the proverbial straw that broke the camel's back with APlus.net, who was providing hosting for servers for one of my clients. During the account cancellation, they asked me why I was cancelling my account and I thought it would be a shame to waste a great "bitch session".

Last week Aplus experienced network issues that caused both dedicated servers we lease from you to become unavailable. When your network came back online, our main web server began logging DCOM errors in the event log. Your support staff tried to resolve the issue, but finally decided that the server needed to have a clean OS image installed. The email was sent Friday evening requesting my approval to perform the rebuild, and I answered Saturday morning. The OS image was completed Monday morning, costing our group another two days of unnecessary down time. On Monday I began to reinstall our application. It should have only taken me a couple of hours to reinstall, but I ex ...

I put in a support call with my host and I just got a cheery response.

Unfortunately, your server has already been compromised.  We found WINNT/system32/rdriv.sys.  The rdriv.sys is the Rbot.aja worm.  The only recourse, at this point, is to reload your operating system on a new primary hard drive.

The virus attacks a weakness in the SMTP service in older versions of Mailenable. The search has come to an end and the misbehaving of applications will cease.

First thing this morning I picked up where I left off yesterday in trying to track down the cause of my recent server malfunctions. No answer from Grisoft yet, but no big surprise there. I expanded my system log search by logging every security event I could get my hands on in the policies. I noticed that IME_User and IME_Admin were generating login failures in the logs. These are the users that Mailenable uses in its webmail and webmail administration applications. I’ve seen them in IIS before. There’s a connection to the issue that started this whole mess.

I used Mailenable’s MEInstaller application to perform the web application set up steps as per the directions found on Mailenable’s site. I still got the same

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.

And my other IIS asp.net applications are now requesting windows credentials. These all use the IUSR_<machinename> account. Apparently th ...

I use Mailenable Pro version 2.091 for mail. I just recently started getting a strange error when I try to access its webmail applications:

HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
Internet Information Services (IIS)

This is very strange because up until a couple of days ago it worked just fine. No complaints ever.

I used Explorer to check all my permissions. I found a list of required permissions for IIS 6.

The first thing I noticed that was out of the ordinary was in the folder <windir>IIS Temporary Compressed Files . The page I found above said that Creator Owner needs Full Control over this folder. However, when I granted that permission, and pressed Apply, all the checkboxes that I placed in the Allow column just disappeared! Anyway... Moving on.

Today I was creating a new DotNetNuke portal with version 3.3.5. When I accessed a module that uses special control inherited from the DNNTreeView control fromdotnetnuke.webcontrols.dll, I encountered this error:

Request for the permission of type System.Security.Permissions.SecurityPermission, mscorlib, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 failed

This error does not happen on any of the other sites using the custom module in question. I did some google searching and learned that I needed to change the trust level of the dnn application from Medium to Full in the web.config file. After doing this, I received this error:

Assembly freetextbox.dll security permission grant set is incompatible between appdomains.

I wasted 2 hours toggling settings, viewing code security settings, blah blah blah. Frustration set in and I rebooted my computer. Problem solved. ...

I installed internet explorer 7 a couple of weeks ago and for the most part I like it. The tabbed views are cool and I like when I click a link from Outlook that a new tab is opened rather than using any currently open windows. But the FTP support is annoying. In IE 6 I used to just type in an ftp address and go. My username usually popped up in the credentials and all I had to do was put in a password and I was able to ftp to my heart's desires. In IE 7, when I type in the same address, I have to type in the username and password every time. Then it takes me to a folder view where all the files are links instead of objects I can work with like explorer. I can click Page, and then click Open FTP Site in Windows Explorer, then enter the credentials all over again. Finally I can ftp!

You would think that all I would have to do is type in the ftp address into explorer, right? WRONG! When I do that, it opens IE 7 and I have to do the window dance again.

...