Diff two files in source offsite doesn't seem to work
Moderator: SourceGear
-
- Posts: 11
- Joined: Fri Nov 16, 2007 7:58 am
Diff two files in source offsite doesn't seem to work
When I try to diff to files in history view, sos kind of freeze. I must press the stop current operaton button. But I can almost never diff two files.
Sos gets the latest file and puts it in the working folder.
But the older version of this file is never fetched.
Sos gets the latest file and puts it in the working folder.
But the older version of this file is never fetched.
-
- Posts: 11
- Joined: Fri Nov 16, 2007 7:58 am
Can you start up client-logging by opening a Vault client and pressing Ctrl-Alt-Shift-F12. Then try the diff again. When finished, first check your Vault server log at C:\Windows\temp\sgvault\sgvault.log for any errors. Then check your client log that is in C:\Documents and Settings\<user name>\Local Settings\Temp\VaultGUIClient.txt. Let me know if any errors occur.
-
- Posts: 11
- Joined: Fri Nov 16, 2007 7:58 am
-
- Posts: 11
- Joined: Fri Nov 16, 2007 7:58 am
Started Log.txt on the server: Found this entry after trying to compare files
11/26/2007 10:02:55 PM - 1: Exception getting file. SourceSafe was unable to finish writing a file. Check your available disk space, and ask the administrator to analyze your SourceSafe database.
There is enough disk space (about 6 GB) . I also analyzed the VSS 'database' => No errors or inconsistencies found. But it didn't help. I still cannot compare files.
11/26/2007 10:02:55 PM - 1: Exception getting file. SourceSafe was unable to finish writing a file. Check your available disk space, and ask the administrator to analyze your SourceSafe database.
There is enough disk space (about 6 GB) . I also analyzed the VSS 'database' => No errors or inconsistencies found. But it didn't help. I still cannot compare files.
Sorry about that. Getting forums confused.
The SOS log is called log.txt and is found on the SOS server in the program files directory.
Are you able to perform a Get of that old file to disk? This would tell me if there's something wrong with the file or not.
Are you the one who installed SOS on that machine? Are you using the same login on that Windows machine as you did for installing? These answers will tell me where it's trying to put the file to diff and if you have access. By default it will place it in C:\Documents and Settings\<user name>\local settings\temp.
The SOS log is called log.txt and is found on the SOS server in the program files directory.
Are you able to perform a Get of that old file to disk? This would tell me if there's something wrong with the file or not.
Are you the one who installed SOS on that machine? Are you using the same login on that Windows machine as you did for installing? These answers will tell me where it's trying to put the file to diff and if you have access. By default it will place it in C:\Documents and Settings\<user name>\local settings\temp.
-
- Posts: 11
- Joined: Fri Nov 16, 2007 7:58 am
-
- Posts: 11
- Joined: Fri Nov 16, 2007 7:58 am
Do you have access to your SOS server log? SourceOffSite log file (log.txt) is located on the machine where the SOS server resides in this path C:\Program Files\SourceOffSite Server.
Try a Get on one of the problem files from History and then immediate check that log for errors. What does it have for errors?
Try a Get on one of the problem files from History and then immediate check that log for errors. What does it have for errors?
-
- Posts: 11
- Joined: Fri Nov 16, 2007 7:58 am
-
- Posts: 11
- Joined: Fri Nov 16, 2007 7:58 am
I have enough space on the server and the client.
Analyze runs every night. (Without any problems)
I can get the files with VSS.
Could it be, that the problem has to do with, when the file has many history entries?.
I mean, on this particularly file I have more than 110 history entries.
I tried to compare other files, which have only about 20 history entries and there it worked perfectly.
Analyze runs every night. (Without any problems)
I can get the files with VSS.
Could it be, that the problem has to do with, when the file has many history entries?.
I mean, on this particularly file I have more than 110 history entries.
I tried to compare other files, which have only about 20 history entries and there it worked perfectly.