Exchange 2013 IMAP Connectivity Failing

I have gone through all of the troubleshooting i can find, and can't get IMAP connectivity to work to my Exchange 2013 server.  I have an application that uses IMAP to connect to a mailbox to create and update help tickets.
I get the following in the log:
2014-04-03T14:03:25.783Z,00000000000000C7,0,10.10.50.55:993,10.10.50.18:56287,,18,0,53,OpenSession,,
2014-04-03T14:03:25.798Z,00000000000000C8,0,10.10.50.55:993,10.10.50.18:56288,,14,0,53,OpenSession,,
2014-04-03T14:03:26.079Z,00000000000000C8,1,10.10.50.55:993,10.10.50.18:56288,,1,27,125,capability,,R=ok
2014-04-03T14:03:26.236Z,00000000000000C8,2,10.10.50.55:993,10.10.50.18:56288,imaptest,95,37,35,login,imaptest *****,"R=""1274136704c94dce NO LOGIN failed."";Msg=User:imaptest:0a2fa0f8-47d9-4ad0-b6a5-8c4853d301d9:SCS_EX2013DB:SCS-VM-EX2013.*****.com;Proxy:SCS-VM-EX2013.****.com:9933:SSL;ProxyNotAuthenticated"
I have tried a few different users, and get the same error with each.
Any ideas??

Hi,
To understand more about the issue, I’d like to confirm the following information:
The detail error message when you login your account in IMAP mode.
The result when you use telnet to check the IMAP connectivity:
http://support.microsoft.com/kb/189326/en-us
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Similar Messages

  • Exchange 2013 - The connection to Microsoft Exchange is unavailable

    Hi there,
    i have some problems on my new Exchange 2013 Server: Here is the topology:
    1 serveur 2012 in workgroup with the Hyper-V role
    2 VM: DC2012 is the DC of the domain: intra.mydomain.com, Windows 2012
    The other VM is member of the domaine, Windows 2012, Exchange 2013 SP 1 installed.
    So, i have dc2012.intra.mydomain.com and mail1.intra.mydomain.com (another DC: DC2008, name: dc2008.intra.mydomain.com)
    I have some troubles with the SSL and the connexion of Outlook outside the LAN.
    In the LAN on a client, i launch Outlook 2010 and the autodiscver make the rest. The connexion is ok.
    But i have a client not in the LAN, so i configured a SSL. I made a request. First Question:
    In the ECP, Server, Certificate, i have 3 times "Microsoft Exchange Server Auth Certificate" and 3 times "Microsoft Exchange" with differents dates. Why?
    I installed my PKI on the DC2012, and paste the request and download the certificate. I retuned on the exchange server in ECP, Server, Certificate and treat the pending request. In Services i checked IMAP, POP, IIS, SMTP.
    Then, in Server, Server, Mail1, OutlookAnywhere, in url extternal: mail.mydomain.com and Authentification: NTLM.
    In ECP, Servers, Virtual Directories i wrote the same url external and internal: mail.mydomain.com for ECP, OWA, ActiveSync, OAB.
    In my DNS on the DC, i created a CNAME record for mydomain.com et i created a A record for mail. on a client if i make nslookup then mail.mydomain.com the IP is the LAN IP of my exchange server.
    I modified the MX record of my public domain: mail.mydomain.com to point on my Public IP. That works.
    On the client outside of the LAN, i installed the root certificate and the exchange certificate.
    second question:
    Why my client outside of the LAN can't connext with outlook.
    Thanks a lot for your answers and sorry for the long post.
    Alex

    I resolved my problem!
    here is the solution that solved it:
    actually, i tried to connect Outlook 2010 ti Exchange 2013. I knew that Exchange now connect Outllok via rpc over http(s), BUT, the Autodiscover (in LAN) transform the field server to something like that:
    [email protected] , the xxx correspond to the GUID of the mailbox. So, for my remote user, i launch this command on Exchange 2013:
    Get-Mailbox test | fl name, exchangeguid , it give to me the GUID, then in te field "Server" i fill ([email protected]): [email protected]
    And in advanced parameters, same things i mentioned in previous post. And it works!!!!!
    Thanks to me.

  • Exchange 2013 cu3 setup fails with 'problem... validating the state of Active Directory... supplied credential... invalid'

    Windows Server 2013; Exchange Server 2013 with Cumulative Update 1
    Cannot install Cumulative Update 3 for Exchange Server 2013. It fails with
    [xxx] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.  See the Exchange setup log for more information on this error.
    [xxx] [0] [ERROR] Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid.
    [xxx] [0] [ERROR] The supplied credential is invalid.
    (Crosses - XXX - replace original values.)
    I have found that a few others have experienced the same problem but found no solution, nor could come up with anything myself. If it is any hint, Event 40961 was logged in the Event Viewer around the same time on almost all installation attempts to be purely
    conincidental:
    The Security System could not establish a secured connection with the server
    ldap/xxx.xxx/[email protected] No authentication protocol was available.
    Both Windows Server and Exchange Server otherwise work OK, and do not recall any issues with Cumlative Update 1 installation.

    Hi vhr1,
    Based on my knowledge, the Event ID 40961 is a warning message.
    This behavior occurs when we restart the server that was promoted to a DC. The Windows Time service tries to authenticate before Directory Services has started.
    Found some resources for your reference even if the Exchange Version is mismatched:
    http://blogs.technet.com/b/jhoward/archive/2005/04/20/403946.aspx
    http://support.microsoft.com/kb/823712/en-us
    About the error message, "Setup encountered a problem while validating the state of Active Directory: Active Directory operation failed on . The supplied credential for 'XXX\Xxx' is invalid."
    The error message InvalidCredentials means: the wrong password was supplied or the SASL credentials cannot be processed.
    Found a similar thread for your reference, hope it is helpful:
    http://social.technet.microsoft.com/Forums/en-US/98e26ad6-8e43-4ef5-8ff9-e9fee6e76bda/bind-operation-is-invalid?forum=exchangesvrdeploylegacy
    Feel free to contact me if there is any problem.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 Domain Prep Fails: Setup /prepareschema, setup /PrepareAD, Setup /PrepareDomain

    Whenever I try to prep for a 2013 exchange install I always get:
    "earlier versions of the server roles that are installed were detected"
    whenever I try to run Setup /prepareschema OR setup /PrepareAD OR Setup /PrepareDomain
    I am working on a Server 2012 standard machine with Exchange 2010 currently installed. This server is a DC (bad I know), DNS, DHCP.
    I am trying to prep the domain so that I can install Exchange 2013 on a VM and eventually remove Exchange 2010 from the organization altogether.
    There are no other domain controlelrs in the domain. The domain started life as a SBS 2003 machine which was demoted and removed once the server 2012 box was up with exchange 2010 running.
    Any help would be greatly appreciated.
    Here is some info that may help:
    1. PrePare Schema
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    Ran setup /PrepareSchema
    This command should perform the following tasks:
    A: Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with 
    Exchange 2013 specific attributes. The LDIF files are copied to the Temp directory and then deleted after they are imported 
    into the schema.
    B: Sets the schema version (ms-Exch-Schema-Verision-Pt) to a Exchange 2013 value.
    This command fails with: Earlier versions of server roles that were installed were detected.
    First I confirmed that administrator account for domain is a member of schema admins and enterprise admins.
    Next I ran asdiedit.
    I navigated to: "CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=BDA,DC=LAN"
    and reviewed the current "rangeUpper" attribute.
    The ms-Exch-Schema-Verision-Pt is not updated to CU3 range Upper setting.
    The current range upper 14734 which means its still at Exchange 2010 SP3 settings. 
    In short, updaing the schema fails.
    2. Prepare Active Directory
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    setup /PrepareAD [/OrganizationName:<organization name>]
    This command fails with: Earlier versions of server roles that were installed were detected.
    schema update version 56
    I began reviewing the long, long list of the following containers and objects under
     CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
    which are required for Exchange 2013:
    missing cn=Auth Configuration
    missing CN=ExchangeAssistance
    missing CN=Monitoring Settings
    missing CN=Monitoring Settings
    missing CN=Monitoring Settings
    missing CN=Workload Management Settings
    Checked Management role groups within the Microsoft Exchange Security Groups OU
    missing Compliance Management group  --- Manually created this entry
    Step 3 Prepare Domain:
    Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
    Ran setup /PrepareDomain
    This command fails with: Earlier versions of server roles that were installed were detected.
    confirmed the following:
    ObjectVersion property fails as it is still set to Echange 2010 sp3 -  13040
    You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers-DONE
    The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.-DONE
    On each domain controller in a domain in which you will install Exchange 2013, the Exchange Servers USG has permissions 
    on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.-DONE
    Thanks.

    Whenever I try to prep for a 2013 exchange install I always get:
    "earlier versions of the server roles that are installed were detected"
    Hi,
    That tells us that you are trying to run the prep on your combined DC and Exchange 2010 Server - That will not work. Run it on the Server where you plan to install Exchange 2013.
    It is not mandatory to run this before the actuall Exchange install - It will run automatically for you, if it hasn't been done already and if you are logged on with an account with the proper permissions.
    Martina Miskovic

  • Outlook 2013 IMAP connecting to Cisco Unity Voicemail

    The ability to use IMAP in our Outlook 2013 stopped working back in November updates, we worked with MS Support for the other Outlook issues that were broken thinking that whatever fix would also resolve the IMAP issue. This was not the case.
    Our voicemail is hosted on a Cisco Unity Server by our provider that we connect to using IMAP. Initially I was unable to connect to their server using IMAP because the November update sent their server to 100% CPU. After a Cisco patch I'm now able to
    connect, however functionality is still not there.
    Outlook 2010 clients seem to work fine. Outlook 2013 clients will sync the inbox the first time connecting but never after that, you are also unable to delete messages from the reading pane (able to open message and delete).
    I'm aware of the root folder "Inbox" and the subscribe methods for troubleshooting this, however neither work.
    Does anyone have any suggestions on where to go from here?
    Thanks much

    So what eventually solved this was Office SP 1.
    Below is a set of packet captures with Outlook 2013 interacting with a Unity server both before and after the SP was installed.
    OUTLOOK 2103 WITH SP1 – WIIN 8 shows:
    Packet 223: UID FETCH 177:4294967295 (UID FLAGS RFC822.SIZE BODY.PEEK[] INTERNALDATE)
    Follow TCP Stream shows CUC handles this request fine:
    x9tf UID FETCH 177:4294967295 (UID FLAGS RFC822.SIZE BODY.PEEK[] INTERNALDATE)
    * 44 FETCH (UID 177 FLAGS (\Recent) RFC822.SIZE 43627 BODY[] {43627}
    Date: Wed, 26 Feb 2014 16:46:47 +0000
    From: "Spare Phone4" <5555555555@XXXdomain>
    To: 4444444444@domain
    MIME-Version: 1.0
    Message-Id: <MAL.1dfcffe1-aef3-4ba4-b4eb-3d728835f4a0@domain>
    X-CiscoUnity-CallerAni: 810168950
    Importance: Normal
    X-Priority: 3
    Sensitivity: None
    Subject: Message from Spare Phone4 (5555555555)
    X-CiscoUnity-MessageType: Voice
    Content-Type: audio/wav; name=VoiceMessage.wav
    Content-Dis; filename=VoiceMessage.wav; voice=Voice-Message
    CUC seems to handle this ok
    Packet 708: UID SEARCH UID 178:4294967295 SINCE 24-Feb-2014
    Follow TCP Stream shows that CUC returns “invalid arg”.  However, IMAP then  performs “Fetch” request afterwards, which ultimately works
    i6kl UID SEARCH UID 178:4294967295 SINCE 24-Feb-2014
    i6kl BAD Invalid Argument
    kkl1 IDLE
    + idling
    DONE
    kkl1 OK IDLE Completed
    y2mw UID FETCH 1:177 (UID FLAGS)
    * 1 FETCH (UID 121 FLAGS (\Seen))
    * 2 FETCH (UID 122 FLAGS (\Seen))
    * 43 FETCH (UID 174 FLAGS (\Seen))
    * 44 FETCH (UID 177 FLAGS (\Seen))
    y2mw OK FETCH Completed
    BROKEN IMAP shows: (non-SP1)
    Packet 32: UID SEARCH UID 155:4294967295 SINCE 17-Feb-2014
    Follow TCP Stream shows that CUC returns invalid arg and then IMAP sends LOGOUT request.
    my5r UID SEARCH UID 155:4294967295 SINCE 17-Feb-2014
    my5r BAD Invalid Argument
    jveg IDLE
    + idling
    * 32 EXISTS
    * 3 RECENT
    DONE
    jveg OK IDLE Completed
    3l5q LOGOUT
    * BYE UMSS IMAP4rev1 Server logging out
    3l5q OK LOGOUT Completed
    So the connectivity is work and the Outlook client now maintains functionality. The last thing I've noticed is that if you try to delete a message from either the view/reading pane or the home ribbon from Win 8/8.1 Outlook 2013/2013 SP1 it fails, you need
    to go open the message to delete it.
    On a Win7 machine Outlook 2013 you experienced the same thing, however after the SP1 is applied all deletion options work.
    When you press the any delete key it seems the client is suppose to send an expunge command (noticed through wireshark). With the delete keys that do not function this command is not sent, those that do work the command is seen with wireshark.

  • Exchange 2013 ECP Login fails HTTP 404 Requested URL: /owa/auth/logon.aspx

    Hi,
    One of our Exchange servers stopped allowing access to OWA and ECP. I have now managed to get OWA working but ECP is still failing. When connecting to ECP using https://servername/ecp/ it asks me for my username and password. After hitting enter it shows
    me an error page:
    Server Error in '/owa' Application.
    The resource cannot be found.
    Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.
    Requested URL: /owa/auth/logon.aspx
    URL in the address bar while on this screen: https://exchangeserver:444/owa/auth/logon.aspx?url=https://exchangeservera:444/ecp/&reason=0
    Question: When the URL points to servername:444/owa/auth/logon.aspx - Is it trying to find the logon.aspx in C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\Owa\auth? There is no such file in that directory?
    I have removed and recreated the ECP and OWA virtual directories several times.
    I am trying to login using a domain administrator account.
    Thanks,

    Hi,
    Is there any Exchange server 2010 coexistence with your Exchange 2013 server? If it is, please try the URL
    https://CAS15-NA/ecp?ExchClientVer=15 to access ECP.
    Also run the following to check your OWA and ECP virtual directories:
    Get-EcpVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
    Get-OwaVirtualDirectory -ShowMailboxVirtualDirectories | FL Identity,*Authentication*
    And make sure the Basic and Forms authentications are enabled in
    Default Web Site and Ntlm, WindowsIntegrated
    authentication methods are enabled in
    Exchange Back End. Then restart IIS service by running
    iisreset /noforce from a command prompt window.
    If the issue persists, please collect any event logs or IIS logs for further analysis.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 Co-Existence Fail

    I went ahead, installed new 2 multi-role exchange 2013 servers.  Followed the exchange deploy assist.  setup external urls, updated exchange 2010 outlook-anywhere, bla bla, changed dns to proxy through my 2013 servers.  All services were fine,
    except outlook clients with mailboxes still on 2010.
    http://blogs.technet.com/b/exchange/archive/2013/05/23/ambiguous-urls-and-their-effect-on-exchange-2010-to-exchange-2013-migrations.aspx
    I found and read this article and it seems to describe my problem.  Pretty ticked that the deployment assist didn't say anything about it.
    None of my external outlook anywhere clients can connet anymore.  I have pretty much reversed as much as possible and 'removed' exchange 2013 out of the mix, my fqdn points back to my Exchange 2010 again, but still external OA cannot connect.
    CAS config;
    ServerName                         : CAS1
    SSLOffloading                      : True
    ExternalHostname                   : webmail.domain.com
    InternalHostname                   :
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm}
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : False
    AdminDisplayVersion                : Version 14.3 (Build 123.4)
    ExchangeVersion                    : 0.10 (14.0.100.0)
    Name                               : Rpc (Default Web Site)
    ServerName                         : CAS2
    SSLOffloading                      : True
    ExternalHostname                   : webmail.domain.com
    InternalHostname                   :
    ExternalClientAuthenticationMethod : Basic
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods           : {Basic, Ntlm}
    ExternalClientsRequireSsl          : True
    InternalClientsRequireSsl          : False
    AdminDisplayVersion                : Version 14.3 (Build 123.4)
    ExchangeVersion                    : 0.10 (14.0.100.0)
    Name                               : Rpc (Default Web Site)
    I use a single url for ALL protocols/services including outlookanywhere.  All databases have rpc url set.. Any clues?
    Andrew Huddleston | Hillsong Church | Sydney

    My Outlook-Anywhere settings, with names changed.  I have the same external hostname for rpc endpoint and exchange 2010 cas array.  Exchange 2010 mailbox are proxying through the 2013 seemingly fine, no problems. 
    Identity                           : EX15SVR1\Rpc (Default Web Site)
    ExternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Basic
    ExternalClientsRequireSsl          : True
    InternalHostname                   : webmail.domain.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    SSLOffloading                      : True
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    Identity                           : EX15SVR2\Rpc (Default Web Site)
    ExternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Basic
    ExternalClientsRequireSsl          : True
    InternalHostname                   : webmail.domain.com
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    SSLOffloading                      : True
    IISAuthenticationMethods           : {Basic, Ntlm, Negotiate}
    Identity                           : EX10SVR1\Rpc (Default Web Site)
    ExternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Basic
    ExternalClientsRequireSsl          : True
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    SSLOffloading                      : True
    IISAuthenticationMethods           : {Basic, Ntlm}
    Identity                           : EX10SVR2\Rpc (Default Web Site)
    ExternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Basic
    ExternalClientsRequireSsl          : True
    InternalHostname                   :
    InternalClientAuthenticationMethod : Ntlm
    InternalClientsRequireSsl          : False
    SSLOffloading                      : True
    IISAuthenticationMethods           : {Basic, Ntlm}
    My problem is with 2013 mailboxes that have migrated.  I have a 2013 mailbox but it cannot connect, why I do not know.  its mailbox is in a 2013 database on a 2013 mailbox server using outlook 2013.  I have removed profile, readded (autodiscover
    works perfectly), but cannot connect.
    EXRCA fails with
    Attempting to ping RPC endpoint 6001 (Exchange Information Store) on server
    [email protected].
    The attempt to ping the endpoint failed.
     <label for="testSelectWizard_ctl12_ctl06_ctl09_tmmArrow">Tell
    me more about this issue and how to resolve it</label>
    Additional Details
    The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
    Elapsed Time: 4314 ms.
    Andrew Huddleston | Hillsong Church | Sydney

  • Exchange2010 migration to Exchange 2013 federation trust failed (Outlook Provider Failure)

    We are in a migration Exchange 2010 to Exchange 2013.
    On the 'old' Exchange 2010 we are using a Federation Trust to 2 order company's. The federation trust for mailbox's on the exchange 2013 wont work.
    We removed the federation trust on the old exchange 2010 server and create a new federation trust on the new Exchange 2013 server. We also changes the DNS TXT records. Creating the new federation trust without errors. But when the 2 order company's trying
    to connect (add our company name for trust) they get a error.
    A have trying to run a couple tests on the new Exchange 2013 server and found this error:
    [PS] C:\Windows\system32>Test-OutlookWebServices -debug -Identity [email protected] -MailboxCredential(Get-Credential
    cmdlet Get-Credential at command pipeline position 1
    Supply values for the following parameters:
    Credential
    Source                              ServiceEndpoint                    
    Scenario                       Result  Latency
    (MS)
    AM111.AM.LAN                        autodiscover.company.nl            Autodiscover: Outlook
    Provider Failure     144
    AM111.AM.LAN                        webmail.company.nl                
    Exchange Web Services          Success     134
    AM111.AM.LAN                        webmail.company.nl                
    Availability Service           Success     207
    AM111.AM.LAN                                                           
    Offline Address Book           Skipped       0

    Hi,
    Are you add primary SMTP domain as a federated domain? If not, please run below command to achieve this function:
    Add-FederatedDomain -DomainName contoso.com
    Configure federated sharing for the Exchange 2013 organization. Complete the steps in
    Configure federated sharing.
    Configure federated delegation (previous name for federated sharing) for the Exchange 2010 SP2 organization. Complete the steps in
    Configure federated delegation.
    Besides, I find an similar thread about Autodiscover service failed within federated trust, for your convenience:
    https://social.technet.microsoft.com/Forums/ie/en-US/ea192e0a-1363-4cb6-9fc4-2973f64afc23/the-response-from-the-autodiscover-service-at?forum=exchange2010
    Best Regards,
    Allen Wang

  • Exchange 2013 SP1 setup fails at prerequisite Analysis

    I installed a completely new server network with Hyper-v 2012R2
    I installed two virtual 2012R2 servers: DC01 as the Domain Controller of "testdomain.local" and EX01 as the Exchange server.
    EX01 is joined the domain "testdomain" from DC01
    I log in on EX01 with an in AD created testdomain\exadmin account who is member of domain admins, enterprise admins, schema admins, administrators and group policy creator owners.
    I have run the command Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,
    NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing,
    Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,
    Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, Telnet-Client, RSAT-ADDS
    on EX01
    I have installed the Microsoft Unified Communications Managed API 4.0
    Then I run the Exchange 2013 SP1 setup and the prerequisite check gives the following errors:
    Error:
    You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
    Error:
    Setup encountered a problem while validating the state of Active Directory: Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.  See the Exchange setup log for more information on this
    error.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
    I can connect with the Active Directory Sites and Domains and other applets to the AD. So Why these errors???
    HELP!
    Regards, Manu
    Manu van Winkel

    Hi, thanks for the answer.
    I restarted the server and did the "run as administrator": same result.
    The first errormessage in the exchangesetup.log is:
    [ERROR] Setup encountered a problem while validating the state of Active Directory: Active Directory server  is not available. Error message: Active directory response: The LDAP server is unavailable.  See the Exchange setup log for more information
    on this error.
    When I run dcdiag /s:DC01 from EX01 it passes all tests except:
    DFSREvent "The RPC server is unavailable"
    KccEvent "The RPC server is unavailable."
    SystemLog  "The RPC server is unavailable."
    Could these be of any influence?
    Running dcdiag on DC01 passes all tests.
    The only thing I changed after setting up DC01, was changing the fixed IP-adres from 192.168.25.3 to 192.168.25.2, but I ran ipconfig /flushdns and ipconfig /registerdns and dcdiag /fix afterwards.
    The only roles installed on DC01 are AD DS (I tried installing exchange before and after adding the AD DS role), AD, DNS, DHCP and Fileservices
    I don't know where to look anymore....
    Manu van Winkel

  • Exchange 2013 SP1 Setup fails

    I am getting very frustrated. It really shouldn't take over a week to install Exchange.
    I have two domain controllers, Windows 2003 and Windows 2008 R2. The 2008 is now all Operations Masters for all roles.
    I have a clean install of W2K8 R2 SP1 installed under Hyper-V on a separate physical W2K8 server. Before starting the install I used ADSIEdit to ensure there was nothing left in the AD of prior Exchange install attempts. This is the first and only installation
    of Exchange.
    I am running the install as the Domain\Administrator and naturally that account is a member of all the appropriate security groups. RSAT are installed on the Exchange server and using them to access Users and Computers clearly shows this. The install fails
    with the errors below, all of which appear to be incorrect.
    *** BEGIN ERROR ***
    Error:
    Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx
    Error:
    You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx
    Error:
    You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx
    Error:
    Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.  See the Exchange setup log for more information on this error.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx
    Error:
    The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx
    Error:
    This computer requires the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit. Please install the software from http://go.microsoft.com/fwlink/?LinkId=260990.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UcmaRedistMsi.aspx
    Error:
    This computer requires the update described in Microsoft Knowledge Base article KB974405 (http://go.microsoft.com/fwlink/?LinkId=262357). Please install the update, and then restart Setup.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.Win7WindowsIdentityFoundationUpdateNotInstalled.aspx
    Error:
    Either Active Directory doesn't exist, or it can't be contacted.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx
    Warning:
    Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.
    For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx
    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
    *** END ERROR
    Why can't Exchange installation see the AD when everything else can?

    It appears that these error messages are pure fiction. I went back to ADSI Edit and removed some MS Exchange container and then reran setup /prepareschema again followed by setup /preparead and finally setup /mosde:install /role:clientaccess,mailbox and
    it churned away for a long time, apparently working.
    It appears than when it says you aren't a member of Schema Admins and that it can't access Active Directory, what it really means is it could find the AD just fine, but didn't like what it saw.
    My guess would be very sloppy programming in which the low level error doesn't bubble up and so when something fails it just assumed you didn't have permissions.
    It's not quite finished yet, but I am beginning to believe it will finish. So that's almost 6 days of non stop effort to install Exchange. It's hard top believe they are allowed to charge for this stuff.

  • Exchange 2013 SP1 - healthsets failing

    Hi,
    I have recently installed two Exchange 2013 SP1 servers in different environments and are experiencing issues on both. Issues that I haven't seen on Exchange 2013 without SP1.
    I have 6 healthsets which are unhealthy. 
    Autodiscover...
    ActiveSync.P...
    EWS.Proxy
    OAB.Proxy
    Outlook.Proxy
    OutlookMapiH...
    I found this article: 
    http://technet.microsoft.com/en-us/library/ms.exch.scom.ecp.proxy(v=exchg.150).aspx
    Which describes, that try to restart the app pool, then an iisreset - and lastly reboot the server. Tried all and none of them helped.
    But then I found this error in the Exchang event log:
    RecycleApplicationPool-MSExchangePowerShellAppPool-RpsDeepTestPSProxyRestart: Throttling rejected the operation
    Which fails almost every minute.
    And I guess that this could be the issue. But I can't figure out which throttling that is causing this.
    Any one else with this issue on Exchange 2013 SP1?
    Thanks in advance.
    /Kim

    Hi,
    I have seen a lot of similar issues with health manager service. For IIS services, we can safely ignore these warnings. Personal experience, we just need to monitor whether there are related
    error reports in event log.
    Thanks,
    Simon Wu
    TechNet Community Support

  • Exchange 2013 -DiscoveryMaxMailboxes Search Fails

    I have set up a throttling policy using the following command Set-ThrottlingPolicy –Name Discovery -DiscoveryMaxConcurrency 2 -DiscoveryMaxMailboxes 25000 , I have applied the policy to a
    user who has search permissions in Exchange. I have confirmed its been applied. I have confirmed that DiscoveryMaxMailboxes is 25000. I run the search, and it fails complaining about searching less than 5000 mailboxes.
    Exchange 2013 SP1 CU5
    Robert Watt
    Hold
    None
    Search
    Status:
    Run by:
    Run on:
    Size: 0 B
    Items: 0
    Errors:
    An unknown error occurred on the   search server. Please contact your administrator for assistance. The message   from the search server
    is 'The search exceeded the maximum number of   mailboxes that can be searched at a time. Please try searching less than 5000   mailboxes.'.
    Statistics:

    Hi,
    I'm afraid that you can't specify the value of DiscoveryMaxMailboxes parameter is more than 5000, there is a limitation to the number of mailboxes that can be searched and it is 5,000*. Any number beyond this and the specified query will return
    the following error: An unknown error occurred on the search server. Please contact your administrator for assistance. The message from the search server is 'The search exceeded the maximum number of mailboxes that can be searched at a time. Please try searching
    less than 5000 mailboxes.'.
    More details refer to the following article:
    http://blogs.technet.com/b/johnbai/archive/2014/02/11/exchange-2013-ediscovery-changes.aspx
    Best regards!
    Niko
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 Auto Attendant fails when using multiple languages

    Hi All,
    Trying to setup UM Auto Attendants as I had it in Exchange 2010, but cannot get it to work as I want.
    Here is my setup:
    Windows 2012 and Exchange 2013.
    Parent - Main Auto Attendant (80)
    Child - English Auto Attendant (81)
    Child - Swedish Auto Attendant (82)
    Child - Finnish Auto Attendant (83)
    All callers are first connected to 80 where they can select the language to continue with (press 81 for English, press 82 for Swedish, press 83 for Finnish).
    This is what I found out this far:
    - If I have English language selected on all Attendants everything works fine I can select all choices and everything works as it should.
    - If I select the proper language for the other languages (82 & 83) only the connection to 80 & 81 works. If I try to connect from 80 to 82 or 83 nothing happens (connection goes quiet) and the only solution to get UM to answer again is to restart the
    UM service on the server.
    Extra info/what I tested this far:
    - I reinstalled the extra language packs just to be sure there were no issues.
    - If I select Swedish or Finnish language on extension 80 they work fine, so the language packs seems to be OK.
    Ideas Anyone?
    //Ase

    Hi All,
    After installing CU1 for Exchange 2013 this behaviour changed a little bit. Instead of getting total freeze of the system I get an error message instead saying "System Error Occured" and then a hangup.
    I also find out that if I remove the checkbox "Set the auto attendant to respond to voice commands" for the extension 82 & 83 (Swedish & Finnish Auto Attendants) this error does not happen, but I like to use the voice commands....
    Also when the error occurs I get the following in the Event Log:
    The VoIP platform encountered an exception Microsoft.Exchange.UM.UMCommon.UMGrayException: A non-fatal exception occurred. For details, please see the inner exception. ---> System.InvalidOperationException: The language for the grammar does not match
    the language of the speech recognizer.
       at Microsoft.Speech.Recognition.RecognizerBase.ThrowIfSapiErrorCode(SAPIErrorCodes errorCode)
       at Microsoft.Speech.Recognition.FileGrammarContent.Load(SapiGrammar sapiGrammar, Boolean enabled, Single weight, Int32 priority)
       at Microsoft.Speech.Recognition.GrammarContent.Load(SapiGrammar sapiGrammar)
       at Microsoft.Speech.Recognition.Grammar.Load(SapiGrammar sapiGrammar, IRecognizerInternal recognizer)
       at Microsoft.Speech.Recognition.RecognizerBase.LoadGrammarIntoSapi(Grammar grammar)
       at Microsoft.Speech.Recognition.RecognizerBase.LoadGrammar(Grammar grammar)
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.PlayPromptsAndRecoSpeechSessionState.LoadGrammar(UMGrammar grammar)
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.PlayPromptsAndRecoSpeechSessionState.LoadGrammars()
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.PlayPromptsAndRecoSpeechSessionState.InternalStart()
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.SessionState.Start()
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.ChangeState(SessionState nextState)
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.PlayPrompts(ArrayList prompts, Int32 minDigits, Int32 maxDigits, Int32 timeout, String stopTones, Int32 interDigitTimeout, StopPatterns stopPatterns, Int32 startIdx, TimeSpan offset, List`1
    grammars, Boolean expetingSpeechInput, Int32 babbleTimeout, Boolean stopPromptOnBargeIn, String turnName, Int32 initialSilenceTimeout)
       at Microsoft.Exchange.UM.UMCore.SpeechMenu.PlayPrompts(ArrayList prompts, BaseUMCallSession vo)
       at Microsoft.Exchange.UM.UMCore.SpeechMenu.SpeechMenuStart(BaseUMCallSession vo)
       at Microsoft.Exchange.UM.UMCore.SpeechMenu.StartActivity(BaseUMCallSession vo, String refInfo)
       at Microsoft.Exchange.UM.UMCore.ActivityManager.ChangeActivity(ActivityBase next, BaseUMCallSession vo, String refInfo)
       at Microsoft.Exchange.UM.UMCore.TransitionBase.Execute(ActivityManager manager, BaseUMCallSession vo)
       at Microsoft.Exchange.UM.UMCore.Menu.OnComplete(BaseUMCallSession vo, UMCallSessionEventArgs voiceObjectEventArgs)
       at Microsoft.Exchange.UM.UMCore.Menu.StartActivity(BaseUMCallSession vo, String refInfo)
       at Microsoft.Exchange.UM.UMCore.ActivityManager.ChangeActivity(ActivityBase next, BaseUMCallSession vo, String refInfo)
       at Microsoft.Exchange.UM.UMCore.TransitionBase.Execute(ActivityManager manager, BaseUMCallSession vo)
       at Microsoft.Exchange.UM.UMCore.Menu.OnComplete(BaseUMCallSession vo, UMCallSessionEventArgs voiceObjectEventArgs)
       at Microsoft.Exchange.UM.UMCore.Menu.StartActivity(BaseUMCallSession vo, String refInfo)
       at Microsoft.Exchange.UM.UMCore.ActivityManager.ChangeActivity(ActivityBase next, BaseUMCallSession vo, String refInfo)
       at Microsoft.Exchange.UM.UMCore.ActivityBase.OnHeavyBlockingOperation(BaseUMCallSession vo, HeavyBlockingOperationEventArgs hboea)
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.HeavyBlockingOperationSessionState.CompleteFinalAsyncCallback()
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.SessionState.CompleteNonTeardownState()
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.<>c__DisplayClassf.<CatchAndFireOnError>b__b()
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.UM.UMCommon.ExceptionHandling.ExceptionCatcher(Object exception)
       at Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate)
       at Microsoft.Exchange.UM.UcmaPlatform.UcmaCallSession.CatchAndFireOnError(UserCodeDelegate function) during the call with ID "Y2M5Y2ZhYzYzMzc4ZTVhYmE0ZjE3MmVjYTVmYmRiZTM.". This exception occurred at the Microsoft Exchange Speech Engine VoIP
    platform during an event-based asynchronous operation submitted by the server. The server will attempt to recover from this exception. If this warning occurs frequently, contact Microsoft Product Support.
    Anyone with ideas that can help me forward?
    //Ase

  • Exchange 2013 SP 1 fails MSSpeech_SR_TELE.ca-ES.msi

    Hi
    After trying to install exchange 2013 SP 1 it fails with the following error : MSSpeech_SR_TELE.ca-ES.msi couldn't be opened.
    I'm running the upgrade through the command line with elevated privileges.
    I've re downloaded the sp already 2 times to no avail.
    The file exists in the extracted version.
    Same error occurred in CU 2 I've read on forums.
    [03/03/2014 13:27:57.0852] [1] [ERROR] The following error was generated when "$error.Clear();
              Install-MsiPackage `
                -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi")) `
                -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
                -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-ca-ES.msilog"))
            " was run: "Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\[03/03/2014 13:27:57.0852] [1] [ERROR] The following error was generated when "$error.Clear();
              Install-MsiPackage `
                -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi")) `
                -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
                -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-ca-ES.msilog"))
            " was run: "Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\[03/03/2014 13:27:57.0852] [1] [ERROR] The following error was generated when "$error.Clear();
              Install-MsiPackage `
                -PackagePath ([System.IO.Path]::Combine($RoleLanguagePacksPath, "Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi")) `
                -PropertyValues ("ARPSYSTEMCOMPONENT=1 ALLUSERS=1") `
                -LogFile ([System.IO.Path]::Combine($RoleSetupLoggingPath, "InstallSpeech-ca-ES.msilog"))
            " was run: "Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify
    that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.".
    [03/03/2014 13:27:57.0852] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify that the package exists and
    that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
    [03/03/2014 13:27:57.0852] [1] [ERROR] This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
    [03/03/2014 13:27:57.0852] [1] [ERROR-REFERENCE] Id=SpeechComponent___c2c075b985784599a14e8fa90dbc0403 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup'. This installation package could not be opened. Verify that the package exists and that you
    can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.".
    [03/03/2014 13:27:57.0852] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify that the package exists and
    that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
    [03/03/2014 13:27:57.0852] [1] [ERROR] This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
    [03/03/2014 13:27:57.0852] [1] [ERROR-REFERENCE] Id=SpeechComponent___c2c075b985784599a14e8fa90dbc0403 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup'. This installation package could not be opened. Verify that the package exists and that you
    can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.".
    [03/03/2014 13:27:57.0852] [1] [ERROR] Couldn't open package 'C:\Program Files\Microsoft\Exchange Server\V15\bin\Setup\ServerRoles\UnifiedMessaging\MSSpeech_SR_TELE.ca-ES.msi'. This installation package could not be opened. Verify that the package exists and
    that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package. Error code is 1619.
    [03/03/2014 13:27:57.0852] [1] [ERROR] This installation package could not be opened. Verify that the package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer package
    [03/03/2014 13:27:57.0852] [1] [ERROR-REFERENCE] Id=SpeechComponent___c2c075b985784599a14e8fa90dbc0403 Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup

    Thanks for the update John!
    From what I have read, it can work running the upgrade in Windows Powershell, but the syntax must be right.
    .\Setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
    compared to:
    Setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
    Rhoderick Milne has a great blog post about this, so check it out: 
    6 Mistakes To Avoid With Exchange 2013 CU Command Line Installations . Personally I haven't tried that - So used to always run any exchange CU/SP or Rollup in the command line :)
    Martina Miskovic

  • Installing Exchange 2013 CU 6 failed

    Hello, we have a big problem with installing CU6 on a new installed exchange 2013 server. Here's the error message:
    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;
              Write-ExchangeSetupLog -Info ("Configuring offline address book(s) for this mailbox");
              Get-OfflineAddressBook | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
    -ge 0 -and $_.GeneratingMailbox -eq $null} | Set-OfflineAddressBook -GeneratingMailbox $sysMbx.Identity;
              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: "Microsoft.Exchange.ProvisioningAgent.RusException:  Failed to generate proxy address. Additional information:
    General Error.
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckReturnCode(ReturnCode rc)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckProxy(RecipientInfo pRecipientInfo, String pwszProxyAddr)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CheckSingleProxy(ProxyAddressTemplate baseAddress, RecipientInfo recipientInfo, ProxyAddress oldProxyAddress)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.GenerateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
    globalCatalogSession, IEnumerable`1 baseAddresses, IEnumerable`1 oldProxies, RecipientInfo recipientInfo, ADRecipient recipient, LogMessageDelegate logger)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CreateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
    globalCatalogSession, IEnumerable`1 baseAddresses, ADRecipient recipient, LogMessageDelegate logger)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateEmailAddresses(List`1 allPolicies, ADRecipient recipient, LdapFilterProvider filterProvider)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateRecipient(ADRecipient recipient)
       at Microsoft.Exchange.ProvisioningAgent.DefaultRUSProvisioningHandler.UpdateRecipient(ADRecipient recipient)
       at Microsoft.Exchange.ProvisioningAgent.RUSProvisioningHandler.UpdateAffectedIConfigurable(IConfigurable writeableIConfigurable)
       at Microsoft.Exchange.Provisioning.ProvisioningLayer.UpdateAffectedIConfigurable(Task task, IConfigurable writeableIConfigurable, Boolean checkProvisioningLayerAvailability)
       at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
       at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    After this error message, the exchange installation is incomplete, there is no repair possible. Also remove the installation is not possible because there is an incomplete update installed.
    Any ideas how to solve this?

    Hi,
    From the description of the error “ Microsoft.Exchange.ProvisioningAgent.RusException:  Failed to generate proxy address. Additional information: General Error. ”
    Appeared to have some valid proxy address. Please check if there are invalid characters in the admin account proxy address.
    To find the proxy address, take the following steps:
    Open ADUC, Click View in the menu then click
    Advanced Features.
    Navigate to yourOrganization >> Users, choose the admin account, right-click to
    Properties.
    Under Attributes Editor tab, find the proxyaddresses
    Attribute, then check the address.
    Hope this will be helpful for you.
    Best Regards.

Maybe you are looking for

  • Is there a way to set which keychain item is used by default for a site/application?

    This question applies primarily to the keychain in Mavericks, but also the iCloud keychain and its use in iOS. There are several sites and services for which I have multiple logins that serve different purposes. Whether it's because they are business

  • Happy Birthday Elvis Presley - what channel?

    They are running all of the Elvis Presley movies today in honor of his birthday. Does anyone know if it's being broadcast on a FiOS channel? Thanks in advance! Solved! Go to Solution.

  • During job work order  PO number consumed

    I maked one jobwork order after saving that order,  one number is generate.. when i am going to open again in me22n screen. system give message that number is not available. i.e. number is skiped... why it is so.. please forward some solution ...

  • Trouble entering dates in YYYY-MM-DD format

    On my system I have set the iCal date format to the correct Canadian ISO 8601 YYYY-MM-DD format for Canada. However when typing in dates (such as birthdates) the numbers do not go in correctly, presumably due to some internal edit process that does n

  • Create table results in error or high cpu

    Hello all, We are using apex 3.0 against oracle 10.2. Most of the times when we try to create a table from the apex 'sql commands' page, it results in high CPU and from OEM i could see the physical blocks(in Kb's) read as 40,000 where as it used to b