I have a dot net nuke web site (4.5) and it is currently down. This is a public facing web site and when a user attempts to connect to the web site it is attempting to redirect them to one of the portal aliases.

When this web site was being developed it was created on a server called dev, so it had a portal alias added to it called dev. Prior to moving it to production we added the portal alias for the real url (www.mysite.com).

I am seeing some entries in the windows event log (sql Exception) that leads me to believe that it is having a hard time connecting to my sql server. I have had my network guys open all of the ports from the public facing web server to our non-public sql server, I have setup a trusted connection between the two, I can login to the sql server as the user account and hit the database.

I have also seen some entries in the windows event log about object reference not set to an instance of an object.

I have seen some other messages in the forms about excessive table size for EventLog, SiteLog,  and ScheduleHistory. I have truncated all of these tables. I have also had the dba increase the size of the transaction log file.

Any suggestions on how to get the web site up and running again ?

What do you see when you

select * from portalalias

Is there something there that matches the virtual directory (URL) folks are using to come to the site? I've seen behavior similar to this when the virtual directory is set up correctly - points the correct physical location for the DNN install - but there was an error in the httpalias so that nothing matched the incoming URL. Then DNN redirects to the default portal.

Worth a look-see.