Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "Some of the properties associated with the solution could not be read" error message when you try to open a project in Visual Studio .NET 2003 or in Visual Studio 2005

"Some of the properties associated with the solution could not be read" error message when you try to open a project in Visual Studio .NET 2003 or in Visual Studio 2005

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry

↑ Back to the top

Symptoms

When you try to open a project in Microsoft Visual Studio .NET 2003 or in Microsoft Visual Studio 2005, or when you try to create a project, you may receive the following error message:
Some of the properties associated with the solution could not be read.
Additionally, you may receive the following error message in Solution Explorer:
The project file cannot be loaded.
If you try to reload the project, you receive the following error message:
Unspecified Error

↑ Back to the top

Cause

If you turn source code control on, Visual Studio .NET 2003 or Visual Studio 2005 tries to load the corresponding Microsoft Source Code Control Interface (MSSCCI) provider when you try to open a project or when you try to create a project. However, an MSSCCI provider that is registered in the Microsoft Windows Registry by using the relative path of the corresponding DLL may pose a security threat to your computer. Therefore, before Visual Studio .NET 2003 or Visual Studio 2005 loads an MSSCCI provider, Visual Studio .NET 2003 or Visual Studio 2005 verifies whether any MSSCCI provider on your computer is registered by using a relative path.

If any MSSCCI provider on your computer is registered by using a relative path, the behavior that is mentioned in the "Symptoms" section occurs.

↑ Back to the top

Resolution

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To resolve this problem, modify the corresponding registry entry for each MSSCCI provider that is registered by using the relative path of the corresponding DLL. Modify the registry entry so that the MSSCCI provider is registered by using the absolute path of the DLL instead. To do this, follow these steps:
  1. Click Start, and then click
    Run.
  2. In the Open box, type
    regedit, and then click OK to start Registry Editor.
  3. In Registry Editor, locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\SourceCodeControlProvider\InstalledSCCProviders

    Notice that each of the registry entries for this subkey contains information about a registry subkey under HKEY_LOCAL_MACHINE. For example, the
    Microsoft Visual SourceSafe registry entry contains the following data: Software\Microsoft\SourceSafe
  4. For each of the registry entries that you noticed in step 3, locate the corresponding registry subkey. For example, locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SourceSafe
  5. For each of the registry subkeys that you located in step 4, if the corresponding SCCServerPath registry entry contains a relative path, follow these steps:
    1. Right-click SCCServerPath, and then click Modify.
    2. Type the absolute path of the MSSCCI provider DLL in the Value data box. You can use Windows Search to locate this absolute path.

      Note Contact your MSSCCI provider vendor to verify that this step does not interfere with the functionality of your MSSCCI provider.
  6. Click OK.
  7. Start Visual Studio .NET 2003 or Visual Studio 2005.
  8. On the File menu, point to
    New, and then click Project. Notice that you can successfully create a project, and you do not see the behavior that is mentioned in the "Symptoms" section.

↑ Back to the top

Status

This behavior is by design.

↑ Back to the top

More Information

Steps to reproduce the behavior

On a computer that has an MSSCCI provider that is registered by using a relative path, follow these steps:
  1. Install Visual Studio .NET 2003 or Visual Studio 2005.
  2. Turn on source code control.
  3. In Visual Studio .NET 2003 or Visual Studio 2005, try to create a Microsoft Visual Basic .NET or Microsoft Visual Basic 2005 Windows Application project or create a Microsoft Visual C# .NET or Microsoft Visual C# 2005 Windows Application project.

↑ Back to the top

References

For moreinformation, visit the following Microsoft Developer Network (MSDN) Web sites
Source Control Services
http://msdn2.microsoft.com/en-us/library/ms173879.aspx
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

820833 PRB: "Unspecified rror" error message when you perform a Source Control Operation in Visual Studio .NET 2003

↑ Back to the top

Keywords: kbprb, kbacl, kbdev, kbmsg, kbserver, kberrmsg, kbwiproauthor, kbregistry, kb, kbvs2005applies, kbvs2005swept, kbwiprotr

↑ Back to the top

Article Info
Article ID : 841707
Revision : 4
Created on : 3/30/2017
Published on : 3/30/2017
Exists online : False
Views : 89