I found the cause yesterday....

This WebApp communicates via WebServices with another WebApp.
It only should communicate after the user has logged in, but it tried to send a certain message too soon. This resulted in this particular error.
Because we never noticed this on our development computer and never saw this error, we didn't think of this before.

Thanks all for your input, sorry for wasting your time...