|
|
|
date: Mon, 23 Jan 2006 17:41:07 -0500,
group: microsoft.public.vsnet.vss
back
Re: VSS Can't Open
>After about 20 minutes, it says: "can't find it.
> Would you like to change it." If you select yes, and pick a new
> server, for some reason it still tries to do something with the last
> one and you go into never never land.
It sounds to me like you're using VSS6, is that right? VSS6 was bad at
connecting to inexistent databases.
VSS2005 should be a bit better, it should drop you directly in the "Open
SourceSafe Database" if the previous database is not found, and I think it
won't try to use the old database after selecting a different database.
To fix SSExp/SSAdmin faster, I'd make sure you have a database on local
system or on a remote share that you can access with WindowsExplorer,
then manually edit the "Current Database" values under the following keys to
point to that database/file_share:
HKEY_CURRENT_USER\Software\Microsoft\SourceSafe
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe
> If you pick work disconnected that's fine but eventually you would
> like to put the project back in vss. If you open source control;
> never never land again.
To fix the solution in VisualStudio, open the solution. Wait until VSS will
complain it cannot find the database, say "No" to any prompt for VSS.
Eventually, VS2005 should prompt with a dialog "SourceControl - Unable to
access database", with 3 options:
"Temporarily work offline", "Permanently remove source control bindings",
"Manually change bindings".
I'd pick the second option, then the solution should open uncontrolled.
Futher open from disk should be fast.
Then you can use AddSolutionToSourceControl menu items and re-add the
solution to source control to a different database if you wish so.
--
Alin Constantin
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chuck P" <Chuck@newsgroup.nospam> wrote in message
news:jefj22pbe7jada1drtblceesn8sibl5fkc@4ax.com...
> After about 20 minutes, it says: "can't find it.
> Would you like to change it." If you select yes, and pick a new
> server, for some reason it still tries to do something with the last
> one and you go into never never land.
>
> If you pick work disconnected that's fine but eventually you would
> like to put the project back in vss. If you open source control;
> never never land again.
>
>
>
> On Sat, 25 Mar 2006 12:07:32 -0800, "Alin Constantin [MSFT]"
> wrote:
>
>>I'd give it a bit of a time...
>>When a Windows share is inaccessible (share does not exist, or machine is
>>down), Windows takes about 30 seconds or so when it tries accessing the
>>share until it gives up.
>>VSS Explorer and VSS Admin should open up eventually and prompt you to
>>pick
>>a different database.
>>Opening a controlled project in VS2005 when the VSS server is inaccessible
>>should prompt eventually with the same dialog, you can cancel it and
>>VS2005
>>will then prompt to work temporarily uncontrolled or completely unbind the
>>solution from source control.
date: Tue, 28 Mar 2006 17:25:50 -0800
author: Alin Constantin [MSFT]
Re: VSS Can't Open
I ended up modifing my hosts file. Set the old server name to
127.0.0.1 Now the time out is a more tolerable few minutes.
On Tue, 28 Mar 2006 17:25:50 -0800, "Alin Constantin [MSFT]"
wrote:
>>After about 20 minutes, it says: "can't find it.
>> Would you like to change it." If you select yes, and pick a new
>> server, for some reason it still tries to do something with the last
>> one and you go into never never land.
>
>It sounds to me like you're using VSS6, is that right? VSS6 was bad at
>connecting to inexistent databases.
>VSS2005 should be a bit better, it should drop you directly in the "Open
>SourceSafe Database" if the previous database is not found, and I think it
>won't try to use the old database after selecting a different database.
>
>To fix SSExp/SSAdmin faster, I'd make sure you have a database on local
>system or on a remote share that you can access with WindowsExplorer,
>then manually edit the "Current Database" values under the following keys to
>point to that database/file_share:
> HKEY_CURRENT_USER\Software\Microsoft\SourceSafe
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe
>
>> If you pick work disconnected that's fine but eventually you would
>> like to put the project back in vss. If you open source control;
>> never never land again.
>
>To fix the solution in VisualStudio, open the solution. Wait until VSS will
>complain it cannot find the database, say "No" to any prompt for VSS.
>Eventually, VS2005 should prompt with a dialog "SourceControl - Unable to
>access database", with 3 options:
>"Temporarily work offline", "Permanently remove source control bindings",
>"Manually change bindings".
>I'd pick the second option, then the solution should open uncontrolled.
>Futher open from disk should be fast.
>Then you can use AddSolutionToSourceControl menu items and re-add the
>solution to source control to a different database if you wish so.
date: Wed, 10 May 2006 11:31:15 -0600
author: Chuck P am
|
|
