In Visual Studio a SourceSafe Get returns Unexpected error encountered on Line number: 5907

In Visual Studio a SourceSafe Get returns Unexpected error encountered on Line number: 5907

Article ID : 952043
Last Review : April 22, 2008
Revision : 1.0
Source: Microsoft Support

Back to the top

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Back to the top

Action

Closing and re-opening Visual Studio 2005 solution containing web projects under SourceSafe control.

Back to the top

Result

Some files appear as new even though they been in SourceSafe for a long time – they show up with a yellow plus icon.

Attempting to do a SourceSafe get get latest on the project:

Unexpected error encountered. It is recommend you restart the application as soon as possible.
Error: Unspecified error.
File: vsee pkgs vssprovider cmsscciabstractionlayer.cpp
Line number: 5907

Attempting to rebind the project:

Unexpected error encountered. It is recommend you restart the application as soon as possible.

Error: Unspecified error.
File: vsee lib path cvapipath.cpp
Line number: 2459

Back to the top

Cause

Line 5907 is Project must be available

Line 2459 is “Can’t unrelativize a non-relative path”

-For websites, something wrong happening with the suo file, and translation map gets incorrect
- For webapp projects, a stale file or setting in solution or in vspscc file that causes the webapp to be treated like website, with enlistment, etc.

Back to the top

Resolution

Open from Source Control from within Visual Studio into a different working location and create new web enlistments if necessary, so stale files won’t be used.

Open solution

– Use ChangeScc dialog to unbind the websites from scc, Ok ChangeScc dialog (this allows scci to clean up the messed up scc sections in suo and sln)

– Remove the websites from the solution

– Make sure the nodes in IIS like <http://localhost/MyInfo (http://localhost/MyInfo)> point to the correct version of the website on local disk (2.1/2.2/2.3). If it points to the wrong version, fix the Virtual folders mapping.

– Add the websites back, using File/Add/ExistingWebsite/LocalIIS, select the nodes in <http://localhost/ (http://localhost/)> (this allows web projects to write their relative locations correctly, if that’s messed up)

– Use ChangeScc dialog to bind back the websites to the correct folders in the VSS database

– Checkin the changes to the solution file.

Back to the top

More Information

A relative path reference is used in the bad Solution along with references to the pre-branched local directory 2.1 instead of 2.3.

***** good.sln
                SccProjectUniqueName1 = MyInfoLib MyInfoLib.vbproj
                SccProjectName1 = u0022$/MY u0020EI u0020ACCOUNT/2.3/Development/project/MyInfoLib u0022, u0020NTGAAAAA
                SccLocalPath1 = MyInfoLib
                SccWebProject2 = true
***** BAD.SLN
                SccProjectUniqueName1 = MyInfoLib MyInfoLib.vbproj
                SccLocalPath1 = .
                SccProjectFilePathRelativizedFromConnection1 = MyInfoLib                 SccWebProject2 = true

***** good.sln
                SccProjectName4 = u0022$/MY u0020EI u0020ACCOUNT/2.3/Development/MyInfoServices u0022, u0020QIHAAAAA
                SccLocalPath4 = C: _Project MY u0020EI u0020ACCOUNT 2.3 Development project MyInfoServices
                SccProjectEnlistmentChoice4 = 2
***** BAD.SLN
                SccProjectName4 = u0022$/MY u0020EI u0020ACCOUNT/2.3/Development/MyInfoServices u0022, u0020QIHAAAAA
                SccLocalPath4 = C: _project My u0020EI u0020Account 2.1 Development project MyInfoServices

Also in the good SLN the Guid identifiers have been updated.

Back to the top

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

Back to the top


APPLIES TO
• Microsoft Visual SourceSafe 2005 Standard Edition
• Microsoft Visual SourceSafe 6.0d
• Microsoft Visual Studio 2005 Professional Edition
• Microsoft Visual Studio 2008 Professional Edition

Back to the top

Keywords: 
kbnomt kbrapidpub KB952043

Back to the top

 

Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
Microsoft Corporation. All rights reserved. Terms of Use | Trademarks


You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

AddThis Social Bookmark Button

Leave a Reply

*
To prove that you're not a bot, enter this code
Anti-Spam Image