"Some of the properties associated with the solution could not be read"

Next to the message in the subject, one of the symptoms we encountered is that although the solution contains some test projects the 'Create private accessor' menu has disappeared. Also, selecting 'Create unit tests...' produces an error. And when editing a testrun config and selecting the 'Code coverage' option, the settings dialog simply closes, without any message.

All these (and probably more) symptoms can occur because of a corrupt solution file. In our case the nested projects section was corrupted. Chances are this is because of some project or solution folder not being removed the way it should have been. Anyway, I tried fixing the solution file by hand but because of too many projects and solution folders this wasn't the way to go. Those GUIDs don't make a file very readable... I made a new solution file, containing the same solution folder structure, and added the existing projects. I overwrote the existing solution file, and that was that. So when you're experiencing any or all of the above symptoms, try building up a new solution file.

Hope this helps.

Technorati tags: , , ,

Published Thu, Dec 6 2007 9:43 PM by Rick van den Bosch
Filed under: , ,

Comments

# re: "Some of the properties associated with the solution could not be read"

We had the same error in our project.  The MS knowledge base article on teh issue about making sure there are no relative paths to Source Control Provider was fruitless.

Turns out it was caused by a second "GlobalSection(TeamFoundationVersionControl) = preSolution" block in our sln file.  We removed the block that was in error, and the properties couild nto be read message went away.

Thursday, December 13, 2007 4:41 PM by Stoney Meyerhoeffer

# re: "Some of the properties associated with the solution could not be read"

This worked for me too. Thanks!

Friday, January 25, 2008 9:58 PM by Joe

# Further Proof I Lack Self-Control : An Experiment in Scotch

Pingback from  Further Proof I Lack Self-Control : An Experiment in Scotch

Tuesday, March 25, 2008 2:39 PM by Further Proof I Lack Self-Control : An Experiment in Scotch

# re: "Some of the properties associated with the solution could not be read"

I also had 2 TeamFoundationVersionControl GlobalSection's in my sln file, removing one fixed my issues as well.  Cheers.

Monday, April 14, 2008 3:57 PM by Jay

# re: "Some of the properties associated with the solution could not be read"

Excellent, exactly what I was looking for too!!

Not to do with Team, but older fashioned VSS 6.0. Duplicate SoureControl section was the cause.

Nice one.

:o)

Tuesday, May 06, 2008 12:30 PM by Dai Clyant

# re: "Some of the properties associated with the solution could not be read"

+1 on the duplicate globalsection

Wednesday, August 06, 2008 7:56 PM by Mike Brown

# re: "Some of the properties associated with the solution could not be read"

That also did the trick for me, thanks.

Monday, October 27, 2008 5:50 PM by Steven Berkovitz

# re: "Some of the properties associated with the solution could not be read"

That was our exact problem too. Thanks.

Tuesday, November 25, 2008 10:41 AM by Rossa MacM

# re: "Some of the properties associated with the solution could not be read"

Bravo!  Problem fixed with removal of the second source control section.  

I had renamed the root namespace on a bunch of my projects and had removed/readded to source control (VSS2005).  I wonder why VS causes this error?  

Friday, February 06, 2009 5:46 PM by Matt

# re: "Some of the properties associated with the solution could not be read"

Thanks! this helped!

Tuesday, March 03, 2009 12:29 PM by Oleg

# re: "Some of the properties associated with the solution could not be read"

I found two duplicate sections in my solution.  Removing the incorrect ones solved the issues.

Friday, March 13, 2009 11:25 AM by Crabby Leg

# re: "Some of the properties associated with the solution could not be read"

Good one!!!

Thursday, April 02, 2009 2:40 AM by Ravi

# re: "Some of the properties associated with the solution could not be read"

Exactly That!

Duplicate removal fixed the problem, thanks :0)

Friday, April 03, 2009 9:54 AM by Digga

# re: "Some of the properties associated with the solution could not be read"

Same thing here, found 2 TeamFoundationVersionControl sections, deleted one and the error went away. Thanks

Tuesday, April 07, 2009 4:06 PM by City Folk

# re: "Some of the properties associated with the solution could not be read"

Thanks for the solution.  We had this problem once, and somehow got rid of it, but it came back on me recently, highly appreciated!

Thursday, May 07, 2009 3:36 PM by Paul

# re: "Some of the properties associated with the solution could not be read"

Thanks, that did it!

Monday, June 22, 2009 11:02 PM by Keegan

# re: "Some of the properties associated with the solution could not be read"

The same solution worked for me.

In my case it started when two developers added new projects at the same time and when both tried to check-in code. Obviously code was not "auto merged" correctly and hence the unpleasant message.

Thanks a lot!

Tuesday, June 23, 2009 3:53 PM by Edijs

# re: "Some of the properties associated with the solution could not be read"

Solved our problem

Duplicate VersionControl in solution file.

Friday, July 10, 2009 8:58 PM by VmsUser

# re: "Some of the properties associated with the solution could not be read"

thanks! GlobalSection was the problem.

Thursday, July 23, 2009 3:22 PM by jur

# re: "Some of the properties associated with the solution could not be read"

Thanx!!!! it works!!!!!!

Tuesday, July 28, 2009 11:07 AM by giga718

# re: "Some of the properties associated with the solution could not be read"

removing GlobalSection  + renumbering the SccProjectUniqueName1, SccProjectName1, SccLocalPath1 + setting the correct value for SccNumberOfProjects helped in my case.

Tuesday, August 11, 2009 9:17 AM by kph

# re: "Some of the properties associated with the solution could not be read"

The GlobalSection fix worked for us too, one of our solutions had no less than five duplicate TeamFoundationVersionControl sections!

Cheers :)

Wednesday, August 12, 2009 10:36 AM by Boidzerg

# re: "Some of the properties associated with the solution could not be read"

Add another one to the list. Thanks!

Friday, October 23, 2009 10:45 PM by j

# re: "Some of the properties associated with the solution could not be read"

+1 duplicated.. thanks

Monday, August 02, 2010 7:30 PM by +1 duplicated

# re: "Some of the properties associated with the solution could not be read"

"GlobalSection(TeamFoundationVersionControl) = preSolution" block was duplicated... removing worked a treat.

CHEERS!!!!!!!!!

Tuesday, August 24, 2010 1:38 PM by Dan

# re: "Some of the properties associated with the solution could not be read"

Nice one!!!

Friday, October 01, 2010 2:49 PM by Sulakhan Bungre

# re: "Some of the properties associated with the solution could not be read"

I get the fix, but does anyone know WHY it happens? I've got a solution that is not in Source Control (but all the projects are). I've taken all the recommended steps (unbound the source control, recreated the solution, edited the solution file), but it seems to be a recurring problem.

Saturday, October 23, 2010 4:13 PM by Andrew

# re: "Some of the properties associated with the solution could not be read"

Excellent.  Got rid of the annoying message, and fixed the Pending Checkins.  Top Man !

Tuesday, February 01, 2011 11:10 AM by Jamie

# re: "Some of the properties associated with the solution could not be read"

Thanks man!!

Monday, February 21, 2011 6:35 PM by kvkr

# re: "Some of the properties associated with the solution could not be read"

Thanks!!

Tuesday, May 17, 2011 1:56 PM by Stefan

Leave a Comment

(required) 
(required) 
(optional)
(required) 
Please add 2 and 1 and type the answer here: