Dears, I’ve got a PMR open for this issue: I’m medium satisfied. The First Level was proposing to switch of Antivirus/Firewall (this answer is bullshit) The 2. Level is proposing to setup the events4.nsf from the scratch. - Well that helps, but in our “old” events4.nsf we have a lot of settings and I’m not very happy to make all our 100 setting new.
Now, I try to find out if the DDM probes a responsible for this issue or something else.
We have solved the problem.
The events4.nsf, the “Monitoring Configuration” has been completely rebuild. But what actually helped was, to install the FP2 on Domino 9.0.1.
After the FP2 installation the error message didn’t appeared any more.
But the actual cause will probably stay a mystery forever.
Subject: Re: The last argument to tell event is an invalid value
I’m also seeing a lot of recurring “invalid value” messages in the log.nsf on one of our 9.0.1 servers (the clustered server doesn’t produce these log entries for some reason?):
The last argument to ‘tell event ddm.nsf’ is an invalid value The last argument to ‘tell event statrep.nsf’ is an invalid value The last argument to ‘tell event cldbdir.nsf’ is an invalid value The last argument to ‘tell event log.nsf’ is an invalid value The last argument to ‘tell event mail.box’ is an invalid value The last argument to ‘tell event mail\somename.nsf’ is an invalid value
Are you saying the solution is to enter the following console commands?