Hi Ivan, * There are no control characters in my commit message * The svn:mime-type is 'application/octet-stream' that was automatically set by TortoiseSVN when the file was added. * There doesn't seem to be any other control characters in other properties of the file
I finally just deleted and re-added my image files late last night and they don't seem to be giving me this error anymore. Instead I'm now getting the 207 error that I described in another support request: PROPFIND of '/svn/Success/!svn/bc/5780/App/trunk/Success/App_Themes/Blue/images/ critical-error.gif': 207 Multi-Status (https://server:8443) Error reading spooled REPORT request response when trying to merge trunk changes into feature branch. Regards, David Hollifield LoadOnCall, Inc. [EMAIL PROTECTED] Phone: (770) 232-1974 Mobile: (678) 428-2851 Fax: (770) 232-0169 + /_\ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of VisualSVN Team Sent: Thursday, November 06, 2008 6:45 AM To: VisualSVN; [EMAIL PROTECTED] Subject: Re: PROPPATCH error when checking in/out and merge Hi David, Please check the follow: * Your commit message does not contain control characters. * Value of svn:mime-type property on the file /Enterprise/App/trunk/Success/App_Themes/Black/images/Account.jpg It should be something like 'application/jpeg-image' * Check for control characters in other properties of the file. -- Ivan Zhakov VisualSVN Team On Thu, Nov 6, 2008 at 12:20 AM, David <[EMAIL PROTECTED]> wrote: > > I keep getting the following error when trying to commit a modified > image file to Subversion: > > Commit > Clients\USCOST\dev\Success\Enterprise\8.1\App\Success\App_Themes\Black > \images\Account.jpg > Commit failed (details follow): > At least one property change failed; repository is unchanged > Server sent unexpected return value (400 Bad Request) in response to > PROPPATCH > request for '/svn/Success/!svn/wrk/09d36451-6082-914f- > b1a4-58d1a8f1f084/Enterprise/App/trunk/Success/App_Themes/Black/images/ > Account.jpg' > > The event log has: > XML Parser Error: XML parser error code: not well-formed (invalid > token) (4) > > Does anyone have any ideas what could be causing this and/or how to > work around it. > > Thanks, > David > > VisualSVN Server: 1.6.2 > VisualSVN: 1.5.4 > TortoiseSVN: 1.5.5, Build 14361 - 32 Bit , 2008/10/24 18:06:34 >
