I get an annoying popup error with lots of entries:
“An internal error occurred during ActivityMonitor”
“Messageprocessor is null or has not been started”
What to do?
brgds
Jesper Kiaer
Subject: Forwarded to development <>
Sametime/jp/hd
Subject: MessageProcessor is null error
This was fixed for Sametime standalone and that fix was brought over to Notes to address this for Notes 8.02 and 8.5, here is the SPR for Notes 8.5: ATHS7BBQ76: Multiple errors have occurred: MessageProcessor is null or has not been started!
The fix was verified and the SPR closed, so I’m wondering if you upgraded to Notes 8.5 from a previous version and if so, if this maybe an upgrade problem? I see this comment in the SPR:
9/1 LD - per James “Yes, I agree. In fact when Eric Spencer thought he had seen this again after we had fixed it for Notes 8.0.2 and 8.5, we’ve now determined he was actually seeing it as part of the previous Sametime from Notes 801, since the real problem was a faulty upgrade. So the text below is a workaround, and we think again that this is indeed fixed for Notes802 and 8.5”
The workaround they discuss is simply disabling Preferences/Sametime/AutoStatus Changes, since that is where this error comes from. Disabling this should stop the error and it’s likely that you could re-enable it after running Notes for sometime, since this was likely a timing issue where this MessageProcessor simply was not started before this AutoStatus change code tried to use it. The fix of course is to check to see if that is the case.
Subject: Sametime not installed
Hi
Thanks for the response.
I looked and there is no preferences/Sametime…
option.
I deselected installation of the integrated Sametime Client when I installed the Notes Clients.
brgds Jesper Kiaer
Subject: Same problem here.
I’m running Notes Standard 8.5, without Sametime. OS: WinXP.
I also get a lot of:
An internal error occurred during: “ActivityMonitor”. MessageProcessor is null or has not been started!
Subject: Same here
I did an upgrade from 8.0.2 without sametime and this error message keeps popping up now.
Subject: Workaround
I had 8.01 installed (with Sametime as it is installed by default). I upgraded to 8.5 and did not install Sametime and I got the ActivityMonitor errors.
So I reinstalled with Sametime and that has stopped the errors.
Subject: Are you serious?
One shouldn’t be forced to install Samtime to resolve this really annoying error…
IBM: are you not interested resolving this…?
All posts here is either “I too have this error” or “seems like…” - not helping!
Subject: An internal error occurred during: “ActivityMonitor”. MessageProcessor is null or has not been started!
Yes -I am routinely getting this on one of my machines - it’s at home and it’s very annoying.
I have 8.5 Client, Admin and Designer version running on Windows XP SP3 but no built-in Sametime - I am however running Sametime Standard 8.0.1 and Notes Minder as separate tasks.
I get these popups every few minutes. It happens whether or not I run VPN
David Clover
IT Development Manager
Maths Computing and Technology Faculty
The Open University
Subject: RE: An internal error occurred during: “ActivityMonitor”. MessageProcessor is null or has not been started!
Thanks to Mangala Sadhu Sangeet S Khalsa for pointing in the right direction!
As poninted out - This has to do with the Activity monitor feature under Eclipse.
My temporary soloution (until IBM bothers to give us a serious response in this forum) was to rename the folder under
…\lotus\notes\framework\shared\eclipse\features
com.ibm.collaboration.realtime.activitymonitor.feature_8.0.0.20080130-1459
to
RENAMED_TO_FIXcom.ibm.collaboration.realtime.activitymonitor.feature_8.0.0.20080130-1459
and the folders under
…\lotus\notes\framework\shared\eclipse\plugins
com.ibm.collaboration.realtime.activitymonitor.win32.win32.x86_8.0.0.20080130-1459
to
RENAMED_TO_FIXcom.ibm.collaboration.realtime.activitymonitor.win32.win32.x86_8.0.0.20080130-1459
and
com.ibm.collaboration.realtime.activitymonitor_8.0.0.20080130-1459
to
RENAMED_TO_FIXcom.ibm.collaboration.realtime.activitymonitor_8.0.0.20080130-1459
You’ll have to close notes while renaming…
Subject: An internal error occurred during; “ActivityMonitor”
I thought I would also mention that the problem also surfaces with the 8.5.1 client for Windows XP. I only noticed the problem after installing SP3.
Subject: Good to hear everything is solved.
Just to clarify that the issue was reported to development earlier in the thread. However this is a community forum not an official place to get interaction with support/development.
In future if you need more focus please open a PMR. Thanks! 
Subject: Manually upgrade ActivityMonitor
I forget if I did a fresh Notes 8 install or upgraded from 7, but in any case I have upgraded from 8.0 to 8.01 and then to 8.02, and now to 8.5. It appears that at every new upgrade the installer failed to update the ActivityMonitor, as after installing 8.5 I discovered the following in Notes\framework\shared\eclipse:
features\com.ibm.collaboration.realtime.activitymonitor.feature_8.0.0.20080130-1459
plugins\com.ibm.collaboration.realtime.activitymonitor.win32.win32.x86_8.0.0.20080130-1459
plugins\com.ibm.collaboration.realtime.activitymonitor_8.0.0.20080130-1459
plugins\com.ibm.collaboration.realtime.service.activitymonitor_8.0.0.20080130-1459.jar
The Notes installer is too lazy to delete the temporary installation files, and I hadn’t got around to it yet, so I looked in there and found updated versions in updateSite.zip:
features\com.ibm.collaboration.realtime.activitymonitor.feature_8.0.1.20081118-0430
plugins\com.ibm.collaboration.realtime.activitymonitor.win32.win32.x86_8.0.1.20081118-0430
plugins\com.ibm.collaboration.realtime.activitymonitor_8.0.1.20081118-0430
plugins\com.ibm.collaboration.realtime.service.activitymonitor_8.0.1.20081118-0430.jar
I deleted the old and copied the new over and haven’t had problems yet… time will tell, but it shouldn’t take much time as the ActivityMonitor error popups would hardly leave me alone before.
Subject: Manual upgrade doesn’t work
It seems this “fixed” my problem because in deleting the old files I got rid of the ActivityMonitor altogether. However, copying the new files in place was not sufficient for upgrading the feature - the new files seem to be ignored and the feature is simply gone.