Exchange 2013 Cumulative Update 5 Install Issue

I have tried installing Exchange 2013 Cumulative Update 5 on our server but it is failing at the Mailbox role: Transport Service section with the following error. I am running the command prompt as Administrator. Any help would be great. 
Error: The following error was generated when "$error.Clear(); Set-LocalPermissions 
" was run: "System.UnauthorizedAccessException: Attempted to perform an unauthorized operation. at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl) at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception
exception, ErrorCategory category, Object target) at Microsoft.Exchange.Management.Deployment.SetLocalPermissions.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.b__b() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String
funcName, Action func, Boolean terminatePipelineIfFailed)".

Hi Tim,
From the Exchange setup log description, there is only one error, "Attempted to perform an unauthorized operation.". The error indicates that it is a permission problem. I would like to verify if you add the account to the local admin group. If no, please
add the account to the admin group and continue to install the CU5.
If the issue persists, I recommend you download a new CU5 for Exchange 2013 and reinstall it to check the result.
For you convenience:
Cumulative Update 5 for Exchange Server 2013
http://www.microsoft.com/en-us/download/details.aspx?id=43103
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact 
[email protected]
Amy Wang
TechNet Community Support

Similar Messages

  • Exchange 2013 CU5 fresh install suffering issues with services not starting and coexistence with 2007

    Hi everyone,
    Hope you can help me out on a couple of issues I've been experiencing during the initial stages of a project to upgrade an on premise Exchange 2007 to 2013.
    On Monday last week I installed the first Exchange 2013 server into the network after a few weeks of careful planning, information gathering and remediation of our current Exchange 2007 environment and associated systems.
    The server itself has been having some issues from the word go, some of which I've resolved but none that are show stoppers but I want to get them resolved before building more servers and setting up the planned 2 x 2 node DAG's
    The main problems are as follows:
    There's usually one service that does not start following an OS restart and it's not always the same service. So far I've seen the following not start: DAG Management, Migration Workflow, Anti-spam Update, Unified Messaging, UM Call Router, Transport
    Service.
    The critical system event log entries are complaining of timeouts when the services are starting up but I can't imagine that the servers boot time is too long...  It's a 2 vCPU/12Gb vRAM VM, Windows 2012 R2
    I receive an error in the Event Log regarding RPC over HTTP Proxy
    to one of the 2007 CAS servers (not our primary one). The first error was because the Windows Component was missing but since installing it, disabling Outlook Anywhere, reenabling it, restarting the server, I now have a new error which is shown further down
    this post
    The Exchange 2013 server install is pretty default, CAS/MBX roles and some basic configuration performed such as new DNS entries, Public SSL certs installed and assigned, URL's updates, SCP updated. I have review and resolved some errors from the event logs
    for over chatty warnings about disk space (the warning is that we have loads of space...)
    This is a brief outline of the environment:
    Exchange 2007 SP3 RU13
    UK - Two physical locations in a stretch LAN (100Mb WAN)
    4 x CCR Cluster Mailbox Servers in two separate CCR Clusters
    Cluster 1 - Windows 2003 R2: One physical, one virtual server - don't ask, legacy install and I know the virtual is not a supported configuration.
    Cluster 2 - Windows 2008 R2: Two virtuals - New cluster built following a 4 day failure of Cluster 1. The aim was to move to supported config and decommission cluster 1.
    Note: Migration of Cluster 1 to Cluster 2 was halted as 2013 was so close it seemed pointless to continue the migration and instead migrate both Clusters to 2013 once in production.
    2 x Virtual Windows 2003 R2 - Hub Transport Servers
    2 x Virtual Windows 2003 R2 - Client Access Servers
    1 x Virtual Windows 2003 R2 - Unified Messaging Server
    1 x Virtual Windows 2003 R2 - Edge Transport Server (DMZ)
    US - One physical location
    1 x Physical Windows 2008 R2 - Mailbox, Client Access, Hub Transport Server
    Exchange 2013 CU5
    UK - Installed into same site along side Exchange 2007 servers
    1 x Virtual Windows 2012 R2 - Mailbox, Client Access Server
    Problem 2 Error Message - Please note, server names and domain name changed:
    Log Name:      Application
    Source:        MSExchange Front End HTTP Proxy
    Date:          18/07/2014 10:00:37
    Event ID:      3005
    Task Category: Core
    Level:         Warning
    Keywords:      Classic
    User:          N/A
    Computer:      EXC2013.domain.local
    Description:
    [RpcHttp] Marking ClientAccess 2010 server EXC2007CAS1.domain.local (https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll) as unhealthy due to exception: System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)
    Event Xml:
    <Event xmlns=http://schemas.microsoft.com/win/2004/08/events/event>
      <System>
        <Provider Name="MSExchange Front End HTTP Proxy" />
        <EventID Qualifiers="32768">3005</EventID>
        <Level>3</Level>
        <Task>1</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2014-07-18T09:00:37.000000000Z" />
        <EventRecordID>64832</EventRecordID>
        <Channel>Application</Channel>
        <Computer>EXC2013.domain.local</Computer>
        <Security />
      </System>
      <EventData>
        <Data>RpcHttp</Data>
        <Data>EXC2007CAS1.domain.local</Data>
        <Data>https://EXC2007CAS1.domain.local/rpc/rpcproxy.dll</Data>
        <Data>System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
       at System.Net.HttpWebRequest.GetResponse()
       at Microsoft.Exchange.HttpProxy.ProtocolPingStrategyBase.Ping(Uri url)</Data>
      </EventData>
    </Event>

    Hi Off2work,
    I've gone through the article and the Get-OutlookAnywhere commandlet looks fine (especially when compared with our working CAS).
    Having looked through IIS I have spotted two additional misconfigurations with a missing setting to require SSL on the RPC folder and also the .NET version was not set.
    I've now set those to Require SSL and .NET 2.0.5072 however this has made no difference following restarted of both 2007 CAS and 2013 servers.
    I could potentially reinstall the CAS server or additionally decommission it as we have two of them and the other is not causing any errors with the 2013 server. This broken CAS server doesn't even have DNS records (except it's own hostname) or firewall
    rules pointing to it, nor does it have any active client connections if I check with a quick netstat -a
    As for UM, it's next on my list following some client/server connectivity testing so I have not yet assigned the SSL to the services or setup the dial plans, etc.
    The services do start most of the time, but others then don't so it's not a consistent issue with just this service. On my current boot, the DAG Management service failed to start, but again I don't have a DAG implemented yet.
    I will see if UM drops out of that list once I've configured it shortly
    Thanks for taking the time to respond (and that goes to DareDevil too)

  • Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

    What am I trying to do?
    I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
    error logs at the bottom of the page but the basics are in order it will throw which loop around are:
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
    What am I running?
    2 X DC on domain and forest functional level 2008R2 both writable
    1 X fresh install of Windows 2012 R2 which is domain joined
    What have I tried?
    Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
    Rebooted every server
    Run setup as Administrator
    My account is part of the domain Enterprise Admin group
    Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
    Computer Configuration Windows Settings
    Security Settings + Local Policies
    User Rights Assignment Mange auditing and security log
    Turned off firewall on DC and Exchange Server even stopped the service
    Turned off all AV on the DC and Exchange Server
    Checked I could telnet to global catalog servers on port 3268 which I can
    Checked the global catalog records existed in DNS which they all do
    Done the obvious ping tests all round which confirms connectivity
    Schema has been prepared using appropriate commands before running the setup exe
    setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
    Making sure the following path has full permissions:
    EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    Restarted Microsoft Exchange Active Directory Topology service
    DcDiag all looks good
    What have I noticed that is suspicious?
    Microsoft Exchange Transport service will not start even though both of its dependences services have started:
    Microsoft Filtering Management Service
    Microsoft Exchange Active Directory Topology Service
    It will eventually error with
    “Windows could not start the Microsoft Exchange Transport Service on local computer
    Error 1053: This Service did not respond to the start of control request in a timely fashion”
    This error is from the GUI wizard itself:
    Error:
    The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
    " was run: "System.Exception: Unable to set shared config DC.
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
    at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
    at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Exchange logs which have been written:
    **The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
    [01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
    '{ mydomain.com}'
    [01/20/2015 17:13:20.0084] [2] User specified parameters: 
    -DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
    [01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
    Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
    [01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
    No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
    [01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
    [01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] 0.  ErrorRecord: System.Exception: Unable to set shared config DC.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    [01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
    $maxWait = New-TimeSpan -Minutes 8
    $timeout = Get-Date;
    $timeout = $timeout.Add($maxWait);
    $currTime = Get-Date;
    $successfullySetConfigDC = $false;
    while($currTime -le $timeout)
    $setSharedCDCErrors = @();
    try
    Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
    $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
    if($successfullySetConfigDC)
    break;
    Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
    catch
    Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
    Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
    Start-Sleep -Seconds 30;
    $currTime = Get-Date;
    if( -not $successfullySetConfigDC)
    Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
            " was run: "System.Exception: Unable to set shared config DC.
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
       at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
       at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    [01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
    [01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
    [01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
    [01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
    Windows Event Viewer:
    Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
    in either the local site 'Default-First-Site' or the following sites:

    Hi apl228,
    1. Please make sure the IPv6 is enabled.
    2. Please make sure the account that install Exchange server has Administrator permission.
    3. Please make sure DNS has been configured correctly.
    Thanks
    Mavis Huang
    TechNet Community Support

  • Exchange 2013 Sp1 says that it is 'Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup'

    So, I have decompressed my brand new download of Exchange 2013 SP1. This was downloaded from the link at the bottom of the post.
    So to start my upgrade I have tried to start by running the schema preparation which then advises me that I am welcomed to:
    'Microsoft Exchange Server 2013 Cumulative Update 3 Unattended Setup'
    Is this poor QA or was the incorrect file uploaded?
    http://www.microsoft.com/en-us/download/details.aspx?id=41994

    Hello,
    Powershell need full path to file you want to run.
    So you should run .\setup.exe instead of just setup.exe.
    Hope this help.
    Regards, Pavel.

  • Office Web Apps Server June 2013 Cumulative Update Excel Freeze Pane and Hide/Un-hide Feature Missing

    Hi,
    I have recently updated the Office Web Apps Server to the June 2013 Cumulative Update (KB2817350) which was published with the new features that allow rendering of freeze pane, hide/un-hide the excel worksheet and row/columns, Header
    Row Snapping, Sorting, Data Validation and Autocomplete. i have followed the TechNet article (http://technet.microsoft.com/en-us/library/jj966220.aspx)
    to update the office web apps server. Current setup is a SharePoint 2013, SQL 2012 and Office Web Apps server. All server are installed on Windows server 2012.
    3vild3vil

    Hi,
    Sorry to inform you that these new features are specific to cloud Excel Web App in both SkyDrive and Office365. There is no update available for on-premise Excel Web Apps installed locally
    yet. Thank you for your understanding.
    http://blogs.office.com/b/microsoft-excel/archive/2013/06/26/we-ve-updated-excel-web-app-what-s-new-as-of-june-2013.aspx
    Miles LI TechNet Community Support

  • WSP deployment and retraction error after December 2013 cumulative update.

    I have installed December 2013 cumulative update on my front end and app servers and ran the configuration wizard. Everything was working fine until I updated the wsp, as it showed me an error on Central admin sites farm solution page. 
    And the error was -  'Cabinet file is corrupt : Failed to extract the cab file in the solution. "
    but I could deploy the same wsp in other environment without December cumulative update.
    Worst thing is that It throws the same error when I try to retract the wsp, and Now I am stuck because I can't add or retract a solution. 
    Any help appreciated.

    Check SharePoint administration service is running or not. It is is running please restart(stop and start) and try to uninstall again. 
    Try to use the below command to remove the solution.
    Remove-SPSolution -Identity your.wsp -force
    http://social.technet.microsoft.com/Forums/sharepoint/en-US/bf16c8d1-0291-4c57-8d73-3162e737dd16/retracting-solution-stuck-hangs?forum=sharepointadmin
    My Blog- http://www.sharepoint-journey.com|
    If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

  • Host Integration Server 2013 Cumulative Update 2 (CU2) is available

    This cumulative update package for Microsoft Host Integration Server 2013 contains hotfixes for issues that were fixed after the release of Host Integration Server 2013.
    Important This cumulative update package includes all the component packages. However, the cumulative update package updates only those features that are currently installed on the system.
    Download Link :
    http://support.microsoft.com/kb/2929767
    Many Thanks to the Product and Support TEAM ! You’ve done a great job !
    Steve Melan - BCEE My Blog : http://stevemelan.wordpress.com

    Hello Jason,
    In your case I recommend you to use the Standard License as you are only using Host Integration Server 2013.
    Then you will need for your architecture to license 16 Cores. 
    1 Core BizTalk 2013 License costs : about $2500
    Total : 40.000€
    As HIS 2013 is very performant, you can also use for instance only 1 CPU with 4 or 6 Core with higher Frequency per Server.
    Here's a good article explaining the licensing model of BizTalk 2013 : http://blogs.biztalk360.com/understand-biztalk-server-2013-licensing/
    Q: What license limitation should I consider with the BizTalk branch edition?
    A: You may Run Instances of the software on Licensed Servers only at the endpoint of your internal network (or edge of your organization) to connect
    business events or transactions with activities processed at that endpoint; provided, the Licensed Server may not:
      act as
    the central node in a “hub and spoke” networking model,
      centralize enterprise-wide
    communications with other servers or devices; or
      automate business processes
    across divisions, business units, or branch offices.
    You may not use the server software, including the Master Secret Server, on a server that is part of a networked cluster or in an operating system environment
    that is part of a networked cluster of OSEs on the same server. 
    Best Regards,
    Steve Melan - BCEE My Blog : http://stevemelan.wordpress.com

  • Exchange 2013 Management Tools Install Error on Win8

    Hello,
    I'm having some trouble installing the management tools for Exchange 2013 on Windows 8. While going through the install if I leave "Automatically install Windows Server roles and features that are required to install Exchange Server" check I get
    this error...
    Error:
    The target of the specified cmdlet cannot be a Windows client-based operating system.
    If I uncheck that option and just check the Management Tools option, the error message changes to...
    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:
    Setup encountered a problem while validating the state of Active Directory: Couldn't find the Enterprise Organization container.
    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:
    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 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
    Any help on resolving this so I can move on with the installation would be appreciated.
    Thanks.

    Hi,
    To install the Exchange 2013 Management Tools, there are many prerequisites we need to understand before installation. And even
    we must manually install some required software.
    Here are some references that may be helpful to you:
    Install the Exchange 2013 Management Tools
    http://technet.microsoft.com/en-us/library/bb232090(v=exchg.150).aspx
    Exchange 2013 Prerequisites
    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Java 2013-003 Update causing issues

    I own several Mac's; one Macbook and two iMacs, each with different versions of OS X and after installing the 2013-003 update I'm having major issues with Java. In fact since Apple decided they didn't want Java running on their OS's and in their browsers, I've had numerous problems.
    Today I was forced to install the 2013-003 update and when I try to run a website I use which requires Java, all I'm seeing is this message:
    Use the Software Update feature (available on the Apple menu) to check that you have the most up-to-date version of Java for your Mac.
    Clearly I've updated to the latest version and I've even tried installing the most up to date version of Java from Oracle's website yet I'm still having the same issue. I love my Apple computers but I'm getting really sick of the constant Java issues.
    Any ideas what's going on?
    Thanks.

    Would like to know the answer to this too.

  • Exchange 2013 Edge Transport install fails

    I'm trying to install the Edge Transport for Exchange 2013 but it gets to step 7 of 9:
    then give's the following error
    Error:
    The following error was generated when "$error.Clear();
     new-ExchangeServer
    " was run: "Value cannot be null.
    Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
    Then in event viewer I have the following two events.
    Watson report about to be sent for process id: 260, with parameters: E12IIS, c-RTL-AMD64, 15.00.0847.032, ExSetupUI, M.E.Data.Directory, M.E.D.D.ADObjectId.GetChildId, System.ArgumentNullException, 2ac6, 15.00.0847.031.
    ErrorReportingEnabled: True
    and
    Exchange Server component Edge Transport Role failed.
    Error: Error:
    The following error was generated when "$error.Clear();
     new-ExchangeServer
    " was run: "Value cannot be null.
    Parameter name: Cannot get child of ADObjectId: this is a GUID based ADObjectId.".
    I've rebuilt the server but since it has something to do with the GUID I assumed it wouldn't work but I was grasping at straws and it didn't fix the issue.
    I can run the setup again and it does finish but it doesn't show up in the list of servers in the ecp management. I've yet to find a solution on this issue if anyone has a suggestion or two it would be greatly appreciated.

    Thanks for response.
    when I run Get-ExchangeServer I get the following
    Name                Site                 ServerRole  Edition     AdminDisplayVersion
    Exchange03                               Edge        Standard... Version
    15.0 (Bu...
    and the errors that are in the log
    [02/17/2015 20:06:33.0084] [0] [ERROR] Setup encountered a problem while validating the state of Active Directory: ADAM is installed on this machine; only the Microsoft Exchange Edge Transport server role may be installed.  See the Exchange setup log
    for more information on this error.
    [02/17/2015 20:07:50.0288] [1] The following 1 error(s) occurred during task execution:
    [02/17/2015 20:07:50.0288] [1] 0.  ErrorRecord: Service SMTPSVC was not found on computer '.'.
    [02/17/2015 20:07:50.0288] [1] The previous errors were generated by a non-critical task and will be ignored.
    then I have a load of error that failed to load dependency below is a small sample
    [02/17/2015 20:07:57.0648] [2] Process standard output: Installing assembly C:\Program Files\Microsoft\Exchange Server\V15\bin\edgetransport.exe
    Failed to load dependency Microsoft.Management.OData of assembly Microsoft.Exchange.Configuration.ObjectModel, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
    from HRESULT: 0x80070002)
    Failed to load dependency Microsoft.Ceres.InteractionEngine.Processing.BuiltIn of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified.
    (Exception from HRESULT: 0x80070002)
    Failed to load dependency Microsoft.Ceres.NlpBase.RichTypes of assembly Microsoft.Exchange.Data.Storage, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception
    from HRESULT: 0x80070002)
    Failed to load dependency System.IdentityModel.Tokens.Jwt of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from
    HRESULT: 0x80070002)
    Failed to load dependency Microsoft.Passport.RPS of assembly Microsoft.Exchange.Security, Version=15.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 because of the following error : The system cannot find the file specified. (Exception from HRESULT:
    0x80070002)
    Thanks

  • Exchange 2013 CU6 Update Error /PrepareAD

    setup /PrepareAD /IAcceptExchangeServerLicenseTerms -- Fails
    I have copied this whole folder up to the Schema FSMO role holder and and the forestprep and the domainprep and the /prepareAD will not run.  I have included entries from the ExchangeSetuplog below.  I only changed the Domain Name and the exchange
    organization for security reasons.
    Current Setup.
    Originally installed Exchange 2013 SP1 on windows 2012r2 via an ISO.  This server only had Exchange 2013 installed was not an upgrade.  Our previous version of Exchange that was running on a different server was Exchange 2007.  This server
    is no longer apart of the Exchange organization.
    [11/14/2014 22:00:39.0848] [1] Executing:
        install-AdministrativeGroup -DomainController $RoleDomainController
    [11/14/2014 22:00:39.0864] [2] Active Directory session settings for 'Install-AdministrativeGroup' are: View Entire Forest: 'True', Configuration Domain Controller: 'DomainController', Preferred Global Catalog: 'DomainController', Preferred Domain Controllers:
    '{ DomainController }'
    [11/14/2014 22:00:39.0864] [2] User specified parameters:  -DomainController:'DomainController'
    [11/14/2014 22:00:39.0864] [2] Beginning processing install-AdministrativeGroup
    [11/14/2014 22:00:39.0895] [2] Processing object "Exchange Administrative Group (FYDIBOHF23SPDLT)".
    [11/14/2014 22:00:39.0926] [2] The properties changed on the object 'Exchange Administrative Group (FYDIBOHF23SPDLT)' (CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local)
    are: "{  }".
    [11/14/2014 22:00:39.0926] [2] Saving object "Exchange Administrative Group (FYDIBOHF23SPDLT)" of type "AdministrativeGroup" and state "Unchanged".
    [11/14/2014 22:00:39.0926] [2] Previous operation run on domain controller 'DomainController'.
    [11/14/2014 22:00:39.0942] [2] Reading new object "Exchange Administrative Group (FYDIBOHF23SPDLT)" of type "AdministrativeGroup".
    [11/14/2014 22:00:39.0942] [2] Previous operation run on domain controller 'DomainController'.
    [11/14/2014 22:00:40.0036] [2] [ERROR] Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'
    already exists.
    [11/14/2014 22:00:40.0036] [2] [ERROR] The object exists.
    [11/14/2014 22:00:40.0083] [2] Ending processing install-AdministrativeGroup
    [11/14/2014 22:00:40.0083] [1] The following 1 error(s) occurred during task execution:
    [11/14/2014 22:00:40.0083] [1] 0.  ErrorRecord: Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'
    already exists.
    [11/14/2014 22:00:40.0083] [1] 0.  ErrorRecord: Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException: Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
    Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local' already exists. ---> System.DirectoryServices.Protocols.DirectoryOperationException: The object exists.
       at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
       at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
       at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
       at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
       at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
       at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
       at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
       at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InstallConfigurationObject[TObject](ADObjectId id, Boolean force, TObject instance)
       at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
    [11/14/2014 22:00:40.0098] [1] [ERROR] The following error was generated when "$error.Clear();
        install-AdministrativeGroup -DomainController $RoleDomainController
    " was run: "Microsoft.Exchange.Data.Directory.ADObjectAlreadyExistsException: Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft
    Exchange,CN=Services,CN=Configuration,DC=domain,DC=local' already exists. ---> System.DirectoryServices.Protocols.DirectoryOperationException: The object exists.
       at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
       at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
       at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
       at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
       --- End of inner exception stack trace ---
       at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
       at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
       at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
       at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
       at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InstallConfigurationObject[TObject](ADObjectId id, Boolean force, TObject instance)
       at Microsoft.Exchange.Management.Deployment.InstallAdministrativeGroup.InternalProcessRecord()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    [11/14/2014 22:00:40.0098] [1] [ERROR] Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local'
    already exists.
    [11/14/2014 22:00:40.0098] [1] [ERROR] The object exists.
    [11/14/2014 22:00:40.0098] [1] [ERROR-REFERENCE] Id=CommonGlobalConfig___48aad7b8f00942afbc699677d60bb3fe Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
    [11/14/2014 22:00:40.0098] [1] Setup is stopping now because of one or more critical errors.
    [11/14/2014 22:00:40.0098] [1] Finished executing component tasks.
    [11/14/2014 22:00:40.0130] [1] Ending processing Install-ExchangeOrganization
    [11/14/2014 22:00:40.0130] [0] CurrentResult console.ProcessRunInternal:198: 1
    [11/14/2014 22:00:40.0145] [0] CurrentResult launcherbase.maincore:90: 1
    [11/14/2014 22:00:40.0145] [0] CurrentResult console.startmain:52: 1
    [11/14/2014 22:00:40.0145] [0] CurrentResult SetupLauncherHelper.loadassembly:452: 1
    [11/14/2014 22:00:40.0145] [0] The Exchange Server setup operation didn't complete.  More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
    [11/14/2014 22:00:40.0145] [0] CurrentResult main.run:235: 1
    [11/14/2014 22:00:40.0145] [0] The registry key, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\V15\Setup, wasn't found.
    [11/14/2014 22:00:40.0145] [0] CurrentResult setupbase.maincore:396: 1
    [11/14/2014 22:00:40.0145] [0] End of Setup

    Hi Ryan,
    From the exchange setup log information, we can find the following error :
    Active Directory operation failed on DomainController. The object 'CN=Folder Hierarchies,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=ExchangeOrg,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain,DC=local' already exists
    I recommend you refer to the following article to resolve the issue :
    http://www.expta.com/2013/04/active-directory-operation-failed.html
    This happens when the Public Folder tree object has been manually deleted from Active Directory using a tool such as ADSI Edit. In some organizations it becomes impossible to remove Public Folders properly from a legacy Exchange org and admins resort to
    using brute force to remove them.  However, there are lingering attributes in AD that are still pointing to the deleted PFTree, which causes CU1 setup to fail.
    Please note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. And the changes made in the above blog is not supported officially
    by Microsoft.
    Best regards,
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 CU6 update cannot pass preresquites?

    When I go to update our Exchange 2013 server to CU6 (from CU5) I get the following error:
    I was doing something with the Tasks, which cannot be scheduled anymore. How do I fix this?
    Thanks
    Error:
    The following error was generated when "$error.Clear();
    try
    $Target = $env:COMPUTERNAME
    try
    $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
    catch
    Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup will continue.";
    if ($exSrv -eq $null)
    Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive. Setup will continue.";
    return
    Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
    Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."
    Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
    Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."
    Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
    Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
    catch
    Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup can not continue.";
    throw;
    " was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
    Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
    ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
    at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
    at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
    at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    --- End of inner exception stack trace ---
    at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
    at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Error:
    The following error was generated when "$error.Clear();
    try
    $Target = $env:COMPUTERNAME
    try
    $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
    catch
    Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup will continue.";
    if ($exSrv -eq $null)
    Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive. Setup will continue.";
    return
    Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
    Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."
    Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
    Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."
    Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
    Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
    catch
    Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup can not continue.";
    throw;
    " was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
    Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
    ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
    at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
    at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
    at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    --- End of inner exception stack trace ---
    at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
    at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    Error:
    The following error was generated when "$error.Clear();
    try
    $Target = $env:COMPUTERNAME
    try
    $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
    catch
    Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup will continue.";
    if ($exSrv -eq $null)
    Write-ExchangeSetupLog -Warning "$Target is not an Exchange Server. Unable to set monitoring and server state to inactive. Setup will continue.";
    return
    Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
    Write-ExchangeSetupLog -Info "Monitoring has been set to Inactive while setup is running."
    Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
    Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactive while setup is running."
    Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
    Write-ExchangeSetupLog -Info "The server state has been set to Inactive while setup is running."
    catch
    Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive. Setup can not continue.";
    throw;
    " was run: "Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
    Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
    ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
    at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
    at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
    at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    --- End of inner exception stack trace ---
    at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
    at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
    at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
    at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
    at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
    at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

    Based on "Was Run" error it looks like you don't have permission to store something in AD. Can you try putting server into maintenance mode first and see if you can?
    http://windowsitpro.com/blog/installing-exchange-2013-cu1-dag-member-servers-some-care-and-maintenance-mode-required
    http://vanhybrid.com/2013/11/28/script-putting-exchange-server-2013-into-maintenance-mode/
    If server goes into maintenance mode successfully then re-run the setup...

  • Exchange 2013 Public Folder Accessability Issues

    After migrating from Exchange 2010 to Exchange 2013 we are experiencing random issues accessing Public Folders.  Issues range from a hung server requests to on-screen errors like this one:
    “Cannot expand the folder. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance”
    We are using groups to manage permissions, verified that they are mail enabled, and have used the following PS command to re-propagate permissions:
    ./AddUsersToPFRecursive.ps1 -TopPublicFolder "%folder%" -User "%groupname" -Permissions %permissionlevel"
    The odd thing is that if the user bounces between on of their Inbox folders then back to one of the Public folders or restarts Outlook it seems to resolve itself.
    Ideas?

    Hi Niko,
    Firstly, apologies for the delayed update...
    We are still experiencing random loss of access to Public Folders, I would think it would be so much easier if I could replicate the problem quickly and easily however that is not the case as I ran into this issue again this morning.
    I am really at a loss for explanation, what I can offer is when we had migrated from Exchange 2000 to Exchange 2010 I had to export the PF out to a pst file prior to importing them on the new server installation.  While migrating from Exchange 2010
    to Exchange 2013 we did follow the migration process.
    Here is what our current settings from Get-OutlookAnywhere -Server %Server%
    RunspaceId                         : e2e4f324…
    ServerName                        
    : %server%
    SSLOffloading                     
    : True
    ExternalHostname                  
    : <set>
    InternalHostname                   : <set>
    ExternalClientAuthenticationMethod : Ntlm
    InternalClientAuthenticationMethod : Ntlm
    IISAuthenticationMethods          
    : {Basic, Ntlm, Negotiate}
    XropUrl                           
    ExternalClientsRequireSsl         
    : True
    InternalClientsRequireSsl         
    : True
    MetabasePath              
            : IIS://%server%/W3SVC/1/ROOT/Rpc
    Path                              
    : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
    ExtendedProtectionTokenChecking    : None
    ExtendedProtectionFlags           
    ExtendedProtectionSPNList         
    AdminDisplayVersion               
    : Version 15.0 (Build 775.38)
    Server                             : %server%
    AdminDisplayName             
    ExchangeVersion                   
    : 0.20 (15.0.0.0)
    Name                              
    : Rpc (Default Web Site)
    DistinguishedName                 
    : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=%server%,CN=Servers,CN=Exchange
                        Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=%company%
    Software,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=%domain%,DC=net
    Identity                           : %server%\Rpc (Default Web Site)
    Guid                              
    : 0bf08d0e…
    ObjectCategory                    
    : %domain%/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
    ObjectClass                       
    : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
    WhenChanged                       
    : 5/5/2014 3:08:31 PM
    WhenCreated                       
    : 2/20/2014 2:13:17 PM
    WhenChangedUTC                    
    : 5/5/2014 8:08:31 PM
    WhenCreatedUTC                    
    : 2/20/2014 8:13:17 PM
    OrganizationId                    
    OriginatingServer                 
    : %server%
    IsValid                           
    : True
    ObjectState                       
    : Changed

  • Exchange 2013 Windows Updates Help Please!

    Hello
    My Setup:
    Server01: Server 2012 Standard + Exchange 2013 Standard
    Server02: Server 2012 Standard + Exchange 2013 Standard
    DAG Enabled.
    Well I'm wondering the best way to Install Windows Updates.
    Which Server first? the Passive or Active node of Databases?
    because after a Windows Update there are reboots required, what is the best practise when installing Windows Updates.
    Thank You!

    Hi,
    There is no order in a DAG because there is no "active server" or "passive server", there is only servers that host either active or passive database copies. So when updating a DAG member you should make sure it is only hosting passive database copies at
    the time.
    Per my known, if the server need be restarted after installing certain Windows update, I suggest you run the maintenance scripts to avoid some unexpected situation.
    Here is a related thread which can help you for your reference.
    http://social.technet.microsoft.com/Forums/en-US/ff206f9c-6e39-4bae-ac1d-1b9d9b465854/best-practices-for-patching-exchange-2010-servers?forum=exchange2010
    Hope this helps.
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Lync integration not working after Exchange 2013 SP1 is installed...

    Hi,
    I have two Exchange 2013 servers running and everything is fine, almost.
    The problem is that on the first server we had OWA with Lync integration working before installing SP1, but after the installation of SP1, it doesn't Work any more.
    The second server was installed with SP1 from the start, but we can't get the Lync integration to Work on this one either..
    When we log in to OWA, it just starts to sign in but then says "there was a problem signing in, if this continues please contact your helpdesk"
    I have checked the Exchange server for events, and i can see the event ID 112 everytime i recycle the Application Pool, so there are some connection between Exchange and Lync..
    Have any of you Guys seen or experienced any thing like this?
    Thanks in advance.
    Regards
    Kenneth

    Hi,
    I recommend that you refer to the following article to troubleshoot the issue:
    Troubleshooting tips for Exchange 2013 OWA IM Integration to Lync 2013
    This post describes how to configure Exchange 2013 OWA to have IM integration to Lync 2013. Here I would like to give some troubleshooting tips in case you can't get the integration to work.
    In addition, here is a similar thread for your reference:
    Lync 2013 with Exchange 2013 SP1 OWA integration failed   
    Hope this helps!
    Thanks.                              
    Niko Cheng
    TechNet Community Support

Maybe you are looking for

  • Itunes Radio does not operate on my IPad.  All stations are unavailable

    I have downloaded the newest version of ITunes on both my IPhone and IPad.  I can use ITunes Radio on my IPhone, but not my IPad.  It comes up, but all the stations say that they are unavailable.  I am at home with wi-fi.  What's going on?

  • Default large Excel file to client application rather than prompting for PowerBI

    I have a user working with OneDrive for Business to share a 13MB Excel file that contains PowerPivot data.  When a user clicks the shared link or the guest link they receive this message: We cannot determine a way to open this file in the Excel clien

  • Adobe acrobat pro 9.5.5 incompatibility with preview

    anybody having incompatibility btwn these two programs?  when I edit a PDF in Acrobat Pro 9.5.5, like this: and then open the edited PDF in Preview, it looks like this: text boxes disappear, arrows disappear, some text turns to nonsense (here's anoth

  • IDoc to File scenario Monitoring Problem

    Hi, I have a problem in monitoring. In my IDoc to file scenario the ftp server is not reachable (wrong ip) but still in sxmb_moni I get a successful processed message with acknowledgement system error. Now, why dont I get an normal error in sxmb_moni

  • Why can't I install 10.10.3 update?

    I currently have OS 10.10.2 and have downloaded 10.10.3 but can't get it installed. I did restart my computer. Any suggestions?