Answered by:
WHS Console "settings" window crashes when Routing and Remote Access is enabled.

Question
-
On my WHS, I tried to enable Routing and Remote Access so that I could set up NAT for an OpenVPN server to forward my internet traffic when I am on an untrusted network. I got the OpenVPN to work, but as soon as I click on the "Settings" button in the WHS console, it crashes with Event ID 5000 (see below), even when I am access it locally from the server itself. As soon as I disabled Routing and Remote Access, the crashing went away.
I know that I am asking WHS to do more that it was designed for, but it really would be convenient to have a way to use the internet securely from hotels or unsecured wireless access points.
Is this a known conflict?
Here is the event log info:
Event Type: Error
Event Source: .NET Runtime 2.0 Error Reporting
Event Category: None
Event ID: 5000
Date: 4/22/2009
Time: 2:23:34 AM
User: N/A
Computer: SERVER
Description:
EventType clr20r3, P1 homeserverconsole.exe, P2 6.0.0.0, P3 49b739c9, P4 whscommon, P5 6.0.0.0, P6 49b73949, P7 334, P8 1b, P9 n3ctrye2kn3c34sgl4zqyrbfte4m13nb, P10 NIL.For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 63 00 6c 00 72 00 32 00 c.l.r.2.
0008: 30 00 72 00 33 00 2c 00 0.r.3.,.
0010: 20 00 68 00 6f 00 6d 00 .h.o.m.
0018: 65 00 73 00 65 00 72 00 e.s.e.r.
0020: 76 00 65 00 72 00 63 00 v.e.r.c.
0028: 6f 00 6e 00 73 00 6f 00 o.n.s.o.
0030: 6c 00 65 00 2e 00 65 00 l.e...e.
0038: 78 00 65 00 2c 00 20 00 x.e.,. .
0040: 36 00 2e 00 30 00 2e 00 6...0...
0048: 30 00 2e 00 30 00 2c 00 0...0.,.
0050: 20 00 34 00 39 00 62 00 .4.9.b.
0058: 37 00 33 00 39 00 63 00 7.3.9.c.
0060: 39 00 2c 00 20 00 77 00 9.,. .w.
0068: 68 00 73 00 63 00 6f 00 h.s.c.o.
0070: 6d 00 6d 00 6f 00 6e 00 m.m.o.n.
0078: 2c 00 20 00 36 00 2e 00 ,. .6...
0080: 30 00 2e 00 30 00 2e 00 0...0...
0088: 30 00 2c 00 20 00 34 00 0.,. .4.
0090: 39 00 62 00 37 00 33 00 9.b.7.3.
0098: 39 00 34 00 39 00 2c 00 9.4.9.,.
00a0: 20 00 33 00 33 00 34 00 .3.3.4.
00a8: 2c 00 20 00 31 00 62 00 ,. .1.b.
00b0: 2c 00 20 00 6e 00 33 00 ,. .n.3.
00b8: 63 00 74 00 72 00 79 00 c.t.r.y.
00c0: 65 00 32 00 6b 00 6e 00 e.2.k.n.
00c8: 33 00 63 00 33 00 34 00 3.c.3.4.
00d0: 73 00 67 00 6c 00 34 00 s.g.l.4.
00d8: 7a 00 71 00 79 00 72 00 z.q.y.r.
00e0: 62 00 66 00 74 00 65 00 b.f.t.e.
00e8: 34 00 6d 00 31 00 33 00 4.m.1.3.
00f0: 6e 00 62 00 20 00 4e 00 n.b. .N.
00f8: 49 00 4c 00 0d 00 0a 00 I.L.....
And this I believe is the corresponding exception from the WHS log file:
[1]090422.022331.6406: Error: Exception thrown
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Reflection.TargetInvocationException: An exception occurred during the operation, making the result invalid. Check InnerException for exception details. ---> System.Runtime.InteropServices.COMException: There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9) (ErrorCode: -2147023143)
at Windows.HomeServer.Common.FirewallHelper.Native.INetFwPolicy.get_CurrentProfile() in WHSCommon.dll
at Microsoft.HomeServer.ServerTroubleShooter.FirewallHelper2.IsEnabled() in HomeServerConsoleTab.Toolkit.dll
at Microsoft.HomeServer.ServerTroubleShooter.RDPStatus.CheckFirewallSettings() in HomeServerConsoleTab.Toolkit.dll
at Microsoft.HomeServer.HomeServerConsoleTab.Toolkit.CompanionControl.refreshConnectivity(Object sender, DoWorkEventArgs e) in HomeServerConsoleTab.Toolkit.dll
at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e) in System.dll
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument) in System.dll
--- End of inner exception stack trace ---
at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary() in System.dll
at System.ComponentModel.RunWorkerCompletedEventArgs.get_Result() in System.dll
at Microsoft.HomeServer.HomeServerConsoleTab.Toolkit.CompanionControl.endRefreshConnectivity(Object sender, RunWorkerCompletedEventArgs e) in HomeServerConsoleTab.Toolkit.dll
at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(RunWorkerCompletedEventArgs e) in System.dll
at System.ComponentModel.BackgroundWorker.AsyncOperationCompleted(Object arg) in System.dll
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) in mscorlib.dll
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) in mscorlib.dll
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) in mscorlib.dll
at System.Delegate.DynamicInvokeImpl(Object[] args) in mscorlib.dll
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme) in System.Windows.Forms.dll
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj) in System.Windows.Forms.dll
at System.Threading.ExecutionContext.runTryCode(Object userData) in mscorlib.dll
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) in mscorlib.dll
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) in mscorlib.dll
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) in mscorlib.dll
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme) in System.Windows.Forms.dll
at System.Windows.Forms.Control.InvokeMarshaledCallbacks() in System.Windows.Forms.dll
at System.Windows.Forms.Control.WndProc(Message& m) in System.Windows.Forms.dll
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(Message& m) in System.Windows.Forms.dll
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(Message& m) in System.Windows.Forms.dll
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) in System.Windows.Forms.dll
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) in System.Windows.Forms.dll
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) in System.Windows.Forms.dll
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) in System.Windows.Forms.dll
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) in System.Windows.Forms.dll
at System.Windows.Forms.Application.RunDialog(Form form) in System.Windows.Forms.dll
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner) in System.Windows.Forms.dll
at System.Windows.Forms.Form.ShowDialog() in System.Windows.Forms.dll
at Microsoft.HomeServer.Controls.SettingsDialog.Init(Guid settingSelection) in HomeServerControls.dll
at Microsoft.HomeServer.Controls.SettingsDialog.Init() in HomeServerControls.dll
at Microsoft.HomeServer.HomeServerConsole.MainForm.settingsBtn_Click(Object sender, EventArgs e) in homeserverconsole.exe
at System.Windows.Forms.Control.OnClick(EventArgs e) in System.Windows.Forms.dll
at System.Windows.Forms.Button.OnClick(EventArgs e) in System.Windows.Forms.dll
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) in System.Windows.Forms.dll
at Microsoft.HomeServer.Controls.QButton.OnMouseUp(MouseEventArgs ea) in HomeServerControls.dll
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) in System.Windows.Forms.dll
at System.Windows.Forms.Control.WndProc(Message& m) in System.Windows.Forms.dll
at System.Windows.Forms.ButtonBase.WndProc(Message& m) in System.Windows.Forms.dll
at System.Windows.Forms.Button.WndProc(Message& m) in System.Windows.Forms.dll
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(Message& m) in System.Windows.Forms.dll
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(Message& m) in System.Windows.Forms.dll
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) in System.Windows.Forms.dll
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) in System.Windows.Forms.dll
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData) in System.Windows.Forms.dll
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) in System.Windows.Forms.dll
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) in System.Windows.Forms.dll
at System.Windows.Forms.Application.Run(Form mainForm) in System.Windows.Forms.dll
at Microsoft.HomeServer.HomeServerConsole.MainForm.Main(String[] args) in homeserverconsole.exeThursday, April 23, 2009 5:42 PM
Answers
-
Hi,
Routing and Remote Access is functionality of Windows Server 2003, which is not enabled by default.
Activating such functions is a violation of the EULA.
Since Routing and Remote Access/VPN also disables the Windows Firewall Service, this causes the crash in context with an installed Windows Home Server Toolkit.
Best greetings from Germany
Olaf- Proposed as answer by Lara JonesModerator Thursday, April 23, 2009 7:09 PM
- Marked as answer by unprovoked Thursday, April 23, 2009 7:12 PM
Thursday, April 23, 2009 7:04 PMModerator
All replies
-
Hi,
Routing and Remote Access is functionality of Windows Server 2003, which is not enabled by default.
Activating such functions is a violation of the EULA.
Since Routing and Remote Access/VPN also disables the Windows Firewall Service, this causes the crash in context with an installed Windows Home Server Toolkit.
Best greetings from Germany
Olaf- Proposed as answer by Lara JonesModerator Thursday, April 23, 2009 7:09 PM
- Marked as answer by unprovoked Thursday, April 23, 2009 7:12 PM
Thursday, April 23, 2009 7:04 PMModerator -
Wow, I had no idea about the EULA violation. I guess the crash is unintentionally enforcing it on me, since I can't run Routing and Remote Access anyhow. I will have to OpenVPN to another machine or to a DD-WRT router. Thank you.
Thursday, April 23, 2009 7:12 PM