Installation of Service Pack 3 on Exchange 2010 Fails

Hello Everyone and thank you in advance for any advice.
I am trying to install exchange SP3 on an Exchange 2010 server. I have One Exchange server has Mailbox, Client Access and Hub Transport on it.
We had one exchange 2003 server and then installed a new hardware/software server and put Exchange 2010 standard on it. We followed all the upgrade KB articles we could find. After we were done, we then waited for Pub folders and OAB to sync. We then decommissioned
the old 2003 exchange server, removed it from the domain and disconnected all legacy mailbox stores.
We are not trying to install Exchange SP3 and below is the error we get. I may point out that I am suspicious it may have something to do with our email address policy because when I go to Organization Configuration > Hub Transport there is
nothing in the email Address Policies Tab and then I get a warning;
Microsoft Excahnge Warning
Warning
Get-EmailAddressPolicy
Warning: Recipient policy objects that don't contain e-mail address won't be show unless you include the includemailbopxsettingonlypolicy parameter in the Get-EmailAddressPolicy cmdlet.
Well I run it in the poweshell and I can see it but doesn't tell me anything. Anyway back to my issue when trying to install SP3. I get the following error.
Summary: 15 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:03
Organization Preparation
Failed
Error:
The following error was generated when "$error.Clear();
          Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
          $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
          $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
          $index = $defaultSmtpTemplate.IndexOf("@") + 1;
          $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index);
          $acceptedDomains = Get-AcceptedDomain;
          $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq $eapAuthoritativeDomain -or $_.DomanName -eq "*.$eapAuthoritativeDomain" };
          # If an accepted domain couldn't be found which matches the default email address policy, then try and find
          # the wildcard domain which matches it and set that as the default
          While ($defaultDomain -eq $null -and $eapAuthoritativeDomain.Contains(".")) {
              $index = $eapAuthoritativeDomain.IndexOf(".") + 1;
              $eapAuthoritativeDomain = $eapAuthoritativeDomain.Substring($index);
              $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq "*.$eapAuthoritativeDomain" };
          $defaultDomain | set-accepteddomain -MakeDefault:$true;
          Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
        " was run: "The operation couldn't be performed because object 'Default Policy' couldn't be found on (DNS Server Name.domain.com).".
The operation couldn't be performed because object 'Default Policy' couldn't be found on
'DNS Server Name.domain.com.'
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
Error:
The following error was generated when "$error.Clear();
          Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
          $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
          $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
          $index = $defaultSmtpTemplate.IndexOf("@") + 1;
          $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index);
          $acceptedDomains = Get-AcceptedDomain;
          $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq $eapAuthoritativeDomain -or $_.DomanName -eq "*.$eapAuthoritativeDomain" };
          # If an accepted domain couldn't be found which matches the default email address policy, then try and find
          # the wildcard domain which matches it and set that as the default
          While ($defaultDomain -eq $null -and $eapAuthoritativeDomain.Contains(".")) {
              $index = $eapAuthoritativeDomain.IndexOf(".") + 1;
              $eapAuthoritativeDomain = $eapAuthoritativeDomain.Substring($index);
              $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq "*.$eapAuthoritativeDomain" };
          $defaultDomain | set-accepteddomain -MakeDefault:$true;
          Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
        " was run: "You cannot call a method on a null-valued expression.".
You cannot call a method on a null-valued expression.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
Error:
The following error was generated when "$error.Clear();
          Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
          $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
          $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
          $index = $defaultSmtpTemplate.IndexOf("@") + 1;
          $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index);
          $acceptedDomains = Get-AcceptedDomain;
          $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq $eapAuthoritativeDomain -or $_.DomanName -eq "*.$eapAuthoritativeDomain" };
          # If an accepted domain couldn't be found which matches the default email address policy, then try and find
          # the wildcard domain which matches it and set that as the default
          While ($defaultDomain -eq $null -and $eapAuthoritativeDomain.Contains(".")) {
              $index = $eapAuthoritativeDomain.IndexOf(".") + 1;
              $eapAuthoritativeDomain = $eapAuthoritativeDomain.Substring($index);
              $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq "*.$eapAuthoritativeDomain" };
          $defaultDomain | set-accepteddomain -MakeDefault:$true;
          Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
        " was run: "You cannot call a method on a null-valued expression.".
You cannot call a method on a null-valued expression.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
Error:
The following error was generated when "$error.Clear();
          Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
          $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
          $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
          $index = $defaultSmtpTemplate.IndexOf("@") + 1;
          $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index);
          $acceptedDomains = Get-AcceptedDomain;
          $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq $eapAuthoritativeDomain -or $_.DomanName -eq "*.$eapAuthoritativeDomain" };
          # If an accepted domain couldn't be found which matches the default email address policy, then try and find
          # the wildcard domain which matches it and set that as the default
          While ($defaultDomain -eq $null -and $eapAuthoritativeDomain.Contains(".")) {
              $index = $eapAuthoritativeDomain.IndexOf(".") + 1;
              $eapAuthoritativeDomain = $eapAuthoritativeDomain.Substring($index);
              $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq "*.$eapAuthoritativeDomain" };
          $defaultDomain | set-accepteddomain -MakeDefault:$true;
          Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
        " was run: "You cannot call a method on a null-valued expression.".
You cannot call a method on a null-valued expression.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
Error:
The following error was generated when "$error.Clear();
          Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
          $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
          $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
          $index = $defaultSmtpTemplate.IndexOf("@") + 1;
          $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index);
          $acceptedDomains = Get-AcceptedDomain;
          $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq $eapAuthoritativeDomain -or $_.DomanName -eq "*.$eapAuthoritativeDomain" };
          # If an accepted domain couldn't be found which matches the default email address policy, then try and find
          # the wildcard domain which matches it and set that as the default
          While ($defaultDomain -eq $null -and $eapAuthoritativeDomain.Contains(".")) {
              $index = $eapAuthoritativeDomain.IndexOf(".") + 1;
              $eapAuthoritativeDomain = $eapAuthoritativeDomain.Substring($index);
              $defaultDomain = $acceptedDomains | Where {$_.DomainName -eq "*.$eapAuthoritativeDomain" };
          $defaultDomain | set-accepteddomain -MakeDefault:$true;
          Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
        " was run: "Cannot bind argument to parameter 'Identity' because it is null.".
Cannot bind argument to parameter 'Identity' because it is null.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.123.3&e=ms.exch.err.Ex88D115&l=0&cl=cp
Elapsed Time: 00:00:04Preparing Setup
Cancelled
Stopping Services
Cancelled
Languages
Cancelled
Remove Exchange Files
Cancelled
Preparing Files
Cancelled
Copy Exchange Files
Cancelled
Language Files
Cancelled
Restoring services
Cancelled
Languages
Cancelled
Hub Transport Role
Cancelled
Client Access Role
Cancelled
Mailbox Role
Cancelled
Management Tools
Cancelled
Finalizing Setup
Cancelled
Thanks again everyone.
P.S. I have taken the info below from the setup log. I am guessing my whole issue is with default policy
[01/30/2014 21:31:22.0289] [2] [ERROR] Unexpected Error
[01/30/2014 21:31:22.0289] [2] [ERROR] The operation couldn't be performed because object 'Default Policy' couldn't be found on 'DNS_Server.domain.com'.
[01/30/2014 21:31:22.0289] [2] Ending processing get-EmailAddressPolicy
[01/30/2014 21:31:22.0351] [2] Active Directory session settings for 'Get-AcceptedDomain' are: View Entire Forest: 'True', Configuration Domain Controller: 'DNS_Server.domain.com', Preferred Global Catalog: 'DNS_Server.domain.com', Preferred Domain Controllers:
'{ DNS_Server.domain.com }'
[01/30/2014 21:31:22.0351] [2] Beginning processing Get-AcceptedDomain
[01/30/2014 21:31:22.0351] [2] Searching objects of type "AcceptedDomain" with filter "$null", scope "SubTree" under the root "$null".
[01/30/2014 21:31:22.0351] [2] Previous operation run on domain controller 'DNS_Server.domain.com'.
[01/30/2014 21:31:22.0351] [2] Preparing to output objects. The maximum size of the result set is "unlimited".
[01/30/2014 21:31:22.0351] [2] Ending processing Get-AcceptedDomain
[01/30/2014 21:31:22.0367] [2] Active Directory session settings for 'Set-AcceptedDomain' are: View Entire Forest: 'True', Configuration Domain Controller: 'DNS_Server.domain.com', Preferred Global Catalog: 'DNS_Server.domain.com', Preferred Domain Controllers:
'{ DNS_Server.domain.com }'
[01/30/2014 21:31:22.0367] [2] Beginning processing set-accepteddomain -MakeDefault:'True'
[01/30/2014 21:31:22.0382] [2] Ending processing set-accepteddomain
[01/30/2014 21:31:22.0382] [2] Default domain 
[01/30/2014 21:31:22.0382] [1] The following 5 error(s) occurred during task execution:
[01/30/2014 21:31:22.0398] [1] 0.  ErrorRecord: The operation couldn't be performed because object 'Default Policy' couldn't be found on 'DNS_Server.domain.com'.
[01/30/2014 21:31:22.0398] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ManagementObjectNotFoundException: The operation couldn't be performed because object 'Default Policy' couldn't be found on 'DNS_Server.domain.com'.

Hi Martina, we no longer have the system Manager anymore for the EX2003 server. But I looked in adsi edit - in
the value msExchPolicyOptionList and
the value reads <not set>, so nothing to delete there. 
I also tried "Upgrade
the Default E-Mail Address Policy from LDAP Filters to OPATH Filters" and when i run the command 
Set-EmailAddressPolicy "Default Policy" -IncludedRecipients AllRecipientscomes back with "The operation can't be performed on the default e-mail address policy."So i ran Get-EmailAddressPolicyComes back with Warning: Recipient policy objects that don't contain email address wont be shown unless you include the IncludeMailboxSettingOnlyPolicy parameter in the Get-EmailAddressPolicy cmdlet.I then include the command it wants then it returnsNAME=Default Policy Priority=Lowest RecipientFilter=Alias -ne $null Then someone suggested to run "Get-EmailAddressPolicy "Default Policy" | FL"after running command above I get The operation coudn't be performed because object "Default Policy" Couldn't be found "DNSServer.Domain.COMANY other advice is welcome and appreciated.

Similar Messages

  • Errors when trying to install Service Pack 3 for Exchange 2010

    I have 2 Exchange 2010 servers that are running SP2 and I am trying to install SP3 on both.
    They are installed in a DAG and so I am running the .\StartDAGserverMaintenance.ps1 script before attempting to install SP3.  When attempting to run the SP3 setup I get the following errors:
    Setup cannot continue with the upgrade because the 'powershell' (Machine: P-E10-2.company.com) process (ID: 5296) has open files. Close the process and restart Setup.
    AND
    Install hotfix Microsoft Knowledge Base article 2550886 from http://support.microsoft.com/kb/2550886 to improve Windows Failover Cluster transient communication instability when deploying stretched Database Availability Groups across datacenters.
    I can download the hotfix and apply it but has anyone had any issues with this particular hotfix?  Does anyone have any ideas about the powershell error?
    thanks for your help.

    Hi,
    That hotfix relates to a known issue implementing DAG's across data centres (an issue particularly with Windows failover clustering). As a best practice is should always be installed. Please review the following article, which describes why it should be
    installed:
    http://blogs.technet.com/b/exchange/archive/2011/11/20/recommended-windows-hotfix-for-database-availability-groups-running-windows-server-2008-r2.aspx
    In regards to the open files, as the other poster suggested, there will be another user logged onto the server who has a powershell window open. Ensure all other users are logged off the server before performing the upgrade.
    Best Regards

  • BSP does not show up after installation of service pack 9 on BW 7.0

    Hi,
    We are working on netweaver 2004s.
    We have a very simple BSP page, which has been developed in BW box. Its just used to load flat files to the application server.
    It was working well when we were at service pack 8. Recently we have installed service pack 9 and this BSP page either through portal or directly in web-browser does not show up at all i.e all we see is a blank page and the status bar of the browser keeps running forever.
    Could you please advise what has gone wrong and is there a fix to this.
    Note: other 2 BSP pages in the same BW system are working fine.
    kind regards,
    Waseem.

    Hi Raja,
    Thanks for your prompt reply.
    I activated the BSP page and re-tested but it does not work.
    When I activate in SE80, I get the message 'Active object generated'.
    When I run it through portal or web-browser ... it does not show any message but the status bar of the browser keeps moving .... forever, indicating its doing something.
    There are other 2 BSP pages which are working fine, but this BSP page ( which is the most important) is giving this porblem.
    kind regards,
    Waseem.

  • Exchange 2010 failing to upgrade to SP1, SP2, or SP3

    My host server is running Windows Server 2008 R2 Standard. Currently Exchange 2010 is without any service pack. I initially tried to upgrade to SP1 but that failed with the message below. Thinking that I could perhaps skip to SP2 or even SP3 I attempt that
    upgrade and received a similar message though not posted here. The Schema for our domain shows that it is at the Windows Server 2008 R2 level. I am attempting to apply the update using the Enterprise/Schema admin account for our network.
    Here is the error message that I receive. This happens after all prereq checks are done and the installation has actually started.
    Summary: 15 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:00:04
    Organization Preparation
    Failed
    Error:
    The following error was generated when "$error.Clear();
    Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
    $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
    $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
    $index = $defaultSmtpTemplate.IndexOf("@");
    $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index+1);
    $defaultDomain = get-accepteddomain | where {$_.DomainName -eq $eapAuthoritativeDomain };
    $defaultDomain | set-accepteddomain -MakeDefault:$true;
    Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
    " was run: "The operation couldn't be performed because object 'Default Policy' couldn't be found on 'marvin.intercity.org'.".
    The operation couldn't be performed because object 'Default Policy' couldn't be found on 'marvin.intercity.org'.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=m...
    Error:
    The following error was generated when "$error.Clear();
    Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
    $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
    $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
    $index = $defaultSmtpTemplate.IndexOf("@");
    $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index+1);
    $defaultDomain = get-accepteddomain | where {$_.DomainName -eq $eapAuthoritativeDomain };
    $defaultDomain | set-accepteddomain -MakeDefault:$true;
    Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
    " was run: "You cannot call a method on a null-valued expression.".
    You cannot call a method on a null-valued expression.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=m...
    Error:
    The following error was generated when "$error.Clear();
    Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
    $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
    $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
    $index = $defaultSmtpTemplate.IndexOf("@");
    $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index+1);
    $defaultDomain = get-accepteddomain | where {$_.DomainName -eq $eapAuthoritativeDomain };
    $defaultDomain | set-accepteddomain -MakeDefault:$true;
    Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
    " was run: "You cannot call a method on a null-valued expression.".
    You cannot call a method on a null-valued expression.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=m...
    Error:
    The following error was generated when "$error.Clear();
    Write-ExchangeSetupLog -Info "Set the default Accepted domain from the default recipient policy";
    $defaultEmailAddressPolicy = get-EmailAddressPolicy -Identity:"Default Policy";
    $defaultSmtpTemplate = $defaultEmailAddressPolicy.EnabledPrimarySMTPAddressTemplate;
    $index = $defaultSmtpTemplate.IndexOf("@");
    $eapAuthoritativeDomain = $defaultSmtpTemplate.Substring($index+1);
    $defaultDomain = get-accepteddomain | where {$_.DomainName -eq $eapAuthoritativeDomain };
    $defaultDomain | set-accepteddomain -MakeDefault:$true;
    Write-ExchangeSetupLog -Info "Default domain $defaultDomain";
    " was run: "Cannot bind argument to parameter 'Identity' because it is null.".
    Cannot bind argument to parameter 'Identity' because it is null.
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=m...
    Elapsed Time: 00:00:04
    Preparing Setup
    Cancelled
    Stopping Services
    Cancelled
    Languages
    Cancelled
    Remove Exchange Files
    Cancelled
    Preparing Files
    Cancelled
    Copy Exchange Files
    Cancelled
    Language Files
    Cancelled
    Restoring services
    Cancelled
    Languages
    Cancelled
    Hub Transport Role
    Cancelled
    Client Access Role
    Cancelled
    Mailbox Role
    Cancelled
    Management Tools
    Cancelled
    Finalizing Setup
    Cancelled

    Agreed - check the default email address policy is not corrupt and same for remote domains - did you make ay modifications to them?
    Since he is running this as das Uber-admin, it will prep Exchange schema and AD even if not explicitly done prior.  Exchange setup is helpful like that, well some times....
    Cheers,
    Rhoderick
    Microsoft Senior Exchange PFE
    Blog:
    http://blogs.technet.com/rmilne 
    Twitter:   LinkedIn:
      Facebook:
      XING:
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

  • Exchange 2010 failing during setup - Managment Tools

    Hello,
    I am hoping that someone can assist me with this error I am getting while trying to install Exchange 2010 on server 2008 R2. It seems that towards of the installation of the Management Tools it fails. Please see my screenshot. Any assistance would be appreciated.
    Here are the steps that I have taken to troubleshoot:
    Uninstalled exchange failed install
    attempted to reinstall - fail
    The firewall was turned off so I turned it back on because I read that someone else had the same issue and it worked for them.
    So far nothing is working for me. I installed Exchange once before as a VM and didn't have any issues at all.
    Phil Balderos

    Hi
    Did you set the service to automatic and start it? Did you reboot the server after that and then run the setup again?
    Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thanks Ed,
    When I first built the VM I stopped the firewall server then disabled it. So when I had to start troubleshooting this issue I started the fire wall and then and set the startup type to manual. I did reboot the server several times when I had to
    uninstall the failed installation.
    Phil Balderos

  • Error Installing Service Pack 3 for Exchange Server 2010 (Hub Transport)

    I get the following error;
    "[ERROR] Couldn't remove product with code 4934d1ea-be46-48b1-8847-f1af20e892c1. Fatal error during installation. Error code is 1603.
    This is one of two Hub Transport only servers. The Client Access servers upgrade without a problem.
    Thanks,
    Randel

    Hi,
    Based on my research, to remove the error, here is a solution you can refer to:
    1. Run the MsiExec.exe /X {4934d1ea-be46-48b1-8847-f1af20e892c1} to uninstall the Microsoft Full Text Indexing Engine for Exchange.
    2.  Manually start the World Wide Web Publishing Service and IIS Admin Service then run the setup again.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Error while using web service pack to deploy exchange agent

    Hi all,
    I have a problem of deploying exchange agent before creating exchange source in SES.
    OS : Windows Server 2003 R2
    The exchange server was installed successfully, I follow the steps below to create the exchange agent:
    1. unzip $ORACLE_HOME/search/lib/plugin/msexchange/ExchangeWebService.zip to the exchange server(I want to deploy exchange agent and server on the same machine).The path is c:\EXWEBService
    2. Enter IIS Manager, Activate all extended services.
    3. Right click default website to create a virtual directory:
    Name : EXWEBService
    Path : c:\EXWEBService
    Access permission: Check 1,2 & 3 checkboxs.
    4. After creating the virtual directory, right click on it , select property from the popup menu.
    5. Enter Directory security Tab.Click the first 'EDIT' button.
    6. Input the domain\username & password.
    7. Click ASP.NET Tab, set ASP.NET version as 2.0.x and click “Apply”.
    8. After applying, Click “Edit Configuration”.
    9. Input the Application Setting, and click 'Apply'.
    10.Click “Application” tab, Check “Local impersonation”, and input exchange domain\administrator & password.
    11. Execute the command : "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\gacutil.exe /i adodb.dll"
    The last step -> Test it:
    Select the site just create and Right-click ExchangeHttpsService.asmx and choose “Browse”. An error page shows.
    Configuration Error
    Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
    Parser Error Message: An error occurred creating the configuration section handler for system.web/httpHandlers: The type initializer for 'System.Web.Configuration.HttpHandlerAction' threw an exception.
    Source Error:
    Line 150: </healthMonitoring>
    Line 151:
    Line 152: <httpHandlers>
    Line 153: <add path="trace.axd" verb="*" type="System.Web.Handlers.TraceHandler" validate="True" />
    Line 154: <add path="WebResource.axd" verb="GET" type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
    Source File: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\web.config Line: 152
    Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42
    Is there someone encounter the problem?
    null
    null

    OMG, Sorry, I read a document which was out of date!

  • Service Pack Update Upgrade Status showing failed

    I have SharePoint 2010 Server. I upgraded the same to SP2. In upgrade status it shows failed but once I run command 
    (get-spserver $env:computername).NeedsUpgrade.
    It shows false. How to check if patch is successful? 
    Please remember to mark the replies as answers or vote as helpful if they help.

    Hi,
    From your description, my understanding is that upgrade status shows failed when you upgrade SharePoint, but when you run PowerShell Command, it shows “false”.
    Have you run the SharePoint Configuration wizard again after the status shows failed,  then check if it will show successful status?
    As upgrade status is failed, you should check if there are some error message in your USL log.
    In addition, you could check the version of SharePoint if it is upgraded to the correct version number.
    Best Regards
    Vincent Han
    TechNet Community Support

  • Trying to install SP1 for Exchange 2010 on Win Server 2008 R2. A pre-req is KB982867. It is no where to be found. How to find it?

    The SP1 wizard says "Install Hotfix Microsoft Knowledge Base article 982867 from http://code.msdn.microsoft.com/KB982867
    However, that link no longer exists.
    How to get this hotfix?
    Another post said that the Win 7 hotfix would work. Windows6.1-KB982867-v2-x64 But I can't locate that either.
    How to fix?
    john11

    Hi John,
    Exchange 2010 Service Pack 3 is the latest service pack. It is recommended to install it. Service Packs are cumulative, Exchange 2010 SP3 includes all fixes included in previous RUs and service packs. Here is a blog for your reference:
    Exchange Server 2010 SP3
    http://blogs.technet.com/b/exchange/archive/2013/02/12/released-exchange-server-2010-sp3.aspx
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Need to update Exchange 2010 to SP1 from base

    I need to update my base install of Exchange 2010 to SP1 and eventually SP2. This sits on a 2008 R2 server. in reading other upgrade articles, there are references to needing hotfixes at the server level - 2008 R2. There are about 5 hot fixes referenced
    to upgrade to SP1 and I would assume there are a few others for the update to SP2.
    Currently the 2008 R2 server is patched via Windows update through February 2014 (including SP1 for the server). Given that, can I assume that the hot fix updates have been incorporated into other updates/patches along the way for the Windows 2008 R2
    server? Or do i still have to install each of those hotfixes manually?
    Also, in one of the patches, it spoke of needing, or using .net framework 2.0 and 3.51. currently my system has 4.5.1 on it. do i need 2.0 and 3.51 for SP1 to be installed and work correctly?
    thanks
    dave

    Hi Dave,
    I recommend you install Exchange 2010 SP3 directly. There is no need to upgrade to Exchange 2010 SP1 and then to SP2.
    Service Packs are cumulative, Exchange 2010 SP3 include all fixes included in previous RUs and service packs. Here is a blog for your reference.
    Released: Exchange Server 2010 SP3
    http://blogs.technet.com/b/exchange/archive/2013/02/12/released-exchange-server-2010-sp3.aspx
    Since Windows updated through February 2014, you don't need to install each of those hotfixes manually.
    Besides, I would like to verify if you download .net framework 4.5.1 from website. There is no need to install it that way. You just need to open Server Manager, add .Net Framework 3.5.1 feature.
    Hope my clarification is helpful.
    Best regards,
    Amy
    Amy Wang
    TechNet Community Support

  • Exchange 2010 Rollup 2 SP3 update cannot find installation package exchangeserver.msi file on SBS 2011... NEED HELP!!!

    Hello,
    I am running a windows SBS 2011 standard system and there was currently an update for Exchange 2010 Rollup 2 Service Pack 3 and it keeps failing.  It says that it cannot find the installation package (exchangeserver.msi) and it is looking for it
    in E:\Software\Exchange2010-SP3-x64\ folder but there never was this folder.  There is only an Exchange2010-SP3-x64.exe file.
    The only exchangeserver.msi file that I find on the server any where is in C:\ProgramFiles\Windows Small Business Server\Bin\CMPNENTS\EXCHANGE14_SP1 but it won't accept it (says not authorized for this update or something alike).
    Please help.  It is currently causing issues with email.  Some of the features are not working because it says exchange is currently under maintenance.
    Any suggestions would be greatly appreciated.  Thank you.

    Susan you are correct:  After I installed Exchange 2010 SP3, I deleted the msi just to "clean up' my hard disk...  While trying to install Rollup 2 for SP3, the installer is trying to find it.  I downloaded the installer, used 7-zip to get
    the msi and I pointed the installer to it when asked.
    The installation failed 3 times... 
    NOTE: I was using WSUS to install the Rollup:  I downloaded the Rollup installer and I executed:  I could see where the installer was hanging up!  First it asked me to stop an SBS service and something else (sorry I do not remember), I stopped
    the services and installation continued.  Then it asked me for more files from the SP3 installation which I found on the installation folder that I created with 7-zip.  I copied to the path that the installer was looking and installation finished
    (finally!)...
    NOTE 2:  If you have any firewall appliance that denies Internet access to un-authenticated requests, you better turn that rule off because the installer accesses the internet (not sure why - probably for Dot Net assemblies)...
    Susan THANKS for all your help to the community!  You have helped so much! 
    All the Best
    Constantine

  • Compatibility between Exchange 2007 service packs

    Hi all, I have 5 servers Exchange:
    - 3 Servers CAS and HUB
    - 2 Servers Mailbox server in Microsoft Failover Cluster (MSCS)
    Domain Controllers are all
    Windows Server 2003 SP2
    The versions of Exchange 2007 SP1 servers are all:
    8.1 Build 240.6
    I have thought about installing SP3 and RU13 in all 5 servers for Exchange, but I'm going to install SP3 and RU13 on 2 servers CAS / HUB and the following week at the other CAS / HUB server.
    Finally, the following week in the two Mailbox Servers.
    Is there any problem if I miss 2 servers CAS / HUB with SP3 RU13 and the other CAS / HUB in SP1, this will only be for a few days?
    Is there any problem if I leave the servidors Mailbox Servers in SP1 while CAS / HUB are in SP3 RU13, this will only be for a few days?
    regards
    Microsoft Certified IT Professional Server Administrator

    Hi Yupikaiey.
    Only thing you should be concerned is if you have CAS-CAS proxy or the Mailbox Cluster part.
    Your current plan looks good. Just stay alert for any uncommon issues popping up, which would normally mean due to the difference.
    If you upgrade your servers in this order, you may avoid potential service interruptions.
    Details below:
    Version Constrains are more of between roles of 2007-2010-2013 and not between same version SPs or RUs.
    Exchange 2013 Server Role Architecture
    The Past: Exchange 2007 and Exchange 2010
    Our goal was to make these server roles autonomous units. Unfortunately, that goal did not materialize in either Exchange 2007 or Exchange 2010. The server roles were tightly coupled along four key dimensions:
    2.This also necessitated a tight versioning alignment – a down-level Hub Transport or Client Access shouldn’t communicate with a higher version Mailbox server; in some cases this was enforced (e.g., Exchange 2007 Hub Transport servers cannot deliver messages
    to Exchange 2010 Mailbox servers), but in other cases they were not (e.g., an Exchange 2010 SP1 Client Access server can render data from an Exchange 2010 SP2 Mailbox server).
    The versioning restriction also meant that you could not simply upgrade a single server role to take advantage of new functionality – you had to upgrade all of them.
    The Present: Exchange Server 2013
    If I upgrade the Mailbox server with a service pack or cumulative update, then for a given mailbox hosted on that server, all data rendering and content conversions for that mailbox will be local, thus removing version constraints and functionality issues
    that arose in previous releases.
    Exchange 2007 Servicing
    http://technet.microsoft.com/en-in/library/dd421853(v=exchg.80).aspx
    Deployment Order
    Our test infrastructure guarantees that Exchange hotfixes work across multiple server roles. The order in which you apply the update rollup to the servers is not important except if you are deploying CAS-CAS proxying. Because the update rollups are not segmented
    for different Exchange server roles or for specific file configurations, apply each update rollup package to all Exchange 2007 servers in your environment.
    If you have multiple Active Directory sites, and if you deploy a Client Access server in the proxy sites that do not face the Internet, you must
    apply the update rollup to the Internet-facing Client Access servers
    and to the non-Internet-facing Client Access servers in the proxy site simultaneously. For other Exchange 2007 configurations, we recommend that you
    apply the update rollup package to the Client Access servers before
    you apply it to servers that are running other Exchange 2007 server roles, such as the Mailbox server role, the Hub Transport server role, and the Edge Transport server role.
    Note:
    Applying service packs and update rollups to clustered Mailbox servers requires specific planning and application steps. For more information about how to apply service packs to Exchange 2007 clustered Mailbox servers, see
    Upgrading Clustered Mailbox Servers to Exchange 2007 SP1 or later. For more information about how to apply update rollups to Exchange 2007 clustered Mailbox servers, see
    Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers.
    For Patching and compatibility between versions:
    Determine the service pack level of Exchange. 
    Update rollups are service pack dependent. For example, an Update Rollup 5 package is available for Exchange 2007 and for Exchange 2007 Service Pack 1. To determine the service pack level of Exchange, examine the
    ExchangeVersion property. For more information about how to view the
    ExchangeVersion property and about the build number that is associated with each Exchange version, see
    Exchange Server 2007: Platforms, Editions, and Versions.
    References:
    How to Install the Latest Service Pack or Update Rollup for Exchange 2007
    Exchange Server Updates: build numbers and release dates
    We are looking at doing the roll-up to SP3
    Coexistence of Exchange2007 SP1 and Exchange 2007 SP3
    Regards,
    Satyajit
    Please “Vote As Helpful”
    if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

  • Exchange 2010 Management Pack Data Warehouse Synchronization Fails

    Hi Everyone!
    Has anyone had success with importing the Exchange 2010 management pack into Service Manager 2012?
    When we try to import it, it fails.
    Upon further investigation, the 'System Center Core Monitoring' management pack (which is not included with Service Manager 2012) is a dependency of the Exchange 2010 management pack but
    after we import it from the OpsMgr 2012 media, we still get the following warning when we import the  Exchange 2010 management into Service Manager 2012...
    "The management pack was imported successfully.
    Warnings (1):
    Override verification failed, cannot find Management Pack Element : : Cannot find ManagementPackElement [Type=ManagementPackRule, ID=Microsoft.SystemCenter.Agent.MonitoringHost.PrivateBytesThreshold] in management pack ManagementPack:[Name=Microsoft.SystemCenter.2007,
    KeyToken=31bf3856ad364e35, Version=6.0.6246.0]."
    ...and, the Exchange 2010 management pack status in the Service Manager 2012 Data Warehouse 'Management Pack' view indicates 'failed' after the MPSyncJob completes.
    We have a few 'Business Services' which depend on the Exchange 2010 management pack that we are trying to synchronize from OpsMgr 2012 and we are stuck until we can get the Exchange 2010 management
    successfully imported into Service Manager 2012 and have it show a status of 'Completed'  the Service Manager 2012 Data Warehouse 'Management Pack' view.
    Nothing useful in the
     Service Manager 2012 Data Warehouse and Management servers events logs that we could see.
    Any help or guidance would be GREATLY appreciated!
    Regards,
    JJ

    Update: I Just tested with CU2 installed for SrvMgr 2012 and OpsMgr 2012 and version 14.3.38.2 of the Exchange 2010 management, but the management pack still fails to deploy to the SrvMgr 2012 data warehouse (the management pack status shows
    up as 'failed' and the MPSyncJob shows the management pack as 'pending association').  The only clue I have for this problem is the folllowing warning which occurs when I import the management pack into SrvMgr 2012...
    I also get the following 33519 Event ID warning in the Operations Manager event log on the data warehouse server...
    ~~~~~
    Management pack association ignored. This does not require any action. If you continue to frequently see this warning, contact your administrator. This process will continue to retry.
    Management pack ID: e2296ed5-ddbc-ebc7-3881-c5288adaa7cf
    Management pack name: Microsoft.Exchange.2010
    Management pack version: 14.3.38.2
    Data source name: SRV 
    Message: Either the MP has failed deployment Or any of its references has failed deployment
    ~~~~~
    Has anyone had success with getting the Exchange 2010 management pack imported and successfully deployed to the SrvMgr 2012 data warehouse?  
    The good news is that even though the Exchange 2010 management pack has a status of failed, the distributed applications in OpsMgr 2012 that depend on the Exchange management pack now show up under Configuration Items/Business Services including
    all related service component objects which was what I was trying to accomplish in the first place, so for now I'll just leave the Exchange 2010 management pack in the data warehouse with a failed status.
    Regards,
    JJ

  • MSCS SQL Server Service Pack Installation

    Dear All,
    We are using Microsoft Cluster and i completed Microsoft SQL Server 2005 Installation on Cluster.
    Now when i am trying to Install Service Pack 2 of SQL Server i can't get success when both node are running.
    But when i swhiched off Node 2 and did installation on Node 1 i get success.
    But after finishing Installation on Service Pack 2 i can't get that service pack on Node 2.
    Here i want to confirm that i have to do installation of Service Pack 2 on both node ?
    Regards,
    Nikunj Thaker.

    Hi,
    Have you run the SQL 2K5 SP2 upgrade on the other node. What happens is that you upgrade the SQL Server binaries on the Clustered instances but not the local files.
    If you run SP2 on the "Passive" node it will upgrade server compoments that are not cluster aware (like SSIS). I normally upgrade the Client Components first on the passive node, reboot and then upgrade all components on the active node afterwards.
    On a standalone machine - all components are upgraded at the same time - both per instance and the server components so you won't have that issue.
    --Kishore

  • Does Service Pack installation modify the repository db ?

    Hello,
    Does anybody know if installation of Service Packs on a old XI R2 platform modify in some way the repository database ?
    The purpose of this question is this :
    My production platform is XI R2 SP1, and I would like to upgrade to SP4 without any risk for my users.
    To do that, I wonder if building a new platform with SP4, testing, and then shutting down the old CMS and linknig the new CMS to the production repository would work.
    It should be the case if SP doesn't need new structure or data on the repository database...
    Can anybody confirm that this works ?
    Thanks in advance

    Hi Francois,
    I presume you're on some flavor of Windows. If that's the case, do the following to copy the CMS db (once your new system is up and working):
    1. Stop the CMS from the CCM.
    2. Right-click on the CMS --> Properties.
    3. Switch to the configuration tab.
    4. In the CMS Data Source section, click on Specify.
    5. Select Copy data from another Data Source.
    This will copy data from your Production data source to your new environment.
    As for the FRS, you do not need to copy the FRS folders. Once your CMS db is copied, you only need to point the I/O FRS of your new (SP4) environment to the FRS locations of your old(SP1) environment.
    Please do ensure that everything is backed up though (i.e. FRS folder structure and CMS db).
    Also, if Auditing is enabled on your SP1 deployment, it would be best to turn off auditing before stopping the CMS, copying the CMS db.
    Best,
    Srinivas

Maybe you are looking for

  • Firefox opens in task manager but does not display.

    This morning my Firefox stopped working and I had to end task. Afterwards when trying to restart Firefox the firefox process will open under task manager but nothing displays on the screen. I've tried ending all firefox processes and restarting my pc

  • Error in third party sales

    Dear Raja, Thanks for  give me good solution in third party sales, But it was half is done. What you told is Key-in Country Code: IN, and "Exter" Key-in Tax Code: VN, and "Enter" At Top, Click Tab: Tax Accounts. Key-in Charts of Accounts. Give the G/

  • .Mac Web Gallery - How to change key photo and order or galleries?

    How can I choose which photo is the key photo for each .Mac web gallery? Also, how can I re-arrange the order of the web galleries?

  • Logging of Forwarded HTTP Requests using RequestDispatcher in Weblogic

    Can anyone help me on this? Logging of Forwarded HTTP Requests using RequestDispatcher in Weblogic Access Log File: 1. I have a servlet(S1) which decides which JSP to be published based on some logic. If I try to forward the request from a servlet to

  • Right content.jar for web service API?

    I have a java application that interacts with Content Services via the Content Services Web Services API. I wish to update the content-ws-client.jar file my app uses, since we have undergone several upgrades since I set my app up. When I search my ne