UAG SP3 Rollup 1 - Hotfix

I have a UAG 2010 Array with 5 members for Direct-Access only. I'm needing to upgrade to SP4 to support Windows 8.1 DA clients and have a question about the Rollup 1.
Do I need to go through the same process I used for a Service Pack - Upgrading the Array Manager first, activating, then each member after and activate - or can I just apply the hotfix and reboot?

Hi,
By experience i would recommand to follow the same process as for a SP :
http://technet.microsoft.com/en-us/library/dn511694.aspx
BenoitS - Simple by Design http://danstoncloud.com/blogs/simplebydesign/default.aspx

Similar Messages

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

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.

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

Contacts created with Lotus notes are not seen in Exchange 2007 SP3 Rollup 7.

Contacts created with Lotus notes are not seen in Microsoft Exchange 2007 SP3 Rollup 7. the same is seen in Microsoft Exchange 2010 without issues.
when we create a new contact on Microsoft Exchange 2007, the contacts gets created but it is not seen unless we filter the EMC to list the contacts. Microsoft Exchange 2010 does not have any issues.
any help or inputs will be appreciated.
Thanks,
Sid

You shouldn't be using the 2007 EMC or cmdlets to create new objects if you have a more recent release installed in your organization. Use the 2010 software.
If you create the mail-enabled contact with the 2010 EMC or cmdlets do you see it in the 2007 EMC?
When you say the contact "is not seen unless we filter the EMC to list the contacts", does that mean you don't see the contact when you're looking at the "Recipient configuration" container? Is there a default filter on that container? Do you have a limit
on the number of objects shown?
As for the objects created by 3rd-party software (Lotus), are they creating the contacts correctly?
--- Rich Matheisen MCSE&I, Exchange MVP

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 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 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

Unable to install Exchange 2007 SP3 Rollup 13

Grettings,
I have a Server 2008 SP2 (64bit) DC with Exchange Server 2007 SP3 installed.
I have followed all the pre-reqs per http://technet.microsoft.com/en-us/library/ee221147%28EXCHG.80%29.aspx?ppud=4
However, it keeps failing. I've run the install in debug mode (/lvx*) and have narrowed it down to the following, but I can't make sense of it.
All the proper services are running (WMI, various exchange services), all proper rights are give (domain admin, exchange admin, etc...) And proper user-rights are setup.
No GPO's are setup.
Need help. Here is a partial log:
MSI (s) (74:14) [12:42:39:535]: Doing action: InstallExecute
Action 12:42:39: InstallExecute.
Action start 12:42:39: InstallExecute.
MSI (s) (74:14) [12:42:39:550]: Running Script: C:\Windows\Installer\MSI16A2.tmp
MSI (s) (74:14) [12:42:39:550]: PROPERTY CHANGE: Adding UpdateStarted property. Its value is '1'.
MSI (s) (74:14) [12:42:39:550]: Machine policy value 'DisableRollback' is 0
MSI (s) (74:14) [12:42:39:550]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (74:14) [12:42:39:550]: Executing op: Header(Signature=1397708873,Version=405,Timestamp=1151821140,LangId=1033,Platform=589824,ScriptType=1,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (74:14) [12:42:39:550]: Executing op: ProductInfo(ProductKey={24B2C164-DE66-44FE-B468-A46D9D5E6B31},ProductName=Microsoft Exchange Server,PackageName=exchangeserver.msi,Language=1033,Version=134414419,Assignment=1,ObsoleteArg=0,,,PackageCode={16D94F8A-4406-41EA-9146-7A80F4F42DC1},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3)
MSI (s) (74:14) [12:42:39:550]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (74:14) [12:42:39:550]: Executing op: DialogInfo(Type=1,Argument=Update Rollup 13 for Exchange Server 2007 Service Pack 3 (KB2917522))
MSI (s) (74:14) [12:42:39:550]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back actions,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1])
MSI (s) (74:14) [12:42:39:550]: Executing op: SetBaseline(Baseline=0,ProductVersion=8.3.83)
MSI (s) (74:14) [12:42:39:566]: Executing op: SetBaseline(Baseline=1,)
MSI (s) (74:14) [12:42:39:566]: Executing op: ActionStart(Name=CA_CUSTOMER_PATCH_ROLLBACK,,)
Action 12:42:39: CA_CUSTOMER_PATCH_ROLLBACK.
MSI (s) (74:14) [12:42:39:566]: Executing op: CustomActionSchedule(Action=CA_CUSTOMER_PATCH_ROLLBACK,ActionType=1345,Source=BinaryData,Target=CAQuietExec,CustomActionData="D:\Program Files\Microsoft\Exchange Server\\bin\QuietExe.exe" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
" -command . 'D:\Program Files\Microsoft\Exchange Server\\scripts\customization\CustomPatchInstallerActions.ps1' PatchRollbackActions")
MSI (s) (74:14) [12:42:39:566]: Executing op: ActionStart(Name=CA_CUSTOMER_PREPATCH_INSTALL,,)
Action 12:42:39: CA_CUSTOMER_PREPATCH_INSTALL.
MSI (s) (74:14) [12:42:39:566]: Executing op: CustomActionSchedule(Action=CA_CUSTOMER_PREPATCH_INSTALL,ActionType=1089,Source=BinaryData,Target=CAQuietExec,CustomActionData="D:\Program Files\Microsoft\Exchange Server\\bin\QuietExe.exe" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
" -command . 'D:\Program Files\Microsoft\Exchange Server\\scripts\customization\CustomPatchInstallerActions.ps1' PrePatchInstallActions")
MSI (s) (74:14) [12:42:39:566]: Creating MSIHANDLE (17) of type 790536 for thread 5908
MSI (s) (74:F8) [12:42:39:566]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI183A.tmp, Entrypoint: CAQuietExec
MSI (s) (74:EC) [12:42:39:566]: Generating random cookie.
MSI (s) (74:EC) [12:42:39:582]: Created Custom Action Server with PID 4576 (0x11E0).
MSI (s) (74:40) [12:42:39:660]: Running as a service.
MSI (s) (74:40) [12:42:39:675]: Hello, I'm your 32bit Impersonated custom action server.
MSI (s) (74!80) [12:42:40:832]: Creating MSIHANDLE (18) of type 790531 for thread 3712
CAQuietExec: Error 0x80070001: Command line returned an error.
MSI (s) (74!80) [12:42:40:832]: Closing MSIHANDLE (18) of type 790531 for thread 3712
MSI (s) (74!80) [12:42:40:832]: Creating MSIHANDLE (19) of type 790531 for thread 3712
CAQuietExec: Error 0x80070001: CAQuietExec Failed
MSI (s) (74!80) [12:42:40:832]: Closing MSIHANDLE (19) of type 790531 for thread 3712
MSI (s) (74:F8) [12:42:40:832]: Closing MSIHANDLE (17) of type 790536 for thread 5908
MSI (s) (74:14) [12:42:40:847]: Executing op: ActionStart(Name=CA_ROLLBACK_SAVEDATA_STOP_SERVICES,,)
Action 12:42:40: CA_ROLLBACK_SAVEDATA_STOP_SERVICES.
MSI (s) (74:14) [12:42:40:847]: Executing op: CustomActionSchedule(Action=CA_ROLLBACK_SAVEDATA_STOP_SERVICES,ActionType=1281,Source=BinaryData,Target=CAQuietExec,CustomActionData="D:\Program Files\Microsoft\Exchange Server\\bin\QuietExe.exe" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
" -command . 'D:\Program Files\Microsoft\Exchange Server\\bin\servicecontrol.ps1' AfterPatch")
MSI (s) (74:14) [12:42:40:847]: Executing op: ActionStart(Name=CA_SAVEDATA_STOP_SERVICES,Description=Stopping services,Template=Service: [1])
Action 12:42:40: CA_SAVEDATA_STOP_SERVICES. Stopping services
MSI (s) (74:14) [12:42:40:847]: Executing op: CustomActionSchedule(Action=CA_SAVEDATA_STOP_SERVICES,ActionType=1025,Source=BinaryData,Target=CAQuietExec,CustomActionData="D:\Program Files\Microsoft\Exchange Server\\bin\QuietExe.exe" "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe"
" -command . 'D:\Program Files\Microsoft\Exchange Server\\bin\servicecontrol.ps1' BeforePatch")
MSI (s) (74:14) [12:42:40:847]: Creating MSIHANDLE (20) of type 790536 for thread 5908
MSI (s) (74:BC) [12:42:40:847]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI1D3D.tmp, Entrypoint: CAQuietExec
MSI (s) (74!44) [12:50:03:781]: Creating MSIHANDLE (21) of type 790531 for thread 5444
CAQuietExec: Error 0x80070001: Command line returned an error.
MSI (s) (74!44) [12:50:03:797]: Closing MSIHANDLE (21) of type 790531 for thread 5444
MSI (s) (74!44) [12:50:03:797]: Creating MSIHANDLE (22) of type 790531 for thread 5444
CAQuietExec: Error 0x80070001: CAQuietExec Failed
MSI (s) (74!44) [12:50:03:797]: Closing MSIHANDLE (22) of type 790531 for thread 5444
MSI (s) (74:BC) [12:50:03:797]: Closing MSIHANDLE (20) of type 790536 for thread 5908
Action ended 12:50:03: InstallExecute. Return value 3.
/r
Joe Hanchey

Hi Joe,
Glad to know that you have solved this issue.
Thanks for your generous sharing.
Have a nice day : )
Thanks
Mavis
Mavis Huang
TechNet Community Support

Export mailbox from 2010 (sp3) and import into 2007 Sp3 rollup 10

I have no issue exporting the mailbox from 2010.
The issue is importing into 2007. I have a 2003 32 bit server with outlook 2003 sp2 running etc. Every time I try to import I get the below error. Is this even supported?
I've scoured the web, tried fixmapi, added permissions, different switches, etc. The pst attaches fine to the mailbox without issues.
[5/15/2014 8:15:51 AM] [0] [2007import2] Opening Exchange mailbox.
[5/15/2014 8:15:51 AM] [0] [ERROR] Error was found for 2007import2 ([email protected]) because: Error occurred in the step: Approving object. An unknown error has occurred., error code: -2147221219
[5/15/2014 8:15:51 AM] [0] [2007import2] The operation has finished.
Any help or sugesstions would be great!

Steve I see that Belinda suggests that this may be a bug and that you are on SP3, however it may be that you need to update your systems completely to see if the issue is resolved. To be able to find the actual patch level you are on you would need
to follow the steps below. Once you know your actual patch level you can either just update to the latest and greatest and try again OR read through the various fixes for each patch newer then what you have applied
1.   This is the link for the Exchange Server Build #'s including Service Packs
http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollups-builds-numbers.aspx
a.   Only thing you will not find in this list are the IU (Interim Update #’s) because they are unofficial patches to fix specific issues and then must be uninstalled before moving on to the next RU, CU or SP.
2.   To find the SP, RU, CU level that your server is on use this Powershell command.
GCM exsetup |%{$_.Fileversioninfo}
EXAMPLE 1: Below is the result from a server with 2010 SP1 RU6 installed and you will see this referenced in the above link
Product Version         File Version          File Name
14.01.0355.002           14.01.0355.002   C:\Program Files\Microsoft\Exchange Server\V14\bin\ExSetup.exe
EXAMPLE 2: Below is the result from a server with 2010 SP1 RU6 installed WITH an IU from MS and you will not see this version referenced in the above link but it is sequential, i.e. SP1 RU6 is .002 and the IU is 003. So in short by looking at this
and the above link you could easily infer that this system has SP1 RU6 with some type of IU installed.
ProductVersion   FileVersion      FileName
14.01.0355.003   14.01.0355.003   C:\Program Files\Microsoft\Exchange
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

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 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.

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

Microsoft.Exchange.RpcClientAccess.Service.exe 50% cpu usage after sp3 rollup 6

Hi,
Anybody having the same issue?
Running on 2008 R2 on hyper-v 2012R with 2 virtual cores and 20gb of Ram.
thx

Hello,
Also check the application log to see whether there are related error reports.
Thanks,
Simon Wu
TechNet Community Support

Exchange 2007 SP3 Rollup 2 installed - OWA stopped working!

After running this update on our Exchange server, everything seemed fine. Then a few days later, someone said they can't access /owa. At first I wasn't able to recreate the problem in IE8 but on other browsers I was getting the 403 access denied
error. Then playing around with the HTTP redirects I was able to get the same error. Now i can't get OWA working at all. I have this article settings which worked before
http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx . Now no go. Also, can't get to owa from IIS 7 directly anymore. My domain admin credentials don't take
so not sure if the virtual directory is missing somehow or what's causing this. Also, my iPhone still receiving email so not sure why owa isn't working.

Yeah, I did the kb/941201 but that didn't help either (the other link appears to be broken). Microsoft was kind enough to help me without charge. Here's the correct IIS 7 settings that got it working again for me.
Default Web Site - Authentication = Anonymous + Windows, SSL = unchecked + igonore, HTTP Redirect = Check Redirect (entery your
https://URL), Check "Only redirect" box and Status code Found 302.
owa - Authentication = Basic, SSL = Check Require SSL + 128-bit SSL + Ignore radio button, HTTP Redirect = Unchecked
I already had this in EMC but just in case - expand Server Configuration>Client Access>r-click owa under Outlook Web Access tab>Properties Authentication tab and check the USE forms-based authentication button Logon Format: Domain\user name.
And not sure how the service pack messed up those IIS settings. They say not to play with the IIS settings, but hope this helps someone.

UAG SP3 Rollup 1 - Hotfix

Similar Messages

Maybe you are looking for