MiCollab Client - Login Notify not working

[VinceWhirlwind]

When I right-click on an entry in MiCollab Client, Corporate Directory, normally I can "Enable Login Notify".
 
Today, I get "Failed to Enable Login notify for this contact".
I've tried a bunch of different people and it fails for all of them.
 
I wonder if I've inadvertently broken this somehow...?
 
Otherwise, if I tried it, would restarting the MiCollab Client service have any relevance to this error, do you think?

[VinceWhirlwind]

Just found a guy I already had "Login Notify" enabled for.
"Disable Login Notify" does nothing, not even en error message like "Login Notify" does.
 
It's like the whole "login notify" thing has failed. Is this thing on its own service or is it just part of the MiCollab Client service?

[io]

I'm almost wondering if your server is running out of memory, and is preventing you from writing any further information to it. Do you have any other issues within the client, such as creating new users or modifying their information? Have you tried restarting the server? 

[VinceWhirlwind]

The problem with restarting the server is that it makes all MiCollab users available for video chat (the green video icon comes up against everybody). Seeing as they don't use video, this makes it obvious that the server has restarted, and therefore I'm up for having to provide a Post Incident Report explaining why the server restarted.
 
Your memory idea is good though, I've always been sus about the MiCollab memory.

[VinceWhirlwind]

So the MiCollab memory utilisation had reached about 84% - and 2/3 of that was "cached".
I suspect "cached" memory is being poorly managed and some of it is never released.
 
Anyway, restarting it released all the cached memory so memory is back down to 30%.
 
Enable Login Notify still fails.
 

[io]

Do you still get notifications in your OS when someone calls or chats? Any recent changes in network infrastructure that might account for this?

[VinceWhirlwind]

Calls and Chats are working fine.
Missed calls appear in the system tray as per normal.
 
Nothing else seems to be broken.
 
However, you got me thinking...."Enable Login Notify" might be using a specific connection that nothing else uses.
If I can understand the source/destination/port then perhaps I can point the finger at some new security funny business that might have occurred.