SourceGear Support

According to our IT department Below is what the key file looks like. It has been so long time since I set it up but I am guessing that I just put in the username and the SOS Server IP address. The name of the key file is your username. Username:buckv Server:131167013012 Key-Format:1 Expires:Never E...

We turned encryption back on the server side. Attached is the output from the last set of tests we ran Using the encrypted client with no key to connect to the encrypted server results in a message that we need a key. Using the encrypted client with key to connect to the encrypted server results in ...

Beth, There is no change in trying Jeff's suggestion. We tried a few different permutations here of the checkoutfile command: We turned off encryption on the server. Here are the results we received: Using an unencrypted cmdline client to connect to the now unencrypted server. Issuing a CheckOutFile...

Log output from around the time I ran the test (approx 1 minute before to 5 minutes after). 7/3/2008 11:26:21 AM - Connection accepted from 131.167.91.144:49222 on local address 131.167.13.12:8081, session id is 94. 7/3/2008 11:26:26 AM - 94: Unable to get hostname from address: 131.167.91.144 7/3/2...

Beth, Sorry if I confused you with my responses. In response to your questions: Question (1) When you were trying with the GUI, you had imported the encryption key into the GUI and used the secure port there also, right? Answer(1): Yes we had imported the key and used the secure port. Question (2) I...

The version of SOS cmd line client without encryption works.
The version of SOS cmd line client with encyrption without using the encryption key also works.
The version of SOS cmd line client with encyrption and using the encryption key does not work.

I have attached the entire log and am posting the segments from roughly the time I was running my tests (2:00-7:00). 6/30/2008 2:16:59 PM - Connection accepted from 131.167.91.144:17385 on local address 131.167.13.12:8081, session id is 3. 6/30/2008 2:17:04 PM - 3: Unable to get hostname from addres...

I was trying to verify certain features of the encrypted command line client before we use them in our development cycle. To that end we wrote a test plan. We have been using the SOS Linux GUI client version 4.2 for a few months. The goal of the test was to verify that the command line client using ...

Jeff, Thanks for looking into it. We aren't using the old return codes. We did a little experimental test here and found that indeed the directory listing we were getting compressed was greater than 400 bytes (433 bytes). The code returned was -1 (255). When we did a test on a new database with fewe...

Your description about what you are returning disagrees with standard documentation regarding Unix process exit statuses. You can't really return a negative number or value greater than 255 in a Unix process. The exit status is limited to an 8 bit unsigned value. For reference the man page for bash ...

The client is 4.2 standard edition and encrypted editions

The server is also 4.2

We are using the Linux Command Line client for Fedora.

We have been experiencing some errors with the behavior of the SOS command line client. I am paraphrasing from some emails that our IT staff and an engineer have been experiencing. To the best of our knowledge, the SOS client did not change, the SOS server did not change. The SOS server was rebooted...

Jeff, Excluding the directory from the virus scanner has definitely helped. Sourceoffsite seems faster and more stable (i.e no segmentation faults as of this morning). Thank you for all your help, I will evaluate SourceOffSite for our needs. In the meantime can you answer a few questions for me or p...

The version of ssapi.dll we are using is 8.0.5.0727.42 with VSS 2005. The log.txt did have error messages; I have attached a copy; incidentally we have deleted all the messages in the log file and will attempt to recreate some of the errors to get a better log file. Thanks for looking into this Jeff...

I tried to a branch in a test project on our local server. Another GTK related failure occurred and the application exited. This was after I selected a folder, decided to share it, unchecked recursive, selected branch after share and gave it a new name. [vimal@localhost bin]$ ./sos (sos:21903): Gtk-...