Stefan,
Thanks for the reply. I think I've discovered the source of the authentication corruption. After you suggested the virus scan I ran a few tests to see how long after being re-established did the authentication get hosed. During that time I had the virus scan status console. In two different tests the time before corruption was 40 minutes apart. However I didn't see that the virus scanner ever affected the file in question. That got me thinking down the road of other possible applications that may have access to the file that could corrupt it. It turns out that it is quite possibly the svn integration within the JDeveloper IDE that was messing it up. During both tests the IDE was open and there is a window showing 'Pending Changes' for the code base. After disabling the svn support in Jdeveloper, a few hours ago, the authentication files remain in tact. So hopefully this has resolved my problem.
Thanks again,
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2447782
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-02-15 17:37:55 CET