To fix this problem, contact Microsoft Customer Support Services to get the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, go to the following Microsoft website:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will fix your problem. The usual support costs will apply to additional support questions and issues that don't qualify for the specific update in question.
PrerequisitesTo apply this hotfix, you must have the .NET Framework 3.5 SP1 installed.
Restart requirementYou have to restart the computer after you apply this hotfix if any affected files are being used. We recommend that you close all .NET Framework-based applications before you apply this hotfix.
Hotfix replacement informationThis hotfix package doesn't replace a previously released hotfix package.
Issues that this hotfix rollup fixesIssue 1
The ResourceManager has a race condition in AddResourceSet. When multiple threads are adding resourcesets, ObjectDisposedExceptions occur.
ResourceManager uses one ResourceSet for potentially multiple cultures, such as fr-FR and fr. If you add one culture (like fr-FR) on one thread and then add fr on another thread, the first thread may try to add its ResourceSet for fr. In this situation, the first thread will close the already-added resource for fr-FR, and that causes ObjectDisposedExceptions on other threads.
When you try to run a command on the server, it time outs on the client-side, but finishes on the server. Then, the client sends an attention packet to the server, and sets itself into a timed-out state. However, the client doesn't reset the state as soon as it recovers from the time-out if the server processed the statement that the client timed out on.
This fix resets the state for the client when it can recover from a time-out.
Article ID: 3096438 - Last Review: Oct 29, 2015 - Revision: 1