Ugh!  Someone, please help!

I deleted two module definitions from my DNN 3.3.5 install, and now the site is crashing.  I'm getting these kinds of errors:

AssemblyVersion: 03.03.05
PortalID: 0
PortalName: Psi Phi Delta Fraternity
UserID: 506
UserName: xxxxxxxx
ActiveTabID: 73
ActiveTabName: Forums
RawURL: /Members/Forums/tabid/73/forumid/23/postid/3295/view/topic/ptarget/3310/Default.aspx
AbsoluteURL: /Default.aspx
AbsoluteURLReferrer: http://www.psiphidelta.net/Members/Forums/tabid/73/Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows 98)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: b5936a3b-42d2-4596-a9d1-a35fdc00e700
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Framework.CDefault.Page_Init
StackTrace:
Message: DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Framework.CDefault.Page_Init(Object sender, EventArgs e) at System.Web.UI.Control.OnInit(EventArgs e) at DotNetNuke.Framework.PageBase.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain() --- End of inner exception stack trace ---
Source:
Server Name: xxxxxxxxxx

My guess is that one of the modules was still on some page somewhere -- and possible set to Show On All Tabs.  Could that explain why this is happening?

I'm trying to dig through all the "module" tables and figure out what's messed up, but I'm not having much luck.

Can anyone offer up suggestions to get this back up and running?

Thanks in advance,

-- Bryan

Stephanie,

Thanks for the reply.  I deleted the whole module, using the hosts account, not just one instance of it on a page.

I believe I have gotten past the problem, however.  This appears to be (yet another) side-effect of caching.  An instance of one of the modules was set to "display on all tabs".  When the module was deleted, all of the instances were also deleted, along with the DLL and ASCX files in the DesktopModules folder.  What I think was happening is that the cached pages were still being run, and they were failing because the DLL they needed was now gone.

In any event, I've got my fingers crossed.  Since I cleared the cache, things seem to be back to normal....

Thanks again for the response!

 - Bryan