Something very very strange started to happen this morning...

While processing a server event, K2 started trying to bind a DLL completely unrelated to the workflow, or a DLL the workflow uses.

Imagine the workflow has a .NET DLL containing functions that it uses, and has done for ages - we'll call it "foo.dll"

Now imagine there is another dll called "bar.dll" that does exist in other projects, but is not referenced *at all* in the K2 project, or by foo.dll.

In our case, as soon as a specific method in foo.dll is called, the K2 server complains that it cannot bind "bar.dll" because it can't find it.

WEIRD

Any ideas where to look beyond the normal log files ?