Hi, thanks for the reply.
I posted in the DNN forums to try and get some comment on the issue, because I had found more than one thread talking about it without a solution. That post is
here. I'll bump that post up again soon.
In the meantime, I've screen-grabbed the event log from the point I created a page and added the module. One can see where the module added the scheduled task and presumably it changed to timer mode after that.
Because I saw the info in the module intro screen and already knew that my portal would likely freeze in timer mode, I tested by restarting the application in Host Settings to check - this saves waiting for my daily recycle. Sure enough, the portal froze.
Now... the other person posting in my thread, Fooberichu, is thinking it might be caused by other tasks. I'm not sure what happens, but there are no scheduler errors.. it feel more like the event queue just doesn't even start. All my other tasks have been running for a long time. I have most of them slowed down and offset by minutes to avoid overlap.
The second to top event in the image is where the application started and just stayed.. then, 7 minutes later the top event shows where I started it again by force in IIS manager. There are no further events inbetween, so the problem is somewhere immediately after the Event Schedule Start operation.
I signed in using my host's SQL manager tool and simply went hunting for where I thought the setting might be.. that was in Tables, HostSettings, SchedulerMode. That was set to 1. But as I was unsure what the real value should be and didn't want to waste time, I signed into my test portal and checked there and found it to be 2. Applying that let me restart the portal.
I haven't been back to the page where the module is since.
I haven't got much else I can add at this point I'm afraid.
Rob