Cannot Retrieve or Difference Previous Versions of Files
Moderator: SourceGear
Yes it is safe to assume that this file does exist. As mentioned before we can use the VSS client and it works fine.
Also I run Analyze on a weekly basis.
I first run "E:\Program Files (x86)\Microsoft Visual SourceSafe\ANALYZE.EXE" -v4 "E:\VSSDatabases\VSS\data" and if there are any errors reported I then run
"E:\Program Files (x86)\Microsoft Visual SourceSafe\ANALYZE.EXE" -FL -v4 "E:\VSSDatabases\VSS\data"
if there are still problems (VERY RARELY) then I run
"E:\Program Files (x86)\Microsoft Visual SourceSafe\ANALYZE.EXE" -FL -C -v4 "E:\VSSDatabases\VSS\data"
Also I run Analyze on a weekly basis.
I first run "E:\Program Files (x86)\Microsoft Visual SourceSafe\ANALYZE.EXE" -v4 "E:\VSSDatabases\VSS\data" and if there are any errors reported I then run
"E:\Program Files (x86)\Microsoft Visual SourceSafe\ANALYZE.EXE" -FL -v4 "E:\VSSDatabases\VSS\data"
if there are still problems (VERY RARELY) then I run
"E:\Program Files (x86)\Microsoft Visual SourceSafe\ANALYZE.EXE" -FL -C -v4 "E:\VSSDatabases\VSS\data"
Brian C Drab
Brian:
I've uploaded a temp build of 4.2. Please let me know when you've downloaded it.
You'll need to :
1) Notify your users the SourceOffSite server will be going down.
2) Shut down the SourceOffSite 4.2 Server service.
3) Open the SourceOffSite Server directory. By default this is located at "%SYSTEMDRIVE%\Program Files\SourceOffSite Server"
4) Rename the following files in the SourceOffSite Server directory:
- ICSharpCode.SharpZipLib.dll TO ICSharpCode.SharpZipLib.dxy
- Interop.SourceSafeTypeLib.dll TO Interop.SourceSafeTypeLib.dxy
- SosService.exe TO SosService.exy
5) Uncompress the attached file, and place the 3 files into the SourceOffSite 4.2 Server. These new files should be replacing the files named in the previous step.
6) Start up the SourceOffSite 4.2 service.
After this, try the GET again. Note, I still expect the same results, but the log file generated with the GET will have some additional information. I'll examine the log file tomorrow to see where we should go from here.
Once you have the log file, reverse the steps to put your system back in its original state.
I've uploaded a temp build of 4.2. Please let me know when you've downloaded it.
You'll need to :
1) Notify your users the SourceOffSite server will be going down.
2) Shut down the SourceOffSite 4.2 Server service.
3) Open the SourceOffSite Server directory. By default this is located at "%SYSTEMDRIVE%\Program Files\SourceOffSite Server"
4) Rename the following files in the SourceOffSite Server directory:
- ICSharpCode.SharpZipLib.dll TO ICSharpCode.SharpZipLib.dxy
- Interop.SourceSafeTypeLib.dll TO Interop.SourceSafeTypeLib.dxy
- SosService.exe TO SosService.exy
5) Uncompress the attached file, and place the 3 files into the SourceOffSite 4.2 Server. These new files should be replacing the files named in the previous step.
6) Start up the SourceOffSite 4.2 service.
After this, try the GET again. Note, I still expect the same results, but the log file generated with the GET will have some additional information. I'll examine the log file tomorrow to see where we should go from here.
Once you have the log file, reverse the steps to put your system back in its original state.
Jeff Clausius
SourceGear
SourceGear
Darn...I'm ready. It would have been nice to have it to try tonight when no one is using the system.
You can send the file through a service such as http://yousendit.com to my email address so we don't have to miss each other again.
Thanks.
You can send the file through a service such as http://yousendit.com to my email address so we don't have to miss each other again.
Thanks.
Brian C Drab
OK, attached is the requested log file. I also switched everything back. Let me know what the next steps are.
Thank you.
Thank you.
- Attachments
-
- log.txt
- (5.96 KiB) Downloaded 621 times
Brian C Drab
According to the log:
You did a GET on "$/Visual Basic .NET 2005/Reporting Services Solution/Safety Reports/Horizon Current Violations All Terminals.rdl" @ version 1.
Is that correct?
And the SOS Server has all rights to create / write on "E:\Program Files\SourceOffSite Server\temp\briand633423355697073768\Horizon Current Violations All Terminals.rdl"
According to the log, the SOS Server is doing everything correct. The failure appears to be generated within the Microsoft SourceSafe Automation Libraries.
Another idea I have is to make a backup of your VSS database, delete and undelete the file, and then check to see if the problem still exists.
If the delete/undelete doesn't work, I have one more idea. It is a bit more drastic, so I'd like to try the delete/undelete option first.
Code: Select all
3/28/2008 9:13:47 PM - 1: GetFile() project=$/Visual Basic .NET 2005/Reporting Services Solution/Safety Reports file=Horizon Current Violations All Terminals.rdl
3/28/2008 9:13:47 PM - 1: GetFile() project=$/Visual Basic .NET 2005/Reporting Services Solution/Safety Reports file=Horizon Current Violations All Terminals.rdl requesting version=1
Is that correct?
And the SOS Server has all rights to create / write on "E:\Program Files\SourceOffSite Server\temp\briand633423355697073768\Horizon Current Violations All Terminals.rdl"
According to the log, the SOS Server is doing everything correct. The failure appears to be generated within the Microsoft SourceSafe Automation Libraries.
Another idea I have is to make a backup of your VSS database, delete and undelete the file, and then check to see if the problem still exists.
If the delete/undelete doesn't work, I have one more idea. It is a bit more drastic, so I'd like to try the delete/undelete option first.
Jeff Clausius
SourceGear
SourceGear