Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Source Safe / February 2007

Tip: Looking for answers? Try searching our database.

The source control plug-in returned the following error: Access failure.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
adam@innovational.com - 16 Jan 2007 04:27 GMT
I'm trying to access a VSS 2005 database over the internet on a
computer running Windows Server 2003 using VS 2005. Specifically, I'm
trying to Open a Website from the remote VSS database (Create local
project from SourceSafe Internet). I choose File - Open - Web Site...;
next I "Select Source Control Project..." and choose the remote VSS
database. I am NOT connecting using SSL. I am prompted for my VSS
credentials, I key them in and I can browse the VSS tree (so, I know
that I'm communicating with the remote web service). I choose a path
under "Save to local folder" and check the checkbox "Run as IIS Web
site." After clicking OK, the dialog goes away for about 20-30 seconds
until I see an error dialog:

Cannot contact the Visual SourceSafe Internet Web Service or cannot
access the specified database. The server returned the following error:
The operation timed out (0x80072EE2).

followed by the dialog:

The current source control operation cannot be completed. The source
control plug-in returned the following error: Access failure.

Any thoughts or suggestions?
Douglas J. Badin - 16 Jan 2007 22:29 GMT
I am having the same problem when I am trying to get a large website.

When I look on the VSS Server in the VssWebDownload directory, a new
directory is created with a name like 6a7ec4c6-cbda-4fc0-b733-9a9b4e3d7474
during the process

For the Large site, there are 804 objects which took almost 13 minutes to
build.

For the Small site, there are 16 objects which to about 2 minutes to build.

I am guessing the timeout is because it takes 13 minutes to get all the
files in the VssWebDownload directory.

I haven't figured out how to configure the timeout value yet.

Doug

> I'm trying to access a VSS 2005 database over the internet on a
> computer running Windows Server 2003 using VS 2005. Specifically, I'm
[quoted text clipped - 18 lines]
>
> Any thoughts or suggestions?
Douglas J. Badin - 17 Jan 2007 18:37 GMT
I tried changing the Client timeout to 20 minutes:

HKCU\Software\Microsoft\SourceSafe = 1,200,000

and it Timed Out after 20 minutes

For the Server, the VssService was already set to 30 minutes

<httpRuntime executionTimeout="1800"/>

On the Server the files in the VssWebDownload were enumberated in about 13
minutes.

During this whole time, activity was going on over Internet Connection.

However, nothing showed up in the Client Destination Directory.

Maybe they go into a temp directory first?

Doug

>I am having the same problem when I am trying to get a large website.
>
[quoted text clipped - 37 lines]
>>
>> Any thoughts or suggestions?
ewuphoff - 09 Feb 2007 22:50 GMT
Anybody ever find a resolution to this?  I'm having the same issue, and it only occurs when I select open website. All else functions fine, and I'm able to use the service.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.