Hello Jeroen,
No, nothing is reported in the errorlog.
I have altered that message. Executing the query still doesn't report something in the errorlog.
We have this with only one query, it's a small table, so I copied it into a table with a different name, renamed the original table and created a view on the new table with the original name.
That worked and eliminated our production problem.
The problem was still reproducable on the old table.
Difference with the new situation is that triggers were added to the new table and didn't cause problems.
So I dropped and recreated the update trigger on the old table, and then the problem disappeared.
Conclusion is that there must have been some corruption in the trigger code.
The original situation is restored and the query is running fine.
Thanks,
Luc.