The localadmin installed visualstudio 6.0 in my machine, to use sourcesafe.
Now the problem is that when I log into windows with my user id I can't open the sourcesafe database.
But if we log into windows as localadm and try to login into sourcesafe using my sourcesafe user id it those works.
Any help
Thanks
You may need to adjust the NTFS permissions on the VSS database folder or one of the database files.
I suspec the folder has read-write permissions for localadmin account, but not for your Windows user account (you need read-write permissions to use a VSS database).
You should grant R/W permissions to the srcsafe.ini and users.txt files in "C:\Program Files\Microsoft Visual Studio\VSS\", and on the data, users and temp subfolders there,
Or better, use the Administrator account and the Admin tools to create a new VSS database in a different / new folder (not in ProgramFiles), where you can better control the NTFS and share permissions.
Alin
Digging into the sourcesafe known problems. I found this:
Users that do not log in as an Administrator or Power User on the local computer cannot access a local SourceSafe database when it is installed to the default location on a Windows NT 4.0, Windows 2000 or Windows XP NTFS partition. If you attempt to access a SourceSafe database under these conditions the following error appears, "Unable to open user login file ...\VSS\data\loggedin\username.log" where username is your SourceSafe login name.
To work around this issue either install the SourceSafe database to a UNC path or log in as a Power User or Administrator.
For more details about this issue, see http://www.microsoft.com/windows2000/techinfo/planning/security/secdefs.asp.
I'm sorry, but I don't understand your problem. Can you please be more specific.
I' solved mine by changing my user permissions from normal user to super user.
There are two issues with permissions. There are permissions on the folder itself and also permissions on the Share. Make sure that you set both of them. I originally only changed the folder permissions and still had the problem. Once I changed permissions on the Share as well access to the files worked fine.
