Hello,

I seemed to have hosed my dev machine DNN install. All of my aliases for my second site are returning 404.

Here is how I got here:

It had been quite a while since I had been to this site on my dev machine and when I went to my default dnn site (localhost/dotnetnuke) the install started running. I continued as I thought maybe I had reloaded the OS since my last visit. When it got to the database settings page, I remembered that I had disabled the SQLExpress service to save resource, since I rarely use it. I started the service and went back to localhost/dotnetnukeand it loaded.

But when I tried to go to my other site (note: Site 0 is the default sample site, Site 4 is my actually web site) using its usual alias (localhost/hylandstudiodnn) I got a 404 error.

I tried to create a new alias in case the other was hosed somehow and it also got a 404. I clicked on the alias links in the Site Management page in case I was typing them in wrong. No joy.

How do I get my site back?

I am using DNN 06.01.05 (142)

Thanks,

Brad

Sebastian,

That did not work. Maybe my recent misadventure did not cause the problem, but something else I did to IIS in the months since I was last in DNN?

I bounced around the interwebs, but nothing seemed to relate to my problem directly.

I can get to localhost/dotnetnuke alias and see the default web site (portal 0), but none of the alias's for portal 4 get me anything but 404.0 errors. I am not really sure how DNN wires up the alias to the web site with IIS in the first place.

Danke sehr for your help so far.

- Brad

Sebastian,

Yes, I understand that they need to point to a DNN server. Below is a screenshot of my Site Management page.

localhost/dotnetnuke works to bring up portal 0, so it is pointing to my local DNN server.

localhost/hylandstudiodnn doe NOT work to bring up portal 4. Same DNN server. Attached is a screenshot of the error.

- Brad