Is the 4.0 command line client suppose to be backward compatible with 3.x servers?
If the databasen.sos says it's vesion 3.0 does that refer to the db file format or the version of the server?
With the 4.0 command line client and our 3.x server my GetProject calls
get lines like these interspersed in otherwise correct file gets
Requesting file: 1 <= Will request a number
Error: Server response = 401 NoSuchFileOrProject
Requesting file: 02/06/2003 12:24 <= and a date
Error: Server response = 400 OperationFailed
Requesting file: <= and a blank
Error: Server response = 400 OperationFailed
If I switch to using 3.5 soscmd.exe it works much better but doesn't respect the -skipwritable parameter.
(I clean out the database files before switching)
Please help.
soscmd.exe 4.0 and 3.5 server
Moderator: SourceGear
We have found some incompatibilities when using the SOS 4.0 command line client with an SOS 3.5.x server.
The 4.0.x GUI client is more compatible, but for best results, we recommend using matching versions of SOS Client and Server.
Although a 4.0 client can connect to a 3.5.3 server for basic operations, it's intended as a transition and not as a long-term solution.
The 4.0.x GUI client is more compatible, but for best results, we recommend using matching versions of SOS Client and Server.
Although a 4.0 client can connect to a 3.5.3 server for basic operations, it's intended as a transition and not as a long-term solution.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-skipwritable
OK but what about the fact that the 3.5 command line client doesn't seem to honor the -skipwritable parameter?
Eric
Eric