Invalid Handle while opening VSS(Run As administrator in win7)

Question

Hi ,

     Recently am facing one problem while connecting to VSS(network machine). When I run SSEXP.exe in run as administrator then am encountered "Invalid Error" message. But when I run SSEXP.exe in normal mode(just double click) then am getting user name and password Dialog (once i enter my user name and password then i could able to connect VSS). I checked my network connections it's fine and manually mapped server to my system. Can anyone reply me how to resolve this problem?? 

Answer 1

Hi SSRAO,

I have tested this in Window 7, but I can't repro this issue in my side. Have you tried to run other application as Administrator to see if this issue also happen?

And please check the following link to see if it is in the case:

http://www.dotnet247.com/247reference/msgs/46/231776.aspx

Best Regards,

Nancy

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Answer 2

Hi Nancy,

                Thank you for your reply, I have checked this http://www.dotnet247.com/247reference/msgs/46/231776.aspx but i didnt find any solution / related problem.. I will explain the problem little more detail.

1. I installed VSS netsetp in my system by mapping server to my system

2. After installed netsetup(VSS). once i run Start->all programs->Microsoft Visual source safe 6.0  then it shows me login promt , once i entered username and password then I can able to see projects.

3. But once i use run as administrator then it shows me that Invalid error. this issue i am not seen in all the machines.

4. I run other programs as run as administrators , the other programs are fine ,, but only VSS throwing error!!

 

Thank you for your help!!

Answer 3

Hi SSRAO,

What's the error message? And I would suggest you checking Event Viewer for more detailed error message.To open Event Viewer, follow these steps:

1. Click Start, and then click Control Panel. Click Performance and Maintenance, then click Administrative Tools, and then double-click Computer Management. Or, open the MMC containing the Event Viewer snap-in.
2. In the console tree, click Event Viewer.

And I think this issue is possibly caused by compatibility between VSS 6.0 and Windows 7 operating System.

Best Regards,

Nancy

---

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.

Answer 4

Hi, I have the same problem:

Win7 Pro (64bit) / Visual Studio 2010 Ultimate /  VSS 2005

The VSS database is on a network share, if you open studio with "run as admin" and try to open a project in VSS you get a dialog box saying, "The Database at sharedDrive does not exist or cannot be accessed at this time.  Would you like to select another?"   There are no warnings or errors in the event viewer that correspond to the message in the dialog box.

Thanks

Answer 5

Hi, Same problem here too.

Win7 Pro (64Bit) / VS2008 , SourceSafe 2005

I get errors when open with either Visual Studio 2008 or Sourcesafe. (running as administrator)

message  "invalid handle" , "The Database at xxxx does not exist"

 

Is there any solution?

 

Answer 6

Have you solved the issue?

Answer 7

When Win 7 was installed, what account was created with Administrative privileges?  Can you log in under that user and try the VSS Admin Tool?  Does that at least work?

---

Jeff Clausius - SourceGear

Stretching VSS to its limits? Have you looked at SourceGear Vault?

Answer 8

My user account has admin privileges on Win7.  I can open the VSS Admin Tool and access the vss libraries normally, but when i run VSS Admin Tool with "rus as administator" the application runs fine and i can select the vss database but get the same error message.  "Database does not exist".

 

update: the vss account also has admin privileges.

 

Thanks. 

Answer 9

Where is the location of the database (srcsafe.ini) file?  Is it under your "Program Files" directory?

If so, what happens if you copy (or move) the database into a different spot on a hard drive to a location where everyone has security rights?

---

Jeff Clausius - SourceGear

Stretching VSS to its limits? Have you looked at SourceGear Vault?

Answer 10

It's on a network share.

Answer 11

What is the OS on the UNC destination?  If that is on a Windows 7 machine, is it in "Program Files" on the path local to that machine?

---

Jeff Clausius - SourceGear

Stretching VSS to its limits? Have you looked at SourceGear Vault?

Answer 12

Server 2008 r2 standard edition.  Destination not under system drive or under "Program Files".

Answer 13

First of all, make sure your Windows accounts has full permissions to the UNC share as well as permissions on the files/folders within that share on the network machine.

Second, with nothing running, check the following items in your registry:

HKCU\Software\Microsoft\SourceSafe - Do you have values for "Current Database" and "PromptForConnect"?  If so, try renaming those registry value names (add an "X" or something ("Current DatabaseX" and "PromptForConnectX").  Also check HKLM\Software\Microsoft\SourceSafe for the same values.  Again, rename by adding an "X" or some character to the name of the registry value names.

Now restart the VSS admin tool.  It should bring up a dialog asking you for which VSS database to use.  Remove any entries to your UNC share, and then re-add using the "Add.." button and setting up a connection to an existing database through the "Add SourceSafe Database Wizard."

Did that work?

---

Jeff Clausius - SourceGear

Stretching VSS to its limits? Have you looked at SourceGear Vault?

Answer 14

Thanks, Jeff for pointing me in the right direction.  You were close.  Not sure why this was the problem, but i had mapped the shared folder to a drive letter.  Following your instructions i was running VSS admin as admin and removed the vss database from the list.  When i went to add it back via the browse button, that's when i noticed that the mapped drive wasn't available; oddly though i can run windows explorer as admin and see it.  Instead of using the mapped drive i used the UNC path to the file share.  Now it magically works. Yeah!

Answer 15

Glad you got it worked out.

---

Jeff Clausius - SourceGear

Stretching VSS to its limits? Have you looked at SourceGear Vault?

Answer 16

Just thought I'd add one more thing to this discussion.   I was having the exact same problem described by SSRAO and none of the solutions described above solved my problem. 

The VSS database was on a network share \\fileserver\files\...  I had created a local user account on the file server hosting the VSS database with the exact same login and password as the account I used when trying to access the VSS database from my Win7 development workstation.  After all of the above failed to fix my problem, I looked at the user account on the file server and noticed that its 'User must change password at next login' checkbox was checked.  I unchecked this, checked the 'Password never expires' box and reset the password to the same password as the account on my Win7 development workstation.  Problem solved!

I am still scratching my head though:  why did it work when I ran VSS normally and fail when I ran VSS as adminstrator? If this was a file permissions problem, shouldn't it have failed in both cases? 

---

Kevin Woram