I found the solution to my problem, and it was simple one at that.  The problem was that a couple weeks ago, I had set up an application in IIS, and in order to set up that application, I had to add a virtual directory called "admin".  So when I installed DNN, it seems that because this admin application already existed, DNN could not install its own admin.  So when I am trying to go to the portal, DNN it's looking for its admin folder but is not finding it.

So all I had to do was delete that first virtual directory that I had created, restart IIS and BAM!!!...the portal now shows up...as simple as that.

I've been seeing the admin application, but never thought to expand IIS to see what folder the admin virtual directory was pointing to.  When I did that, I saw that it was pointing to a folder other than the DNN admin folder.

So anyway, if anyone is experiencing this same problem, a good tip would be to check IIS to ensure that all virtual directories are pointing to the correct folders, particularly the admin folder for DNN.

Now I can move on to bigger problems!!

ltsolis

Hi,

I am having exactly same issue, with slightly different scenario.

I had the working directory of DNN (4.9), i compiled a VS 2003 application, in VS 2008 and ran it. The VS made a virtual directory in  the same directory in which my DNN website was, consequently when i run DNN localhost\default it gives Null Reference error.

From this post I do get the idea that the references (probably directory) are out of order. But couldnt get it working even after deleting the virtual directory, restarting IIS or even trying to reinstall DNN on same and different directories.

I'd also like to mention i have another DNN website installed on the machine, which is working fine.

Any help will be of immense value.

Thanks & Best regards.

Kaft