Exchange 2010 sp3 rollup 7 fails

Exchange 2010 sp3 rollup 7 fails. This is ran at an elevated prompt and the UAC off. This server is also logged in as the domain Administrator account.
The server currently has rollup 4 SP3 installed. I'm wondering if I should uninstall it, reboot then try the Rollup 7 SP3 update?

Hi,
Can you please post the error?
At the same time please check these.
http://technet.microsoft.com/en-us/library/ee861125(v=exchg.141).aspx
http://exchangeserverpro.com/how-to-install-updates-on-exchange-server-2010-database-availability-groups/
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.

Similar Messages

Exchange 2010 SP3 Rollup 8v2 causes client connectivity issues

I installed SP3 Rollup 8v2 this weekend, going from 7. Since then we are having random client connectivity issues. New profiles can't be created, and some users can't access resources when booking meetings. We can do a registry fix to their machines to add
a DS Server, but this is a workaround only. I have uninstalled the Rollup 8v2 and we are still having the issue.
I thought 8v2 was supposed to fix this issue!

Hi,
According to your post, I understand that outlook client cannot connect to Exchange server to configure profile and cannot get list of resources room when upgrade to Exchange 2010 SP3 Rollup 8v2, the temporary solution is that specify the DC in registry.
If I misunderstand your concern, please do not hesitate to let me know.
Is there error message when configure Outlook failed?
Please run Test E-mail AutoConfiguration and Outlook connection status to double confirm the URL and FQDN of Exchange server.
As additional, please run below command to double check the state of Exchange system component:
Get-ServerComponentstate -Identity “servername”
If the state is Inactive, please run below command to active relevant component:
Set-ServerComponentState <Identity> -Component “component name” -Requester HealthAPI -State Active
More details about Server Component States in Exchange, for your reference:
http://blogs.technet.com/b/exchange/archive/2013/09/26/server-component-states-in-exchange-2013.aspx
Thanks
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]
Allen Wang
TechNet Community Support

Removed Exchange 2010 SP3 Rollup 8; some clients still having Outlook issues

We have removed Exchange 2010 SP3 Rollup 8 and rebooted the Exchange servers; but some Outlook clients are still experiencing the issues where calendar appointments can't be saved. They get "the item cannot be saved to this folder. The folder was deleted
or moved or you do not have permission." Then "the operation failed". Everyone has created new Outlook profiles. This fixes some computers; but not all. This is happening on Windows 7 with Office 2010 and Windows 8.1 with Office 2010.
Does anyone have a fix?
Thanks!
Mary Cato

Hi Mary,
Is there the same issue when using OWA ?
If OWA is ok, except recreate outlook profile, I also recommend you try moving mailboxes to another database and check if any helps.
Best regards,
Niko Cheng
TechNet Community Support

Exchange 2010 SP3 Rollup 7 not showing right version

I have installed Rollup 7. I can see it in programs installed / updates
but when I check the version number via the shell or console it show the number corresponding to sp3 no rollups
tried to re install rollup7, but it fails

There is:
Update Rollup 8 for Exchange Server 2010 SP2,
and Update Rollup 8 for Exchange Server 2010 SP1
But, as far as I know, there is no Update Rollup 8 for Exchange Server 2010
SP3 yet.
Please take a moment to Vote as Helpful and/or Mark as Answer where applicable. Thanks.
That's correct Idan. Exchange 2010 SP3 RU7 is the latest - released in August this year:
http://blogs.technet.com/b/rmilne/archive/2014/08/26/exchange-2010-sp3-ru7-released.aspx
Just like in Exchange 2003 & 2007 only service packs increment the version # you see in the management console and shell. Check the exsetup file as mentioned in the first post Idan linked.
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 SP3 Rollup Update 6

Our Exchange environment is currently on Exchange 2010 SP3 RU3 and the Forefront Protection 2010 for Exchange server version is 11.0.713.0 (Rollup 3).
We planning to upgrade Exchange servers and install Exchange 2010 SP3 RU6, question which I have is it Mandatory to upgrade the Forefront Protection 2010 for Exchange server version is 11.0.727.0 (Rollup 4) before we install Exchange 2010 SP3 RU6 on the
Exchange servers.
Thanks,
AJ

Thanks Adam for the prompt response and yes I recall these cmdlets to disable and there is a similar cmdlet to enable it. Also after Exchange 2010 SP2 after some RU there is no need to disable FPE before installing RU however it is recommended to disable
it.
If you refer the comments section mentioned in the blog below it talks about it:-
http://blogs.technet.com/b/exchange/archive/2014/05/27/released-update-rollup-6-for-exchange-2010-service-pack-3.aspx
If you read the comment posted by James Knoch posted on this blog which is as below,
SP3 & the Rollup Updates are not supposed to require you to disable Forefront anymore, but it doesn't hurt to be safe and disable/enable it anyways. Make sure you are running Forefront Rollup 4 (http://support.microsoft.com/kb/2619883)
& the latest security update (http://www.microsoft.com/en-us/download/details.aspx?id=41836).
Above stated confused me a bit, is it mandatory to upgrade Forefront or it is NOT.
Thanks,
AJ

Exchange 2010 SP3 Rollup 8 and Rollup 7

Hi
I have a customer with a Small Business Server 2010 with Exchange 2010 SP3.
The Customer installed updates on the server 10/12/2014 where Rollup 8 for Exchange was included.
After that the Customer has a lot of problems with connection from Outlook to Exchange and they phoned us.
We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
The customers still has problems with connection from Outlook.
One of the errors:
From: Systemadministrator
Sent: 15. december 2014 10:54
Subject: Unable to be delivered: Test
This message did not reach one or all of the recipients.
      Subject:     Test
      Sent:15-12-2014 10:54
Unable to deliver to the following recipient(s):
      MST the 15-12-2014 10:54
            This message could not be sent. Try to send the message again later, or contact the networkadministrator. Error [0x80004005-00000000-00000000].
Another error in Application log:
Log Name:      Application
Source:        MSExchange Common
Date:          16-12-2014 08:09:00
Event ID:      4999
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      <servername>.<domain>.local
Description:
Watson report about to be sent for process id: 9340, with parameters: E12, c-RTL-AMD64, 14.03.0224.001, M.E.RpcClientAccess.Service, M.E.RpcClientAccess.Handler, M.E.R.H.ViewCache.IsRowWithinUnreadCache, System.IndexOutOfRangeException, 8e38, 14.03.0224.001.
ErrorReportingEnabled: False
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="MSExchange Common" />
    <EventID Qualifiers="16388">4999</EventID>
    <Level>2</Level>
    <Task>1</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-12-16T07:09:00.000000000Z" />
    <EventRecordID>174679</EventRecordID>
    <Channel>Application</Channel>
    <Computer><servername>.<domain>.local</Computer>
    <Security />
</System>
<EventData>
    <Data>9340</Data>
    <Data>E12</Data>
    <Data>c-RTL-AMD64</Data>
    <Data>14.03.0224.001</Data>
    <Data>M.E.RpcClientAccess.Service</Data>
    <Data>M.E.RpcClientAccess.Handler</Data>
    <Data>M.E.R.H.ViewCache.IsRowWithinUnreadCache</Data>
    <Data>System.IndexOutOfRangeException</Data>
    <Data>8e38</Data>
    <Data>14.03.0224.001</Data>
    <Data>False</Data>
    <Data>
    </Data>
</EventData>
</Event>
What to do ?
Best Regards
John B

Hi John,
Please type
outlook /safe in RUN to start Outlook in safe mode and then check if this issue still exists. Meanwhile, please run Exchange Best Practices Analyzer and check if find relevant issues.
à
This message could not be sent. Try to send the message again later, or contact the networkadministrator.
Error [0x80004005-00000000-00000000].
The issue typically occurs if send messages to a large number of recipients.
When this issue occurred, did you check if send message successfully via OWA?
à
We have looked on the problem and found a Microsoft article about rollup 8 where they said DO NOT INSTALL
Did you mean this article:
Exchange releases: December 2014?
à
We ran Windows Update again on the 13/12/2014 where Rollup 7 was installed
From the Event ID 4999, I noticed that point to
14.03.0224.001, it should mean the old Exchange Server 2010 SP3 Update Rollup 8. From above
mentioned article (Exchange releases: December 2014),
Exchange Server 2010 SP3 Update Rollup 8 has been re-released to the Microsoft download center resolving a regression discovered in the initial release. The update RU8 package
corrects the issue which impacted users connecting to Exchange from Outlook. The updated RU8 package is version number 14.03.0224.002. Just a confirmation, did you
reinstall that re-released Exchange Server 2010 SP3 Update Rollup 8? Any difference?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
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]

Exchange 2010 SP3 Installation Failed. - Error While Locating Source (Windows Installer)

Hey Guys,
Urgent question here: I was trying to install SP3 for Exchange 2010. Unfortunately it failed on the install (all pre-requisites checked and passed). The problem: Windows Installer couldn't find a the exchangeserver.msi file. This happened immediately
after setup stopped the services.
I tried re-downloading the service pack and reinstalling, I got the same error. Anytime I selected the file using browse it failed and re-prompted me.
Error:
"click ok to try again or enter an alternate path to a folder containing the installation package "exchangeserver.msi" in the box below"
So here is what I did:
1) I reset all the services to automatic (the same way as before)
2) Rebooted the server
3) All Service started
4) DAG replication is working
I am going to work on figuring out how to fix the issue, however will this be a problem? will there be any data corruption? am I safe to let the server sit until I can open a ticket (if needed) ?
Thanks,
Robert
Robert

Hi,
Thank you for your question.
In order to resolve it, we could click the Browse button in the dialog box, locate the ExchangeServer.msi file, and then click OK
to continue the installation. The ExchangeServer.msi file is located on the Exchange Server 2010 installation media。
There are a referred link for us:
https://support.microsoft.com/en-us/kb/2888399
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support

Exchange 2010 SP3 /PrepareAD failing; "A reboot from a previous installation is pending. Please restart the system..." error

I am attempting to prepare our Exchange 2010 Server (RTM) for an upgrade to SP3.
When attempting to run "setup.com /PrepareAD" to prep the AD schema, the command fails and I receive the following error in the ExchangeSetup log:
[12/19/2013 21:50:48.0650] [1] Beginning processing Get-OrganizationConfig
[12/19/2013 21:50:48.0665] [1] Searching objects of type "OrganizationConfig" with filter "$null", scope "SubTree" under the root "$null".
[12/19/2013 21:50:48.0806] [1] Previous operation run on domain controller 'DC1.company.com'.
[12/19/2013 21:50:48.0806] [1] Preparing to output objects. The maximum size of the result set is "unlimited".
[12/19/2013 21:50:49.0945] [1] Ending processing Get-OrganizationConfig
[12/19/2013 21:51:42.0753] [1] [REQUIRED] A reboot from a previous installation is pending. Please restart the system and rerun setup.
[12/19/2013 21:51:43.0190] [1] Ending processing test-setuphealth
[12/19/2013 21:51:43.0221] [0] The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the <SystemDrive>:\ExchangeSetupLogs folder.
[12/19/2013 21:51:43.0283] [0] End of Setup
I am receiving this error when attempting to run "setup.com /PrepareAD" from either of our two GCs and I get the same error from both GCs, so the issue doesn't appear to be related to the individual servers.
What should I be checking, to clear this error so the AD schema update can be performed?
Environment
Exchange: Exchange Server 2010 RTM
Server: Windows 2008 R2 (fully patched)
Domain and Forest functionality: Windows 2008 R2 native

One follow up:
If I go into regedit, I see that under HKLM\System\CurrentControlSet\Control\Session Manager there is an entry from when I recent installed Google Chrome.
The entry looks like:
MultiString: PendingFileRenameOperation
Value Data: \??\C:\Program FIles (x86)\Google\Chrome
Is this "pending rename" what's causing SP3 to refuse to install, because it thinks the OS install state isn't 'clean'?

Exchange 2010 SP3 Installation Failed

I have Exchange 2010 SP2 RU8. We tried to install SP3 but continue to get a failure.
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you
have the correct upgrade.
Error code: 1642
Here is the MSI log:
=== Verbose logging started: 5/30/2014 17:44:11 Build type: SHIP UNICODE 5.00.7601.00 Calling process: C:\Windows\System32\msiexec.exe ===
MSI (c) (F4:C8) [17:44:11:684]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (F4:C8) [17:44:11:684]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (F4:CC) [17:44:11:699]: Resetting cached policy values
MSI (c) (F4:CC) [17:44:11:699]: Machine policy value 'Debug' is 0
MSI (c) (F4:CC) [17:44:11:699]: ******* RunEngine:
******* Product: {4934D1EA-BE46-48B1-8847-F1AF20E892C1}
******* Action:
******* CommandLine: **********
MSI (c) (F4:CC) [17:44:11:699]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (F4:CC) [17:44:11:699]: Cloaking enabled.
MSI (c) (F4:CC) [17:44:11:699]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (F4:CC) [17:44:11:699]: End dialog not enabled
MSI (c) (F4:CC) [17:44:11:699]: Original package ==> C:\Windows\Installer\48e783.msi
MSI (c) (F4:CC) [17:44:11:699]: Package we're running from ==> C:\Windows\Installer\48e783.msi
MSI (c) (F4:CC) [17:44:11:715]: APPCOMPAT: Uninstall Flags override found.
MSI (c) (F4:CC) [17:44:11:715]: APPCOMPAT: Uninstall VersionNT override found.
MSI (c) (F4:CC) [17:44:11:715]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (c) (F4:CC) [17:44:11:715]: APPCOMPAT: looking for appcompat database entry with ProductCode '{4934D1EA-BE46-48B1-8847-F1AF20E892C1}'.
MSI (c) (F4:CC) [17:44:11:715]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (F4:CC) [17:44:11:715]: MSCOREE not loaded loading copy from system32
MSI (c) (F4:CC) [17:44:11:731]: Opening existing patch 'C:\Windows\Installer\f63d4979.msp'.
MSI (c) (F4:CC) [17:44:11:731]: Opening existing patch 'C:\Windows\Installer\596a3.msp'.
MSI (c) (F4:CC) [17:44:11:731]: Original patch ==> C:\Temp\ExchSP3_RU6.msp
MSI (c) (F4:CC) [17:44:11:731]: Patch we're running from ==> C:\Temp\ExchSP3_RU6.msp
MSI (c) (F4:CC) [17:44:11:731]: SOFTWARE RESTRICTION POLICY: Verifying patch --> 'C:\Temp\ExchSP3_RU6.msp' against software restriction policy
MSI (c) (F4:CC) [17:44:11:731]: SOFTWARE RESTRICTION POLICY: C:\Temp\ExchSP3_RU6.msp has a digital signature
MSI (c) (F4:CC) [17:44:11:996]: SOFTWARE RESTRICTION POLICY: C:\Temp\ExchSP3_RU6.msp is permitted to run at the 'unrestricted' authorization level.
MSI (c) (F4:CC) [17:44:11:996]: SequencePatches starts. Product code: {4934D1EA-BE46-48B1-8847-F1AF20E892C1}, Product version: 14.2.247.5, Upgrade code: {A4A259AB-A77F-4039-832A-27B431DDFFEA}, Product language 1033
MSI (c) (F4:CC) [17:44:11:996]: Full optimizations are not possible in the patch sequencer because new patch[es] had been added in the current transaction.
MSI (c) (F4:CC) [17:44:11:996]: The patch sequencer will optimize its execution by not checking the applicability of applied patches.
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: verifying the applicability of QFE patch C:\Temp\ExchSP3_RU6.msp against product code: {4934D1EA-BE46-48B1-8847-F1AF20E892C1}, product version: 14.2.247.5, product language 1033 and upgrade code: {A4A259AB-A77F-4039-832A-27B431DDFFEA}
MSI (c) (F4:CC) [17:44:11:996]: Validating transform 'E14_DAT_RTMToE14_DAT_UPG' with validation bits 0x922
MSI (c) (F4:CC) [17:44:11:996]: Note: 1: 2749 2: E14_DAT_RTMToE14_DAT_UPG 3: C:\Temp\ExchSP3_RU6.msp 4: 14.3.123.4 5: 14.2.247.5
MSI (c) (F4:CC) [17:44:11:996]: 1: 2749 2: E14_DAT_RTMToE14_DAT_UPG 3: C:\Temp\ExchSP3_RU6.msp 4: 14.3.123.4 5: 14.2.247.5
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: QFE patch C:\Temp\ExchSP3_RU6.msp is not applicable.
MSI (c) (F4:CC) [17:44:11:996]: The original #_QFESequence table:
MSI (c) (F4:CC) [17:44:11:996]: PatchGUID: {2D4DEC16-9DFE-4A3F-89C7-8D19F374B426}
ResultantVersion: 14.2.247.5 PatchFamily: E14_DAT
Sequence: 14.2.375.0 Type: QFE
MSI (c) (F4:CC) [17:44:11:996]: PatchGUID: {1B1DA2D5-6EFD-4EF7-B225-EAFBF51ABCBE}
ResultantVersion: 14.2.247.5 PatchFamily: E14_DAT
Sequence: 14.2.298.4 Type: QFE
MSI (c) (F4:CC) [17:44:11:996]: The pre-sorted #_QFESequence table: - this is useful to see if patches had been ordered correctly within resultant versions and patch families
MSI (c) (F4:CC) [17:44:11:996]: PatchGUID: {1B1DA2D5-6EFD-4EF7-B225-EAFBF51ABCBE}
ResultantVersion: 14.2.247.5 PatchFamily: E14_DAT
Sequence: 14.2.298.4 VersionOrder: 0
SequenceOrder: 0 Type: QFE
MSI (c) (F4:CC) [17:44:11:996]: PatchGUID: {2D4DEC16-9DFE-4A3F-89C7-8D19F374B426}
ResultantVersion: 14.2.247.5 PatchFamily: E14_DAT
Sequence: 14.2.375.0 VersionOrder: 0
SequenceOrder: 1 Type: QFE
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: The initial #_Predecessor table:
MSI (c) (F4:CC) [17:44:11:996]: PatchFamily: E14_DAT,
PatchGUID: {1B1DA2D5-6EFD-4EF7-B225-EAFBF51ABCBE},
Predecessor GUID: NULL
MSI (c) (F4:CC) [17:44:11:996]: PatchFamily: E14_DAT,
PatchGUID: {2D4DEC16-9DFE-4A3F-89C7-8D19F374B426},
Predecessor GUID: {1B1DA2D5-6EFD-4EF7-B225-EAFBF51ABCBE}
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: Step 1
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: patch {1B1DA2D5-6EFD-4EF7-B225-EAFBF51ABCBE} (PatchFamily E14_DAT) will be sequenced.
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: Step 2
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: patch {2D4DEC16-9DFE-4A3F-89C7-8D19F374B426} (PatchFamily E14_DAT) will be sequenced.
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: The resulting #_OrderedGUIDs table:
MSI (c) (F4:CC) [17:44:11:996]: Patch: {1B1DA2D5-6EFD-4EF7-B225-EAFBF51ABCBE}
Order: 0 (Family: E14_DAT)
MSI (c) (F4:CC) [17:44:11:996]: Patch: {2D4DEC16-9DFE-4A3F-89C7-8D19F374B426}
Order: 1 (Family: E14_DAT)
MSI (c) (F4:CC) [17:44:11:996]: The ordered #_QFESequence table: - has the final sequence of QFEs. It lists each PatchGUID only once.
MSI (c) (F4:CC) [17:44:11:996]: PatchGUID: {1B1DA2D5-6EFD-4EF7-B225-EAFBF51ABCBE}
ResultantVersion: 14.2.247.5 PatchFamily: E14_DAT
Sequence: 14.2.298.4 Order: 0
MSI (c) (F4:CC) [17:44:11:996]: PatchGUID: {2D4DEC16-9DFE-4A3F-89C7-8D19F374B426}
ResultantVersion: 14.2.247.5 PatchFamily: E14_DAT
Sequence: 14.2.375.0 Order: 1
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: there's no supersedence information available, so no patches will be superseded.
MSI (c) (F4:CC) [17:44:11:996]: SequencePatches returns success.
MSI (c) (F4:CC) [17:44:11:996]: Final Patch Application Order:
MSI (c) (F4:CC) [17:44:11:996]: {1B1DA2D5-6EFD-4EF7-B225-EAFBF51ABCBE} -
MSI (c) (F4:CC) [17:44:11:996]: {2D4DEC16-9DFE-4A3F-89C7-8D19F374B426} -
MSI (c) (F4:CC) [17:44:11:996]: Other Patches:
MSI (c) (F4:CC) [17:44:11:996]: Unknown\Absent: {32539431-026C-467E-98AD-9932CAC4B304} - C:\Temp\ExchSP3_RU6.msp
The upgrade cannot be installed by the Windows Installer service because the program to be upgraded may be missing, or the upgrade may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have
the correct upgrade.
C:\Windows\Installer\48e783.msi
MSI (c) (F4:CC) [17:44:11:996]: Product: Microsoft Exchange Server - Update '{32539431-026C-467E-98AD-9932CAC4B304}' could not be installed. Error code 1642. Additional information is available in the log file C:\Users\dgates\AppData\Local\Temp\2\MSI4736a.LOG.
MSI (c) (F4:CC) [17:44:11:996]: Windows Installer installed an update. Product Name: Microsoft Exchange Server. Product Version: 14.2.247.5. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: {32539431-026C-467E-98AD-9932CAC4B304}. Installation
success or error status: 1642.
MSI (c) (F4:CC) [17:44:11:996]: Note: 1: 1708
MSI (c) (F4:CC) [17:44:11:996]: Product: Microsoft Exchange Server -- Installation failed.
MSI (c) (F4:CC) [17:44:11:996]: Windows Installer installed the product. Product Name: Microsoft Exchange Server. Product Version: 14.2.247.5. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1642.
MSI (c) (F4:CC) [17:44:12:011]: MainEngineThread is returning 1642
=== Verbose logging stopped: 5/30/2014 17:44:12 ===
HossFly, Exchange Administrator

As per the below log entries it seems that it is trying to install SP3 UR6 directly and failing saying its not applicable. If you are trying to install just SP3 then it shouldn't try installing UR6 at the same time so that seems strange to me...
MSI (c) (F4:CC) [17:44:11:731]: SOFTWARE RESTRICTION POLICY: C:\Temp\ExchSP3_RU6.msp has a digital signature
MSI (c) (F4:CC) [17:44:11:996]: SOFTWARE RESTRICTION POLICY: C:\Temp\ExchSP3_RU6.msp is permitted to run at the 'unrestricted' authorization level.
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: verifying the applicability of QFE patch C:\Temp\ExchSP3_RU6.msp against product code: {4934D1EA-BE46-48B1-8847-F1AF20E892C1}, product version: 14.2.247.5, product language 1033 and upgrade code: {A4A259AB-A77F-4039-832A-27B431DDFFEA}
MSI (c) (F4:CC) [17:44:11:996]: Note: 1: 2749 2: E14_DAT_RTMToE14_DAT_UPG 3: C:\Temp\ExchSP3_RU6.msp 4: 14.3.123.4 5: 14.2.247.5
MSI (c) (F4:CC) [17:44:11:996]: 1: 2749 2: E14_DAT_RTMToE14_DAT_UPG 3: C:\Temp\ExchSP3_RU6.msp 4: 14.3.123.4 5: 14.2.247.5
MSI (c) (F4:CC) [17:44:11:996]: PATCH SEQUENCER: QFE patch C:\Temp\ExchSP3_RU6.msp is not applicable.
Looks like time to re-download
SP3 and give it a try.
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2010 SP3 upgrade fails at stopping services for Management tools station

Attempting to upgrade a Windows 7 SP1 64bit virtual machine from Exchange 2010 SP2 management tools to SP3 fails with the following error:
Summary: 11 item(s). 1 succeeded, 1 failed.
Elapsed time: 00:15:19
Preparing Setup
Completed
Elapsed Time: 00:00:00
Stopping Services
Failed
Error:
The following error was generated when "$error.Clear();
          & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
          & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
        " was run: "Service 'NetBT' failed to reach status 'Stopped' on this server.".
Service 'NetBT' failed to reach status 'Stopped' on this server.
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:15:19
Here is the powershell execute policy:
PS C:\> Get-ExecutionPolicy -list
Scope
ExecutionPolicy
MachinePolicy
Unrestricted
UserPolicy
Unrestricted
Process
Undefined
CurrentUser
RemoteSigned
LocalMachine
RemoteSigned

Hi Bad Dos,
Any updates?
You can also try to uninstall sp2 Management Tool first, then install SP3 directly.
Frank Wang
TechNet Community Support

Exchange 2010 SP3 Rollup 6 issue with Forefront

This rollup, 2936871, when installed on a server having Forefront Protection for Exchange Server integrated with Exchange services, causing Information Store not starting. For this we have to disable the integration and start the services. When again you
try to integrate and start the services, Exchange services will not start. So you should not integrate Forefront with Exchange services at all, finally.
Has anybody already in this soup?
Whether Microsoft has checked this? Any solution?
The error events are the below two:
Log Name:      Application
Source:        MSExchangeIS
Event ID:      9581
Task Category: Virus Scanning
Level:         Error
Keywords:      Classic
Description:
Error code 1 returned from virus scanner initialization routine. Virus scanner was not loaded.
Log Name:      Application
Source:        MSExchangeIS
Event ID:      9564
Task Category: General
Level:         Error
Keywords:      Classic
Description:
Error 0x1 starting the Microsoft Exchange Information Store.
Failed to start virus scan.

Hi,
Hotfix Rollup 3 for Microsoft Forefront Protection for Exchange can address the issue that the Exchange Information store crashes with Forefront Protection for Exchange installed. I recommend you install Hotfix Rollup 3 for Microsoft Forefront Protection
for Exchange to check the result.
Here is a related article for your reference.
Description of Hotfix Rollup 3 for Microsoft Forefront Protection for Exchange
http://support.microsoft.com/kb/2538719/en#Fix4
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 SP3 Upgrade Failed

Dear All,
I'm trying to upgrade Exchange 2010 on SP2 or 3 but I'm getting below error.
Setup encountered a problem while validating the state of Active Directory: An Active Directory error 0x51 occurred when trying to check the suitability of server 'Server.Domain.Com'. Error: 'Active directory response: The LDAP server is unavailable.'
I have 3 DCs
PDC 2003
ADC 2003
ADC 2008 R2, All FSMO Roles are on 2008 R2.
Exchange 2007 SP3 is in place with 1 Exchange 2010 box which is working fine.
Please help me in this regard.
Thanks in advance.

Hi
Can you ping your DC from your exchange server? On exchange 2010 can you run the following from your EMS, what does the results give you?
Get-ADServerSettings | fl

Unable to connect to Exchange 2010 Management console after - Exchange 2010 SP3 Rollup 7

We have been having issue with our Exchange Server 2010's Transport Service failing due to a database corruption. I was hoping that maybe applying the Roll-up 7 for Exchange might fix this issue, however after applying the patch we are unable to start the
MSExchangeMailboxAssistants "Error 1053: The service did not respond to the start or control request in a timely fashion."
Then I notice that we were unable to connect to the Management Console or through PowerShell.
Event 1000, Application Error
Faulting application name: MSExchangeMailboxAssistants.exe, version: 14.3.210.2, time stamp: 0x53e2bf34
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x5315a05a
Exception code: 0xe0434f4d
Fault offset: 0x000000000000940d
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13
PowerShell error:
Exception calling "TryLoadExchangeTypes" with "2" argument(s): "Could not load file or assembly 'Microsoft.Exchange.Man
agement, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. Strong name va
lidation failed. (Exception from HRESULT: 0x8013141A)"
At C:\Program Files\Microsoft\Exchange Server\V14\bin\RemoteExchange.ps1:75 char:92
+ $typeLoadResult = [Microsoft.Exchange.Configuration.Tasks.TaskHelper]::TryLoadExchangeTypes <<<< ($ManagementPath, $t
ypeListToCheck)
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : DotNetMethodException

Hi,
Please try the following steps to narrow down the issue:
1. Uninstall and reinstall .NET package in Exchange server.
2. Under location C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG, took a copy of Machine.Config.default, renam it to Machine.config and copy it under this path again.
3. Do IIS reset by running iisreset from a Command Prompt window.
4. Reboot the server and verify whether the Exchange services are started.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2010 SP3 Rollup 5 "Queued" MoveRequest

I cannot run the New-MoveRequest to move mailboxes from a database to another database. It always gets stuck in the "Queued" state. I have attempted to restart the Microsoft Exchange Mailbox Replication service on both of my CAS but it still remains
stuck.
Anyone know how I can get this to start? I see nothing in the event viewer that gives me a hint to what the problem is.

Hi,
How about restart Mailbox servers?
How many move requests were being processed at the same time?
thanks.
Niko Cheng
TechNet Community Support

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013
Detected Problems:
- Access denied for attached mailbox (department mailbox)
- Access denied for delete or move messages on own mailbox
- Can't send new messages with error (Error: [0x80004005-00000000-00000000])
Solution:
- Rollback to Exchange 2010 SP3 - Rollup 7
- You can rollback to Exchange 2010 SP3 - RollUp 7 in 30 min
Algunos de los destinatarios no recibieron su mensaje.
Asunto: Hola
Enviado el: 11/12/2014 8:35
No se puede localizar a los destinatarios siguientes:
'[email protected]' en 11/12/2014 8:35
Este mensaje no se pudo enviar. Inténtelo de nuevo más tarde, o póngase en contacto con el administrador de red.
Error: [0x80004005-00000000-00000000].

See the following forum thread:
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8

Exchange 2010 sp3 rollup 7 fails

Similar Messages

Maybe you are looking for