MKACTIVITY ERROR 200 OK during commit

["Scheie, Eric" <es...@ncr.com>]

Hello,
 
We've stood up 3 different subversion instances across the country, call them locations A, B, and C.  We use apache 2.2.3 and WebDav for remote access.  Location A users can commit to location A without any errors.   Location B and C users can also commit to location B and C respectively without any errors.  If a location A user tries to commit to location B or C, the user gets the following error:
 
 
 Commit failed 
MKACTIVITY of '/svn/!svn/act/35981eaa-0a77-1f44-924e-2f13c87c6555': 200 OK (http://xxxx.xxxx.xxxx) 
 
 
If the location A user tries again, the commit is successful.     Same results with location B user commits to locations A and C and location C user commits to locations A and B.   Commits after the first failed commit are always successful.  The first commit of the day to a remote location always fails.  This problem has been noticed with the TortoiseSVN client, the SVN command line tool, and the SVN plugin for IntelliJ.    Does anybody have any clue of what's causing these commits to fail the first time they are issued?
 
Thanks,
-Eric