Sp1 failed on exchange 2013

Hello i've installed SP1 on exchnage 2013 ( windows 2012 ) ant it failed with this error
ErrorRecord: Échec de l'installation du produit « D:\temp\en\MSSpeech_SR_TRANS.en-US.msi ». Erreur irrécupérable lors de l’installation. Le code d'erreur est 1603.
[06/03/2014 11:55:49.0102] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Échec de l'installation du produit « D:\temp\en\MSSpeech_SR_TRANS.en-US.msi ». Erreur irrécupérable lors de l’installation. Le code d'erreur est 1603.
---> System.ComponentModel.Win32Exception: Erreur irrécupérable lors de l’installation
--- Fin de la trace de la pile d'exception interne ---

Hi,
I recommend you try to re-download the SP1 from the following link and re-install again.
http://www.microsoft.com/en-US/download/details.aspx?id=41994
Here is a similar thread for your reference:
http://social.technet.microsoft.com/Forums/exchange/en-US/1de7daab-9cdd-4696-8cc4-6b4418be33ca/error-1603-during-a-new-installation?forum=exchange2010
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Similar Messages

SMIME lookup failing on Exchange 2013

Hello all,
I've been at this for a week and still cannot figure out what the cause of the issue might be. I'm trying to setup SMIME encrypting and signature capabilities for an Exchange environment. The UserCertificate Attribute is populating in ActiveDirectory
for the users. I have an online Root CA that does not issues anything but the Subordinate CA cert. I then have a Subordinate CA that issues all client certificates. The CRLs and AIA locations are functioning and downloadable.
When I try to send an encrypted message in OWA, all I receive is the message "An error occurred while encrypting this S/MIME message. Certificates can't be found for any recipients." Not sure what else do verify. I believe I've
configured the SMIMEConfig correctly in Exchange as well. Based on this....http://technet.microsoft.com/en-us/library/dn626155(v=exchg.150).aspx
Thanks for any help

Hi,
Is there any related error message in APP log?
Thanks,
Simon Wu
TechNet Community Support

POP3 Authentication fails on Exchange 2013 server.

We have an internal help desk app that needs to use POP3 to send acknowledgements. Everything worked fine with the previous Exchange 2010 server, but I am getting "Connection reset" from the help desk app and
unexpected terminations (0x800CCC0F) from an Outlook Express client I am using to test this scenario.
The two POP3 services: the Microsoft Exchange POP3 service and the Microsoft Exchange POP3 Backend services are running.
My Test-PpoConnectivity returns this:
RunspaceId                        : 4d16307d-e2e0-4a98-b69d-f05d1a778351
Name                              : 1
ProtocolName                      : POP3
MaxCommandSize                    : 512
MessageRetrievalSortOrder         : Ascending
UnencryptedOrTLSBindings          : {0.0.0.0:110, [::]:110}
SSLBindings                       : {0.0.0.0:995, [::]:995}
InternalConnectionSettings        : {Mail.WTI.LOCAL:995:SSL, Mail.WTI.LOCAL:110:TLS}
ExternalConnectionSettings        : {}
X509CertificateName               : Mail
Banner                            : The Microsoft Exchange POP3 service is ready.
LoginType                         : PlainTextLogin
AuthenticatedConnectionTimeout    : 00:30:00
PreAuthenticatedConnectionTimeout : 00:01:00
MaxConnections                    : 2147483647
MaxConnectionFromSingleIP         : 2147483647
MaxConnectionsPerUser             : 16
MessageRetrievalMimeFormat        : BestBodyFormat
ProxyTargetPort                   : 9955
CalendarItemRetrievalOption       : iCalendar
OwaServerUrl                      :
EnableExactRFC822Size             : False
LiveIdBasicAuthReplacement        : False
SuppressReadReceipt               : False
ProtocolLogEnabled                : False
EnforceCertificateErrors          : False
LogFileLocation                   : C:\Program Files\Microsoft\Exchange Server\V15\Lo
LogFileRollOverSettings           : Daily
LogPerFileSizeQuota               : 0 B (0 bytes)
ExtendedProtectionPolicy          : None
EnableGSSAPIAndNTLMAuth           : True
Server                            : MAIL
I need some help regarding what might be wrong.
Thanks!

Hi,
Does this issue occur on Office Outlook client?
About port.
By default port 25 is for outgoing access, and port 110 is for incoming access.
If you are not sure about the ports, please contact your ISP or system administrator to double confirm it.
About error 0x800CCC0F.
Please see following KB in details:
Error occurs when you send or receive an email message in Outlook or Outlook Express
http://support.microsoft.com/kb/813514/en-us
Thanks
Mavis
Mavis Huang
TechNet Community Support
No answer in a week?
Really??

Exchange 2013 SP1 prerequ errors

Current installation. 4 Exchange 2013 machines on Server 2008 R2 platform (VM with Hyper-V), all have CAS and mailbox role installed. DAG across all for servers. 2 servers
reside in main datacenter and 2 on a DR site.
The Exchange installation is at CU 2 and working.<o:p></o:p>
We have 2 domain controllers in the main datacenter (win 2008 R2) and 2 domain controllers in the DR site (Win 2012 R2).<o:p></o:p>
DCDIAG checks out fine on all. Network is fine for all.
Running SP1 installation on the Exchange servers in the DR site results in prerequisites in a bunch of errors which all stem from one root issue: <o:p></o:p>
Error:
Either Active Directory doesn't exist, or it can't be contacted.<o:p></o:p>
Running the same on the main site (DC= Win 2008 R2) completes prereq for SP1 with no errors.
So the difference is that the 2 Exchange servers on the DR site have Win 2012 R2 for their domain controllers and fail.<o:p></o:p>
Any advise?<o:p></o:p>
Gerhard Waterkamp ACSLA Inc.

No, I am not done.
The situation is that on the DR site SP1 on 2 Exchange 2013 servers (on 2008 R2) using Windows 2012 R2 Domain controllers does not install.
Error messages: ( a whole bunch more, but all related to this)
Error:
Either Active Directory doesn't exist, or it can't be contacted.
It is not resolved but still open.
Gerhard Waterkamp ACSLA Inc.

Exchange 2013 autodiscover prompt

Hi,
Over the weekend i installed SP1 on our exchange 2013 DAG. Now users are getting an authentication prompt when opening outlook. This didn't happen prior to SP1.
When testing email auto configuration in outlook it prompts for auth, typing in my creds it goes through ok.
It looks like it getting a 401
I'm not sure what has changed but its very frustrating.
Any Ideas?

Please check the server settings on exchange... Update might change the the settings back to Basic. Roll back to NTLM to see what happens..
UMESH DEUJA MCP,MCTS,MCSA,CCNA

Move Exchange 2013 to new Virtual Server including settings?

Since we have a failing VM Exchange 2013, we need to move the installation to a new server. We have created a new Hyper-V Server 2012 and installed a new Exchange 2013 on it. After connecting the new server to the domain we can see all settings and users
of the existing Exchange Installation.
Since the old server has a corrupt RAID, we need to move all data and settings to the new server. We have moved some user mailboxes with the ecp to the new server. They are still working, but mailtraffic takes exactly 1 hour now?! Also these users who logon
with Outlook now get the error message 'problem with the safetycertificate of the proxyserver (translated)'. The mail still works, but 1 hour delay.
Can we now move the other mailboxes too? And if we have moved them, how can we move the settings of this server? If we shutdown the old server, will Exchange (the moved one) still be up and running? Because we are afraid that when we shutdown the old server
it will not boot again.
Thanx for any tips of leads in the right direction.

1. Outgoing mail from https://echange/owa is
working.
Did you try https://ip-address-of-newserver/owa and send an email outside?
2. Outlook 2010 does not start, cannot find mailboxes to open, so user won't have mail in the morning.
Get-OutlookProvider -Identity EXCH | FL
If is field CertPrincipalName empty type following:
Set-OutlookProvider EXCH -CertPrincipalName msstd:FQDN-YOUR-MAIL-SERVER
After this it should work (assuming all your mailboxes moved to the new server).
Please check this to see you the mailbox servername
http://www.zerohoursleep.com/2013/02/manual-outlook-configuration-with-exchange-2013/
3. Incoming mail cannot be delivered by the Barracuda (connection refused).
Ensure Barracuda is sending email to the new server and new server is not blocking incoming traffic.
4. OWA and ECP not working from outside (public IP).
Ensure you NAT is correct by site. Check it is listening to the port using http://www.canyouseeme.org/
Please check these and get back
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 SP1 readiness check failing

Trying to install our first Exchange 2013 SP1 server on Windows 2012 R2 in our datacentre, the readiness check fails with:
Error:
The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.
For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx
There are many more errors relating to Enterprise admin rights etc.
Please note that:
My account is Domain admin, Schema admin and Enterprise admin member, it always has been.
I tried the built-in AD Administrator which of course is part of the groups as well, no difference.
Active Directory is at 2008 R2 for domain and forest functional levels.
I tried rejoining the new Exchange designated server to the domain
I've installed RSAT-ADDS, the Managed API 4.0 and all the other windows roles via powershell
There is a local domain controller that is a global catalog server on the new Exchange server subnet
I tried running the Exchange Setup on a different server on the same subnet as where the active 2010 Exchange server resides as well as the FSMO AD role holder resides, this works fine. I even did the AD prep from there no problem, that made no difference
on the datacentre server
AD replicates fine between the FSMO role holder and the Datacentre (no errors in dcdiag or repadmin /showrepl)
This error is in the event log:
The description for Event ID 4027 from source MSExchange ADAccess cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
ExSetupUI.exe
6724
Get Servers for domain.local
TopologyClientTcpEndpoint (localhost)
3
System.ServiceModel.EndpointNotFoundException: Could not connect to net.tcp://localhost:890/Microsoft.Exchange.Directory.TopologyService. The connection attempt lasted for a time span of 00:00:02.0475315. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:890. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:890
at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
--- End of inner exception stack trace ---
Server stack trace:
at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at System.ServiceModel.ICommunicationObject.Open()
at Microsoft.Exchange.Net.ServiceProxyPool`1.GetClient(Boolean useCache)
at Microsoft.Exchange.Net.ServiceProxyPool`1.TryCallServiceWithRetry(Action`1 action, String debugMessage, WCFConnectionStateTuple proxyToUse, Int32 numberOfRetries, Boolean doNotReturnProxyOnSuccess, Exception& exception)
the message resource is present but the message is not found in the string/message table

So I decided to re-install the OS, worked perfectly now. Only difference from before would be:
SCCM hasn't pushed SCEP 2012 to the new build of the same server yet
The original server was installed in a different AD site and then it was physically mode and reassigned to an new AD site and subnet
I might have installed the pre-reqs in a slightly different order (RSAT-ADDS, all the IIS etc things via powershell
and then the UCM API 4.0. (saw few comments that the order of how you install them matters in other forums).
10 or so Microsoft Windows updates haven't installed on the new OS build yet.
Other than that, its identical. But if its not broken don't fix it, perhaps the above can help someone else though.

Exchange 2013 SP1 Setup fails

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

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

SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'server/name'.
Parameter name: VirtualDirectoryName".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
!! And now transport service won't start and mail is unavailable !!
Any help would be appreciated.
I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

Hi,
Thanks for your response.
From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Uninstalling Exchange 2013 SP1 failed on Step 8 Lanugage

Hello,
I am trying to uninstall Exchange 2013 SP1 but it is failing while uninstalling Language step # 8 the error is;
Error:
The following error was generated when "$error.Clear();
                    $regPath='HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall';
                    $PackageGUIDRegEx = "{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}";
                    $InstallPath = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup').MsiInstallPath;
                    if(test-path ($regPath))
                        Write-ExchangeSetupLog -info ("Removing " + $RoleLanguagePackType + " Language Packs.");
                        Get-ChildItem ($regPath) | foreach{
                            if($_ -match "(?<ProductCode>$PackageGUIDRegEx)") {
                                $langPackPackageCode = $matches['ProductCode'];
                                if($langPackPackageCode -ne $null -and $langPackPackageCode.Length -ne
0) {
                                    Write-ExchangeSetupLog -info ("Removing package
$langPackPackageCode");
                                    $language = $langPackPackageCode.Substring(20,4);
                                    $logFilePath = [IO.Path]::Combine($RoleLogFilePath,"Uninstall")
+ '.' + $language + '.' + "Client" + "." + $RoleLogDateTime + ".msilog";
                                    uninstall-MsiPackage -ProductCode ($langPackPackageCode)
-LogFile ($logFilePath);
                        Get-Childitem -Path $InstallPath -include "*.Localized.js","*.Localized.min.js" -recurse | foreach
($_) {remove-item $_.fullname};
                        Write-ExchangeSetupLog -info "Remove Language Packs completed.";
        " was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
I am also attaching the snapshots. Please guide me how to uninstall Exchange 2013. I had some issue with Exchange Server and it need to uninstall and re-install the Exchange Server.

        " was run: "The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.".
Hi,
Based on this error, possible cause may the path of language package is too long. Please check the following things:
Where is your language package installed? Please check it.
Under 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{DEDFFB[0-9a-fA-F]{2}-42EC-4E26-[0-9a-fA-F]{4}-430E86DF378C}", please check the following entries. By default, it should be like this.
InstallSource (Z:\Applications\Server\Exchange\2013\64-Bit\RTM\en\)
ModifyPath (MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C})
UninstallString MsiExec.exe /X{DEDFFB64-42EC-4E26-0409-430E86DF378C}
Under 'HKLM:\SOFTWARE\Microsoft\ExchangeServer\v15\setup, check this entry MsiInstallPath. By default, the value should be “C:\Program Files\Microsoft\Exchange Server\V15\”
Best Regartds.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Exchange 2013 SP1 Install on W2K12R2 Pre-requisite fail

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

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

Exchange 2013 SP1 - 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 SP1 - The attempt to search the administrator audit log failed.

During migration process from Exchange 2010 to 2013, after moving Arbitration mailbox from Exchange 2010 database to Exchange 2013 SP1 database, cmdlet Search-AdminAuditLog fails with following error.
The attempt to search the administrator audit log failed. Please try again later.
+ CategoryInfo : NotSpecified: (:) [Search-AdminAuditLog], AdminAuditLogSearchException
+ FullyQualifiedErrorId : [Server=EX2013,RequestId=517873e3-a623-4363-bfdc-e5aa23595c33,TimeStamp=29. 4. 2014
8:38:37] [FailureCategory=Cmdlet-AdminAuditLogSearchException] 2774D0CF,Microsoft.Exchange.Management.SystemConfig
urationTasks.SearchAdminAuditLog
+ PSComputerName : ex2013.domainname.local

Hi,
First, please make sure the Microsoft Exchange Search and the Microsoft Exchange Search Host Controller service are running and please run the get-mailbox -arbitration cmdlet to check the result.
Besides, please check the properties of the DiscoverySearchMailbox and verify that the homeMDB attribute is set to a mounted database.
If the steps above don't work, please try to re-create a new Discovery System Mailbox to check the result. You can refer to the following article.
Re-Create the Discovery System Mailbox
http://technet.microsoft.com/en-gb/library/gg588318(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

SCCM 2012 SP1 and Exchange 2013 Connector Get-Recipient cmdlet failed

I have been trying to get my Exchange Connector working with SCCM 2012 SP1 for a week or so now. Every post tells me that the Get-Recipient cmdlet failed is a security permissions error. I have given the service account running the connector full Exchange
Server Management rights including Recipient Management and Organization View-Only. I have even tested remote power shell to the CAS server and run the cmdlet with no issues.
For some reason it just does not want to work for me. Has anyone been running into this issue?

Now before you read the following error and say oh this is a permission issue I am telling you it is not. I have given the account full Exchange admin rights and I have even tested the Get-Recipient cmdlet remotely to the Exchange server and it works with
no issues. I have also noticed multiple forum posts with the exact same issues.
I have noticed one thing that stands outs "Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean"
I believe this issue may be related to changes in the powershell commands with Exchange 2013, but I do not know where or how to edit the ps1 script.
I am getting the error below:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to
type System.Boolean."~~ at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings
settings)~~ at System.Management.Automation.PowerShell.Invoke()~~ at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
STATMSG: ID=8817 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_EXCHANGE_CONNECTOR" SYS=MySite SITE=MySiteID PID=xxx TID=xxx GMTDATE=Thu Sep 19 07:00:01.653 2013 ISTR0="Get-Recipient" ISTR1="ParameterBindingFailed,Microsoft.Exchange.Management.RecipientTasks.GetRecipient"
ISTR2="Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)

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.

Sp1 failed on exchange 2013

Similar Messages

Maybe you are looking for