Outlook 2013 Category view not updating after Exchange 2010 SP3 RU3

After updating to Exchange 2010 SP3 RU3 last night, users who use categories view in Outlook 2013 are complaining that the view does not update. The alert is received in the notification area and the unread message count next to Inbox updates appropriately.
The view can be force updated by switching between All and Unread, by using Reset View, or closing and opening Outlook.  It seems anything that forces a 'redraw' of the view will update it - except for the actual reception of email.  I easily replicated
this issue.  For reference:
Exchange 2010 SP3 RU3
Windows 7 x64 Ent
Outlook 2013 (15.0.4551.1004) 32-bit
I do see that SP3 RU4 has been released, however the only change listed is a security patch.
Thank you for any ideas.

Hi, Everyone –
This has been a known issue for a very long time – we have people at our workplace that are very disappointed since a feature as great as categorizing email (not using tasks) has become broken and has not even been considered to be fixed for
over half a year.  It was not fixed in the updates for Patch Tuesday this week.
I would like to confirm that this is an issue with Outlook 2010 and 2013 when running the latest Exchange 2010 and there is NO FIX
– I have scoured the internet for a solution – all proposed "textbook" solutions do not work and I am positive that the issue can be recreated; however, everyone from Microsoft does not mention trying to recreate the issue at all. 
The workaround of creating a rule to send new emails to a category could break other pre-existing rules and cause more frustration and wasted time for users/IT before and after the issue is fixed.
Please fix this issue sooner than later, as the Categories view is completely broken and unusable at this point in time.
Regards,
IT Helper

Similar Messages

  • 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 - RU3 RU4 Public Folders issues ( not refreshing ) when grouping by Categories for "(None)" Group

    After installing Exchange 2010 SP3 RU3, I had an issue in Public Folders, once having group by categories in Outlook, the Group of "(None)" categories is not refreshing when changing flag... I also installed RU4 but nothing changed, any reason
    Thx

    Hi,
    From your description, the group with none categories won’t fresh when changing flag in Category view. If I misunderstood, please point it out.
    As you can in the View tab as below, there is Category as well as Flag: Start date or Due Date. It means that grouping per color categories is more or less different from that
    grouping by flag.
    Should you need more assistance, feel free to tell me.
    Regards,
    Rebecca Tu
    TechNet Community Support

  • After Exchange 2010 SP3 and rollup 4 update conditional formatting causes messages not to appear in Outlook 2010

    Hi,
    after updating to exchange 2010 sp 3 from sp 2 and also updating to rollup 4, users who use conditional formatting cannot see new message unless they close and reopen Outlook.
    If you decide to change the font colour for unread messages, the messages do not appear in Outlook but a pop up indicates that a new message has arrived.
    If you reopen Outlook, the unread messasge appears.
    remove the conditional formatting and no issue with viewing unread messages as they arrive.
    running Outook version 14.0.7106.5003
    is this a known issue?  a user who never used conditional formatting will experience this right away.
    Thanks,
    rudif

    Hi rudif,
    If the issue only happens to users who use conditional formatting and OWA can work well for all mailbox, I think the issue should be in client side.
    Please try to reset View then set the conditional formatting back to have a try. If the issue continues, please try to recreate the Outlook profile to check whether the issue persists. Also try restarting Outlook in Safe mode by running
    Outlook /safe switch.
    Thanks,
    Winnie Liang
    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.  

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

  • Outlook 2013 asks for credentials connecting to Exchange 2010 multiple times

    I'm having a problem with Outlook 2013 asking for my credentials a few times a day for no apparent reason. Some info on my setup...
    CLIENT
    Windows 7 Professional SP1 64 bit, fully patched
    Office 2013 Pro Plus 32 bit, fully patched (has there even been any patches released yet?)
    Outlook auto-configured to Exchange during setup.
    Online Archive setup with server
    Connected via gigabit ethernet on same network and domain as Exchange server.
    SERVER
    Exchange 2010 SP2, fully patched.
    One server, holds all roles.
    I have zero clue as to why I'm getting popped for credentials. This did not happen prior to my upgrade to Office 2013. I was previously using Office 2007 Pro Plus.
    My credentials are always accepted, never a problem putting them in.
    Thanks in advance!

    I have been testing and testing also for days, then waiting for any responses to other people's questions on other places as well.
    After some time started my own tries again.
    Now I fixed my issue - don't fully comprehend it. But anyway here comes the solution that worked for me (and hopefully for more of y'all)...
    Go to the Exchange account from within Outlook, click special settings, tab connection. Open up the button proxy settings, UNtick options 3 and 4 (connections with HTTP/then TCP/IP). Make sure to UNtick both.
    Press OK, Hit Save and OK again. Press NEXT and close the screens.
    Logout from Outlook. LOG OFF your RDP session if you're in one. Restart the RDP session after some 15 seconds. Or start Outlook if you were only in Outlook.
    My issue was then solved.

  • Exchange 2013 EAC will not run with Exchange 2010 CAS\HT servers shut down.

    Hi Folks,
    A little background - We have just migrated all our user mailboxes and public folders to Office 365 using a hybrid configuration. Now that the migration is essentially finished, I'd like to decommission our on-prem Exchange infrastructure and remove the
    hybrid config. We are using dirsync with password sync to replicate our AD to the cloud.
    I've read that even if you remove your hybrid configuration, it's a good idea to keep one on-prem Exchange server around so you can edit Exchange attribs (such as email addresses) in a supported manner, rather than using ASDI edit, etc.
    To this end, I installed a single Exchange 2013 CA\MBX server. After installation, the EAC worked fine, and I was able to view our on-prem users, groups, etc. Last week, I shut down our two Exchange 2010 CAS\HT servers as a test to see if anything broke
    prior to decommissioning them (these were the hybrid servers as well). After doing so, the Exchange 2013 EAC no longer works for some reason, and behaves in a very bizarre fashion. About once every 20 times or so, it will actually start and run. The other
    times, it just has you enter your creds, then generates an HTTP 500 internal server error after entering them. It seems to make no difference if you attempt to access it by the fqdn, hostname, or localhost right on the box itself. Same behavior on Chrome or
    IE.
    Today as a test, I started up one of the 2010 CAS servers and lo and behold, the 2013 EAC ran without difficulty again. Any idea why this might be so? Thanks for any help,
    Ian

    Hi,
    From your description, I recommend you use the following URL to check if you can access EAC. I see it works for several people about this issue.
    https://<Exchange 2013 CAS FQDN>/ecp?ExchClientVer=15
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Online Archives in Outlook 2010 disappeared after Exchange 2010 SP3 upgrade

    I have Exchange 2010 and noticed it has never been updated since having it in production for 3 years now. So I downloaded SP3 and installed it after hours. After the install was complete, rollups 5,6,7, showed up in Windows Update so I installed those too.
    Before I did the upgrade to SP3, I had Online Archives visible on just my user account mailbox and have about 2 years worth of emails in there. Since the upgrade, it is no longer visible in my Outlook 2010. I have tried to fix to remove SELF and re add it
    to the mailbox with no change to the issue. I have tried to disable Archive for my mailbox and re-add. Nothing. Don't really know what else to try. Any ideas?

    Anyone?

  • OOF not working after Exchange 2010 install

    I have a Exchange 2007 server environment where I recently installed a new Exchange 2010 server.  After installing the 2010 server, my clients are receiving the following error when trying to configure OOF.  "Your automatic reply settings
    cannot be displayed because the server is currently unavailable.  Try again later."  I've not moved any mailboxes to the new server, just installed it.
    I've done all the tests I can find online and all pass without issue.  I'ma able to get to the OOF URL without issue as well.
    The 2007 server is on SP 3 rollup 12.

    Hi,
    The above problem generally occurs because the CAS server uses the credentials that you used to log on to Windows instead of the credentials that you used to log on to the mailbox in Outlook. I recommend you install the hotfix in the following KB to solve
    this issue.
    "Your Out of Office settings cannot be displayed, because the server is currently unavailable. Try again later" error when you try to open the Out of Office Assistant in Outlook 2010
    http://support.microsoft.com/kb/2596516
    Hope it helps.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support
    Not sure that would be the issue with every machine on the network, plus the user I'm logging in with is the mailbox I need to access so the credentials should be the same.

  • Outlook 2011 for Mac not authenticating with Exchange 2010

    Hi,
    We have an issue with our Mac Clients authenticating with our Exchange Server. We have Exchange 2010 Version 14.03.0174.001. 
    Outlook is saying the credentials are incorrect for the user when we know they work fine in OWA and in Outlook 2010.
    It seems this is since we re-keyed are SSL certificate. I have changed the EWS directory to Basic Authentication and also re-created the EWS directory. I have also re-ran all the SBS Wizards.
    Is there anything else we can do to get this sorted?
    Thanks 

    Hi Robert,
    I found a KB for your reference:
    Sending email error "Authentication failed. Error 17897" in Outlook 2011 for Mac
    http://support.microsoft.com/kb/2492901
    If it not matches to yours, please paste the details without sensitive information.
    Thanks
    Mavis
    Mavis Huang
    TechNet Community Support

  • AutoDiscover not working after Exchange 2010 SP2 - SP3 update.

    Hi Everyone, 
    I'm sorry if this is a really simple thing, but i've played around for hours and exhausted google.
    I run a 2010 exchange server for everyone at the office, and today I updated from 2010 SP2 to SP3.
    The problem I have is auto discover no longer accepts anyones username or password. If you set the account up on the client machine by manually entering the details everything works great.
    All the DNS records are correct and have been working for 2+ years. I have recreated the Autodiscovery virtual directory in EMC.
    If i manually browse to mydomain/Autodiscover/Autodiscover.xml, when asked for a username and password it says it incorrect. I can then log in to OWA with the same credentials and it works. 
    Thanks,
    Garrett
    The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://mydomaincom.au:443/Autodiscover/Autodiscover.xml for user mydomain.com.au.
    The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response.
    Additional Details
    An HTTP 401 Unauthorized response was received from the remote Unknown server. This is usually the result of an incorrect username or password. If you are attempting to log onto an Office 365 service, ensure you are using your full User Principal Name (UPN).
    HTTP Response Headers:
    Transfer-Encoding: chunked
    Connection: keep-alive
    Content-Type: text/html
    Date: Wed, 22 Apr 2015 00:44:51 GMT
    Set-Cookie: __cfduid=dc0261b4643b5dbe27f750bbc28bfef7c1429663490; expires=Thu, 21-Apr-16 00:44:50 GMT; path=/; domain=.macarthurcs.com.au; HttpOnly
    Server: cloudflare-nginx
    WWW-Authenticate: Negotiate,NTLM,Basic realm="mydomain.com.au"
    X-Powered-By: ASP.NET
    CF-RAY: 1dad4d701ae911c5-SJC
    Elapsed Time: 3357 ms.
    Attempting to test potential Autodiscover URL https://autodiscover.mydomain.com.au:443/Autodiscover/Autodiscover.xml
    Testing of this potential Autodiscover URL failed.

    Hi,
    Based on my knowledge, the above issue is caused by the loopback check being enabled. Please follow the steps below to disable loopback on the CAS servers:
    1. Run regedit, in Registry Editor, locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
    2. Right-click Lsa, point to New, and then click DWORD Value.
    3. Type DisableLoopbackCheck, and then press ENTER.
    4. Right-click DisableLoopbackCheck, and then click Modify.
    5. In the Value data box, type 1, and then click OK.
    6. Quit Registry Editor, and then restart your computer.
    Hope this can be helpful to you.
    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]
    Amy Wang
    TechNet Community Support

  • Free/busy information unavailable in Outlook 2013 on Windows 8.1 on Exchange 2010

    Hi,
    This has been discussed a lot inf forums but unfortunately having followed all the guides I have found, I can't resolve it.  I am the only user with the issue.  
    I have primarily followed https://social.technet.microsoft.com/Forums/office/en-US/ee9e1b89-bea1-48aa-9008-cae205c5e816/forum-faq-why-cant-i-retrieve-freebusy-information?forum=outlook 
    including recreating my profile, installing http://support.microsoft.com/kb/2850061/en-us via
    Ofifce 2013 SP1, verifiying the funtion works through OWA etc etc.
    I have the full version of Office 2013 Pro not the Click to Run version.  It seems to be the Outlook client itself not the Exchange server.  I am at a loss what to do next... please help! :)

    Hi,
    Please also enable Automatic Replies in Outlook, check if this feature works well.
    Since the issue only occurs to one client and it works on OWA, I suggest you try these steps below to troubleshoot the issue:
    1. Start Outlook in Safe Mode. It is always a helpful method to troubleshoot Outlook client issues, when in Safe Mode, Outlook doesn't load with add-ins, we can check if this issue persists when add-ins are disabled:
    Press Win + R, type "outlook.exe /safe" in the blank box, press Enter.
    If there's no issue in Safe Mode that you can find free/busy information again, disable the suspicious add-ins to verify which one caused the problem.
    2. Perform a clean boot. This helps determine whether the issue is related to some background programs, any 3rd-party programs will be disabled. If the issue doesn't occur in Clean Boot, then we may suspect it's related to some 3rd-party programs, the detailed
    steps can be found in this link below:
    http://support.microsoft.com/kb/929135
    Regards,
    Melon Chen
    TechNet Community Support
    It's recommended to download and install
    Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
    programs.

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

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

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

  • Exchange 2010 SP3 Rollup 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

Maybe you are looking for