We have upgraded the server from 5 to D6, nd the client as well… now the subscriptions aren’t working, as seen in some other posts we get a message in headline.nsf that says: “Retrying: Monitor has already been registered”. So we tried disableing some of the subscriptions, and even deleting them to re-add new ones. Now the new ones don’t even show up in the Welcome Page frame.
We also changed the Welcome screen, then changed it back thinking it might ‘jog’ the memory of the headline.nsf database… still doesn’t display the names of the 2 new subscriptions, and doesn’t display the new documents added to the ones that are displaying titles.
I just wanted to say here that we have that same problem too.Even if deleting the subscriptions and recreating them using new names (as proposed from Lotus Support as a workaround) in some cases the old subscriptions reappeared mysteriously from anywhere. Other subscriptions were suddely multiplicated (resulting in lets say 30 subscription documents of the same subscription name.
Another proposed workaround was to restart the server after change in the subscriptions. Thanks, Lotus, for that joke. Indeed I will restart the server each time after any user changed any of his subscriptions… ROTFL
I already spend some hours in discovering that problem. So far, I’m very depressed now. I even was not able to find a way to bullet-proof reproduce the failures.
I also launched a call at lotus support last week regarding that issue, it is currently open.
What we need is that Lotus changes its plans to “yes we will fix it asap”. But, I expect this will only happen in reaction to massive customer complaints. So you all are invited to do so.
Many of our users are using subscriptions with their current R5 clients, And I won’t roll out the R6 cient until that issue has been fixed.
As long as lotus (or ibm?) has no plans to fix it I could believe Lotus wants to let the Notes Client agonizingly die over time.
We’re running Notes 6.0.2 CF1 on our server and my client. I had a couple of database subscriptions that I created in R5 that didn’t seem to be working, so I deleted them and recreated them in 6.0.2. I also get the message “Retrying: Monitor has already been registered, no action taken”.
I read that subscriptions were suppose to refresh twice as often as you checked for new mail. Is there anywhere that shows this? As far as I can tell, mine hasn’t refreshed since 9/15, even though I’ve purposely made changes to a database to see if the changes showed up in my subscriptions.
Finally somebody who has experienced the same problem as I have. If you, or anybody else ever get this feature of subscriptions to work, please post the solution here.Thanks a lot.
I had an incident open with Lotus about this and the support told me that the problem is known to Lotus support (Software Problem Report (SPR) SPR # MTAA4QF57X), but the state of this SPR is “no plans to fix in codestream 6”
That’s exactly what we have now, after upgrading the servers from R5 to R6.03.
Some of the first test findings was the “Retrying: Monitor has already been registered” error when using subscriptions in an R6 mail database which was also upgraded from R5. Deleting or re-creating the subscriptions doesn’t make any difference. But even worse, I had three (3!) server crashes in a couple of minutes and this was definetely caused by exact these subscriptions. Before the crashes the server was getting slower and slower over the time of one or two days. Some console errors - to which I haven’t access right now to post it here - showed up a “Monitor list corrupted” or something similar.
Another issue is that subscriptions cannot be sorted in the view by any criteria and/or loose their position after restarting the client.
Third problem is the hoover line over an new subscription topic: It seems this is now a real story teller; it displays way too much information as in R5. (Canonical names, topic, subjects, all twice).
Looks like Lotus isn’t interested in these problem!?