[WislegC]

Here it is, I just wanted to post this for posterity.

In our environment we have two NT Login accounts per person, for example "foobar\foo" and "foobar\fooA". The A account is for more secure access to sensitive areas.

We use Windows remote desktop to access our Windos XP build machine, which is where the visual build scripts live. On Windows XP only one user can be logged into a machine at a time via Remote Desktop. A user "foobar\foo can cleanly log themselves out of the machine, so that when user "foobar\fooA" logs themselves in every thing works fine, this error does not occur.

However if foobar\foo is still logged into the machine one can log in with a different account like foobar\fooA, but the session foobar\foo gets terminated. In this scenario the error I explained occurs. Logging out of foobar\fooA or rebooting fixes the problem.

I think Visual Build is having a problem (or probablly likely Windows is mucking things up) when an account is forcefully terminated in remote desktop, rather than cleanly logged out.