none
RD Gateway Manager Crashing adding a RAP RRS feed

  • 質問

  • I've set up a HA Connection Broker cluster, and in order to get the web gateway working again, I need to set up a new RAP policy that specifies the RD Broker RR Address, but every time I try, when I click 'Add' in 'User Groups' (And anywhere else in the MMC, it seems), the MMC crashes with the following output:

    Problem signature:
      Problem Event Name:    BEX64
      Application Name:    mmc.exe
      Application Version:    6.3.9600.17415
      Application Timestamp:    54504e26
      Fault Module Name:    clr.dll
      Fault Module Version:    4.6.1055.0
      Fault Module Timestamp:    563c12de
      Exception Offset:    00000000002fdbd8
      Exception Code:    c0000409
      Exception Data:    0000000000000002
      OS Version:    6.3.9600.2.0.0.400.8
      Locale ID:    1033
      Additional Information 1:    96f9
      Additional Information 2:    96f9c5010a52aa0dfa6dd4f9281ffe93
      Additional Information 3:    7b9b
      Additional Information 4:    7b9b3ea08d2dac897bb696ccf51055a9

    As far as I can tell from searching, it seems to be .NET that's crashing, but I haven't found any solutions.All three servers (Web Gateway and both Connection Brokers) are fully patched.

    has anyone else sen this and/or have any ideas how to either fix it or maybe some kind of workaround?


    • 編集済み DaveK1701 2016年2月10日 22:34
    2016年2月10日 22:33

回答

  • Hi

    just had the same problem on a Windows Server 2012R2 system, every time i wanted to add a security group to a CAP or RAP the MMC console crashed.

    Seams to be related to the .NET Update (KB 3102467) I installed today. Uninstalled the patch and MMC worked again.

    Hope this works for you as well..

    Regards

    • 回答としてマーク DaveK1701 2016年2月11日 18:06
    2016年2月11日 15:32
  • Hello,

    Exact same problem here.  MMC Remote Desktop Gatewayt Manager crash when adding a security group.
    Uninstalling .NET Framework  4.6.1 Update for Microsoft Windows (KB3102467) fix the issue.


    Problem signature:
      Problem Event Name:    BEX64
      Application Name:    mmc.exe
      Application Version:    6.3.9600.17415
      Application Timestamp:    54504e26
      Fault Module Name:    clr.dll
      Fault Module Version:    4.6.1055.0
      Fault Module Timestamp:    563c12de
      Exception Offset:    00000000002fdbd8
      Exception Code:    c0000409
      Exception Data:    0000000000000002
      OS Version:    6.3.9600.2.0.0.272.79
      Locale ID:    2060
      Additional Information 1:    a715
      Additional Information 2:    a715ff4bba0b93b9826cd6354225c284
      Additional Information 3:    c5d2
      Additional Information 4:    c5d26c223668c731173a112e5754dcfb
    • 回答としてマーク DaveK1701 2016年2月11日 18:06
    2016年2月11日 15:40
  • Hi,

    Please install the June 2016 update rollup and test to see if this issue is fixed.

    RD Gateway Manager console crashes with the latest .NET Framework 4.6.1 update on Windows Server 2012 R2

    https://support.microsoft.com/kb/3162871

    Thanks.

    -TP

    2016年6月22日 12:54
    モデレータ

すべての返信

  • Hi,

    Based on the “OS Version: 6.3.9600.2.0.0.400.8” you mentioned, it is Windows Server 2012 R2.

    Which .NET version has been installed on your server?

    You may reference below link and try to verify the installation state of the .NET:
    http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx

    If any missing/crash, you may try to repair/re-install with DISM. 

    Reference below link for more information:
    https://blogs.technet.microsoft.com/askcore/2012/05/14/windows-8-and-net-framework-3-5/

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    2016年2月11日 6:03
    モデレータ
  • I have the exact same problem. I recently built a new RD Gateway Management server, with no updates. I was able to create and test a RAP. After I installed updates, 175 of them, it no longer works.
    2016年2月11日 15:24
  • Hi

    just had the same problem on a Windows Server 2012R2 system, every time i wanted to add a security group to a CAP or RAP the MMC console crashed.

    Seams to be related to the .NET Update (KB 3102467) I installed today. Uninstalled the patch and MMC worked again.

    Hope this works for you as well..

    Regards

    • 回答としてマーク DaveK1701 2016年2月11日 18:06
    2016年2月11日 15:32
  • Hello,

    Exact same problem here.  MMC Remote Desktop Gatewayt Manager crash when adding a security group.
    Uninstalling .NET Framework  4.6.1 Update for Microsoft Windows (KB3102467) fix the issue.


    Problem signature:
      Problem Event Name:    BEX64
      Application Name:    mmc.exe
      Application Version:    6.3.9600.17415
      Application Timestamp:    54504e26
      Fault Module Name:    clr.dll
      Fault Module Version:    4.6.1055.0
      Fault Module Timestamp:    563c12de
      Exception Offset:    00000000002fdbd8
      Exception Code:    c0000409
      Exception Data:    0000000000000002
      OS Version:    6.3.9600.2.0.0.272.79
      Locale ID:    2060
      Additional Information 1:    a715
      Additional Information 2:    a715ff4bba0b93b9826cd6354225c284
      Additional Information 3:    c5d2
      Additional Information 4:    c5d26c223668c731173a112e5754dcfb
    • 回答としてマーク DaveK1701 2016年2月11日 18:06
    2016年2月11日 15:40
  • Version=1
    EventType=BEX64
    EventTime=130996809142985111
    ReportType=2
    Consent=1
    ReportIdentifier=a0180c27-d0da-11e5-80c9-00155d000b0d
    IntegratorReportIdentifier=a0180c26-d0da-11e5-80c9-00155d000b0d
    NsAppName=mmc.exe
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=mmc.exe
    Sig[1].Name=Application Version
    Sig[1].Value=6.3.9600.17415
    Sig[2].Name=Application Timestamp
    Sig[2].Value=54504e26
    Sig[3].Name=Fault Module Name
    Sig[3].Value=clr.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=4.6.1055.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=563c12de
    Sig[6].Name=Exception Offset
    Sig[6].Value=00000000002fdbd8
    Sig[7].Name=Exception Code
    Sig[7].Value=c0000409
    Sig[8].Name=Exception Data
    Sig[8].Value=0000000000000002
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.3.9600.2.0.0.272.79
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=2060
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=0739
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=07399f36e57f83e8d71c20ed9467211b
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=222e
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=222e9cfec961921500b189c3893e9575
    UI[2]=C:\Windows\system32\mmc.exe
    UI[3]=Microsoft Management Console has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Windows\system32\mmc.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\system32\KERNEL32.DLL
    LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\system32\GDI32.dll
    LoadedModule[5]=C:\Windows\system32\USER32.dll
    LoadedModule[6]=C:\Windows\system32\MFC42u.dll
    LoadedModule[7]=C:\Windows\system32\msvcrt.dll
    LoadedModule[8]=C:\Windows\system32\mmcbase.DLL
    LoadedModule[9]=C:\Windows\system32\ole32.dll
    LoadedModule[10]=C:\Windows\system32\SHLWAPI.dll
    LoadedModule[11]=C:\Windows\system32\UxTheme.dll
    LoadedModule[12]=C:\Windows\system32\DUser.dll
    LoadedModule[13]=C:\Windows\system32\OLEAUT32.dll
    LoadedModule[14]=C:\Windows\system32\ODBC32.dll
    LoadedModule[15]=C:\Windows\SYSTEM32\combase.dll
    LoadedModule[16]=C:\Windows\system32\RPCRT4.dll
    LoadedModule[17]=C:\Windows\SYSTEM32\sechost.dll
    LoadedModule[18]=C:\Windows\system32\ADVAPI32.dll
    LoadedModule[19]=C:\Windows\system32\SHCORE.DLL
    LoadedModule[20]=C:\Windows\system32\IMM32.DLL
    LoadedModule[21]=C:\Windows\system32\MSCTF.dll
    LoadedModule[22]=C:\Windows\system32\DUI70.dll
    LoadedModule[23]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.9600.18006_none_623f33d3ecbe86e8\Comctl32.dll
    LoadedModule[24]=C:\Windows\system32\SHELL32.dll
    LoadedModule[25]=C:\Windows\SYSTEM32\kernel.appcore.dll
    LoadedModule[26]=C:\Windows\system32\CRYPTBASE.dll
    LoadedModule[27]=C:\Windows\system32\bcryptPrimitives.dll
    LoadedModule[28]=C:\Windows\system32\urlmon.dll
    LoadedModule[29]=C:\Windows\system32\iertutil.dll
    LoadedModule[30]=C:\Windows\system32\WININET.dll
    LoadedModule[31]=C:\Windows\system32\USERENV.dll
    LoadedModule[32]=C:\Windows\system32\profapi.dll
    LoadedModule[33]=C:\Windows\SYSTEM32\clbcatq.dll
    LoadedModule[34]=C:\Windows\system32\mmcndmgr.dll
    LoadedModule[35]=C:\Windows\System32\msxml6.dll
    LoadedModule[36]=C:\Windows\system32\apphelp.dll
    LoadedModule[37]=C:\Windows\system32\dwmapi.dll
    LoadedModule[38]=C:\Windows\System32\oleacc.dll
    LoadedModule[39]=C:\Windows\system32\CRYPTSP.dll
    LoadedModule[40]=C:\Windows\system32\rsaenh.dll
    LoadedModule[41]=C:\Windows\system32\bcrypt.dll
    LoadedModule[42]=C:\Windows\system32\propsys.dll
    LoadedModule[43]=C:\Windows\system32\SETUPAPI.dll
    LoadedModule[44]=C:\Windows\system32\CFGMGR32.dll
    LoadedModule[45]=C:\Windows\system32\mlang.dll
    LoadedModule[46]=C:\Windows\system32\xmllite.dll
    LoadedModule[47]=C:\Windows\system32\atlthunk.dll
    LoadedModule[48]=C:\Windows\system32\VERSION.dll
    LoadedModule[49]=C:\Windows\SYSTEM32\mscoree.dll
    LoadedModule[50]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
    LoadedModule[51]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    LoadedModule[52]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll
    LoadedModule[53]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
    LoadedModule[54]=C:\Windows\system32\sxs.dll
    LoadedModule[55]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\diasymreader.dll
    LoadedModule[56]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.9600.18123_none_932c6b81474ee6d2\gdiplus.dll
    LoadedModule[57]=C:\Windows\system32\WindowsCodecs.dll
    LoadedModule[58]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.9600.17810_none_34ae2abd958aedeb\comctl32.dll
    LoadedModule[59]=C:\Windows\system32\ws2_32.dll
    LoadedModule[60]=C:\Windows\system32\NSI.dll
    LoadedModule[61]=C:\Windows\system32\mswsock.dll
    LoadedModule[62]=C:\Windows\system32\DNSAPI.dll
    LoadedModule[63]=C:\Windows\System32\rasadhlp.dll
    LoadedModule[64]=C:\Windows\system32\IPHLPAPI.DLL
    LoadedModule[65]=C:\Windows\system32\WINNSI.DLL
    LoadedModule[66]=C:\Windows\System32\fwpuclnt.dll
    LoadedModule[67]=C:\Windows\system32\wbem\wmiutils.dll
    LoadedModule[68]=C:\Windows\SYSTEM32\wbemcomn.dll
    LoadedModule[69]=C:\Windows\system32\wbem\wbemprox.dll
    LoadedModule[70]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\wminet_utils.dll
    LoadedModule[71]=C:\Windows\system32\wbem\wbemsvc.dll
    LoadedModule[72]=C:\Windows\system32\wbem\fastprox.dll
    LoadedModule[73]=C:\Windows\Microsoft.Net\assembly\GAC_64\aagwrapper\v4.0_6.3.0.0__31bf3856ad364e35\aagwrapper.dll
    LoadedModule[74]=C:\Windows\system32\CRYPT32.dll
    LoadedModule[75]=C:\Windows\SYSTEM32\CRYPTUI.dll
    LoadedModule[76]=C:\Windows\system32\MSASN1.dll
    LoadedModule[77]=C:\Windows\system32\COMDLG32.dll
    LoadedModule[78]=C:\Windows\system32\DWrite.dll
    LoadedModule[79]=C:\Windows\system32\RichEd20.DLL
    LoadedModule[80]=C:\Windows\system32\USP10.dll
    LoadedModule[81]=C:\Windows\system32\msls31.dll
    LoadedModule[82]=C:\Windows\System32\objsel.dll
    LoadedModule[83]=C:\Windows\System32\ACTIVEDS.dll
    LoadedModule[84]=C:\Windows\System32\NETAPI32.dll
    LoadedModule[85]=C:\Windows\System32\Secur32.dll
    LoadedModule[86]=C:\Windows\System32\NTDSAPI.dll
    LoadedModule[87]=C:\Windows\System32\credui.dll
    LoadedModule[88]=C:\Windows\System32\DSPARSE.dll
    LoadedModule[89]=C:\Windows\system32\WLDAP32.dll
    LoadedModule[90]=C:\Windows\System32\adsldpc.dll
    LoadedModule[91]=C:\Windows\System32\netutils.dll
    LoadedModule[92]=C:\Windows\System32\srvcli.dll
    LoadedModule[93]=C:\Windows\System32\wkscli.dll
    LoadedModule[94]=C:\Windows\System32\LOGONCLI.DLL
    LoadedModule[95]=C:\Windows\System32\DSROLE.DLL
    LoadedModule[96]=C:\Windows\System32\SSPICLI.DLL
    LoadedModule[97]=C:\Windows\System32\DPAPI.DLL
    LoadedModule[98]=C:\Windows\system32\riched32.dll
    LoadedModule[99]=C:\Windows\system32\adsldp.dll
    LoadedModule[100]=C:\Windows\system32\cscapi.dll
    FriendlyEventName=Stopped working
    ConsentKey=BEX64
    AppName=Microsoft Management Console
    AppPath=C:\Windows\system32\mmc.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=8B3135AAE035E407EF38FF64DE30C670
    
    
    
    
      
    


    2016年2月11日 16:20
  • Thanks guys - KB3102467 was the culprit. Gotta love it when an update breaks core functionality.
    2016年2月11日 18:07
  • Hi,

    Thank you for taking the time to update the result. Your sharing might be helpful for other people who has the similar problem.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact tnmff@microsoft.com.

    2016年2月12日 3:47
    モデレータ
  • Indeed! Uninstalling the KB3102467 fixed it for me as well.

    Thank you all

    2016年2月12日 12:28
  • Thanks.

    Worked for me aswell.

    2016年2月22日 8:41
  • Tnx. It worked well for me. Regards.

    2016年2月26日 7:49
  • Worked here as well...hope Microsoft comes out with a fix soon.
    2016年3月3日 16:27
  • I have a different hot fix, different KB number related to the 4.61 .net framework.

    I will uninstall and see if it will fix the problem. I experiencing the same problem as mentioned above.

    2016年3月9日 0:58
  • Removing KB3102467 fixed the Remote Desktop Gatewayt Manager, but broke the RDWeb function.

    After removing it, I can no longer user https://domain.com/RDWeb/Feed/webfeed.aspx

    2016年3月9日 4:21
  • Has anyone contacted Microsoft support to see if they have a fix by now?
    2016年3月10日 0:10
  • This is a serious issue, I uninstalled the above mentioned hotfix and still the same issue. It has something to do with other patches as well.
    2016年3月10日 17:48
  • design_express - could you tell me what the KB number was that you uninstalled please?  I'm experiencing this same issue but don't have KB 3102467 listed as installed.

    Thanks.

    2016年3月17日 17:41
  • Any update on a fix from MS on this issue?
    • 編集済み taf_mynet 2016年3月23日 6:30
    2016年3月21日 13:37
  • Remove also update KB 3045563 if not working after remove KB 3102467.
    2016年3月26日 10:48
  • Hello, This solution has worked for me too.
    But now I have a problem because I can not read my RDWeb/feed/webfeed.aspx file..., just the same as quoted by jktech81.

    The good news is that my windows tells me that I need to install a new patch (the one I removed previously, KB3102467) and after re-installing the patch everything works as before, that is, cannot edit RAP policy because MMC crashes but webfeed.aspx works perfect.

    • 編集済み PacoAbal 2016年3月30日 17:58
    2016年3月29日 13:12
  • guys... please... this issues is present since 10th february... 

    would it be possible to release an update which solves this problem?!

    Has anyone a workaround how i can add users to a CAP with the update installed(i tried via powershell but it doesn't work as well...)

    2016年4月1日 9:14
  • guys... please... this issues is present since 10th february... 

    would it be possible to release an update which solves this problem?!

    Has anyone a workaround how i can add users to a CAP with the update installed(i tried via powershell but it doesn't work as well...)

    Has anyone had any luck with this?

    Due to a number of dependant services i cant remove the update mentioned.

    Is there another workaround, im in big trouble here.

    2016年4月2日 9:10
  • Removing both worked for me, thanks Jari.

    Just doing KB 3102467 didn't, even if I remove and re-install Gateway Manager. Doing both did work.

    Thanks for post and responses All.

    2016年4月4日 13:39
  • Manage the RD Gateway server(s) from a host that has the RD Gateway Management tool but not the KB 3102467 , that should keep you going for now. Some do it that way with good results

    Hope it helps,

    Didier

    2016年4月6日 18:53
  • This is a JOKE.

    wusa.exe /uninstall /kb:3102467

    "This KB is required by the system and cannot be removed."

    All my images have this update and I am ****ed. 

    What is going on, microsoft?!
    2016年5月5日 18:12
  • I am having this problem to. adding myself to this thread to hear about any potential updates. Really not impressed :(
    2016年5月9日 13:05
  • Same issue here. Removed the mentioned KB and it didn't fix it, so also installed all of the updates from May. Same issue still.

    The second KB doesn't show as installed for me.

    2016年5月12日 11:24
  • I figured I'd try the .NET 4.6.2 Preview to see if that fixes the problem (and would help in situations like trickydrizzle's where 4.6.1 is slipstreamed into the image)...no dice, unfortunately. :(

    2016年5月16日 20:33
  • KB3045563 is .NET 4.6 (as in .NET 4.6.0!!!!!)

    In other words, .NET 4.6.anything + RD Gateway = Bad News Bears
    2016年5月16日 21:11
  • Thanks you for this!  Got to love Microsoft—almost four months later and still no fix.  Forced Windows Updates in the latest version of Windows is a blast…


    2016年5月30日 20:37
  • I have removed all traces of .net 4.6

    I had to run DISM to repair my .net framework to get everything to work.

    If I have no policies in my NPS - the NPS and Remote Desktop Gateway will start

    If I have any policies then NPS and Remote Desktop Gateway will not start.

    I am at a bit of a loss as to why removing 4.6 has not resolved all my issues.

    thanks

    jack

    2016年5月30日 23:59
  • I am also experiencing this issue and would like to know if MS plan to release an updated patch?
    2016年6月6日 22:22
  • Hi,

    Please install the June 2016 update rollup and test to see if this issue is fixed.

    RD Gateway Manager console crashes with the latest .NET Framework 4.6.1 update on Windows Server 2012 R2

    https://support.microsoft.com/kb/3162871

    Thanks.

    -TP

    2016年6月22日 12:54
    モデレータ
  • Thanks for this solution TP; Upvoting this
    2016年6月22日 17:30
  • This worked
    2016年6月22日 18:58
  • Adding the policies via Powershell is a good workaround for me. https://blogs.technet.microsoft.com/manojnair/2011/12/02/rds-powershell-tfm-part-v-configuring-a-rd-gateway-using-powershell/
    2016年6月22日 19:01
  • Worked for me too.

    Thank you.

    2016年8月13日 14:23
  • Finaly a technet page that actual solved the problem :)

    MS Fix your errors before sending out updates that can kill our core systems or loos the trust from people.
    2016年9月20日 13:51
  • This still appears to be an issue with 4.6.2 (we went from the .Net version installed with 2012 R2 and a functional RD Gateway Manager to installing 4.6.2 and now have a broken RD Gateway Manager).

    I guess we'll have to use the Powershell workaround but if MS fixed it in 4.6.1 with a patch is appears they've broken it again in 4.6.2, if anyone is aware of a 4.6.2 equivalent to KB3162871 please post it!

    2017年3月14日 16:39
  • Yea still an issue, even in .NET 4.7

    How do they expect us to use windows updates is they constantly break stuff.

    I wish there was a viable RDS alternative that is not citrix

    2017年6月26日 13:58
  • I'm seeing this exact issue, and already have the latest (oct 2017) roll up patch.

    Where do we go from there?

    2017年11月6日 17:44
  • You can use Powershell:

    Import-Module RemoteDesktopServices
    #get info
    Get-ChildItem RDS:\GatewayServer -Recurse

    #here change your RDP CAP name
    $capName = "RDP CAP"

    #Here change RDPGroup@domain.local for your AD group
    New-Item -Path RDS:\GatewayServer\CAP -Name $capName -UserGroups @("RDPGroup@domain.local") -AuthMethod 1

    2018年8月14日 10:40
  • Still actual. Thank you.
    2019年2月21日 6:16
  • Thanks this worked perfectly!
    2019年2月21日 9:02
  • KB3172614 fix for me. 
    2019年4月3日 13:36