Expected 300, but got a 415.

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

Post Reply
mvh

Expected 300, but got a 415.

Post by mvh » Thu Sep 22, 2005 8:36 am

I'm trying to run soscmd with these parameters:

-verbose -soshome "c:\Program Files\SourceOffsite" -server SERVER:PORT -name USER -password PWD -database DATABASE -project PROJECT -command GetProject -skipwritable -recursive

where PORT is a secure port.

But I'm getting this:
SourceOffSite Command Line Client: 128 bit Encryption version 4.1.2
Connected to server SERVER at port PORT.
Received Secure Challenge from server
Unexpected server message after login. Expected a 300 Success, but got a 415 (InvalidEncryptionKey)
Server Message Body = (null).
Closed connection to server SERVER at port PORT.


I tried "telnet SERVER PORT" and it gets connected ok. Also, I use the GUI client with no problems. More info: the key was imported ok, the .key file name is the same as the server.

What could be the problem?

Thanks,
mvh.

bfinney
Posts: 81
Joined: Fri Dec 17, 2004 11:27 am

Post by bfinney » Thu Sep 22, 2005 8:41 am

Any command using the secure port must use the -soshome parameter to specify the location of the key. Note that -soshome will get the files to your working folders (as set in the GUI client), so if you don't want that, you must specify -workdir as well.
Brody Finney
SourceGear QA Thug
"I break things for a living"

mvh

Post by mvh » Thu Sep 22, 2005 8:54 am

I'm using -soshome:

-soshome "c:\Program Files\SourceOffsite" ...

I also added the -workdir but I'm still having the same problem.

mvh.

Bill Medland
Posts: 25
Joined: Fri Dec 03, 2004 12:55 pm
Location: Canada (Pacific)

Post by Bill Medland » Thu Sep 22, 2005 9:00 am

And are you sure that is the correct SOSHOME? Does it contain an index.sos?

bfinney
Posts: 81
Joined: Fri Dec 17, 2004 11:27 am

Post by bfinney » Thu Sep 22, 2005 9:02 am

D'oh! That'll teach me to read too quickly.

The home directory in 4.x versions of SOS is not within the install directory - by default it's in C:\Documents and Settings\<user>\Application Data\SourceGear\SOS.

If you look in that path, you should see a <servername>.key file. This is the actual key - the .iky file that's probably hanging around in you SOS directory is not the live one.
Brody Finney
SourceGear QA Thug
"I break things for a living"

mvh

Post by mvh » Thu Sep 22, 2005 9:10 am

Hi.

No it does not, that's where the .key file is. The index.sos file is located at "C:\Program Files\SourceOffSite\servers\SERVER\index.sos". (SERVER = the server I'm trying to connect to).

However if I change -soshome to that path, I get the error "Unable to open key file". I tried copying the .key file to that path and after doing that I get the error "Expected a 300 Success, but got a 415" once again.

Thanks, mvh.

mvh

Post by mvh » Thu Sep 22, 2005 9:15 am

Yes!... that worked. I changed the path to C:\Documents and Settings\USER\Application Data\SourceGear\SOS and now it's working.

Now, I'm getting this error: Failed to open database: DATABASE. Where DATABASE is the name of my databse.

Thanks!.
mvh.

bfinney
Posts: 81
Joined: Fri Dec 17, 2004 11:27 am

Post by bfinney » Thu Sep 22, 2005 9:19 am

The -database parameter takes a path on the machine that hosts the server. If you're supplying the name listed in the GUI dropdown, substitute the -alias parameter for -database.

Otherwise, run a GetDatabases command to see the sever path to the database.

Honestly, -alias is probably much easier!
Brody Finney
SourceGear QA Thug
"I break things for a living"

mvh

Post by mvh » Thu Sep 22, 2005 9:27 am

Thanks guys. Now it's working, good support.

Regards,
mvh.

Post Reply