This post is still helping! It's a good thing it showed up fairly high in my search results. Thank you! Thanks for your solution, it worked for us.
Funniest part was, I did not know what should be the content of template. Post a Comment. I hate wrong error messages. I hate messages that lead me in wrong direction.
Yesterday I've spend too much time on resolving problem with VSS. I had to add new user to VSS. Pretty simple task. Hi Brad. Thanks for the quick reply. I stumbled across the old Analyze ver 6.
Anyway, the problem is fixed as your post points out in that I needed to create a shorcut and pass params to it with the path included. Yes, I do get the message about it preferring to run on the server, but it seemed quite fast and our network is very stable we are a small shop so I'm thinking it should be ok. Scenario 2 Moving a project or projects from one database to another, while preserving the project's history.
This scenario eliminates the need to modify clients accessing the database. Scenario 1 Moving the entire VSS server installation from one machine to another. Make sure that the Visual SourceSafe clients can still access the data from the new location. Best regards, Willem Bogaerts. I've encountered the same problem two different ways, so the way you start up SourceSafe needs to be known. However, here's the "fixes" depending on your setup: 1 If you start SourceSafe from the command line, you need to create an environment variable system type, not user called ssdir and give it the UNC path as the value.
I'm guessing your doing method 2. Note that if you access more than 1 SourceSafe database, there is still the tendency to get that message. My fix for that is to change the include to the path of the other database's srcsafe. Why this include is there, I have no idea since it seems to limit you access to one database at a time, though in practice I've found that to not be true. It just needs to be set to one in order for things to work. Good luck. I start sourcesafe via the GUI.
However, I want sourcesafe to connect with the shared database by default.
0コメント