We are seeing this on some of our machines as well, but only in Max 2010 32bit. Can you confirm that it works as expected for other platforms/releases. We currently do not know why this is the case.
Ok, I’m still not clear on which version of Max you are seeing this for. At our location we only seem to get this error when running Max2010 32bit, and only on a handful of machines. Are you seeing this problem with Max2010 64bit?
Thanks for the information. I had been giving our IT department a hard time because I thought it was just our machines. At least now I know that build of Krakatoa is the real culprit.