Two users complained of System.ExecutionEngineException being thrown by their GUI client when connecting to a particular repository.
After rebooting, re-installing the client and the .Net Framework the problem was still there. So we resorted to deleting the client-side cache.
That fixed the problem, but I've noticed that both users always show as 'Logged In' in the Admin tool, regardless of whether they are or not. I've checked the logs and confirm that they're not logged in from other machines.
I'm not sure whether this was caused by the client crash, or whether it is indicative of the cause.
After deleting the entire cache I found the post saying you could delete individual files from it (d'oh!). In both cases their CacheMember_PendingLocalDeletions file was enormous (0.5GB for one guy), so I'll try just deleting that if another one comes along.
Meanwhile, is there a way of ending a users session (i.e. getting rid of that spurious Logged In status)?
I've tried setting them to InActive and back again, it made no difference.
Thanks.
Users still show Logged In after logout (version 2.0.6)
Moderator: SourceGear
Re: Users still show Logged In after logout (version 2.0.6)
That would not be a popular move with our other developers, as we need to do it too frequently anyway because of another issue (which of course hasn't happened since I've been looking at this).
I was after a more precise method that would only affect individual developers.
Out of curiosity, are they showing as 'Logged In' because the logins are 'reference counted' and the client crashed before it could logout?
I was after a more precise method that would only affect individual developers.
Out of curiosity, are they showing as 'Logged In' because the logins are 'reference counted' and the client crashed before it could logout?