I'm getting the following error message when I try to use VSS over the internet:
The specified share path cannot be accessed by the SourceSafe Web Service.
I have been through auto and manual configuring of the server.
I have been through all of this post:
http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=209792&SiteID=1
and through
http://alinconstantin.homeip.net/webdocs/scc/VSS_Internet.htm
and
http://msdn2.microsoft.com/en-us/library/ms230398(en-US,VS.80).aspx
I can access the web service description if I browse to the web service. The user has the same credentials in the VSS db and the File Share. Evering thing appears to be correct. I have set this up on two other boxes.
The only really different thing I have here is Windows Server 2003 R2. I've never set it up on R2 but I wouldn't think that would have changed anything. This server is also a DC but I've set it up on one of those before too.
From a computer that is not joined to the domain but on the network I can get to file share through windows explorer, view the web service, but I cannot get past this error in VS 2005.
I've tried 2 different client computers, and I have auto and manually added the settings.
Any help is appreciated.
Thanks,
Tyler

The specified share path cannot be accessed by the SourceSafe Web Service
DONG
Hmm... Is VSS Database located on the same computer as IIS server
If not you need to configure "delegation" as described in following article:
http://msdn2.microsoft.com/en-us/library/ms230206.aspx
Make sure impersonation is turned on for SourceSafe IIS App. To verify that you could open web.config (by default located in C:\Program Files\Microsoft Visual SourceSafe\VssWebService\web.config)
Web.config should have following record in it
<identity impersonate="true"/>
SourceSafe virtual folder should have Anonymous access disabled and Integrated Windows authentication enabled. This can be found in Directory Security Tab of the SourceSafe properties dialog in IIS Manager.
Thank you
Roman
RWBitters
For me, it was the permissions on the server share point. I had to give permissions to the local machine/Administrators group rather (in addition to) the Domain Admins group. Everything was fine after that.
Found a clue here:
http://msdn2.microsoft.com/en-us/library/ms181068(VS.80).aspx
Mike =:-)