SVN 200 Error committing binaries

Jul 30, 2010 at 10:26 AM
Edited Jul 30, 2010 at 10:34 AM

I've spend all morning trying to repair projects that has been broken by the migration to TFS2010 and I'm stuck.

Since the UUID's didn't match (see http://codeplex.codeplex.com/Thread/View.aspx?ThreadId=220228) I had to do a "fresh checkout" but now I can't check in changes since it always ends up with something like:

Server sent unexpected return value (200 OK) in response to PUT request for '/svn/!svn/wrk/1dd031a9-6f47-8347-8c4c-63897da7c672/trunk/Qreed.Xna/Qreed.Xna.SandBox/GameThumbnail.png'

It's only occurs when I'm committing binaries and it doesn't matter which SVN client I'm using.

Any clues?

Thanks.

(Edit: and why aren't my enters saved in this message? :S)
(Edit: seems that Codeplex only likes IE?)

Jul 30, 2010 at 7:04 PM

same problem here. 

Aug 5, 2010 at 10:59 AM

Same problem for me but with a project created yesterday.
I'm unable to commit a resx file containing an image, it ends with the same 200 error :

Server sent unexpected return value (200 OK) in response to PUT request for '/svn/!svn/wrk/11c9dc0e-0bc0-4345-9368-66771e7c7f65/trunk/IrChat.Interface.WinForms/Interface/Windows/LogWindow.resx'

Thanks in advance.

Aug 5, 2010 at 12:59 PM
Just +1 to the problem... Began getting 200 error pulling svn projects today....
Aug 5, 2010 at 2:17 PM

I've got the same problem here while committing binary files.

Server sent unexpected return value (200 OK) in response to PUT request for '/svn/!svn/wrk/61215e4a-0386-524e-b9fe-b486c952aa99/trunk/libs/Microsoft%20SQL%20Server%20CE%204%20CTP%201/x86/sqlceca40.dll'

Plz fix :)

 

Aug 6, 2010 at 6:49 AM

Fixed for me, everything has been comitted this morning without problem.

Aug 9, 2010 at 7:19 AM

Yep, now it works. But i'm a little bit angry about the codeplex team. What caused the problem? And why does this occur so often. If you search for this problem you'll find many post from the last months / years that this problem happens frequently.

Maybe the codeplex team should add a "current technical issues" section to the home page where they report such problems und also their solutions. So that users don't need allways to open such threads :)

anyway thx for fix.