Remote Access Management leaks memory when a VPN or Direct Access connection is used in Windows Server 2012 R2 and Windows Server 2012
Assume that Direct Access or a VPN is configured on a computer that is running Windows Server 2012 R2 or Windows Server 2012. When users use the VPN or Direct Access connection to access the Internet in a forced tunneling (FT) scenario, the Remote Access management service (RaMgmtSvc.dll) leaks memory.
This issue occurs because the Remote Access management service keeps information about every endpoints (IP addresses) over Internet that is accessed by the client. This resource information is for monitoring and reporting. It is not freed until the service is stopped.
To resolve this issue for Windows Server 2012 R2, install update 2919355.
To resolve this issue for Windows Server 2012, install the hotfix that is described in this article.
Update information for Windows Server 2012 R2For more information about how to obtain update 2919355, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014
Hotfix information for Windows Server 2012A supported hotfix is available from Microsoft. 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 this specific problem.
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, submit a request to 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, visit 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 be running Windows Server 2012.
Registry informationTo apply this hotfix, you do not have to make any changes to the registry.
Restart requirementYou do not have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2012 file information notesImportant Windows Server 2012 hotfixes are included in the same Windows 8 hotfix packages. However, only Windows 8 is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8". Always refer to the "Applies To" section in an article to determine the actual operating system that each hotfix applies to.
- The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version Product Milestone Service branch 6.2.920 0.20 xxx Windows Server 2012 RTM LDR
- GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
- The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2012" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2012
|File name||File version||File size||Date||Time||Platform|
|Raacctdbschema.sql||Not applicable||28,577||06-Jul-2012||19:57||Not applicable|
|Remoteaccess.events.xml||Not applicable||1,015||06-Jul-2012||19:57||Not applicable|
To work around this issue, restart the Remote Access Management service periodically.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional file information
Additional file information for Windows Server 2012
Additional files for all supported x64-based versions of Windows Server 2012
|File version||Not applicable|
|File version||Not applicable|
Article ID: 2895930 - Last Review: 04/08/2014 18:42:00 - Revision: 3.0
Windows Server 2012 R2 Datacenter, Windows Server 2012 R2 Essentials, Windows Server 2012 R2 Foundation, Windows Server 2012 R2 Standard, Windows Server 2012 Datacenter, Windows Server 2012 Essentials, Windows Server 2012 Foundation
- kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseadvanced KB2895930