Sign in
 
Home2012Previous VersionsLibraryForumsGallery
Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
System Center TechCenter >
> 
> 
Systems Centre Virtual Machine Manager 2012 (Console) Crashes

Answered Systems Centre Virtual Machine Manager 2012 (Console) Crashes

  • Monday, June 11, 2012 2:50 AM
     
     
    Sign In to Vote
    0

    Currently I am using Systems Centre Virtual Machine Manager 2012 (Console) ona  windows 7 x64 enterprise machine on HP hardware (z210 Workstation with Xeon 2.66 QC CPU) and after I type in the credentials (as we do cross domain authentication) the console crashes before it finishes loading. No errors in the event log at all!! Just this stack trace when debugging through Visual Studio..... Help appreciated:

    System.Configuration.ConfigurationErrorsException was unhandled

      Message=The 'system.serviceModel/commonBehaviors' configuration section cannot be created. The machine.config file is missing information. Verify that this configuration section is properly registered and that you have correctly spelled the section name. For Windows Communication Foundation sections, run ServiceModelReg.exe -i to fix this error.

      Source=System.ServiceModel

      BareMessage=The 'system.serviceModel/commonBehaviors' configuration section cannot be created. The machine.config file is missing information. Verify that this configuration section is properly registered and that you have correctly spelled the section name. For Windows Communication Foundation sections, run ServiceModelReg.exe -i to fix this error.

      Line=0

      StackTrace:

           at System.ServiceModel.Configuration.ConfigurationHelpers.UnsafeGetAssociatedSection(ContextInformation evalContext, String sectionPath)

           at System.ServiceModel.Description.ConfigLoader.LookupCommonBehaviors(ContextInformation context)

           at System.ServiceModel.Description.ConfigLoader.LoadCommonClientBehaviors(ServiceEndpoint serviceEndpoint)

           at System.ServiceModel.ChannelFactory.InitializeEndpoint(Binding binding, EndpointAddress address)

           at System.ServiceModel.DuplexChannelFactory`1..ctor(Object callbackObject, Binding binding, EndpointAddress remoteAddress)

           at Microsoft.SystemCenter.VirtualMachineManager.Remoting.ServerConnection.CreateConnection()

           at Microsoft.VirtualManager.UI.Data.ConnectionManager.DoConnect(ConnectionInfo connInfo)

           at Microsoft.VirtualManager.UI.Data.ConnectionManager.InvokeRemoteMethod[TResult](Func`1 rmiWrapper)

           at Microsoft.VirtualManager.UI.Data.ConnectionManager.<>c__DisplayClass3.<Connect>b__0(Object state)

           at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

           at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)

           at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

      InnerException:

     
     

All Replies

  • Monday, June 11, 2012 3:08 AM
     
     
    Sign In to Vote
    0

    As a side note - I have many other Win 7 64bit & x86 that work fine with the console - Also, the console works fine on the Library server it self as well.

    I have tried the fix mentioned where using more than 1 monitor causes the console to crash and this did nothing for me.

     
  • Tuesday, June 26, 2012 11:28 PM
     
     
    Sign In to Vote
    0

    I have just updated the Local Console with the Update Rollup 1 patch for SC VMM 2012 but still get the same result (See below). I have also tried to the following as recommended in the stacktrace:

    C:\Windows\Microsoft.NET\Framework\v4.0.30319>ServiceModelReg.exe -ia

    Microsoft (R) WCF/WF registration tool version 4.0.0.0

    Copyright (c) Microsoft Corporation.  All rights reserved.

    Administration utility that manages the installation and uninstallation of

    WCF and WF components on a single machine.

    [Warning]The HTTP namespace reservation already exists.

    Here is the new (But the same) Stack Trace:

    System.Configuration.ConfigurationErrorsException was unhandled

      Message=The 'system.serviceModel/commonBehaviors' configuration section cannot be created. The machine.config file is missing information. Verify that this configuration section is properly registered and that you have correctly spelled the section name. For Windows Communication Foundation sections, run ServiceModelReg.exe -i to fix this error.

      Source=System.ServiceModel

      BareMessage=The 'system.serviceModel/commonBehaviors' configuration section cannot be created. The machine.config file is missing information. Verify that this configuration section is properly registered and that you have correctly spelled the section name. For Windows Communication Foundation sections, run ServiceModelReg.exe -i to fix this error.

      Line=0

      StackTrace:

           at System.ServiceModel.Configuration.ConfigurationHelpers.UnsafeGetAssociatedSection(ContextInformation evalContext, String sectionPath)

           at System.ServiceModel.Description.ConfigLoader.LookupCommonBehaviors(ContextInformation context)

           at System.ServiceModel.Description.ConfigLoader.LoadCommonClientBehaviors(ServiceEndpoint serviceEndpoint)

           at System.ServiceModel.ChannelFactory.InitializeEndpoint(Binding binding, EndpointAddress address)

           at System.ServiceModel.DuplexChannelFactory`1..ctor(Object callbackObject, Binding binding, EndpointAddress remoteAddress)

           at Microsoft.SystemCenter.VirtualMachineManager.Remoting.ServerConnection.CreateConnection()

           at Microsoft.VirtualManager.UI.Data.ConnectionManager.DoConnect(ConnectionInfo connInfo)

           at Microsoft.VirtualManager.UI.Data.ConnectionManager.InvokeRemoteMethod[TResult](Func`1 rmiWrapper)

           at Microsoft.VirtualManager.UI.Data.ConnectionManager.<>c__DisplayClass3.<Connect>b__0(Object state)

           at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)

           at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)

           at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)

      InnerException:

     
  • Thursday, July 05, 2012 2:26 AM
     
     
    Sign In to Vote
    0
    Hello - Does anyone have any ideas? Current work around is less than desirable. Using a Remote Desktop Services session!
     
  • Thursday, January 03, 2013 3:49 PM
     
     
    Sign In to Vote
    0

    For me, the problem was the video card:

    http://social.technet.microsoft.com/Forums/en-US/virtualmachinemanager/thread/f43a763b-7642-4751-bba4-61f5d2e0359a

    Good luck....

     
  • Saturday, January 12, 2013 8:06 PM
     
     Answered
    Sign In to Vote
    0

    I never fixed this. As we have upgraded to SCVMM 2012 RTM SP1 this question is no longer valid.

    I have to say though, SP1 has brought a new set of issues :)

     
  • Sunday, January 13, 2013 11:51 AM
    Moderator
     
     Answered
    Sign In to Vote
    0
    Thanks for the update please feel free to open this thread again if you face this problem once more.

    Mohamed Fawzi | http://fawzi.wordpress.com