SourceGear Support

I'm not in the office this week and will have to get authorisation before I can upload our database, and I'm afraid it may well not be possible to get authorisation. I will see what I can arrange. Below are the responses to your questions... --You can use that database normally in every other way ex...

Same problem I'm afraid 8/25/2006 3:21:27 PM - Waiting for a connection....secure = True 8/25/2006 3:21:43 PM - Connection accepted from 192.168.0.32:2829 on local address 192.168.0.22:8890, session id is 1. 8/25/2006 3:21:43 PM - 1: Enter Authorized() 8/25/2006 3:21:45 PM - 1: Enter Login() 8/25/20...

Beth, As a quick test, I configured our old server that still has SOS Server and SourceSafe 6 on it to reference the live 2005 database on our new server. The history is retrieved fine. Looks like I will have to roll back to VSS 6.0 unless you have any other ideas. The changes in ssapi.dll for 2005 ...

Up until last week our remote developers had been accessing our SourceSafe 6.0 repositiory using the SOS client and from within VB6. Locally we were accessing the repository using SourceSafe Explorer 6.0 and integrated with VB6, VS2003 and VS2005. Our new Development Server hosts Team Foundation Ser...

Hi Beth, This is the first time I have posted in this topic. I was searching the forums to see if anyone else had the same issue as myself and found this thread. Was hoping there might have been some progress, otherwise I may have to revert back to SourceSafe 6.0 for reliable SOS access. Regards Mark

Hi, Has there been any progress on this? We have just moved to SourceSafe 2005, with our remote developers continuing to use SOS to access the database. Our new server is running Windows Server 2003 R2, with SourceOffsite Server Manager 4.1.2. The vssapi.dll version is 8.0.50727.42. Not sure the num...

Thanks for the information.

I presume that MSVCR71.DLL being missing from 4.1 is an install package issue and that will be fixed also?

Thanks for the update Corey.

Of course, it's the windows version we use, but I can understand you wishing to synchronise releases for all platforms.

Is there a list of mods/issues that 4.1.2 addresses available so that I can decide whether to update to 4.1.0 now rather than wait?

Corey, could you give an update on the availability of 4.1.2?

I was just about to upgrade from 4.0.2 to 4.1 when I noticed this posting earlier this week and thought it better to wait.