Exchange 2010 SP3 RU8

I am trying to rollback Exchange 2010 SP3 RU8. When I uninstall the update the installer asks for exchangeserver.msi for Exchange 2010 SP3 RU7. I downloaded RU7 from the Microsoft website. It did not accept it as the correct msi. I ran the Exchange 2010
SP3 RU7 update I download and it comes up as RU8. I need the exchangeserver.msi from Exchange 2010 SP3 RU7. Thank you for your help.

You may need the original SP3 binaries located here:
http://www.microsoft.com/en-us/download/details.aspx?id=36768
See this thread for more ideas about rolling back:
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8
Update:Microsoft has released version 2 of SP3 RU8 today. The link should be live soon.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

Exchange 2010 SP3 maximum journal mailbox size for performance

Hello all,
Does anyone know if there is a limit mailbox
size near 01 terabyte than
above it generates performance problems?
We have a journaling mailbox that
reached today 1.077 GB and
from there began the process very
slowly messages to store.
All (4) Exchange Hub Trasnport that try to connect to this store get an 4.32 store drive error. A new
journal mailbox was created in the same
database, and the problem was solved.
Thanks
João Paulo.
Exchange 2010 SP3 RU8 on-premisses

Hi Paulo,
Base on my knowledge, journaling mailbox as the same as any other mailbox, the maximum size depends on the data to be stored in the mailbox, the hardware resources available, and the disaster recovery requirements
for the server where the journaling mailbox is located.
If you configure journaling mailboxes without storage quotas, monitor the Mailbox server to ensure that it doesn't exceed the available hardware resources or disaster recovery capabilities.
Best regards,
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]
Niko Cheng
TechNet Community Support

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

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

Install Exchange 2010 Sp3 on Windows 2012 R2

Dear All,
From Microsoft Exchange support matrix, I can tell that Exchange 2010 Sp3 is not listed on supported page. However when I run the setup, the prerequisite setup check, dose not list any warnings or issues with the setup, all check are green. Is it possible
that the support OS matrix has not been updated? Is Exchange 2010 Sp3 supported on Windows 2012 R2?
http://blogs.technet.com/b/rmilne/archive/2013/09/17/exchange-support-for-windows-server-2012-r2.aspx
Thank you

The prerequisite check is checking that the required Windows components are installed. Exchange 2010 is still not supported on Windows Server 2012 R2.

Sharepoint 2013 vs Exchange 2010 SP3 search (Error while crawling LOB contents)

Hi there:
We are trying to solve the problem: ERROR CRAWLING LOB CONTENTS when we wish to search Exchange 2010 SP3 public folder content on Sharepoint 2013 Foundation.
Quick briefing:
Followed this instructions:
http://technet.microsoft.com/en-us/library/jj591608(v=office.15).aspx
* Created CRAWL RULE
- Used Domain Admin for content access ---> IS THIS WRONG?
- Domain Admin can access public folder thru Outlook Web Access (checked)
- Included all items in this path
PRINTSCREEN 1
* Added a content source for Exchange Server public folders
- Logged to Outlook Web Access with domain admin, expanded Public folders and opened 1st subfolder in new window and copied the address
- Logged to Outlook Web Access with domain admin, expanded Public folders and opened 2nd subfolder in new window and copied the address
PRINTSCREEN2
* Did a FULL CRAWL
PROBLEM:
- Search results does not throw "correct data". Some items are not being found
CRAWL LOG is reporting: Error while crawling LOB contents
Detailed error message:
https://mail.domain.com/OWA/?ae=Folder&id=PSF.LgAAAAAaRHOQqmYRzZvIAKoAL8RaAwAnt2ed15IATLg8XoXLNj4EAAAAXsN8AAAB&t=IPF.Note
Error while crawling LOB contents.
Error caused by exception: Microsoft.BusinessData.Infrastructure.BdcException
The shim execution failed unexpectedly - Exception has been thrown by the target of an invocation..:
System.InvalidOperationException An internal server error occurred.
Try again later.; SearchID = 4E8542D3-48EF-404E-8025-8D9AAEFE777A )
We thought it's a throttling issue / found possible solution:
http://powersearching.wordpress.com/2013/07/23/exchange-public-folders-search-fail-error-while-crawling-lob-contents/
Tried it, still same Error messages, problem not resolved.
Any hints? Please advise.
With best regards
bostjanc

Hi Bostjan,
From the error message, the issue might be caused by throttling policy on Exchange side. And the article you posted provides the right solution, some modification to the solution and please try again.
For throttling policy part
1.Execute the command for Set-ThrottlingPolicy
Set-ThrottlingPolicy SharePoint -RCAMaxConcurrency Unlimited -EWSMaxConcurrency Unlimited -EWSMaxSubscriptions Unlimited -CPAMaxConcurrency Unlimited -EwsCutoffBalance Unlimited -EwsMaxBurst Unlimited -EwsRechargeRate Unlimited
2.Execute the command Get-ThrottlingPolicy SharePoint to double confirm the policy setting has been successfully executed
For registry key part
1. Start Registry Editor (regedit).
2. Navigate to the following registry subkey:
\\HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\MSExchangeIS\ParametersSystem
3. Right-click ParametersSystem, point to New, and then click Key.
A new key is created in the console tree.
4. Rename the key MaxObjsPerMapiSession, and then press Enter.
5. Right-click MaxObjsPerMapiSession, point to New, and then click DWORD (32-bit) Value.
The new value is created in the result pane.
6. Rename the key to <Object_type>, where <Object_type> is the name of the registry object type that you're modifying. For example, to modify the number of messages that can be opened, use objtMessage. Press Enter.
7. Right-click the newly created key, and then click Modify.
8. In the Value data box, type the number of objects that you want to limit this entry to, and then click OK. For example, type 350 to increase the value for the object.
9. Restart the Microsoft Exchange Information Store service.
If it still doesn’t help, please check ULS log for related error message.
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 Subscriber Support, contact
[email protected] .
Rebecca Tu
TechNet Community Support

After Exchange 2010 SP3 upgrade, UAG publised OWA is throwing a "You do not have permissions to view this folder or page" error

Hi,
We have an issue with our OWA page. We are currently publishing OWA via UAG.
We recently upgraded to Exchange 2010 SP3 and then SP3 Rollup7. Since the upgrade, we are keep getting the following error after entering our credentials on the login page. I've tried with every possible browser.
You do not have permissions to view this folder or page
Strangely enough, the mobile phones are sending and receiving emails just fine, the phones use the same OWA link, so it's not an authentication issue, the phones login into the UAG servers with no issues. I can see this on the Active Sessions screen
on Web Monitor.
I've attempted to connect to the OWA by bypassing the UAG server, so putting in the local OWA address of one of my Exchange servers, it works... so the OWA page is up and running.
No error logs get generated on Web Monitor when we receive the permission error, I think this is because it's past authentication, it's on the Exchange layer.
Any insight would be helpful? I'm assuming something changed on the Exchange side after the upgrade.
Just in case, I've upgraded the UAG and TMG servers to the latest SP and Rollup packets.
UAG > SP4
TMG > SP2 Rollup 5

I've found a solution; UAG requires Basic Authentication over OWA. For some reason Integrated Windows Authentication got turned on after the SP3 upgrade.
http://technet.microsoft.com/en-us/library/ee921443.aspx
Turning Integrated Windows Authentication off via the Client Access OWA settings resolved the issue. Though beware, you
have do this on all your Client Access servers.

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

Is WMF3 or WMF4 supported in Exchange 2010 SP3 UR5 installed on Server 2008 R2 SP1?

We'd like to upgrade WMF (aka powershell) on our Exchange 2010 servers but I haven't been able to find any updated information on support with the most recent servicepack/update rollup.
Is installing WMF3 or WMF4 supported on Server 2008 R2 SP1 w/ Exchange 2010 SP3 UR5?

WindowsPowerShell 3.0 is supported. Haven't seen 4.0 running for exchange 2010 on 2008 R2
http://blogs.technet.com/b/heyscriptingguy/archive/2013/11/30/weekend-scripter-wmf-powershell-and-exchange-server-compatibility.aspx
http://blog.crayon.no/blogs/janegil/archive/2013/11/17/how_2D00_to_2D00_install_2D00_windows_2D00_powershell_2D00_4_2D00_0.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
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.
Gulab,
Where did you read that WMF3 is supported on Exchange 2010 SP3 on Server 2008 R2?
Neither of the links you pasted suggest that and in fact explicitly say "There has been no testing with ExchangeServer 2010 SP3 and WMF 3.0 installed on Windows Server 2008 R2."
My Bad, that was TYPO...
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
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 - Can DAG member be on OS 2012 R2 STD?

Hi guys.
We have Exchange 2010 SP3 on 2008 r2 enterprise.
now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
with best regards,
bostjanc

Hi guys.
We have Exchange 2010 SP3 on 2008 r2 enterprise.
now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
with best regards,
bostjanc
No. It wont let you do that.
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx
DAGs are available in both Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition. In addition, a DAG can contain a mix of servers running Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition.
Each member of the DAG must also be running the same operating system. Exchange 2010 is supported on both the Windows Server 2008 and Windows Server 2008 R2 operating systems. All members of a DAG must run either Windows Server 2008 or Windows Server 2008
R2. They can't contain a combination of both Windows Server 2008 and Windows Server 2008 R2.
In addition to meeting the prerequisites for installing Exchange 2010, there are operating system requirements that must be met. DAGs use Windows Failover Clustering technology, and as a result, they require the Enterprise version of Windows.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Problems with OWA after installing Exchange 2010 SP3

Hi,
I just installed Exchange 2010 SP3 on a SBS 2011 machine. The installation completed successfully, but after the installation OWA isn't working anymore. When I browse to OWA I get the following message:
I did a reset for the OWA vritual directory, but nothing helps..
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Microsoft.Exchange.Clients.Owa.Core.Logon..ctor() +28
ASP.auth_logon_aspx..ctor() +17
__ASP.FastObjectFactory_app_web_9ficbu1h.Create_ASP_auth_logon_aspx() +30
System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +137
System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +49
System.Web.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +424
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +262

Hi Alelieveld,
When you reset a virtual directory, the virtual directory is removed and a new virtual directory with default settings is created.
After you reset the VD, did you restart IIS?
For more information, please see:
Reset Client Access Virtual Directories
http://technet.microsoft.com/en-us/library/ff629372(v=exchg.141).aspx
Frank Wang
TechNet Community Support

SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine. SnapDrive sees my drives. SME connects to Exchange Server. However in the process of configuring SME, I get the following error. I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem. Has anyone run into this before? SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3. I am in a real bind here. Thanks in advance.

the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

Exchange 2010 SP3 - Delayed emails with XLSM attachments...

Running Exchange 2010 SP3 Rollup 5. Clients running Windows 7 and Office 2010 Pro Plus SP2. Have one specific user / client that when sending emails with an XLSM attachment around 5:30AM, the email is delayed getting to the Exchange server and
is delayed up to 16 hours. Unfortunately, this is a random occurrence, and not necessarily easy to duplicate.
The Sent Items on the Outlook client reflect the correct sent time, but the Message Tracking Log on the Exchange server shows the server did not receive the email until approximately 12 to 16 hours later.
The desktop is a shared system and this issue appears to be isolated to the user's profile, AD account, or Exchange. I've literally blown away the users local profile and reconfigured it with no resolution.
Any suggestions are greatly appreciated.
Fuel

Hi,
Please verify whether there is any error/warning/information message left in App log. If yes, please paste the details without sensitive information.
I suggest re-send a .xlsm attachment for testing to verify whether it delays.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2010 SP3 UR9 OWA users cannot open mail items

We recently had users reporting unable to open items in OWA. Issue is confirmed across all CAS servers.
Issue started while on Exchange 2010 SP3 UR8v2, we upgraded to Exchange Server 2010 SP3 UR9 during troubleshooting.
3 AD Site DAG, multi-role servers
So far we have done the following to troubleshoot:
* Check security propagation for account permissions.
* Check security on all virtual directories.
* Check permissions on web.config
* Re-run PrepareAD
* Uninstall and reinstall CAS role
Please review the errors below and let me know if you have any words of wisdom on this issue. Thanks!
Errors:
Request
Url: https://domain.com:443/owa/forms/premium/SubPageEventHandler.aspx?ae=Item&a=Preview&t=IPM.Conversation&id=CID.K5jy5dmxQru9sRoituQBvQ%3d%3d.LgAAAAD5wKVzMPRWToarE%2bpbowlJAQAqvhe3P6jjT4tregHxbY2pANbZjrf2AAAB.1DEA1tmOt%2fIAAAAAiIUWAAAAAAA%3d&calist=&canary=BV_LDf9RIkOwB1AREM0QuJ6gLZ_9QNIIWwpFOZKWH-iRvFnaQLhvOrQQBEkvAoafNX8eyWt3pOI.&SP=1&pfmk=M46%3a1427993956363&subpage=ReadConversation.ascx
User: user
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
SMTP Address: [email protected]
OWA version: 14.3.235.1
Mailbox server: server.domain.com
Exception
Exception type: System.UriFormatException
Exception message: Invalid URI: The format of the URI could not be determined.
Call stack
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
Microsoft.Exchange.Clients.Owa.Premium.ConversationUtilities.LoadConversation(UserContext userContext, OwaStoreObjectId owaConversationId, PropertyDefinition[] requestedProperties)
Microsoft.Exchange.Clients.Owa.Premium.ReadConversation.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Request
Url: https://domain.com:443/owa/forms/premium/SubPageContainer.aspx?ae=Item&a=Open&t=IPM.Note&id=RgAAAAD5wKVzMPRWToarE%2bpbowlJBwAqvhe3P6jjT4tregHxbY2pANbZjrf4AACsvITjR9r%2fQaXcC90BhfOwAI8oXwgBAAAJ&pspid=_1427993955843_521407833&subpage=ReadMessage.ascx
User: user
EX Address: /o=company/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=user
SMTP Address: [email protected]
OWA version: 14.3.235.1
Mailbox server: server.domain.com
Exception
Exception type: System.UriFormatException
Exception message: Invalid URI: The format of the URI could not be determined.
Call stack
System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind)
Microsoft.Exchange.Security.RightsManagement.DrmClientUtils.GetServiceLocation(SafeRightsManagementSessionHandle sessionHandle, ServiceType serviceType, ServiceLocation serviceLocation, String issuanceLicense)
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetOnPremiseRmsServerUri()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.GetRmsServerActiveCryptoMode()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.DrmEnvironment.InitializeEnvironment()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.Initialize()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.InitializeIfNeeded()
Microsoft.Exchange.Data.Storage.RightsManagement.RmsClientManager.get_IRMConfig()
Microsoft.Exchange.Clients.Owa.Core.UserContext.get_IsIrmEnabled()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddIrmMessageToInfobar()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.AddMessagesToInfobar()
Microsoft.Exchange.Clients.Owa.Premium.ReadMessage.OnLoad(EventArgs e)
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Control.LoadRecursive()
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

Hi Noel,
Base on my search, it may be due to IRM feature been enabled for OWA.
I recommend you use the following command to check if the value of IRMEnabled parameter is true:
Get-OWAVirtualDirectory – Identity “servername\owa (default web site)” |FL name,IRMEnabled
If the value is true, you can use "Set-OWAVirtualDirectory" cmdlt to change it to false, and check if any helps.
Best regards,
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]
Niko Cheng
TechNet Community Support

Exchange 2010 SP3 Create Dynamic DL for Direct Reports

I am not sure this is possible but if there is a will there is a way I guess.
System: Exchange 2010 SP3 on Windows Server 2008 R2
I am trying to see if there is a way to create dynamic DLs for Manager(s) direct reports.
Example: Manager has 5 people that report directly to them, is there a way to make an dynamic email distribution list that will poll the direct reports as people leave or hired.
I know I can create one manually but some depts. may have high turnover rates which increase overhead so I am just trying to simplify the process. I of course googled my question but not getting the results I intended.
Thanks.

hi,
as from above i understand you are asking about creating an custom attribute and then referencing them .. if yes please check below command
Get-Mailbox -OrganizationalUnit Sales | Set-Mailbox CustomAttribute1 "SalesOU"Now you can create an e-mail address policy for all recipients that have the CustomAttribute1 property that equals SalesOU, as shown in this example.
New-EmailAddressPolicy -Name "Sales" -RecipientFilter { CustomAttribute1 -eq "SalesOU"} -EnabledEmailAddressTemplates "SMTP:%s%[email protected] check this.. http://technet.microsoft.com/en-us/library/ee423541%28v=exchg.150%29.aspx
MARK AS USEFUL/ANSWER IF IT DID
Thanks
Happiness Always
Jatin

Exchange 2010 SP3 RU8

Similar Messages

Maybe you are looking for