Hallo Matthias,
I will check do a big check next week. I looked around in the database and everything seems to have the right user. All other modules run fine.
I also checked the logs again. And maybe I have found a clue. I checked in the database and discoverd that de DesktopModuleID mentioned in the logentry below doesn't exist. The current forum has a different DeskopModuleID.
I'm thinking that the system is trying to upgrade an old forum module. Then tries to tell the module it's finished upgrading. But the module doesn't exist, so next time it's upgraded again and again and again....
It's probably because I removed the module files of the forum by hand when the system crashed when I installed modules (the systemadmin hadn't given the ASP.NET worker process access to a temporary directory needed for compiling. I thought is was my fold. And tried to get the system running again by removing the stuff by hand)
So somewhere in the system there must be a reference to the old module. Do you have any idea where I need to look? Could my hunch be right?
The permissionproblem I mentioned (not the one that caused the crash) was that users couldn't access the images because they had no permissions to access the image directory. The ASP-workerprocess permissions where fine.
**** LOG MESSAGE ***
ProcessorType: DotNetNuke.Entities.Modules.EventMessageProcessor, DotNetNuke
Body:
Sender:
BusinessControllerClass: DotNetNuke.Modules.Forum.ThreadController, DotNetNuke.Modules.Forum
DesktopModuleId: 56
UpgradeVersionsList: 03.00.00,03.00.10,03.00.11,03.00.12,03.10.01,03.10.02,03.10.03,03.10.04,03.10.05,03.20.00,03.20.01,03.20.02,03.20.03,03.20.04,03.20.06,03.20.07,03.20.08
ExceptionMessage: Object reference not set to an instance of an object.
Server Naam: W3ZKHAS18