invalid EOL specified!

George · Post by **George** » Fri Dec 23, 2005 1:48 pm

We recently branched for a new release. Then we started getting errors of the form:

Local file update for <FILENAME> failed: System.Exception: invalid EOL specified!
   at VaultClientOperationsLib.OperationsMisc.ChangeEOL(String fileNameIn, String fileNameOut, Int32 EOLin, Int32 EOLout)
   at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(VaultClientFile file, Int64 targetVersion, Int64 displayVersion, MergeType merge, DateTime dt, Boolean makeBackups, OverwritePrompt PromptData)
   at VaultClientOperationsLib.WorkingFolder.UpdateWorkingFile(VaultClientFile file, Int64 targetVersion, Int64 displayVersion, MergeType merge, DateTime dt, OverwritePrompt PromptData)
   at VaultClientOperationsLib.ClientInstance.ProcessGetFileRequests(GetFileInfo[] infos, MakeWritableType makeWritable, SetFileTimeType setFileTime, MergeType merge, Boolean updateHiddenFilesOnly

These errors start about 2/3 of the way through the checkout portion (vault.exe get -destpath) of our automated build process. This seems to affect only the branch and not the trunk. This error happens on both the Windows gui client and the Linux cmdline client (mono 1.1.12).

We are using Vault 3.1.4.3543 (client and server). I also noticed that the release notes for version 3.1.5 sound relevant to our problem (although not all our problem files are binary or recently modified). Being close to release we don't want to upgrade Vault if this will not fix our problem.

dan · Post by **dan** » Fri Dec 23, 2005 2:02 pm

This is the exact problem that 3.1.5 addresses, so it would be a good idea to upgrade.

Sorry for the inconvenience...

George · Post by **George** » Wed Dec 28, 2005 12:15 pm

Can we get by with just upgrading the client. Or do we need to upgrade the server?

lbauer · Post by **lbauer** » Wed Dec 28, 2005 12:26 pm

This was a server-side problem, so you do need the 3.1.5 Vault Server for the fix.

For best results, Vault client and server should match.