SourceSafe: “Only one database connection at a time is supported.”
I’ve been having intermittent problems with Visual Studio 2005 and SourceSafe 2005 occasionally complaining that “Only one database connection at a time is supported” when I load up solutions with multiple projects in them.
A Microsoft Knowledge-base article pointed me to the potential problem. Looking in the mssccprj.scc files for both .csproj files loaded in the solution, I spotted one of them had an extra entry for a .sln file as well as the .csproj file. Both of the SCC_Aux_Path variables for the .csproj definitions were the same so the knowledge-base fix wasn’t quite correct.
Removing the definition for the .sln file from the mssccprj.scc file has helped remove this problem. Saves doing the usual suggestion of ‘SourceSafe is screwed on your machine, you should get it reinstalled’.
- Share this:
- StumbleUpon
2 Responses to SourceSafe: “Only one database connection at a time is supported.”
Leave a Reply Cancel reply
Tag Cloud
3G adobe agriculture analogy Apple authentication berkovitz BIN Contacts CreatePageURLSegment credit card credit cards developers Episerver Esendex Google iPhone Joost Linux log4net logging luhn Mac maestro Mastercard Microsoft NMock Page PATH payWave Plesk regex RFID security software SQL Server Stored Procedures SugarOS T-SQL TechEd uk validation Visa Windows XCodeCategories
Jbjon
- If anyone from 1989 calls and needs a database reference manual get them in touch with me! #dataease #mandrawer http://t.co/CbnFBuUq
- @KnackeredCoder oh I agree. It all helps. 2nd in the table is a great start. I'd just like wins to be try based,penalty light tussles
- @KnackeredCoder not exactly singing. As they said it was Scotland that lost not England that won.
- That was so close to a try for Scotland. I reckon it was his wrist that stopped that ball rotating but it was nearly his hand. #BBC6nations
- @rhys_isterix I think they're getting back on top of this game. England dented their confidence mid first half.
Correct. For each project I had to remove the solution entry in the mssccprj.scc file. In addition, my Visual Studio solution file was saving over at My Documents\Visual Studio 2008\Projects instead of the working folder. In Visual Studio click on Change Source Control and double check your bindings.
Thanks for that, it fixed it for me. After removing the .sln reference and making sure the URIs matched, I still had to remove and re-add the project to the solution for it to work.
Good stuff, thanks -