I posted this back in 9/2006, but didn't get a reply.
http://groups.google.com/group/microsoft.public.visual.sourcesafe/brow...frm/thr
Note that since then, the problem has never gone away and I have
rebuilt my server (new hard drive, fresh install of Windows Server
2003, etc...). I still must bounce the HTTPS server at least once a
day, many times multiple times a day.
Any help on this would be greatly appreciated... or even an
aknowledgement that you're experiencing the same problem.
Here's the original post:
--------------------------------------------
Help!
I've got VSS 2005 installed on my server successfully and have even
successfully gotten Visual Studio 2005 working with it using HTTPS
(after many many many many hours of trial and error).
There's still one lingering problem though: Frequently, when I try to
check out a file from within Visual Studio 2005, I get an 80005
error. I can fix it every time it happens (about 2 or 3 times a day),
but it's combersome:
I have to remote control my server and bounce the HTTP SSL service.
What's strange is other sites on my server that use SSL work just
fine, wether or not I bounce the HTTP SSL service. It's just
accessing my Visual SourceSafe 2005 database from Visual Studio 2005
HTTPS access that has a recurring problem.
I've seen some authorities on the subject saying that if you have
SharePoint installed on the same web site that it can cause problems
with HTTPS access to VSS. I don't have SharePoint installed on the
same website that I have my VSS database on, but I *DO* have
SharePoint on *OTHER* websites on the same server. So, is THAT the
problem? and if so, what can I do about it without losing either
SharePoint nor VSS.
Does anyone know how to resolve this problem? Currently, I'm forced
to keep a paid subscription to gotomypc.com in order to remote control
my server to bounce the HTTP SSL service because I'm behind a firewall
that allows ONLY HTTP traffic through.
Additionally, if anyone knows of any good remote control software that
works totally via HTTPS traffic on ports 443 or 80, that would be a
big help too. VNC does NOT, Remote Desktop (part of Windows) does
NOT... and half a dozen other products I've tried do not either.
But most importantly, how do I prevent the problem of having to
restart the HTTP SSL service?
TIA
Microsoft Office (other)