Visual Sourcesafe Link To Individual Projects

[BJD1613]

I do have a user name and account password.

[BJD1613]

here is the version in case there is still discussion about the version. 🙂

[Amanda_H]

Have you seen this behavior on other PCs and with other versions of SourceSafe? Have you noticed this behavior every time, or just intermittently? Have you always experienced this behavior?

[BJD1613]

I will continue to check with some other developers here but I know one person has had this problem also.  I have always experienced this since I have used 8.5.  With 8.2 the project properties were not the same.  I will see if I can setup a machine with the version 6.0 of visual sourcesafe.  Do you think this is an IT administration issue or configuration issue on my pc? Have you been able to reproduce this problem? 

[Amanda_H]

Hi,

I haven't been able to reproduce it because I don't have a copy of the Visual SourceSafe software. Does this occur every time? I would double check with your IT representative to ensure that the programs are able to communicate effectively.

[BJD1613]

After I retarget the project to the VSS project all of the functionality works perfectly fine.  I can check things in and out and add items to VSS also.  It only occurs when I close LabVIEW or change projects.  Is this something that you can follow up with me in the future when you would get the latest copy of VSS?  I am very interested in this issue.  I will continue to check with my IT department and I will keep you posted.  Thanks for your help.

[gmart]

I setup LabVIEW to connect to VSS 2005 (the version we are talking about) in Tools>>Options. I entered my user name (which is the same as my Windows login) and configured LabVIEW to use a VSS project. I then created a LabVIEW project and via Project>>Options configured it to use a different VSS project. Finally I created a second LabVIEW project and pointed it to yet a different VSS project. I closed all. I then opened the first project and second project and did not get an error.

I found this post from back in January of 07 detailing the password problem I remembered:

"I have used a non-system user name successfully with Visual SourceSafe. One issue that has come up with SourceSafe is that it does not remember a non-system user's password between sessions. This seems to be a limitation with the interface that Visual SourceSafe exposes. So perhaps the issue you are seeing is that admin has a password (which is usually the case) and therefore when LabVIEW restarts, the SourceSafe interface requires the password (yet doesn't prompt for one, go figure). There is an option in the SourceSafe admin tool - "Use network name for automatic user log in" which may be related to this. I believe for now, your recommendation of having a user account with the same name as the system user is the workaround."

[BJD1613]

As a follow up to this thread I have some recent findings.  Apparently my company doesn't require your VSS password to be the same as your network password.  When I changed my VSS password (after I had them tell me what it is.... since I created it two years ago) the problem that i was having seemed to have gone away.  So I would update the Knowledge base article to state that if your VSS password and network password do not match using VSS 2005 you could see this error.  The work around is to change your password to your current network password.  Unfortunetly I was told that there is no way to have the two match from the IT side so I will have to change it everytime that I change my network password.  The reason you might not have seen the problem is because you probably had the same password for both your network and VSS database.  Try changing them and see if you can recreate the problem.

[BJD1613]

I don't have access to the admin tool to match both passwords and apparently they tell me that it isn't possible... who knows I am just glad it is fixed.  Thanks for all your help.

[gmart]

Glad to hear that you're up and going. Sorry it took so long to get you to this point, but issues with third-party source control providers are not always cut and dry.