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

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

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

Similar Messages

  • 2012 Domain Prep fails in root domain

    Hi
    We are tryiing to introduce 2012 DCs into our root domain.
    The schema has updated fine but the domain prep fails, both on the 2012 server we are trying to promote and whilst running it direct from the infrastructure server itself.
    Replication is good and AD itself seems happy enough.   The account has the necessary rights.
    Any help gratefully received.
    Thanks
    The error log contains:
    Adprep was about to call the following LDAP API. ldap_search_s(). The base entry to start the search is cn=d262aae8-41f7-48ed-9f35-56bbb677573d,cn=Operations,cn=DomainUpdates,cn=System,DC=xxxx,DC=xx,DC=xx.
    [2014/12/08:08:32:53.055]
    LDAP API ldap_search_s() finished, return code is 0x20
    [2014/12/08:08:32:53.055]
    Adprep verified the state of operation cn=d262aae8-41f7-48ed9f35-56bbb677573d,cn=Operations,cn=DomainUpdates,cn=System,DC=xxxx,DC=xx,DC=xx.
    [Status/Consequence]
    The operation has not run or is not currently running. It will be run next.
    [2014/12/08:08:32:53.055]
    Adprep was about to call the following LDAP API. ldap_modify_s(). The entry to modify is DC=xxxx,DC=xx,DC=xx.
    [2014/12/08:08:32:53.055]
    LDAP API ldap_modify_s() finished, return code is 0x13
    [2014/12/08:08:32:53.070]
    Adprep was unable to modify some attributes on object DC=xxxx,DC=xx,DC=xx.
    [2014/12/08:08:32:53.070]
    Adprep encountered an LDAP error.
    Error code: 0x13. Server extended error code: 0x20b5, Server error message: 000020B5: AtrErr: DSID-03152A9F, #1:
        0: 000020B5: DSID-03152A9F, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 9054f (otherWellKnownObjects)
    DSID Info:
    DSID: 0x181112dd
    ldap error = 0x13
    NT BUILD: 9600
    NT BUILD: 16384
    [2014/12/08:08:32:53.086]
    Adprep was unable to update domain information.
    [Status/Consequence]
    Adprep requires access to existing domain-wide information from the infrastructure master in order to complete this operation.

    Hi,
    If possible,could you please post more detail information about adprep.log?
    I noticed that the error indicates the otherWellKnownObjects attribute, it may be related the
    Managed Service Accounts container was missing.
    In order to troubleshot, please first verify that the Managed Service Accounts container was not exists in the domain.
    For more detail information, you could refer to the similar thread:
    https://social.technet.microsoft.com/Forums/windowsserver/en-US/1a7f9de4-d201-4ac6-a3e7-e396743c31fa/windows-2008r2-adprep-domainprep-fails?forum=winserverMigration
    Regards.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Installing Exchange 2013 - Domain/forest prep

    Hi guys
    I've just installed the first Exchange 2013 server in our forest.
    The server was installed in the root domain of the forest.
    We have several child domains in the forest. These contains our users.
    I haven't done any prepping in these domains.
    The painful question is: Should I have done that? And if so, can it be done post installation of Exchange 2013?
    My own test account is located in one of these child domains, and so far I haven't experienced any problems with this account using OWA.
    Just want to make sure that I'm not set up for failure later in the migration.
    Best Regards
    Klaus Ringe Nielsen
    Best regards Klaus Ringe Nielsen

    i dont think this should create an issue untill unless your DNS/AD are properly setup for your child domains also.
    MARK AS USEFUL/ANSWER IF IT DID
    Thanks
    Happiness Always
    Jatin

  • Exchange 2013 Co-Existence Fail

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

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

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

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

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

  • Exchange 2013 - schema prep (net assambly error)

    Setup.exe /prepareschema /IAcceptExchangeserverlicenseterms
    gives error:  [ERROR] An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default,
    so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See
    http://go.microsoft.com/fwlink/?LinkId=155569 for more information. ; Any hints how to solve this?
    bostjanc

    Hello,
    According to the above error, exchange setup file is copied from a network location. So please try to unblock "
    this file came from another computer and might be blocked to help protect this computer" on properties of exchange setup file.
    Please follow the Ed's suggestion to check the exchange 2013 prerequisites.
    Here is an article for your reference.
    http://technet.microsoft.com/en-us/library/bb691354(v=exchg.150).aspx
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

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

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

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

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

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

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

  • Exchange 2013 Auto Attendant fails when using multiple languages

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

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

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

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

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

  • Exchange 2013 SP1 - healthsets failing

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

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

  • Exchange 2013 IMAP Connectivity Failing

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

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

  • Exchange 2013 -DiscoveryMaxMailboxes Search Fails

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

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

  • Installing Exchange 2013 CU 6 failed

    Hello, we have a big problem with installing CU6 on a new installed exchange 2013 server. Here's the error message:
    Error:
    The following error was generated when "$error.Clear();
              if ($RoleIsDatacenter -ne $true -and $RoleIsDatacenterDedicated -ne $true)
              if (Test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)
              $sysMbx = $null;
              $name = "SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}";
              $dispName = "Microsoft Exchange";
              Write-ExchangeSetupLog -Info ("Retrieving mailboxes with Name=$name.");
              $mbxs = @(Get-Mailbox -Arbitration -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1 );
              if ($mbxs.Length -eq 0)
              Write-ExchangeSetupLog -Info ("Retrieving mailbox databases on Server=$RoleFqdnOrName.");
              $dbs = @(Get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);
              if ($dbs.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Retrieving users with Name=$name.");
              $arbUsers = @(Get-User -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);
              if ($arbUsers.Length -ne 0)
              Write-ExchangeSetupLog -Info ("Enabling mailbox $name.");
              $sysMbx = Enable-Mailbox -Arbitration -Identity $arbUsers[0] -DisplayName $dispName -database $dbs[0].Identity;
              else
              if ($mbxs[0].DisplayName -ne $dispName )
              Write-ExchangeSetupLog -Info ("Setting DisplayName=$dispName.");
              Set-Mailbox -Arbitration -Identity $mbxs[0] -DisplayName $dispName -Force;
              $sysMbx = $mbxs[0];
              # Set the Organization Capabilities needed for this mailbox
              if ($sysMbx -ne $null)
              # We need 1 GB for uploading large OAB files to the organization mailbox
              Write-ExchangeSetupLog -Info ("Setting mailbox properties.");
              set-mailbox -Arbitration -identity $sysMbx -UMGrammar:$true -OABGen:$true -GMGen:$true -ClientExtensions:$true -MailRouting:$true
    -MessageTracking:$true -PstProvider:$true -MaxSendSize 1GB -Force;
              Write-ExchangeSetupLog -Info ("Configuring offline address book(s) for this mailbox");
              Get-OfflineAddressBook | where {$_.ExchangeVersion.CompareTo([Microsoft.Exchange.Data.ExchangeObjectVersion]::Exchange2012)
    -ge 0 -and $_.GeneratingMailbox -eq $null} | Set-OfflineAddressBook -GeneratingMailbox $sysMbx.Identity;
              else
              Write-ExchangeSetupLog -Info ("Cannot find arbitration mailbox with name=$name.");
              else
              Write-ExchangeSetupLog -Info "Skipping creating E15 System Mailbox because of insufficient permission."
            " was run: "Microsoft.Exchange.ProvisioningAgent.RusException:  Failed to generate proxy address. Additional information:
    General Error.
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckReturnCode(ReturnCode rc)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.SingleProxySession.CheckProxy(RecipientInfo pRecipientInfo, String pwszProxyAddr)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CheckSingleProxy(ProxyAddressTemplate baseAddress, RecipientInfo recipientInfo, ProxyAddress oldProxyAddress)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.GenerateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
    globalCatalogSession, IEnumerable`1 baseAddresses, IEnumerable`1 oldProxies, RecipientInfo recipientInfo, ADRecipient recipient, LogMessageDelegate logger)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.ProxySession.CreateProxies(IConfigurationSession configSession, IRecipientSession recipientSession, IRecipientSession
    globalCatalogSession, IEnumerable`1 baseAddresses, ADRecipient recipient, LogMessageDelegate logger)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateEmailAddresses(List`1 allPolicies, ADRecipient recipient, LdapFilterProvider filterProvider)
       at Microsoft.Exchange.DefaultProvisioningAgent.Rus.EmailAddressPolicyHandler.UpdateRecipient(ADRecipient recipient)
       at Microsoft.Exchange.ProvisioningAgent.DefaultRUSProvisioningHandler.UpdateRecipient(ADRecipient recipient)
       at Microsoft.Exchange.ProvisioningAgent.RUSProvisioningHandler.UpdateAffectedIConfigurable(IConfigurable writeableIConfigurable)
       at Microsoft.Exchange.Provisioning.ProvisioningLayer.UpdateAffectedIConfigurable(Task task, IConfigurable writeableIConfigurable, Boolean checkProvisioningLayerAvailability)
       at Microsoft.Exchange.Configuration.Tasks.SetTaskBase`1.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.SetRecipientObjectTask`3.InternalValidate()
       at Microsoft.Exchange.Management.Common.SetMailEnabledRecipientObjectTask`3.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetUserBase`2.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetMailboxBase`2.InternalValidate()
       at Microsoft.Exchange.Management.RecipientTasks.SetMailbox.InternalValidate()
       at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
       at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
    After this error message, the exchange installation is incomplete, there is no repair possible. Also remove the installation is not possible because there is an incomplete update installed.
    Any ideas how to solve this?

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

  • Upgrade of Integation Services (Windows 2012 R2) on Windows 2008 R2 with Exchange 2013 SP1 DAG fails

    Here is the scenario:
    Legacy Host: Windows 2008 R2
    Guest VM: Windows 2008 R2 with Exchange 2013 SP1 DAG cluster.
    After importing the VM (2008 R2 and Exchange 2013 DAG) into a 2012 R2 host (Cluster).  (copy VM files to new 2012 R2host) Everything works fine.
    Then upgrading "Installation Services" (for Windows 2012 R2 host) on the imported VM runs fine with no errors to the "Restart" prompt. VM than shows: "Configuring Windows updates 32% complete. Do not turn
    of your computer." Hangs there for about 20 minutes until is says "shutting down". Hangs there for 20 minutes until power off. Restart to normal start; "Preparing to configure Windows. Do not turnoff your computer." proceeds slowly
    to "Configuring Windows updates 32% complete. Do not turn of your computer." hangs there again indefinite. Sometime hangs at shutdown cycle and "Configuring Windows updates 32% complete. Do not turn of your computer." indefinitely.
    I moved 20 other machines from a 2008 R2 host to new Windows 2012 R2 hosts all of these machines install the 2012 R2 Integration services just fine on the 2008 R2 VM. Just the 2008 R2 VMs clustered (DAG) and Exchange 2013 SP1 do not take the Integration
    Services upgrade.
    Any advise from Microsoft? I know I could decommission the DAG and Exchange machines and install Integration services on the native box before Exchange and DAG and that would sure work, but I'd rather avoid that amount of work for a simple integration layer
    upgrade.
    Thanks
    Gerhard Waterkamp ACSLA Inc.

    Hi,
    Could you try use the following method to fix this issue first?
    1. Run the System Update Readiness Tool, then check if there is any error in the Checksur.log and checksur.persist.log.
     1. Please run the System Update Readiness Tool on this affected server. Please download this tool from the following Microsoft article:
     Description of the System Update Readiness Tool for Windows Vista, for Windows Server 2008, and for Windows 7
     http://support.microsoft.com/kb/947821/en-us
    2. The System Update Readiness Tool creates the log files that captures any issues that the tool found or fixed. The log files are located at the following location:
    %SYSTEMROOT%\Logs\CBS\
    3. Please paste the checksur.log here for analysis.
    If there is no error found, please try the following step.
    ==================================
    2. Use Fix it tool to reset the Windows Update components.
     1. Open the following link.
     http://support.microsoft.com/kb/971058/en-nz
     2. Select Windows 8.1, Windows 8 and Windows 7 in the product selection box.
     3. Click “Run Now” to reset the Windows Update components.
    Note: We can reset the Windows Updates manually by following the steps in the KB above.
    3. Use the System File Checker tool to repair missing or corrupted system files
     1. Open the command promote with Administrators.
     2. At the command prompt, type the following command, and then press ENTER:
         sfc /scannow
    Any errors are found in the steps above, please let me know.
    Hope this helpful.
    Best Regards,
    Jason Zeng
    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.

Maybe you are looking for

  • Exception_Access_Violation error while exporting report to excel

    Hello Experts, We have BO 6.5 report designer. We have few reports developed on BO 6.5. While exporting these reports to excel an error occurs with below error message: Unhandled exception Code: C0000005 Description : Exception_Acess_Violation It see

  • Length of IDoc field is cut

    Hello, I have the following problem: I have a vendor master scenario which means XML File to CREMAS IDoc. The problem is here the phone numer. The length of the phone numer is set to max=16 in the IDoc schema. If I have a longer phone number obviousl

  • Purchase Order is not created once in a while

    Hi All, I have peculiar problem that, when we are creating purchase orders some of the purchase orders are not existing even it gives message "Purchase Order created with purchase order number" is displayed. But if I try to create the purchase ordrer

  • How to allow user print their draft anwsers before sending it as final ?

    How to allow user print their draft anwsers before sending it as final in a form central questionnaire ?

  • JOptionPane with multiple inputs

    Well, I want to know , if someone can help me with JOptionPane, I need a windows of JOptionPane.showInputDialog (), that reads 3 inputs in the same window, I mean if I can have three Input Spaces in the same window.