none
Error with ECP and new-powershellvirtualdirectory RRS feed

  • Question

  • Hello, after a slew of updates my exchange installation began acting up.

    ECP does not work:

    ScenarioDescription         : An attempt was made to invoke the Web service at
                                  https://server5.*.com/ecp/RulesEditor/InboxRules.svc/GetList.
    PerformanceCounterName      : ECP Web Sevice Logon Latency
    Result                      : Failure
    Error                       : An exception was thrown by the Web service: The remote server returned an error: (500)
                                  Internal Server Error.
    UserName                    : extest_0073327b313e4
    StartTime                   : 2/14/2013 2:03:04 PM
    Latency                     : -00:00:00.0010000
    EventType                   : Error
    LatencyInMillisecondsString :
    Identity                    :
    IsValid                     : True
    ObjectState                 : New

    The event log shows this when this happens:

    WebHost failed to process a request.
     Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/47329482
     Exception: System.ServiceModel.ServiceActivationException: The service '/ecp/RulesEditor/InboxRules.svc' cannot be activated due to an exception during compilation.  The exception message is: Unrecognized element 'webHttpBinding'. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\web.config line 1819). ---> System.Configuration.ConfigurationErrorsException: Unrecognized element 'webHttpBinding'. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp\web.config line 1819)
       at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
       at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
       at System.Web.Configuration.WebConfigurationManager.GetSection(String sectionName, String path)
       at System.ServiceModel.Configuration.WebHttpBindingCollectionElement.GetSectionFromWebConfiguration(String sectionPath)
       at System.ServiceModel.Configuration.WebHttpBindingCollectionElement.GetBindingCollectionElement()
       at System.ServiceModel.WebHttpBinding.ApplyConfiguration(String configurationName)
       at Microsoft.Exchange.Management.ControlPanel.ServiceHostFactory.EcpServiceHost.CreateBinding(Uri address)
       at Microsoft.Exchange.Management.ControlPanel.EcpServiceHostBase.ApplyConfiguration()
       at System.ServiceModel.ServiceHostBase.InitializeDescription(UriSchemeKeyedCollection baseAddresses)
       at System.ServiceModel.ServiceHost..ctor(Type serviceType, Uri[] baseAddresses)
       at Microsoft.Exchange.Management.ControlPanel.EcpServiceHostBase..ctor(Type serviceType, Uri[] baseAddresses)
       at Microsoft.Exchange.Management.ControlPanel.ServiceHostFactory.CreateServiceHost(Type serviceType, Uri[] baseAddresses)
       at System.ServiceModel.Activation.ServiceHostFactory.CreateServiceHost(String constructorString, Uri[] baseAddresses)
       at System.ServiceModel.ServiceHostingEnvironment.HostingManager.CreateService(String normalizedVirtualPath)
       at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
       at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
       --- End of inner exception stack trace ---
       at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
       at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
     Process Name: w3wp
     Process ID: 6448

    Also, when trying to create the powershell directory (which got removed as I was trying to fix this) I get an error:

    New-PowerShellVirtualDirectory : An error occurred while creating the IIS virtual directory
    'IIS://SERVER5.*.COM/W3SVC/1/ROOT/PowerShell' on 'SERVER5'.
    At line:1 char:1
    + New-PowerShellVirtualDirectory -Name PowerShell
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (SERVER5\PowerShell (Default Web Site):ADObjectId) [New-PowerShellVirt
       ualDirectory], InvalidOperationException
        + FullyQualifiedErrorId : 93A40692,Microsoft.Exchange.Management.SystemConfigurationTasks.NewPowerShellVirtualDire
       ctory

    Not sure where to go from here. Tried everything I could find on google.

    Thursday, February 14, 2013 7:08 PM

Answers

  • May have fixed it by doing this

    New-PowerShellVirtualDirectory -Name "PowerShell (Default Web Site)"

    New error:

    "The wimRM client sent a request to an http server and got a response asying the requested http url was not available" when running EMS!?!

    What is going on!!

    • Marked as answer by omgomgomgomg Thursday, February 14, 2013 9:56 PM
    • Edited by omgomgomgomg Thursday, February 14, 2013 9:57 PM
    Thursday, February 14, 2013 9:56 PM
  • Okay, had to use IIS6 metabase explorer and renamed "powershell (default web site)" to powershell and now EMC + EMS seem to work.

    I really hope this helps someone. 

    • Marked as answer by omgomgomgomg Friday, February 15, 2013 1:00 PM
    Thursday, February 14, 2013 10:13 PM

All replies

  • I fixed the ECP problems by doing 

    PS C:\windows\Microsoft.NET\Framework64\v3.5> .\WFServicesReg.exe /c


    Still experiencing the new-powershellvirtualdirectory problem!!


    + New-PowerShellVirtualDirectory -Name PowerShell
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (SERVER5\PowerShell (Default Web Site):ADObjectId) [New-PowerShellVirt
       ualDirectory], InvalidOperationException
        + FullyQualifiedErrorId : 93A40692,Microsoft.Exchange.Management.SystemConfigurationTasks.NewPowerShellVirtualDire
       ctory

    Not sure where to go from here. Tried everything I could find on google.



    • Edited by omgomgomgomg Thursday, February 14, 2013 8:38 PM
    • Proposed as answer by Norbert Baum Thursday, October 23, 2014 11:20 AM
    Thursday, February 14, 2013 7:37 PM
  • May have fixed it by doing this

    New-PowerShellVirtualDirectory -Name "PowerShell (Default Web Site)"

    New error:

    "The wimRM client sent a request to an http server and got a response asying the requested http url was not available" when running EMS!?!

    What is going on!!

    • Marked as answer by omgomgomgomg Thursday, February 14, 2013 9:56 PM
    • Edited by omgomgomgomg Thursday, February 14, 2013 9:57 PM
    Thursday, February 14, 2013 9:56 PM
  • Okay, had to use IIS6 metabase explorer and renamed "powershell (default web site)" to powershell and now EMC + EMS seem to work.

    I really hope this helps someone. 

    • Marked as answer by omgomgomgomg Friday, February 15, 2013 1:00 PM
    Thursday, February 14, 2013 10:13 PM