Error in Exchange 2010: Event ID 6037

Hello,
I am getting a warning on Exchange 2010 Servers:
The program svchost.exe, with the assigned process ID 2012, could not authenticate locally by using the target name HOST/SOPEXMB5.ad\. The target name used is not valid. A target name should refer to one of the local computer names, for example, the DNS host name.
I could not figure out what is missing in DNS:
Any help would be appreciated,
Thanks,
Dom
System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Hi Felyjos
Try this:
HKLM\system\CurrentControlSet\Services\Lanmanserver\parameters
DisableStrictNameChecking:DWORD=1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
DisableLoopbackCheck:DWORD=1
Fred Chamanara | Advanced Agile Technology LLC
| Hire us for Consulting | please mark "Propose As Answer" if helpful, Thanks.

Similar Messages

  • Exchange 2010 "event id 403/401 The physical consistency check" Backups does not work...Critical!!

    Hi,
    At this moment our backups does not work. We have two error on the event viewer;
    Exchange 2010 sp3 version 14.03.0158.001
    We have only one server Exchange 2010 with two databases for users...
    Event id 401;
    Instance 1: The physical consistency check has completed, but one or more errors were detected. The consistency check has terminated with error code of -106 (0xffffff96).
    Event id 403;
    Instance 1: The physical consistency check successfully validated 629126 out of 1110272 pages of database '\\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy33\exchangedb\global\global.edb'. Because some database pages were either not validated or failed validation,
    the consistency check has been considered unsuccessful.

    Hi Javier,
    From your error description, I recommend you do the following steps for troubleshooting:
    1. Please run CHKDSK and restart server.
    2. Run a Database level Mailbox repair request.
    What's more, here are some useful threads for your reference.
    Create a Mailbox Repair Request
    http://technet.microsoft.com/en-us/library/ff625221(v=exchg.141).aspx
    Database Backup Failing with Event ID 2007, 9782, 401, 403, 254
    http://social.technet.microsoft.com/Forums/en-US/4c8eccbf-435a-43ef-b3f6-0de5096413ee/database-backup-failing-with-event-id-2007-9782-401-403-254?forum=exchangesvravailabilityandisasterrecoverylegacy
    Hope it helps.
    If you need further assistance, please feel free to let me know.
    Best regards,
    Amy
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Exchange 2010 - Event Logging Failure - "System.ServiceModel 3.0.0.0"

    Exchange 2010 14.3 Build 123.4
    Stumped. Can't seem to figure out why this suddenly started but this Exchange error is logging every minute.
    According to Process Explorer, this is the Exchange process (PID 6860) not logging correctly:
    c:\windows\system32\inetsrv\w3wp.exe -ap "MSExchangeServicesAppPool" -v "v2.0" -l "webengine4.dll" -a \\.\pipe\iisipma54689d0-13bc-4c77-a060-0bae334c1a34 -h "C:\inetpub\temp\apppools\MSExchangeServicesAppPool\MSExchangeServicesAppPool.config"
    -w "" -m 0
    This is the error logged:
    Source: System.ServiceModel 3.0.0.0
    Event ID: 5
    Task Category: Message Logging
    Details:
    A message was not logged.
     Exception: System.InvalidCastException: Unable to cast object of type 'System.ServiceModel.Channels.StreamedMessage' to type 'System.ServiceModel.Channels.BufferedMessage'.
       at System.ServiceModel.Security.SecurityVerifiedMessage.GetReaderAtEnvelope()
       at System.ServiceModel.Security.ReceiveSecurityHeader.GetReaderAtSecurityHeader()
       at System.ServiceModel.Security.ReceiveSecurityHeader.OnWriteHeaderContents(XmlDictionaryWriter writer, MessageVersion messageVersion)
       at System.ServiceModel.Diagnostics.MessageLogTraceRecord.WriteHeader(XmlDictionaryWriter dictionaryWriter)
       at System.ServiceModel.Diagnostics.MessageLogTraceRecord.WriteTo(XmlWriter writer)
       at System.ServiceModel.Diagnostics.MessageLogger.LogInternal(MessageLogTraceRecord record)
       at System.ServiceModel.Diagnostics.MessageLogger.LogMessageImpl(Message& message, XmlReader reader, MessageLoggingSource source)
       at System.ServiceModel.Diagnostics.MessageLogger.LogMessage(Message& message, XmlReader reader, MessageLoggingSource source)
     Process Name: w3wp
     Process ID: 6860

    Hi,
    Please firstly confirm if the Autodiscover service, OAB service, Free/Busy information, OOF feature, OWA and ECP can work well for Exchange users or not.
    If there are some issues when using these services or features for client users, please do the following points in IIS manager:
    1. Go to control panel and checked if there are any third party application or message logging application.
    2. Please recycle Autodiscover, MSExchangeServicesAppPool.
    3. Try to install the below hotfixes:
    http://support.microsoft.com/kb/2801728
    http://support.microsoft.com/kb/2637518
    If Autodiscover, EWS and other features are working fine but we still get above error messages reported for the Autodiscover, EWS PID's, please make sure that SystemLogging is turned OFF in Microsoft Exchange Troubleshooting Assistant tool (EXTRA) on the
    Exchange servers:
    1. Launch Microsoft Exchange Troubleshooting Assistant tool by clicking Start > run > type EXTRA > Select a task > Trace control > Set manual trace tags.
    2. Under Components to Trace, uncheck SystemLogging.
    3. Click Start tracing > Stop the tracing once the tracing has started.
    (Please note: Even if we are not running EXTRA but still enabling the SystemLogging component will turn on MessageLogging)
    Then check whether the issue persists.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Error installing Exchange 2010 on Server 2012 R2

    I have the immense displeasure of trying to install Exchange 2010 (migrating from 2003) onto our new Server 2012 R2 server. I get to the install screen when I get this error immediately upon pressing the "Install" button:
    Organization Preparation
    Failed
    Error:
    The following error was generated when "$error.Clear();
     install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema0.ldf")
    " was run: "The system cannot find the file specified".
    The system cannot find the file specified
    Click here for help...
    http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
    Unfortunately there is NO help on the Microsoft site about this error so I have NO clue how to fix this or what file is missing. What do I do next? I'd like to get this installed and running over this weekend. Can anyone shed light on this problem? It's
    2012 R2, just patched the 15 updates that it found BEFORE installing (or attempting I should say) Exchange 2010.

    Hi,
    The support version of Operating system for Exchange 2010 is as follows
    64-bit edition of Windows Server 2008 Standard with Service Pack 2 (SP2)
    64-bit edition of Windows Server 2008 Enterprise with SP2
    64-bit edition of Windows Server 2008 R2 Standard with SP1
    64-bit edition of Windows Server 2008 R2 Enterprise with SP1
    Windows Server 2008 Datacenter RTM or later
    Windows Server 2008 R2 Datacenter RTM or later
    Windows Server 2012 (Requires Exchange 2010 SP3 or later)
    Officially Ms not announced to have Exchange 2010 in Windows Server 2012 R2. Check it out the service pack you are using in Exchange server 2010.
    Try to download new iso image from the Microsoft Volume licensing page or from download site..may the image can be corrupted.
    Ref: http://technet.microsoft.com/en-us/library/aa996719(EXCHG.141).aspx
    Exchange Queries

  • OWA Error after Exchange 2010 Mailbox move to 2013

    Hello,
    We have been experiencing an issue when we move a users mailbox from Exchange 2010 on-prem to Exchange 2013 on-prem.  As a domain admin I was able to access the users mailbox via OWA 2010 with out issues.  However, now that they have been
    moved over to 2013 I am getting the following error message:
    X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.AccessDeniedException
    X-OWA-Version: 15.0.995.28
    X-FEServer: CASServer
    X-BEServer: Mailboxserver.domain.com
    Date: 1/29/2015 5:27:38 PM
    Full Access permissions appear on the mailbox still via the 2013 ECP console for my account.  I have tried running the
    Set-Mailbox UserName -ApplyMandatoryProperties command but receive a message that no settings have been modified.
    I have also tried to remove/re-add inheritable permissions on the users AD account to no avail.
    I have a large group of mailboxes to move over to 2013 and hoping their is a decent solution out there to prevent this from happening.
    Greatly appreciate any feedback on this request.
    Cheers

    Hi,
    Please re-add the full access permission for the administrator:
    Get-Exchange Server "servername" | Get-Mailbox | Add-MailboxPermission -User Administrator -AccessRights FullAccess
    If Administrator is still located in Exchange 2010 and has the full access permission to an Exchange 2013 mailbox ([email protected]) which is moved from Exchange 2010, please use the following URL to open the mailbox:
    https://Exch13.domain.com/owa/[email protected]/
    Then check whether the issue persists.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2010 - Event ID 2107 Warning

    We have a multi-forest environment configured with a forest to forest selective authentication trust with two separate Exchange Orgs.  One of our HT Servers is generating Event ID: 2107 with Source: MSExchange ADAccess and Task Category:
    Topology.  It states:
    Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1272). Exchange Active Directory Provider failed to obtain an IP address for DS server <Server name>, error 11004 (WSANO_DATA (The requested name is valid and was found in the database, but it does not have
    the correct associated data being resolved for.)).  This host will not be used as a DS server by Exchange Active Directory Provider. 
    The DC listed in the error is in a different forest from the HT server reporting the error.
    Why would it be trying to populate this DC in its listing for Directory access?  The error has ceased, there are no connectivity issues, but I'm just curious what is going on here. 
    The only interaction going on between these to Orgs is Availability service communication.  Not sure if this is the reason for this.
    Any insight, would be greatly appreciated.
    Thanks!

    Hi,
    Based on my research, This Error event indicates that Active Directory Provider did not obtain an IP address for an Active Directory server. This host will not be used as an Active Directory server by DSAccess. This could be caused by network problems. This
    is a critical error if there are no other domain controllers available for load balance:
    http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=8.0&EvtID=2107&EvtSrc=MSExchange+ADAccess
    For the error code, except with the resolutions in the above article, we can also use network monitor to find the root cause.
    According to your description,  you are doubting why the server listed is the DC in another forest.
    And I’d like to confirm the following information:
    1. Do you install your Exchange server on DC?
    2. Is the DC global controller?
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • SBS 2011 & Exchange 2010 (Event ID 103) Search Issues

    I have a customer that is having issues with a continuous stream of Event ID 103 "MSExchange Search Indexer" Issues. The details of the event are as follows: 
    The Microsoft Exchange Search Indexer service failed to initialize due to the following error: (HResult)(-2147467262).
    I have tried to do the following:
    Run Troubleshoot-CI
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\Troubleshoot-CI.ps1
    Get-EventLog : No matches found
    At C:\Program Files\Microsoft\Exchange Server\V14\Scripts\CITSLibrary.ps1:622 char:40
    + $msftesqlCrashes = get-eventlog <<<< -computername $Server -after $StartTime -logname "Application" -source
    $msftesqlServiceName | where {$_.eventId -eq $msftesqlCrashEventId}
    + CategoryInfo : ObjectNotFound: (:) [Get-EventLog], ArgumentException
    + FullyQualifiedErrorId : GetEventLogNoEntriesFound,Microsoft.PowerShell.Commands.GetEventLogCommand
    Name IsDeadLocked CatalogStatusArray
    JKW-SBS True {Mailbox Database\JKW-SBS}
    Run Test-exchangesearch
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>test-exchangesearch
    Database Server Mailbox ResultFound SearchTime Error
    InSeconds
    Mailbox D... JKW-SBS SystemMai... False -1 Time out for test thread.
    Tried to manually Rebuild the Text Index
    Tried to run the Repair-ExchangeSearchRymLinks
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\Repair-ExchangeSearchSymlinks.ps1
    Attempting to repair symbolic links
    Stopping msftesql-exchange and msexchangesearch services
    WARNING: Waiting for service 'Microsoft Exchange Search Indexer (msexchangesearch)' to finish stopping...
    Installing symbolic links
    Starting msftesql-exchange and msexchangesearch services
    Symbolic links restored.
    Please run test-exchangesearch to verify installation.
    Get-MailboxDatabase
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Get-MailboxDatabaseCopyStatus -Server $env:ComputerName | Fo
    rmat-Table Name,Status,ContentIndex* -Auto
    Name Status ContentIndexState ContentIndexErrorMessage
    Mailbox Database\JKW-SBS Mounted Healthy
    GetSearchIndexForDatabase.ps1 
    [PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\GetSearchIndexForDatabase.ps1 "Mailbox Database"
    Database Name :Mailbox Database
    Index Directory: Search Index Does Not Exist for This Database

    Hi Robert,
    Would you please let me confirm whether had installed any antivirus software on the SBS 2011? If had installed,
    please temporarily disable and monitor the result.
    Meanwhile, Please refer to following similar thread and check if can help you.
    SBS
    2011 - MsExchange Search Indexer error 103
    If any update, please feel free to let me know.
    Hope this helps.
    Best regards,
    Justin Gu

  • MailBox Move Error With Exchange 2010 sp3

    I initiated a mailbox move for a specific mailbox and let it run all night. The next day, the user stated he cannot log into is mailbox and the error stated "mailbox is moving, check back later".
    Exchange stated the status of the move is "CompletedWithError". I noticed that the mailbox is still in the old database.
    I tried to remove the move request and received an error "couldn't find a move request that corresponds to this identity".
    I rebooted the exchange server.
    Exchange still shows the user in the old database
    There is no move requests in exchange
    The user is still experiencing the same error "You weren't able ti sign in because the mailbox is being move"
    I tried to initiated another move and received:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:00
    John, Doe
    Failed
    Error:
    Couldn't switch the mailbox into Sync Source mode.
    This could be because of one of the following reasons:
      Another administrator is currently moving the mailbox.
      The mailbox is locked.
      The Microsoft Exchange Mailbox Replication service (MRS) doesn't have the correct permissions.
      Network errors are preventing MRS from cleanly closing its session with the Mailbox server. If this is the case, MRS may continue to encounter this error for up to 2 hours - this duration is controlled by the TCP KeepAlive settings on the Mailbox server.
    Wait for the mailbox to be released before attempting to move this mailbox again.
    MapiExceptionMailboxInTransit: Unable to open message store. (hr=0x80004005, ec=1292)
    Diagnostic context:
        Lid: 55847   EMSMDBPOOL.EcPoolSessionDoRpc called [length=163]
        Lid: 43559   EMSMDBPOOL.EcPoolSessionDoRpc returned [ec=0x0][length=264][latency=0]
        Lid: 23226   --- ROP Parse Start ---
        Lid: 27962   ROP: ropLogon [254]
        Lid: 17082   ROP Error: 0x50C     
        Lid: 26937  
        Lid: 21921   StoreEc: 0x50C     
        Lid: 27962   ROP: ropExtendedError [250]
        Lid: 1494    ---- Remote Context Beg ----
        Lid: 26426   ROP: ropLogon [254]
        Lid: 22787   Error: 0x0
        Lid: 13032   StoreEc: 0x8004010F
        Lid: 25848  
        Lid: 7588    StoreEc: 0x8004010F
        Lid: 25840  
        Lid: 6564    StoreEc: 0x8004010F
        Lid: 50999  
        Lid: 2567    StoreEc: 0x50C     
        Lid: 19452  
        Lid: 2199    StoreEc: 0x50C     
        Lid: 56415  
        Lid: 48223   StoreEc: 0x50C     
        Lid: 17097   StoreEc: 0x50C     
        Lid: 8620    StoreEc: 0x50C     
        Lid: 1750    ---- Remote Context End ----
        Lid: 26849  
        Lid: 21817   ROP Failure: 0x50C     
        Lid: 26297  
        Lid: 16585   StoreEc: 0x50C     
        Lid: 32441  
        Lid: 1706    StoreEc: 0x50C     
        Lid: 24761  
        Lid: 20665   StoreEc: 0x50C     
        Lid: 25785  
        Lid: 29881   StoreEc: 0x50C     
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.3.224.2&t=exchgf1&e=ms.exch.err.Ex7E66C2
    Exchange Management Shell command attempted:
    'ab.ad/CD/Users/doe, john' | New-MoveRequest -TargetDatabase 'Carlsbad_Mailbox'
    Elapsed Time: 00:00:00
    At this point, when trying to access the mailbox, exchange states its being moved... when trying to remove the move... Exchange does not see the move.
    any help is appreciated,

    Hi Cudflyn,
    Base on my search, you can try to increase the TCP Keep Alive Time for the servers involved in the move.You can refer to the following
    article to increase it:
    Mailbox Move Error - 'Couldn't switch the mailbox into Sync Source mode'
    Note: Just REMEMBER to DELETE the registry entry when the mailbox moves are compete!
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Database redundansy health check failed ( Exchange 2010 sp3 )

    Hello all ,
    One of the mailbox server have been getting the following error in in application , sometimes
    RealCopyQueu  is 256 and sometimes 0 and healthy  .
    Kindly share how can resolve it please

    Hi,
    I suggest we refer to the following article to troubleshoot this issue. Run
    Database Redundancy Check Script.
    http://social.technet.microsoft.com/Forums/exchange/en-US/b1cfbc4b-b17d-4148-adce-1a565d0f5746/exchange-2010-event-id-4113-msexchangerepl-health-check-failed
    Regards,
    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 Subscriber Support, contact
    [email protected]
    Simon Wu
    TechNet Community Support

  • Exchange 2010 is suddenly unmanageable

    Hi --
    On a SBS 2011 box running Exchange 2010 SP2, Exchange has suddenly become unmanageable. I have no idea what happened overnight to cause this. But I've been trying to get this fixed for two hours already, with no luck.
    Nobody can open OWA. From anywhere. Including from the server itself. IE network diagnostics reveal that "The device or resource (whatever) is not set up to accept connections on port "https".
    The Exchange Management Console won't open. I get the error "The attempt to connect to http://server/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WinRM client cannot process the
    request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication
    mechanisms supported by the server. To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination,
    specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic."
    Opening an Exchange Management Shell results in the error:
    >>>>>>>>>>>>>>>>>>>>>>>>
    VERBOSE: Connecting to server.domain.local
    [server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
    request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
    by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
    ooting Help topic.
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
       eption
        + FullyQualifiedErrorId : PSSessionOpenFailed
    VERBOSE: Connecting to server.domain.local
    [server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
    request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
    by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
    ooting Help topic.
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
       eption
        + FullyQualifiedErrorId : PSSessionOpenFailed
    VERBOSE: Connecting to server.domain.local
    [server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
    request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
    by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
    ooting Help topic.
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
       eption
        + FullyQualifiedErrorId : PSSessionOpenFailed
    Failed to connect to an Exchange server in the current site.
    Enter the server FQDN where you want to connect.:
    <<<<<<<<<<<<<<<<<<<<<<<<
    I have checked and double-checked bindings, Kerberos settings, and a slew of other things. I have reset IIS and rebooted the server multiple times. I can't get past this. Everything referenced in the following articles was checked and verified to be as the
    articles said they should be:
    http://blogs.technet.com/b/bshukla/archive/2012/05/04/exchange-management-shell-error-500-internal-server-error.aspx
    http://technet.microsoft.com/en-us/library/ff607221%28v=EXCHG.80%29.aspx
    http://support.microsoft.com/kb/2028305
    I installed and ran the EMTshooter script referenced in http://blogs.technet.com/b/exchange/archive/2010/12/07/resolving-winrm-errors-and-exchange-2010-management-tools-startup-failures.aspx. This it what it reported:
    >>>>>>>>>>>>>>>>>>>>>>>>
    Welcome to the Exchange Management Troubleshooter!
    We recommend that you run the troubleshooter after making changes to
    IIS to ensure that connectivity to Exchange Powershell is unaffected.
    Checking IIS Service...
    Checking the Exchange Install Path variable...
    Checking the Powershell Virtual Directory...
    Checking the Powershell vdir SSL setting...
    Checking the Powershell vdir path setting...
    Checking HTTP Port 80...
    Checking HTTP Port 80 Host Name...
    Testing for errors...
    VERBOSE: Connecting to server.domain.local
    [server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a r
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
        + FullyQualifiedErrorId : PSSessionOpenFailed
    The Exchange Management Troubleshooter successfully completed connecting to:
    server.domain.local
    Failed to connect to any Exchange Server in the current site.
    Problem found:
    Looking for error...
    These are the possible causes for this error:
    1. The default http binding has been removed from the Default Web Site. Exchange Powershell needs http to be configured
    so that the IP Address is "All Unassigned", the Port is "80", and the Host Name is "".  A common scenario for changing t
    his is if you are running multiple web sites, and attempting to set up a redirect to https://mail.company.com/owa by req
    uiring SSL on the Default Web Site, and creating another web site to do the redirect back to the SSL-enabled website. Re
    mote PowerShell requires port 80 to be available on the Default Web Site for all Internet Addresses. If you want to set
    up an automatic redirect to /owa and redirect http requests to https, you should follow the instructions located at:
    http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx
    and follow the directions under the section:
    "For a Configuration in Which SSL is required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0."
    2. The http binding on the Default Web Site has been modified, and the Hostname field configured. To correct this issue,
     you need to clear out the Hostname field under the port 80 bindings on the Default Web Site.
    After each error is resolved, close this window and re-run the tool to check for additional problems.
    <<<<<<<<<<<<<<<<<<<<<<<<
    However, the bindings on the Default Web site are correct (I've checked them multiple times).
    And the server's System, Security and Application logs are devoid of anything that could even begin to explain what is going on.
    And this was all working yesterday ...
    I have automatic replies to modify/remove and have no way to get to them. Outlook on the PCs won't pull up Automatic Replies, claiming that the server is unavailable. On the other hand, email is coming and going fine ...
    I need to get this fixed _now_. Does anybody know how to get to the bottom of this -- and what could have possibly happened to cause this in the first place?
    Thanks
    CL

    Hi --
    C:\Users\Administrator>winrm quickconfig
    WinRM already is set up to receive requests on this machine.
    WinRM already is set up for remote management on this machine.
    C:\Users\Administrator>winrm invoke Restore winrm/Config
    Restore_OUTPUT
    C:\Users\Administrator>winrm get winrm/config
    Config
        MaxEnvelopeSizekb = 150
        MaxTimeoutms = 60000
        MaxBatchItems = 32000
        MaxProviderRequests = 4294967295
        Client
            NetworkDelayms = 5000
            URLPrefix = wsman
            AllowUnencrypted = false
            Auth
                Basic = true
                Digest = true
                Kerberos = true
                Negotiate = true
                Certificate = true
                CredSSP = false
            DefaultPorts
                HTTP = 5985
                HTTPS = 5986
            TrustedHosts
        Service
            RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)
            MaxConcurrentOperations = 4294967295
            MaxConcurrentOperationsPerUser = 15
            EnumerationTimeoutms = 60000
            MaxConnections = 25
            MaxPacketRetrievalTimeSeconds = 120
            AllowUnencrypted = false
            Auth
                Basic = false
                Kerberos = true
                Negotiate = true
                Certificate = false
                CredSSP = false
                CbtHardeningLevel = Relaxed
            DefaultPorts
                HTTP = 5985
                HTTPS = 5986
            IPv4Filter = *
            IPv6Filter = *
            EnableCompatibilityHttpListener = false
            EnableCompatibilityHttpsListener = false
            CertificateThumbprint
        Winrs
            AllowRemoteShellAccess = true
            IdleTimeout = 180000
            MaxConcurrentUsers = 5
            MaxShellRunTime = 2147483647
            MaxProcessesPerShell = 15
            MaxMemoryPerShellMB = 150
            MaxShellsPerUser = 5
    C:\Users\Administrator>winrm enumerate winrm/config/listener
    C:\Users\Administrator>netstat -aon | find ":80"
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:808            0.0.0.0:0              LISTENING       4856
      TCP    192.168.214.20:80      192.168.214.20:15979   ESTABLISHED     4
      TCP    192.168.214.20:15979   192.168.214.20:80      ESTABLISHED     6336
      TCP    192.168.214.20:15980   192.168.214.20:80      TIME_WAIT       0
      TCP    192.168.214.20:15997   192.168.214.20:8014    SYN_SENT        8528
      TCP    [::]:80                [::]:0                 LISTENING      
    4
      TCP    [::]:808               [::]:0                 LISTENING      
    4856
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15926
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15973
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15978
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15982
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15984
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15989
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15990
      TIME_WAIT       0
    C:\Users\Administrator>
    PID 4 is c:\Windows\system32\ntoskrnl.exe
    PID 6336 is DataCollectorSvc.exe
    I'm still getting all the same errors.

  • Exchange 2010 - Management Console and Shell Very slow

    Heya
    I have an Exchange 2010 SP3 enviroment, with 2 HUBCAs and 5 MBX servers.
    This servers were 2008 R2 standard, and they were working fine.
    This weekend, in order to configure DAG, i upgrade 3 of them to server 2008 R2 enterprise with dsim. Is not the first tiem i do this, and never had problems before.
    After the upgrade, the server started fine, the mailboxes, the database.. everything fine.. except, de mmc and the shell.
    Both, the mmc and the shell wont start. It gives me the winrm error, but because a time out.
    I have installed the installed the iss-winrm feature, delete on regedit and %appdata% the "cache" for the management console, checked the firewal... and nothing worked.
    Well, thats not true, in one of the servers, the Management console started working fine, but the shell, it connect, but every command i launch it takes like 10-15 minutes to execute (for example, a get-mailboxdatabase).
    In the other,, no the Management console, no the shell connects, i get a winrm timeout.
    I dont know were to continue cchecking why happens this, just started after changing the 2008 R2 from standard to enterprise
    Thanks for the help!!

    Hi,
    Please check that your time is in sync as well on your Exchange Server.
    Please check whether this issue caused by performance.
    More details in the following article:
    Understanding Memory Configurations and Exchange Performance
    http://technet.microsoft.com/en-us/library/dd346700(v=exchg.141).aspx
    http://technet.microsoft.com/en-us/library/dd346699(v=exchg.141).aspx
    Please also paste the detailed error message without sensitive information for the further troubleshooting.
    Found some related blog for your reference:
    Resolving WinRM errors and Exchange 2010 Management tools startup failures
    http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx
    Troubleshooting Exchange 2010 Management Tools startup issues
    http://blogs.technet.com/b/exchange/archive/2010/02/04/3409289.aspx
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Event IDs 136 and 137 0x80000000000000 in System Log on Windows 2008 R2 Server, Exchange 2010 in Cluster

    Hi,
    I'm having an issue with one of my exchange 2010 Servers. We had a power outage and upon recovery, I cannot start Services Net.Pipe Listener Adapter and Net.Tcp Listener Adapter (And thus cannot Start IIS and provide Exchange Client Services.) This is a
    physical server (Not VMWare or Hyper-V)
    The System event log has lots of Event 136's and 137s on Ntfs with the keyword - 0x80000000000000 - The General Messages are: The default transaction resource manager on volume C: encountered an error while starting and its metadata was
    reset.  The data contains the error code.
    and
    The default transaction resource manager on volume OS encountered a non-retryable error and could not start.  The data contains the error code.
    XML Output as follows:
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Ntfs" />
      <EventID Qualifiers="32772">136</EventID>
      <Level>3</Level>
      <Task>2</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-11-17T18:10:37.788942300Z" />
      <EventRecordID>315532</EventRecordID>
      <Channel>System</Channel>
      <Computer>server.domain.com</Computer>
      <Security />
      </System>
    - <EventData>
      <Data />
      <Data>C:</Data>
      <Binary>1C00040002003000020000008800048000000000060019C000000000000000000000000000000000060019C0</Binary>
      </EventData>
     </Event>
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="Ntfs" />
      <EventID Qualifiers="49156">137</EventID>
      <Level>2</Level>
      <Task>2</Task>
      <Keywords>0x80000000000000</Keywords>
      <TimeCreated
    SystemTime="2014-11-17T18:10:37.788942300Z" />
      <EventRecordID>315531</EventRecordID>
      <Channel>System</Channel>
      <Computer>server.domain.com</Computer>
      <Security />
      </System>
    - <EventData>
      <Data />
      <Data>OS</Data>
      <Binary>1C0004000200300002000000890004C000000000020100C000000000000000000000000000000000020100C0</Binary>
      </EventData>
      </Event>
    When I attempt to start the services - I get the following errors:
    The Net.Pipe Listener Adapter service depends on the Windows Process Activation Service service which failed to start because of the following error: 
    Transaction support within the specified resource manager is not started or was shut down due to an error.
    The Net.Pipe Listener Adapter service depends on the Windows Process Activation Service service which failed to start because of the following error: 
    Transaction support within the specified resource manager is not started or was shut down due to an error.
    I have tried the "fsutil resource setautoreset true" fix without success.
    Any ideas or direction would be much appreciated. Restoring this server will be extremely difficult.
    Thanks!

    We can close this question.
    From an elevated prompt, I ran 'fsutil resource setautoreset true' and attempted to remove the files with .blf and regtrans-ms file extensions from C:\Windows\System32\config\TxR. but these files were locked by system processes. (They are also
    tagged with the hidden file attrib so you may not see them at first)
    So, I booted the system with a Windows 2008 R2 Install Disk, selected repair OS and selected the command prompt. I then performed a chkdsk /f c: and selected "Y" to unmount the drive. It made some repairs.
    With the system booted from the install disk, and chkdsk executed, the locks were freed and I was able to delete the files from C:\Windows\System32\config\TxR.
    Once the system rebooted, the services came back fine and everything was back to normal.

  • After Exchange 2007 Migration to Exchange 2010, OAB is erroring

    Hello all, 
    I migrated from single server Exchange 2007 to single Exchange 2010 2 months ago using a co-existence environment.  The 2007 server is still running, but it's not doing anything but SMTP relay, as I am waiting on Oracle admin to point their server at
    my new 2010  server.  Yesterday, I noticed a new mail enabled user we created was not showing up in the Address Book.  He is in the Global Address list when I check it from OWA.  And I can see him in my Address book if I search All Users,
    instead of the Global Address List.  Everytime I try to update the Offline Address Book, I get the following error
    OABGen encountered error 80004005 while cleaning the offline address list public folders under /o=2007Server/cn=addrlists/cn=oabs/cn=Default Offline Address Book.  Please make sure the public folder database is mounted and replicas exist of the offline
    address list folders.  No offline address lists have been generated.  Please check the event log for more information. 
    - \Default Offline Address Book 
    There was a Public Folder on the 2007 server, but I don't think anyone was using it.  All of our clients our 2007 or later.  Enable Web-based distribution is enabled and Generation server is my new 2010 server.  Enable public folder distribution
    not enabled.
    Any help would be greatly appreciated.  

    No, the Enable public folder check box is not ticked.  However, the link you provided has led me to other clues.  The author says "To locate the actual
    OAB distribution point on the Client Access Server, the Outlook client will use the autodiscover service."  I wonder if still having the CAS role on the old 2007 Exchange Server still installed is causing issues with Autodiscover.  Below
    are the results of the Test E-mail AutoConfiguration from Outlook.
    The Results tab of the Test E-mail AutoConfiguration:
    Autoconfiguration found the following settings:
    Display Name:  User1
    Redirect URL:  https://Exchange2010.Contoso.com/Autodiscover/Autodiscover.xml
    Internal OWA URL: https://Exchange2010.Contoso.com/owa
    External OWA URL: https://Exchange2007.Contoso.com/owa
    Protocol: Exchange RPC
    Server: Exchange2010.Contoso.com
    Login Name:  user1
    Availability Service URL: https://Exchange2010.Contoso.com/EWS/Exchange.asmx
    OOF URL: https://Exchange2010.Contoso.com/EWS/Exchange.asmx
    OAB URL: https://Exchange2010.Contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6/
    Unified Messaging Service URL: https://Exchange2010.Contoso.com/EWS/UM2007Legacy.asmx
    Auth Package: Unspecified
    Exchange Control Panel URL: https://Exchange2010.Contoso.com/ecp/
    ECP Sub URL: ?p=customize/voicemail.aspx&exsvurl=1
    ECP Sub URL: ?p=personalsettings/EmailSubscriptions.slab&exsvurl=1
    ECP Sub URL: PersonalSettings/DeliveryReport.aspx?exsvurl=1&IsOWA=Is<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>
    ECP Sub URL: ?p=organize/retentionpolicytags.slab&exsvurl=1
    Protocol: Exchange HTTP
    Server: Exchange2010.Contoso.com
    Login Name: user1
    SSL: Yes
    Mutual Authentication: Yes
    Availability Service URL: https://Exchange2007.Contoso.com/ews/exchange.asmx
    OOF URL: https://Exchange2007.Contoso.com/ews/exchange.asmx
    OAB URL: https://Exchange2010.Contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6
    Unified Message Service URL: https://Exchange2007.Contoso.com/ews/UM2007Legacy.asmx
    Auth Package: Basic
    Certificate Principal Name: msstd:Exchange2010.Contoso.com
    Exchange Control Panel URL: https://Exchange2007.Contoso.com
    ECP Sub URL: ?p=customize/voicemail.aspx&exsvurl=1
    ECP Sub URL: ?p=personalsettings/EmailSubscriptions.slab&exsvurl=1
    ECP Sub URL: Personalsettings/DeliveryReport.aspx?exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>
    ECP Sub URL: ?p=organize/retentionpolicytags.slab&exsvurl=1
    The Log tab of the Test E-mail AutoConfiguration:
    [email protected]
    Attempting URL https://Exchange2007.Contoso.com/Autodiscover/Autodiscover.xml found through SCP
    Autodiscover to https://Exchange2007.Contoso.com/Autodiscover/Autodiscover.sml starting
    GetLastError=0; httpStatus=401.
    GetLastError=0; httpStatus=302.
    Autodiscover to https://Exchange2007.Contoso.com/Autodiscover/Autodiscover.xml Failed (0x800C8204)
    Autodiscover URL redirection to https://Exchange2010.Contoso.com/Autodiscover/Autodiscover.xml
    Autodiscover to https://Exchange2010.Contoso.com/Autodiscover/Autodiscover.xml starting
    GetLastError=0; httpsStatus=200
    Autodiscover to https://carus.Contoso.com/Autodiscover/Autodiscover.xml Succeeded (0x00000000)
    The XML tab of the Test E-mail AutoConfiguration:
    <?xml version="1.0" encoding="utf-8"?>
    <Autodiscover xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
      <Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
        <User>
          <DisplayName>Chad Wingo</DisplayName>
          <LegacyDN>/o=Exchange2007/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=cwingo</LegacyDN>
          <AutoDiscoverSMTPAddress>[email protected]</AutoDiscoverSMTPAddress>
          <DeploymentId>c389bc85-adbe-4481-aa25-1fbc209a6fde</DeploymentId>
        </User>
        <Account>
          <AccountType>email</AccountType>
          <Action>settings</Action>
          <Protocol>
            <Type>EXCH</Type>
            <Server>Exchange2010.contoso.com</Server>
            <ServerDN>/o=Exchange2007/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange2010</ServerDN>
            <ServerVersion>738280F7</ServerVersion>
            <MdbDN>/o=Exchange2007/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Exchange2010/cn=Microsoft Private MDB</MdbDN>
            <PublicFolderServer>Exchange2010.contoso.com</PublicFolderServer>
            <AD>DATA.domainskc.com</AD>
            <ASUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</ASUrl>
            <EwsUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</EwsUrl>
            <EcpUrl>https://Exchange2010.contoso.com/ecp/</EcpUrl>
            <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um>
            <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt>
            <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret>
            <OOFUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</OOFUrl>
            <UMUrl>https://Exchange2010.contoso.com/EWS/UM2007Legacy.asmx</UMUrl>
            <OABUrl>http://Exchange2010.contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6/</OABUrl>
          </Protocol>
          <Protocol>
            <Type>EXPR</Type>
            <Server>Exchange2010.contoso.com</Server>
            <SSL>On</SSL>
            <AuthPackage>Basic</AuthPackage>
            <ASUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</ASUrl>
            <EwsUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</EwsUrl>
            <EcpUrl>https://Exchange2007.contoso.com/ecp/</EcpUrl>
            <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um>
            <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt>
            <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret>
            <OOFUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</OOFUrl>
            <UMUrl>https://Exchange2007.contoso.com/ews/UM2007Legacy.asmx</UMUrl>
            <OABUrl>https://Exchange2010.contoso.com/OAB/43e497ff-6fc4-47f8-8e7b-fe252e84ddf6/</OABUrl>
          </Protocol>
          <Protocol>
            <Type>WEB</Type>
            <Internal>
              <OWAUrl AuthenticationMethod="Basic, Fba">https://Exchange2010.contoso.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXCH</Type>
                <ASUrl>https://Exchange2010.contoso.com/EWS/Exchange.asmx</ASUrl>
              </Protocol>
            </Internal>
            <External>
              <OWAUrl AuthenticationMethod="Fba">https://Exchange2007.contoso.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXPR</Type>
                <ASUrl>https://Exchange2007.contoso.com/ews/exchange.asmx</ASUrl>
              </Protocol>
            </External>
          </Protocol>
        </Account>
      </Response>
    </Autodiscover>
    Unified Messaging role has not been installed on 2010 Exchange Server yet and UM has been uninstalled on 2007 Exchange Server.  The URLs are just left in IIS I'm guessing.
    I have also noticed that this directory has not updated since the 11/12/2013 C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB.  While this directory continues to update C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\OAB

  • Exchange 2010 EWS - app_global.asax-error.

    Im setting up an Exchange Online deployment on a costumers server enviroment. They have a single Exchange 2010 SP3 with Rollup 6 installed.
    The users started complaining that they couldnt set out-of-office messages in Outlook, and that they were prompted for Exchange password in Lync repeatedly.
    Now, im not sure if these errors came because of the Hybrid setup of its a coincidence, but here is what Ive done:
    I started the Hybrid Wizard, but this one got some errors, so it didnt complete on the first run. The error was the following:
    http://support.microsoft.com/kb/2626696
    and I ran
    ServiceModelReg.exe –r
    on the server to fix it. This solved this problem, but a new one occurred with publishing of Autodiscover and EWS online. I called it a day, and was busy the next day so this was left like this for a few days.
    The next day a few users complained that they couldnt set out of office. The next day after that, the lync error occured (there was a reboot that night. Im not sure if thats relevat). The errors in the Hybrid-wizard had then been solved, and the Hybrid-wizard
    ran through, but the EWS-problem remained. 
    Now, on the server I get this error every second or so:
    +
    System
    Provider
    [ Name]
    System.ServiceModel 3.0.0.0
    EventID
    3
    [ Qualifiers]
    49154
    Level
    2
    Task
    5
    Keywords
    0x80000000000000
    TimeCreated
    [ SystemTime]
    2014-09-25T15:36:32.000000000Z
    EventRecordID
    933734
    Channel
    Application
    Computer
    <Server Name>
    Security
    [ UserID]
    S-1-5-18
    EventData
    System.ServiceModel.ServiceHostingEnvironment+HostingManager/20974680
    System.ServiceModel.ServiceActivationException: The service '/EWS/Exchange.asmx' cannot be activated due to an exception during compilation. The exception message is: Could not load file or assembly 'App_global.asax.hid_mutt,
    Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.. ---> System.IO.FileNotFoundException: Could not load file or assembly 'App_global.asax.hid_mutt, Version=0.0.0.0, Culture=neutral,
    PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified. File name: 'App_global.asax.hid_mutt, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase,
    Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark,
    Boolean forIntrospection) at System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) at System.Reflection.Assembly.Load(String assemblyString) 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) WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]
    (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. --- End of inner exception stack trace --- at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String
    normalizedVirtualPath) at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
    w3wp
    4440
    Any ideas is appreciated. 

    Hi,
    I am glad to hear that issue solved by yourself.
    Event 3 indicated that Exchange missed Anonymous authentication on autodiscover/EWS Virtual directories.
    To solve this issue, please enable Anonymous authentication on autodiscover/EWS Virtual directories through IIS manager by the following steps:
    Open IIS manager.
    Navigate to Sites>Default Web Site>Autodiscover.
    Refer to the following picture to choose Authentication, then double-click it. Try to enable Anonymous Authentication.
    Repeat steps 1-3 to enable Anonymous authentication on EWS.
    Best Regards.

  • Exchange 2010 sp2 emc initialization error using "kerberos" authentication failed

    We use exchange 2010 SP2.
    We have 2 management stations, both w2k8 R2 SP1.
    I have one mangement station on which the emc and ems works ok.
    On the other management staiton (which is also in another ad site) the emc and ems don't work.
    I get the following error message : The attempt to connect to
    http://fqdnCasServer/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message : Access is denied. For more information, see the about_Remote_Troubleshooting Help topic.
    I have checked the time on the management station and on the exchange server and this is ok.
    It is not a permissions issue because the user functions ok on the other management station.
    On the bad management station I can open the emc once and after a minute I get an error message and the message access denied. From then on I can't connect any more.
    What am I doing wrong?
    Anyone any tips?
    Thanks,
    JB 

    This is what I get in the eventlog of the bad management station.
    Log Name:      MSExchange Management
    Source:        MSExchange CmdletLogs
    Date:          1/10/2012 11:39:27
    Event ID:      6
    Task Category: (1)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      Server.domain.com
    Description:
    The description for Event ID 6 from source MSExchange CmdletLogs cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
    If the event originated on another computer, the display information had to be saved with the event.
    The following information was included with the event:
    Get-ExchangeServer
    {Identity=Servername}
    Domain/ou/ou/ou/ou/username
    Exchange Management Console-Local
    3080
    22
    00:00:00.3593888
    View Entire Forest: 'True', Configuration Domain Controller: 'FQDN DC', Preferred Global Catalog: 'FQDN DC', Preferred Domain Controllers: '{ FQDN DN }'
    Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'FQDN MGMTSTATION' couldn't be found on 'FQDN DC'.
    Context
    the message resource is present but the message is not found in the string/message table
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="MSExchange CmdletLogs" />
        <EventID Qualifiers="49152">6</EventID>
        <Level>2</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2012-10-01T09:39:27.000000000Z" />
        <EventRecordID>11</EventRecordID>
        <Channel>MSExchange Management</Channel>
        <Computer>FQDN MGMT STATION</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Get-ExchangeServer</Data>
        <Data>{Identity=MGMT STATION}</Data>
        <Data>domain/ou/ou/ou/ou/username</Data>
        <Data>
        </Data>
        <Data>
        </Data>
        <Data>Exchange Management Console-Local</Data>
        <Data>3080</Data>
        <Data>
        </Data>
        <Data>22</Data>
        <Data>00:00:00.3593888</Data>
        <Data>View Entire Forest: 'True', Configuration Domain Controller: 'FQDN DC', Preferred Global Catalog: 'FQDN DC', Preferred Domain Controllers: '{ FQDN DC }'</Data>
        <Data>Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'FQDN MGMT STATION' couldn't be found on 'FQDN DC'.</Data>
        <Data>Context</Data>
        <Data>
        </Data>
      </EventData>
    </Event>

Maybe you are looking for