The last argument to tell event <db> is an invalid value

Hi,

I get a lot of these error messages on the domino console: The last argument to ‘tell event ’ is an invalid value.

I have two identical servers. Only difference is that DAOS is turned off on the one producing the errors.

Windows server is 2008 R2 - 64bit.

Best regards

Torben Strand Johansen

Subject: The last argument to tell event is an invalid value

Hi,

I have the same issue, on same environement. (I have only one server, DAOS off also).

No antivirus, no firewall…

Any advise on that matter ?

Thx

Julien.

Subject: tell event invalid value - PMR

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.

Daniel

Subject: Re: The last argument to tell event is an invalid value

Hi!

I also have the same problem…

i made an experiment:

I stopped the event task

i stopped the Symantec Endpoint Protection

I started the event task again…

Now the anoying messages are gone. Even after i started SEP12 again…

I don’t know what happens when i restart the box…

So the question is: In what way are anti-virus software affecting the event task?!?

/Anders

Subject: The last argument to tell event is an invalid value

Thanks for your help !

This works :
tell event quit dbcache flush load event
Regards,

Julien

Subject: Solved

Hi all

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.

cheers,

Daniel

Subject: RE: The last argument to tell event is an invalid value

Hi

Since an upgrade to 9.0.1 form 9.0.0 I have the same issue: “The last argument” to ‘tell event log.nsf’ is an invalid value.

I quit the event task, making a “dbcache flush” and restarting the event task. Then the erreor is gone…

Maybe there is a INI key witch I don’t know?

Cheers

Daniel

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?

tell event quit dbcache flush load event

Thanks for you help!

Subject: Same here

Same issue here. I have 9.0.1 using ScanMail from Trend, but it doesn’t seem to be the problem.

I’ve restarted the Event task and the error is no longer appearing

Subject: Notes.ini

What is the order of the task line in the notes.ini. Based on what you say the sep12 task needs to be started last.

Subject: Re: The last argument to tell event is an invalid value

Hello Torben,

Try to check your Antivirus, Firewall or review Antivirus/Firewall settings

Best Regards