Solution - Responder - Responder Explorer crashes on launch with CLR20R3 error

Version 2

    Behavior

     

    On certain machines Responder Explorer crashes on launch. The Miner event log contains an error similar to the following:

     

    Event Type: Error

    Event Source: Responder Explorer

    Event Category: None

    Event ID: 0

    Date: 8/27/2010

    Time: 14:11:30 PM

    User: N/A

    Computer: URT1793

    Description:

    2010-08-27 14:11:30,274 [Main Thread] ERROR Miner.Responder.Windows.ResponderClientApplication [(null)] - Failed to configure remoting

    System.Runtime.Remoting.RemotingException: Remoting configuration failed with the exception 'System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Messaging.MessageQueueException: Message Queue service is not available.

      at System.Messaging.MessageQueue.Create(String path, Boolean transactional)

      at Miner.Responder.Shared.Channels.MSMQ.MSMQManagement.CreateQueue(String path, Boolean transactional)

      at Miner.Responder.Shared.Channels.MSMQ.MessageEndpoint.CreateQueue()

      at Miner.Responder.Shared.Channels.MSMQ.MSMQClientChannel.CreateQueues()

      at Miner.Responder.Shared.Channels.MSMQ.MSMQClientChannel.SetupChannel()

      at Miner.Responder.Shared.Channels.MSMQ.MSMQClientChannel..ctor(IDictionary properties, IClientChannelSinkProvider sinkProvider)

      at Miner.Responder.Shared.Channels.MSMQ.MSMQChannel..ctor(IDictionary properties, IClientChannelSinkProvider clientSinkProvider, IServerChannelSinkProvider serverSinkProvider)

      --- End of inner exception stack trace ---

      at System.RuntimeMethodHandle._InvokeConstructor(Object[] args, SignatureStruct& signature, IntPtr declaringType)

      at System.RuntimeMethodHandle.InvokeConstructor(Object[] args, SignatureStruct signature, RuntimeTypeHandle declaringType)

      at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)

      at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)

      at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)

      at System.Runtime.Remoting.RemotingConfigHandler.CreateChannelFromConfigEntry(ChannelEntry entry)

      at System.Runtime.Remoting.RemotingConfigHandler.ConfigureChannels(RemotingXmlConfigFileData configData, Boolean ensureSecurity)

      at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData, Boolean ensureSecurity)'.

      at System.Runtime.Remoting.RemotingConfigHandler.ConfigureRemoting(RemotingXmlConfigFileData configData, Boolean ensureSecurity)

      at System.Runtime.Remoting.RemotingConfigHandler.DoConfiguration(String filename, Boolean ensureSecurity)

      at System.Runtime.Remoting.RemotingConfiguration.Configure(String filename, Boolean ensureSecurity)

      at Miner.Responder.Shared.RemotingHelper.Configure()

      at Miner.Responder.Windows.ResponderClientApplication.ConfigureRemotingServices()

     

    and the Application event log contains an error like this:

     

    Event Type: Error

    Event Source: .NET Runtime 2.0 Error Reporting

    Event Category: None

    Event ID: 5000

    Date: 8/27/2010

    Time: 14:11:31 PM

    User: N/A

    Computer: URT1793

    Description:

    EventType clr20r3, P1 miner.responder.explorer.exe, P2 9.2.0.0, P3 49d2e019, P4 mscorlib, P5 2.0.0.0, P6 4889dc80, P7 3d92, P8 11d, P9 system.runtime.remoting.remoting, P10 NIL.

     

    The key aspect to note is the CLR20R3 in the Application event log error.

     

    Cause

     

    The Microsoft Distributed Transaction Coordinator and Message Queuing services are not interacting properly and must be repaired.

     

    Solution

     

    1) Uninstall Microsoft Message Queuing by accessing the Windows Features list and unchecking the component.

     

     

    2) Stop the Distributed Transaction Coordinator service.

     

     

    3) Change the user on the service's Log On tab to Network Service. Despite the appearance in this screenshot, this is not an actual user account and will not have a password.

     

     

    4) Open an administrator-level command prompt and run "msdtc -resetlog" without the quotes.

    5) Restart the Distributed Transaction Coordinator service.

    6) Reinstall Message Queuing.