Error: Collection modified; enumeration operation execute

[jyasgar]

Error: Collection was modified; enumeration operation may not execute.

I am using Vault version 4.0.3.15836 with VS 2005. I get this message during the day periodically, and it is often when VS is not in the foreground.

I will sometimes also have a box that states "Object reference not set to an instance of an object."

I have deleted my cache files twice in the past month. Once because I could not log in at all, another to try and resolve this issue.

Anyone have any suggestions on what might be wrong? Deleting the cach files every week seems to mess up many file status markers which is becoming time consuming to fix and watch for.

[Beth]

In VS Tools - Options - Source Control, which client exactly do you have set?
If you are using the VS 2005 client, the first thing I'd suggest is upgrading your client to Vault 4.0.6 since that has all the latest fixes.

Can you open your Vault client, connect to a repository and go to Help - Technical Support and copy the information from there to me? I don't need the licensing information, just the client and server environment information. That may give me some clues.

Starting some client-side logging for both your client and Visual Studio would be good too. Instructions can be found here: Client Side Logging

[jyasgar]

Hi Beth,

Client Information
Vault Client Version: 4.0.3.15836
.Net Framework Version: 2.0.50727.1433
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 1.99 GB
Time Zone: (GMT-05:00) Eastern Time (US & Canada)

Server Information
Vault Server Version: 4.0.3.15836
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT-05:00) Eastern Time (US & Canada)
SQL Version: Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

[jyasgar]

I believe I tried to upgrade my client some time back and it complained that the server needed to be upgraded as well.

Is that true? If so, that will take a bit to coordinate.

Thanks,

[Beth]

Most times you do want to have the client and server match, especially when it's a major release. Vault 4.0.6 is a maintenance release, so you can connect a Vault 4.0.6 client to a Vault 4.0.3 server. Best results are obtained when connecting a 4.0.6 client to a 4.0.6 server, but for the sake of troubleshooting here, you can feel free to just upgrade your client portion.

Is anyone else receiving the same errors you are?

[jyasgar]

The other main active user says he is NOT receiving these errors.

[Beth]

Have that user also check their Help - Technical support and compare it to yours. That may point out some difference.

Also, have one or both of you installed the VS service packs or the service packs for your OS?