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
Similar Messages
-
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 CatoHi 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 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 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 BHi 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 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,
AJThanks 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 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 failsThere 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 : DotNetMethodExceptionHi,
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 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 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 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.
FuelHi,
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 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 -
Latest Update Rollup for Exchange 2010 SP3
Hi
Currently we are using RU2 for Exchange 2010 SP3. We are facing an issue with OWA through IE 11 (no support for premium). To correct this issue it's recommended to install RU3. Here we are asking the expert opinion about installing RU7
on all Exchange 2010 servers and whether it makes any different issues or is it enough to install RU3
Thanks in advance
LMSHi
Currently we are using RU2 for Exchange 2010 SP3. We are facing an issue with OWA through IE 11 (no support for premium). To correct this issue it's recommended to install RU3. Here we are asking the expert opinion about installing RU7
on all Exchange 2010 servers and whether it makes any different issues or is it enough to install RU3
Thanks in advance
LMS
Personally, if you are going to update the servers, you should apply the latest RU regardless. So I would go with RU7.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
Does Outlook "Connection Status" Show Rollup Updates on Exchange 2010 SP3
Hi all,
I've looked for this answer everywhere, and can't seem to find it. When you CTRL right-click on the Outlook taskbar icon, and select "Connection Status", one of the pieces of information displayed is the Version number of the connected Exchange
server.
Does this build number include installed rollup updates, or does it show only the installed Service Pack. For example, if it's an Exchange 2010 SP3 server with RU6 installed, will I see 14.3.195.1
or just 14.3.123.4 (the SP3 build number)? I'm trying to use this information to troubleshoot
client issues, and it'd be helpful to quickly see if certain updates are installed on the Exchange server or not.
Thanks!Hi,
Just as what mentioned above, connection status displays the Exchange version number.
Start Outlook and connect to the Exchange server if this isn’t done automatically already.
Hold CTRL while clicking on the Outlook icon in the Notification Area
(located in the right bottom area near the time; expand the Notification Area first if the Outlook icon does not show).
From the context menu that pops-up choose: Connection Status…
Scroll the horizontal scrollbar to the right to see the Version column.
(if the dialog is empty, then you are not connected to Exchange)
Here you’ll see a version number.
Best regards,
Belinda Ma
TechNet Community Support -
Exchange 2010 SP3 Update Rollup 6 breaks first OWA login (timezone selection) on SBS 2011
The Exchange 2010 SP3 Update Rollup 6 broke the OWA for Users who access OWA for the first time and have to set a timezone. They get this error:
Request
Url: https://xxxxx:443/owa/languageselection.aspx
User: xxxxxx
EX Address: /o=First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=xxxxx
SMTP Address: xxxxxx
OWA version: 14.3.195.1
Exception
Exception type: System.ArgumentNullException
Exception message: Value cannot be null. Parameter name: value
Call stack
Microsoft.Exchange.Clients.Owa.Core.Utilities.RenderDirectionEnhancedValue(TextWriter output, String value, Boolean isRtl)
Microsoft.Exchange.Clients.Owa.Core.LanguageSelection.RenderTimeZoneSelection()
ASP.languageselection_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer)
System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children)
System.Web.UI.Page.Render(HtmlTextWriter writer)
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
This Server is an SBS2011.
The update broke nothing on a "normal" 2008R2 with exchange 2010.
Uninstalling RU6 helped but thats obviously not the desired way.
Removing the RenderTimeZoneSelection() call from languageselection.aspx obviously helped but then there is no timezone dropdown displayed anymore. The timezone dropdown is working normaly in other places like ecp. Afaik this error occours only in the languageselection.aspx
file which is displayed for "new" OWA users. (Users without a timezone set)
my workaround was to set the language and timezone for these mailboxes via exchange shell.Hello,
Thank you for your post.
This is a quick note to let you know that we are performing research on this issue.
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support -
Exchange Server 2010 SP3 RU 8v2 & ActiveSync Device Quarantined Emails
Hi there,
We are using Exchange Server 2010 SP3 and I recently installed RU 8v2. We always had an ActiveSync Access Policy in place where the devices are quarantined until an Administrator goes in and approves or rejects this.
Prior to installing RU 8v2, there used to be a link in the email sent to Administrators to click on to login to the ECP and approve this device. However, since the install of this update, there is no link in the emails now. It just informs you that you need
to login to ECP and view the quarantined devices. Has this been removed in the RU?
ThanksHi,
According to your post, I understand that quarantine notifications e-mail will not send to administrators after install Exchange 2010 SP3 RU8v2.
If I misunderstand your concern, please do not hesitate to let me know.
Please login ECP to double check the Allow/Block/Quarantine list rule configuration, for your reference:
http://blogs.technet.com/b/exchange/archive/2010/11/15/3411539.aspx
Besides, Exchange 2010 SP3 RU 9 has released on March 17, 2015. Please upgrade to latest version.
Additional, this issue is related to ActiveSync. Please We recommend contact Mobility and ActiveSync Team so that you can get more professional suggestion.
Please refer to:
https://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrmobility
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
Maybe you are looking for
-
ITunes 10.6.1 x64 regularly stops responding.
Hello - My name is Erick and I'm an ACMT/Network Engineer; Apple-certified, but not Apple-employed. I have experienced an issue with iTunes 10.6 in general that has not been resolved by the latest update to 10.6.1. Upon opening the iTunes application
-
Help, why keyRepeated doesn't work
Hello, I created a class to extend GameCanvas in midp2.0. In this class, I overwrote "keyPressed ()","keyReleased()","keyRepeated()" three methods. "keyPressed ()","keyReleased()" both work very well to capture the key. But keyRepeated doesn't work.
-
i got a new computer aswell so itunes isnt the same...
-
Can we use two table in on report
HI how to use two different table views in one report. Regards Birudu
-
Can't run programs or save?
Trying to update some programs of mine and I am unable to. I click on the item to download and it comes up "Save or Run" and no matter what I click on it will act like its downloading and then it disappears. Nothing saves and nothing runs. Any help p