soscmd 4.1 problems

Bill Medland · Post by **Bill Medland** » Thu Feb 03, 2005 11:33 am

I am trying to set up an overnight sync script using soscmd but it appears to be doing unexpected things. Am I using it wrong or is it a bug?

soscmd.exe dated 13 December 2004. I presume this is 4.1 and is up-to-date
I think the server is still running 3.5

a - Weird filenames. When I do a GetProject on an example project and turn on the verbose I see it trying to get "files" which are actually dates. I presume that this is a version incompatibility. Should the 4.1 soscmd be able to run against an old server?

b - Getting to the current directory instead of the working directory. SOSHOME is set and also passed to soscmd in the -soshome. Yet the files are got to the current directory instead of the working directory (and they shouldn't be got anyway; they are up to date). Any idea why?

lbauer · Post by **lbauer** » Fri Feb 04, 2005 10:49 am

We don't support using SOS 4.1 clients with SOS 3.5 servers. Although they can connect, certain operations don't work properly, and we haven't tested this combination, sorry.