For example, the DFS Service may encounter this problem. This is documented in the following Microsoft Knowledge Base article:
By default, events 2898 and 2899 are logged after you apply this hotfix. For more information about the 2898 and 2899 events, see the "More information" section.
Note Apply this hotfix on all domain controllers and AD LDS servers.
Hotfix informationA supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesTo apply this hotfix, you must have Service Pack 1 for Windows 7 or Windows Server 2008 R2 installed.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any previously released hotfix.
Note This logging level also has many other events in which you may have no interest.
Events that resemble the following are logged, together with the following details.
Note LDAP policy names are in bold.
Note Discarding a cookie cache entry based on the total size of the cookie cache (Event 2899) is considered only when there are more than MinResultSets entries in the cookie cache.
Learn about LDAP query policies and their meaning. This document describes cookie pool handling and monitoring.
Learn about how to edit LDAP query policies .
If you find these events, you can either change the query behavior of the application that experiences these problems or increase the quota on the cookie pool to avoid these problems. The setting of MaxResultSetSize is specified in bytes. Therefore, if you have an x64 LDAP server, there should be no problem in letting the cookie pool grow to several hundred megabytes if this is needed.
You should still try to obtain a sense of where the ceiling is and not grow the cookie pool to a large value immediately. For example, you can start with 1,048,576 bytes and then double the value until the events stop. Then, you know that the cookie pool requirement is probably between 8 and 16 megabytes (MB).
We recommend that you add automated monitoring for these events so that you can respond to this condition as needed.
ID članka: 2955074 - Poslednji pregled: 16.05.2014. - Verzija: 1