New Exchange 2013 SP1 install, can't get ECP to display

Hi all,
I stood up a new exchange 2013 environment in my lab running on Server 2012.  Everything looks like it should be working.  All services running, no errors in the event log, I'm able to get into ECS.  When I try and launch the ECP, it spins
for a little bit then I get a page can't be displayed.  I've checked that exchange sees it: 
I'm stumped.  I've been scouring forums and can't pinpoint the issue.  I know I could just blow my lab away and try to re-install from scratch but I'm so close to getting this stood up and don't want to just give up.  Plus, I'm curious as
to what the cause is and how it's tied into Exchange functionality.
Also, when I try to browse to OWA, the page can't be displayed as well.  I've tried to disable Enhanced IE security to no avail.
Any suggestions are appreciated.
Thanks.

Hi,
Please use the https://localhost/ecp URL to logon from the local CAS server and check if you can access EAC.
What's more, I have a test in my environment using Exchange 2013, when I use
https://exc2013cas.contoso.com/ecp to logon EAC, the same error occurs. But when I use
https://exc2013cas/ecp to logon, EAC works well. In your case, I recommend you use the
https://skunkms1/ecp URL to logon EAC and check the result.
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Similar Messages

  • ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!

    Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
    users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
    I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
    As you can see from the error above  ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
    virtual folders?!
    What I’m missing here?! Please help.

    Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
    To check whether inheritance is disabled on the user:
    1.Open Active Directory Users and Computers.
    2.On the menu at the top of the console, click View > Advanced Features.
    3.Locate and right-click the mailbox account in the console, and then click Properties.
    4.Click the Security tab.
    5.Click Advanced.
    6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
    Ref:
    http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
    Also check the Virtual directory authentication
    Microsoft-Server-ActiveSync
     •Basic authentication
     •SSL required
     •Requires 128-bit encryption
    Ref:
    http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
    Check the IIS log if you are able to find any error message on it
    Exchange Queries

  • I just bought the new late 2013 iMac.  Can I get the new iWork for free?

    I just bought a new late 2013 iMac.  Can I get the new iWork for free?  I updated it to Mavericks also.  The Mac App store is showing $19.99 for each iWork component (Pages, Numbers, Keynote).  I also bought the previous iWork version, if that matters.  Free updates for iPhoto and  iMovie seemed to show up with no problems.  Maybe these are just glitches that will clear up in a couple of days?

    Hi.  If you want it to get updated, this should take care of it.
    1. Uninstall iWork from your Mac.
    2. Do a fresh install of iWork from DVD.
    3. Install iWork update from Apple Downloads (direct link here:  http://support.apple.com/kb/DL1563)
    4. Sign into the Mac App Store, and check for updates.  It should now show up as a free update.  You may have to give it a few minutes (i.e. 10-15 minutes).
    I've been a Windows user for years, so I know all of the tricks by now.  I had hoped I would not need this knowledge for a Mac, but oh well...
    Good luck.

  • HTTP 500 ERROR AFTER EXCHANGE 2013 SP1 INSTALL

    Help after exchange 2013 sp1 new install unable to get to the ECP or OWA page with HTTP 500 error in IE the install went ok but not sure what can be causing the error any  help would be appriciated.
    EXCHANGE 2013--SP1 on WIN2K12--R2 Standard
    TY
    M4326

    See the following:
    http://social.technet.microsoft.com/Forums/exchange/en-US/08d3777c-dc03-4411-8c87-7db37d2f406a/exchange-2013-owa-login-error-http-500?forum=exchangesvrclients
    CK

  • Exchange 2013 SP1 cu8 - mssing cmdlet - Get-SendConnector command missing, cannot change smart host port

    Hi Everybody,
    For some reason my Exchange 2013 SP1 cu8 are missing a bunch of cmdlets.
    When i run the exchange powershell and get all the cmdlet command - i noticed all the send and receive connectors are missing.
    This all started when i needed to change the smart host port for a client because their internet provider was blocking port 25.
    So i did the traditional cmdlet
    Get-SendConnector
    Set-SendConnector -Indentity "connector name" -Port 551
    Both commands i get "The term Get-SendConnector is not recognized as the name of a cmdlet, function, etc"
    When i type Get-ExCommand
    Any reference to SendConnector and ReceiveConnector are not on the list.
    Am I missing somethings?  This is a classic example why GUI and cmdlet functions should both be available and not just on cmdlets.
    I went on other Exchange 2013 SP1 cu7 servers to see, and they all have the Send and Receive connectors in the cmdlets.
    The only difference with this particular setup, is that this is the first Exchange 2013 on-premise installation with Windows 2012 r2 Small Business Essentials.  However, i very much doubt the on-premise installation add-on to SBS would cause any issues
    to missing cmdlets.
    I searched all over the internet and found nothing.
    Now my biggest fear is to re-install Exchange and import the mailboxes manually.
    Any help is greatly appreciated.
    MattLok

    Hello
    check role asigment for your user:
    Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "administrator" }
    sorry my english

  • Exchange 2013 SP1 Install on W2K12R2 Pre-requisite fail

    I am tryinig to install SP1 over CU3 for Exchange Server 2013 on Windows Server 2012 R2. During the Readiness Checks - Configuring Prerequisites it gets to 90% and then throws up the following error:
    Error:
    The following error was generated when "$error.Clear();
    $keyPath = "HKLM:\Software\Microsoft\WebManagement\Server";
    if (!(Get-Item $keyPath -ErrorAction SilentlyContinue))
    New-Item $keyPath -Force
    Set-ItemProperty -path $keyPath -name "EnableRemoteManagement" -value 0x1 -Type DWORD -Force;
    if (Get-Service WMSVC* | ?{$_.Name -eq 'WMSVC'})
    Set-Service WMSVC -StartupType Automatic
    Stop-SetupService -ServiceName WMSVC;
    Start-SetupService -ServiceName WMSVC
    " was run: "Service 'WMSVC' failed to reach status 'Running' on this server.".
    I've tried rebooting the Exchange Server, but get the same message.
    Any suggestions would be appreciated.

    Hi,
    See if my answer in the below thread helps.
    http://social.technet.microsoft.com/Forums/exchange/en-US/7f193833-de94-408b-91ad-266d6811a26b/exchange-2013-cu2-to-cu3-upgrade-error?forum=exchangesvrdeploy
    Martina Miskovic

  • Exchange 2013 SP1 Install fails on step 5 of 9: Mailbox Role: Mailbox Service

    We have exchange installed on a windows 2008 R2 box.
    We keep getting the following error when we try to install the update:
    Error:
    The following error was generated when "$error.Clear(); 
              if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
              if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
              $sysMbx = $null;
              $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
              $dispName = "Microsoft Exchange";
              Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
              $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
              if ($mbxs.Length -eq 0)
              Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
              $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
              if ($dbs.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
              $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
              if ($arbUsers.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
              $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
              else
              if ($mbxs[0].DisplayName -ne $dispName )
              Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
              Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
              $sysMbx = $mbxs[0];
              # Set the Organization Capabilities needed for this mailbox
              if ($sysMbx -ne $null)
              # We need 1 GB for uploading large OAB files to the organization mailbox
              Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
              set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
              else
              Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
              else
              Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox.".
    Error:
    The following error was generated when "$error.Clear(); 
              if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
              if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
              $sysMbx = $null;
              $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
              $dispName = "Microsoft Exchange";
              Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
              $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
              if ($mbxs.Length -eq 0)
              Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
              $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
              if ($dbs.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
              $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
              if ($arbUsers.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
              $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
              else
              if ($mbxs[0].DisplayName -ne $dispName )
              Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
              Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
              $sysMbx = $mbxs[0];
              # Set the Organization Capabilities needed for this mailbox
              if ($sysMbx -ne $null)
              # We need 1 GB for uploading large OAB files to the organization mailbox
              Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
              set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
              else
              Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
              else
              Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            " was run: "Database is mandatory on UserMailbox.".
    Any help would be greatly appreciated!
    Thanks, 
    Wes

    Hello,
    Please make sure you do exchange server upgrading or a clean exchange 2013 installation. If you do a upgrading, please refer to the similar thread to assign a database to the arbitration mailbox "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}".
    http://social.technet.microsoft.com/Forums/en-US/239cb4a6-4a07-4b9a-800c-974573bbff32/error-installing-step-12-mailbox-role-service-on-exchange-2013-cu2?forum=exchangesvrdeploy
    Please make sure you have these permission "Schema Admins, Domain Admins and Enterprise Admins" to install exchange 2013 server.
    If this is a clean exchange 2013 installation, please try to recreate the system mailbox to check the result.
    Cara Chen
    TechNet Community Support

  • I have new iMac with Lion installed; can I get a free upgrade for my MacBook Pro?

    Hello
    I recently bought a 27" iMac with Lion installed.  Should I be able to download the upgrade for my MacBook Pro without paying.  If so what should I do.  If I go to the App Store I'll end up paying £20.99
    Any help gratefully received
    margaret

    Margaret,
    No you will need to purchase the upgrade. However if you own other Macs you want to upgrade once you have purchased Lion then you can upgrade the additional machines. Of course the additional machines must be using the same Apple ID. As long as the additional machine's meet the minimum system requirements listed below you are all set.
    General requirements
    Mac computer with an Intel Core 2 Duo, Core i3, Core i5, Core i7, or Xeon processor
    2GB of memory
    OS X v10.6.6 or later (v10.6.8 recommended)
    7GB of available space
    Some features require an Apple ID; terms apply.

  • Exchange 2013 SP1 database missing?? New install of Exchange 2007 co-exist

    Hi all,
    Finally got Exchange 2013 SP1 installed except I am not so sure I have a database. This is installed on a Server 2008 system and is co-existing with Exchange 2007.
     When I go to SERVERS and DATABASES I don't have anything listed. When I click SERVERS on the left hand pane and SERVERS at the top I see both servers, 2007 and 2013. But when I double click my new Exchange Server 2013 name I get the error:
    The operation couldn't be performed because object '*\ExchangeServerName' couldn't be found on 'FirstDCName.mydomain.com'
    Why would I get this error? The install itself was problematic so I am concerned something is broke.
    Thank you in advance.

    Hello,
    Firstly, I recommend you check if the server name "*\ExchangeServerName" exists on DC via ADUC (select Computers).
    Secondly, please run the get-exchangeserver | fl name cmdlet to check your exchange server name.
    And then please check the exchange setup log to check if the exchange 2013 server is installed successfully. If not, please check if there is any error in setup log.
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • What happend New-MailboxExportRequest cmdlet in exchange 2013 SP1 is missing?

    Cmdlet New-MailboxExportRequest is not recognize cmdlet in Exchange 2013 SP1
    How can i do export mailbox to pst file in exchange 2013 SP1?

    You might be facing this issue because of not having the rights to execute the New-MailboxExportRequest CMDLET.
    Follow the steps given below in order to export the mailboxes into PST file
    1. Open the Exchange Console and run:
    New-ManagementRoleAssignment -Name "Import Export PST" -SecurityGroup "Organization Management" -Role “Mailbox Import Export"
    This will generate a new role group called Import Export PST to the Oranization Management group with the role Mailbox Import Export.
    You should Close and Restart the Exchange Management System again so that the changes made will get reflected in the settings, otherwise you will still get the same erroriIf not
    restarted. Now move to the next steps.
    2. Assign “Mailbox Import Export” role to it.
    3.  Add Desired Users to Role Group
    4.  Create Network Share ( Exchange Trusted Subsystem group has read/write permission to NTFS Permissions)
    5. Run PS New-MailboxExportRequest
    6. Monitor New-MailboxExportRequest
    Verify PST File has been created on the network Share and you are done.
    If you get the same error again, then there will be some hardware or software issues due to which you are not able to export mailboxes into PST files. In that case, you can make
    use of any third party tool like Stellar Phoenix EDB To PST converter, which will help you to export your exchange database files to PST files easily and quickly. You can try this software by downloading its demo directly from their site http://www.stellarinfo.com/email-repair/edb-pst-converter.php

  • Exchange 2013 SP1 Readiness Checks: No Exchange 2007 server detected

    Hi there,
    We are planning to upgrade our current Exchange 2007 server with the new Exchange 2013 SP1. I have been following Exchange Server Deployment Assistant to assist me with this task. Only schema update (setup /PrepareSchema) had been done so
    far. I didn’t run setup /PrepareAD command manually because I wasn’t sure if I need to provide ‘Organisation Name’ with it or not?! I have installed all of the prerequisites as noted in the Microsoft documentation.
    Now, I am a bit confuse with the ‘Readiness Checks’ page during graphical user installation of Exchange 2013 SP1 setup on Windows 2012 R2. Windows 2012 R2 server has all available updates applied.
    ===
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    ===
    I get the message why setup wants to run preparation for the Ex2013 with the ‘Setup /PrepareAD’. But, why ‘No Exchange 2010 server role have been detected in this topology’?! Ok, in my case setup doesn’t detect Exchange 2007 server. Is that ok to proceed
    with the installation or something else needs to be done first?
    Thanks in advance.

    I need Exchange guru advice here please. Since we already have Exchange 2007 SP3 RU 10 in our Windows 2008R2 Active Directory domain here I need to be 100% confident that pushing Exchange 2013 SP1 “Install” will not override our existing Ex2007 environment.
    That would be a huge disaster!
    Microsoft is saying that: “Microsoft Exchange Server 2013 Setup displayed this warning because
    no Exchange Server 2010 or Exchange Server 2007 server roles exist in the organization.”
    http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx
    Ok, I get the message about if I continue with Exchange Server 2013 installation, I won’t be able to add Exchange 2010 or Exchange 2007 servers to the organization at a future date..., and why would I need to do that anyway?!
    Microsoft wording about “some solutions may require the use...” are very confusing since we will require to consider “Coexistence or migration requirements"
    Perhaps, before running Exchange 2013 SP1 setup I need to run setup for preparing AD without “Organisation Name” parameter?! Something like this:
    setup /PrepareAD  /IAcceptExchangeServerLicenseTerms

  • New Exchange 2013 CAS server in existing Exchange 2007 Organization

    Dear Friends,
    We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
    R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
    Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
    https://servername/ecp/?ExchClientVer=15
    Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
    Thanks in advance!!

    Dear Friends,
    We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
    R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
    Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
    https://servername/ecp/?ExchClientVer=15
    Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
    Thanks in advance!!
    If you have only the 2013 CAS installed and not the mailbox role, then nothing will really work. Remember, in 2013, the mailbox role does all the work, the CAS is simply a proxy for the most part.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 SP1 RPC 404 Error Page Not Found

    Anyone got any ideas why on my Exchange 2013 SP1 server I am getting a 404 error when trying to access the RPC URL?
    I had a look in the CAS RPC logs and see the following HTTP POST events:
    <snip>
    2014-06-19T15:33:00.558Z,EX-CAS1,RpcHttp,"S:Stage=BeginRequest;S:OutlookSessionId=""{17FD197A-098A-4339-82E9-A480F6DD70F7}"";S:AuthType=Basic;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?pdc.internal.local:6004;S:RequestId=0acc9487-bf8f-4600-ae04-edf2ef00a90b;S:ClientIp=192.168.0.17"
    2014-06-19T15:33:00.558Z,EX-CAS1,RpcHttp,"S:Stage=PostAuthorizeRequest;S:UserName=INTERNAL\SVC_BMA;S:OutlookSessionId=""{17FD197A-098A-4339-82E9-A480F6DD70F7}"";S:AuthType=Basic;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?pdc.internal.local:6004;S:RequestId=0acc9487-bf8f-4600-ae04-edf2ef00a90b;S:ClientIp=192.168.0.17"
    2014-06-19T15:33:00.574Z,EX-CAS1,RpcHttp,"S:Stage=EndRequest;S:UserName=INTERNAL\SVC_BMA;S:OutlookSessionId=""{17FD197A-098A-4339-82E9-A480F6DD70F7}"";S:AuthType=Basic;S:Status=404 Not Found;S:HttpVerb=RPC_IN_DATA;S:UriQueryString=?pdc.internal.local:6004;S:RequestId=0acc9487-bf8f-4600-ae04-edf2ef00a90b;S:ClientIp=192.168.0.17"
    </snip>
    This works fine in Exchange 2010 SP3 so I am wondering if maybe Microsoft have removed the /rpc url functionality in Exchange 2013 SP1?

    Hi JRA,
    Is it possible to provide more info for your issue?
    You receive as you said HTTP 404 error, can you provide the specific HTTP 404 error message?
    For example:
    HTTP/1.0 404 File Not Found
    HTTP/1.0 404 Not Found
    HTTP/1.0 404 Object Not Found
    HTTP/1.0 404 Page Cannot Be Found
    The page cannot be found. The page you are looking for might have been removed, had its name changed, or is temporarily unavailable
     Also a screenshot will be very helpful
    Regards,
    CF

  • Seemingly successful install of Exchange 2013 SP1 turns into many errors in event logs after upgrade to CU7

    I have a new Exchange 2013 server with plans to migrate from my current Exchange 2007 Server. 
    I installed Exchange 2013 SP1 and the only errors I saw in the event log seemed to be long standing known issues that did not indicate an actual problem (based on what I read online). 
    I updated to CU7 and now lots of errors have appeared (although the old ones seem to have been fixed so I have that going for me). 
    Currently the Exchange 2013 server is not in use and clients are still hitting the 2007 server.
    Issue 1)
    After each reboot I get a Kernel-EventTracing 2 error.  I cannot find anything on this on the internet so I have no idea what it is.
    Session "FastDocTracingSession" failed to start with the following error: 0xC0000035
    I did read other accounts of this error with a different name in the quotes but still can’t tell what this is or where it is coming from.
    Issue 2)
    I am still getting 5 MSExchange Common 106 errors even after reregistering all of the perf counters per this page:
    https://support.microsoft.com/kb/2870416?wa=wsignin1.0
    One of the perf counters fails to register using the script from the link above.
    66 C:\Program Files\Microsoft\Exchange Server\V15\Setup\Perf\InfoWorkerMultiMailboxSearchPerformanceCounters.xml
    New-PerfCounters : The performance counter definition file is invalid.
    At C:\Users\administrator.<my domain>\Downloads\script\ReloadPerfCounters.ps1:19 char:4
    +    New-PerfCounters -DefinitionFileName $f
    +    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo         
    : InvalidData: (:) [New-PerfCounters], TaskException
        + FullyQualifiedErrorId : [Server=VALIS,RequestId=71b6bcde-d73e-4c14-9a32-03f06e3b2607,TimeStamp=12/18/2014 10:09:
       12 PM] [FailureCategory=Cmdlet-TaskException] 33EBD286,Microsoft.Exchange.Management.Tasks.NewPerfCounters
    But that one seems unrelated to the ones that still throw errors. 
    Three of the remaining five errors are (the forum is removing my spacing between the error text so it looks like a wall of text - sorry):
    Performance counter updating error. Counter name is Count Matched LowFidelity FingerPrint, but missed HighFidelity FingerPrint, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The
    exception thrown is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Performance counter updating error. Counter name is Number of items, item is matched with finger printing cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown
    is : System.InvalidOperationException: The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Performance counter updating error. Counter name is Number of items in Malware Fingerprint cache, category name is MSExchange Anti-Malware Datacenter Perfcounters. Optional code: 3. Exception: The exception thrown is : System.InvalidOperationException:
    The requested Performance Counter is not a custom counter, it has to be initialized as ReadOnly.
       at System.Diagnostics.PerformanceCounter.InitializeImpl()
       at System.Diagnostics.PerformanceCounter.set_RawValue(Int64 value)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.set_RawValue(Int64 value)
    Last worker process info : System.ArgumentException: Process with an Id of 7384 is not running.
       at System.Diagnostics.Process.GetProcessById(Int32 processId)
       at Microsoft.Exchange.Diagnostics.ExPerformanceCounter.GetLastWorkerProcessInfo()
    Issue 3)
    I appear to have some issues related to the healthmailboxes. 
    I get MSExchangeTransport 1025 errors for multiple healthmailboxes.
    SMTP rejected a (P1) mail from 'HealthMailbox23b10b91745648819139ee691dc97eb6@<my domain>.local' with 'Client Proxy <my server>' connector and the user authenticated as 'HealthMailbox23b10b91745648819139ee691dc97eb6'. The Active Directory
    lookup for the sender address returned validation errors. Microsoft.Exchange.Data.ProviderError
    I reran setup /prepareAD to try and remedy this but I am still getting some.
    Issue 4)
    I am getting an MSExchange RBAC 74 error. 
    (Process w3wp.exe, PID 984) Connection leak detected for key <my domain>.local/Admins/Administrator in Microsoft.Exchange.Configuration.Authorization.WSManBudgetManager class. Leaked Value 1.
    Issue 5)
    I am getting MSExchange Assistants 9042 warnings on both databases.
    Service MSExchangeMailboxAssistants. Probe Time Based Assistant for database Database02 (c83dbd91-7cc4-4412-912e-1b87ca6eb0ab) is exiting a work cycle. No mailboxes were successfully processed. 2 mailboxes were skipped due to errors. 0 mailboxes were
    skipped due to failure to open a store session. 0 mailboxes were retried. There are 0 mailboxes in this database remaining to be processed.
    Some research suggested this may be related to deleted mailboxes however I have never had any actual user mailboxes on this server. 
    If they are healthmailboxes or arbitration mailboxes that might make sense but I am unsure of what to do on this.
    Issue 6)
    At boot I am getting an MSExchange ActiveSync warning 1033
    The setting SupportedIPMTypes in the Web.Config file was missing. 
    Using default value of System.Collections.Generic.List`1[System.String].
    I don't know why but this forum is removing some of my spacing that would make parts of this easier to read.

    Hi Eric
    Yes I have uninstalled and reinstalled Exchange 2013 CU7 for the 3<sup>rd</sup> time. 
    I realize you said one issue per forum thread but since I already started this thread with many issues I will at least post what I have discovered on them in case someone finds their way here from a web search.
    I have an existing Exchange 2007 server in the environment so I am unable to create email address policies that are defined by “recipient container”. 
    If I try and do so I get “You can't specify the recipient container because legacy servers are detected.”
     So I cannot create a normal email address policy and restrict it to an OU without resorting to some fancy filtering. 
    Instead what I have done is use PS to modify extensionAttribute1 (otherwise known as Custom Attribute 1 to exchange) for all of my users. 
    I then applied an address policy to them and gave it the highest priority. 
    Then I set a default email address policy for the entire organization. 
    After reinstalling Exchange all of my system mailboxes were created with the internal domain name. 
    So issue number 3 above has not come up. 
    For issue number one above I have created a new thread:
    https://social.technet.microsoft.com/Forums/office/en-US/7eb12b89-ae9b-46b2-bd34-e50cd52a4c15/microsoftwindowskerneleventtracing-error-2-happens-twice-at-boot-ex2013cu7?forum=exchangesvrdeploy
    For issue number four I have posted to this existing thread where there is so far no resolution:
    https://social.technet.microsoft.com/Forums/exchange/en-US/2343730c-7303-4067-ae1a-b106cffc3583/exchange-error-id-74-connection-leak-detected-for-key?forum=exchangesvradmin
    Issue number Five I have managed to recreate and get rid of in more than one way. 
    If I create a new database in ECP and set the database and log paths where I want, then this error will appear. 
    If I create the database in the default location and then use EMS to move it and set the log path, then the error will not appear. 
    The error will also appear (along with other errors) if I delete the health mailboxes and let them get recreated by restarting the server or the Health Manager service. 
    If I then go and set the retention period for deleted mailboxes to 0 days and wait a little while, these will all go away. 
    So my off hand guess is that these are caused by orphaned system mailboxes.
    For issue number six I have posted to this existing thread where there is so far no resolution:
    https://social.technet.microsoft.com/Forums/exchange/en-US/dff62411-fad8-4d0c-9bdb-037374644845/event-1033-msexchangeactivesync-warning?forum=exchangesvrmobility
    So for the remainder of this thread we can try and tackle issue number two which is the perf counters. 
    The exact same 5 perf counter were coming up and this had been true each time I have uninstalled and reinstalled Exchange 2013CU7. 
    Actually to be more accurate a LOT of perf counter errors come up after the initial install, but reloading the perf counters using the script I posted above reduces it to the same five. 
    Using all of your suggestions so far has not removed these 5 remaining errors either.  Since there is no discernible impact other than these errors at boot I am not seriously bothered by them but as will all event log errors, I would prefer
    to make them go away if possible.

  • Outlook 2013 can't connect to Exchange 2013 SP1

    Hello,
    I've already asked that question on Exchange 2013, now I'd like to ask it again in regard to Exchange 2013 SP1.
    The question i s very easy: suppose I have just installed Exchange 2013 SP1 (in a Win2012 R2 domain)  with three mailboxes (user1, user2, user3). I can successfully run ecp and owa for all users...
    ...but when I'm starting Outlook 2013 and trying to set up a profile manually, for example, [email protected], Exchange 2013 Sp1 keeps saying "Outlook can't log on...The name cannot be resolved."
    In Exchange 2013 this could be fixed by adding the server's ip address to its Hosts file, but I thought it was a bug and it would be corrected later or sooner... Now the same problem with Exchange 2013SP1...
    Would anybody please tell me is there anything special I must do to connect to Exchange 2013SP1 via Outlook 2013 (not Outlook 2013SP1 - without MAPI over HTTP)??? If yes what articles can I read about it?
    Thank you in advance,
    Michael

    Hi,
    When we automatically configure the account, Autodiscover service will help Outlook find the new type and we don't need to run the command to get the mailbox GUID until we manually configure the profile.
    For more information, you can refer to the following article:
    http://technet.microsoft.com/en-us/library/bb124251(v=exchg.150).aspx
    "Through the Autodiscover service, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address."
    Thanks,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Angela Shi
    TechNet Community Support

Maybe you are looking for