Bug Group by Outlook 2010 - Exchange 2013

Hello,
I work in an IT department. We have Office 2010 and we have just migrate in exchange 2013.
I have a problem with Outlook 2010 (64 bits) : When you used the view Group By From, there are not refresh.
When you read a mail, the mail remains not read, when you delete the mail, the mail is always in the inbox.
To make a refresh, you must collapse and expand the Group.
Best Regard...
Didier

Hi Didier,
It seems that your folder can’t be updated automatically when viewing by From. Please open Outlook by using Outlook /cleanviews switch (Start > Run > type Outlook /cleanviews > Enter) to restore default views. Then change the
folder view to Group by From to check whether the issue persists.
If the issue persists, please create a new Outlook profile to have a try:
http://support.microsoft.com/kb/829918/en-us
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

HTML Form Not Displaying Correctly in Outlook 2010 (Exchange 2013)

Hello,
I have recently migrated to Exchange 2013. Clients are still using Outlook 2010. There is an application that automatically sends an HTML form by email for the users to fill in. The form consists of radio buttons, text areas and drop down list. However,
in Outlook 2010, the form is not rendered properly.
When I clicked the "If there are problems with how this message is displayed, click here to view it in a web browser" link, the email is opened in
IE and the form is displayed correctly.
I also tried opening the same email in other clients, such as Thunderbird, Apple Mail Client and in mobile phones - the form is displayed correctly. I wonder
why it fails to do so in Outlook 2010. The user mentioned that this does not happen in Outlook 2003 and prior to migration (I used Exchange 2010 previously). I have also tried using OWA, but the form does not display correctly
Any help?
Note: I can't attach any images or links as it is mentioned that my account is not verified yet. I will post some screenshots when it is possible to do so

Hi
Outlook 2007 or newer use Microsoft Word for their HTML engine.
You can refer this page http://www.campaignmonitor.com/css/ shows
many things that do not work in different clients.I think Someone needs to re-code
the HTML form to make it work in the current versions of Outlook. You can try formatting with text and HTML and see the results.
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Outlook 2010 (+ Exchange 2013) works extremely slow

We have a user that works with Outlook 2010 (on a RDS Server) that is connected with cache to Exchange 2013. The response of Outlook is extremely slow and we think because this user has a 15Gb mailbox. However, he refuses to delete any mail for various
reasons. Is there any way to speed up Outlook? The rest of the system works fine, it's just the email.

Hi,
By "connected with cache to Exchange 2013", do you mean the user is using Cached Exchange mode? If not, please help the user switch to Cached Exchange mode to check the result. If the user has any shared folders, also cache those folders to check if it helps.
If we try to start Outlook in safe mode, will this issue persists? To open Outlook in safe mode, press Windows key + R to open the Run box, type
outlook.exe /safe and press Enter. If performance improves, check again to make sure that you disabled any Outlook add-ins that may affect performance.
In addition, please click File tab > Info > section Mailbox Cleanup and check your Exchange Quota information. We can also try to close Outlook,
rename the OST file, and then reopen Outlook to re-create the OST file.
For more troubleshooting steps about slow Outlook performance issue, please refer:
http://support.microsoft.com/kb/2441551/en-us
Hope this helps.
Best Regards,
Steve Fan
TechNet Community Support

Outlook 2010 / Exchange 2013: The operation failed. An object could not be found.

Both KB2956128 and KB2956203 causing issue. Removing the patch fixes the issue. I need to know what the best way to remove the patch remotely is. Maybe a SCCM job with this:
msiexec /I {90140000-0012-0000-0000-0000000FF1CE}MSIPATCHREMOVE={DEFF916D-4268-49CF-8FF3-E26253582E13}
msiexec /i {90140000-001A-0409-0000-0000000FF1CE}MSIPATCHREMOVE={DEFF916D-4268-49CF-8FF3-E26253582E13}
Please advise. Also looking for time frame for a fix to be published or these updates are rolled back/pulled by Microsoft. Thank you.
Also this is being reported by multiple people with no resolution. Example:
http://community.spiceworks.com/topic/790986-outlook-2010-bug-the-attempted-operation-failed-an-object-could-not?page=1

Hi,
Thank you for your feedback and apologize for the inconvenience caused.
We have heard several reports regarding issues caused by KB2956128. We've escalated this issue, but we're not sure whether and when there will be an hotfix for this issue. Please look out for our official blog articles and install
all available updates released.
Thanks for your understanding and support.
Steve Fan
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.
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]

Outlook 2010 - Exchange 2013 - Meeting request "from" field

We have a shared mailbox that the company uses, each user has full access to the mailbox, within this mailbox is a calendar. If person A creates a meeting in this calendar and invites person B, when person B accepts the acceptance goes to the inbox of the
shared mailbox, not the inbox of the user who invited them. Is there a way I can use a "from" field in meeting requests" so acceptances go to the invitee?
Thanks
Dave

Hi Dave,
This is the expected behavior of Outlook according to your conditions, and there is no option available to change it.
As a workaround, we can create a meeting in the user's own calendar, and then add the shared mailbox as an attendee of the meeting. In this way, the meeting will show in the shared calendar and the meeting responses will be sent to the meeting creator's
mailbox.
Regards,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Outlook 2010 Exchange Server 2010 to Exchange Server 2013 Features

Hi All
We have recently upgraded from Exchange Server 2003 to Exchange Server 2010. We are using the Outlook 2010 (32 bit) email client. When mailboxes were moved on to the new server various features inside the system were activated. For email Internal Out of
Office Messages, External Out of Office Messages, notifications in the email recipient bar when creating emails if the user was out of office.
What new features would be available with Outlook 2010 (32 bit) and Exchange 2013. And are they dependent on the Office Service Pack?
Kind Regards
Please note that I have previously posted this in another forum but was advised to post here in this forum.

Hi,
I find your post on Office forum:
http://social.technet.microsoft.com/Forums/en-US/fc538968-212c-411c-8ce8-0ef1d7acfcca/outlook-2010-exchange-server-2010-to-exchange-server-2013-features?forum=outlook
The Steve's answer is comprehensive, great links on Exchange 2013 new features and removed features.
About "And are they dependent on the Office Service Pack?", I will give the answer.
Based on my knowledge, when new SP releases, it include enhancements in security and compliance, architecture and administration, and user experiences.
For example, Exchange 2013 SP1, it connects to Outlook 2013 SP1 via MAPI over HTTP.
If you want to know more about the Exchange new features, please see Exchange Team Blog.
Find blog about SP1 for your reference:
http://blogs.technet.com/b/exchange/archive/2014/02/25/exchange-server-2013-service-pack-1-available.aspx
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

OWA receives mail long before Outlook (Exchange 2013 with Outlook 2010 and 2013)

I recently upgraded my Exchange environment to Exchange 2013 SP1. The Outlook users are now experiencing a delay when receiving email. When they do arrive they appear in batches, often 20-45 minutes after they were sent, from a mailbox on the same server.
Additionally, the mail appears instantly when you monitor the inbox using OWA. The users are experiencing this on both Outlook 2010 and 2013 clients configured in both cached and non-cached modes. This appears to be a problem with Outlook connecting to Exchange.
Any suggestion about how to correct this would be greatly appreciated. Thanks!

Hi,
From your description, when users use OWA, they can receive emails normally. But if they use Outlook 2010 or Outlook 2013, there is a delay in receiving emails.
I recommend you use the Outlook safe mode to determine whether the problem is caused by add-ins. Also, please make sure users have installed the Outlook latest Service Pack.
If the issue persist, please create a new profile and check the result.
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Outlook 2010 vs 2013 - BITS + OAB download

Has the process/protocol by which Outlook downloads the OAB from Exchange via send/recv >> send/recv groups >> download address book changed from Outlook 2010 to 2013? I stumbled onto the fact that our BITS policy was actually killing OAB
downloads and leading to send/recv progress bar stalling indefinitely depending on Outlook version. if we have BITS throttled to 0 (disabled) during business hours via group policy, a manual OAB download attempt will just hang indefinitely in Outlook
2010 with nothing populating @ C:\Users\username\AppData\Local\Microsoft\Outlook\Offline Address Books\alphanumeric\*.oab
bitsadmin /list
BITSADMIN version 3.0 [ 7.5.7601 ]
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.
{BF84FE64-C742-4B4D-9F50-34F7A851943B} 'Microsoft Outlook Offline Address Book b
83492211975444ab672c2c1339ed931' TRANSIENT_ERROR 0 / 1 0 / 25491
{86402ACD-D048-4D2D-A5F0-4B83D315442C} 'Microsoft Outlook Offline Address Book b
83492211975444ab672c2c1339ed931' TRANSIENT_ERROR 0 / 1 0 / 25491
Listed 2 job(s).
yet in Outlook 2013 on a machine with same BITS policy applied, send/recv >> send/recv groups >> download address book will go through, and the *.oab files populate -
BITSADMIN version 3.0 [ 7.5.7601 ]
BITS administration utility.
(C) Copyright 2000-2006 Microsoft Corp.
{86402ACD-D048-4D2D-A5F0-4B83D315442C} 'Microsoft Outlook Offline Address Book b
83492211975444ab672c2c1339ed931' TRANSFERRING 0 / 1 5264 / 25491
Listed 1 job(s).
I havent done exhaustive testing, but it appears that both 2010 & 2013 will fail to get OAB automatically while BITS policy is throttling/disabling the xfers but the manual download works on 2013. For my own info, how is this happening?
related info: http://support.microsoft.com/kb/2619347

Hi,
Since OAB related questions are always discussed in the Exchange forum, I'd recommend you post your question to the Exchange forum to get more professional response:
http://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver
The reason why we recommend posting appropriately is you will get the most
qualifiedpool of
respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
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.

Body of Accept/Decline messages from resource room mailboxes blank when viewed with Outlook 2010 or 2013.

I stumbled across a funny little problem yesterday after a rash of users calling wanting to know why rooms were declining their meeting requests..
The rooms were declining for perfectly legitimate reasons.. Conflicts or no end date but the accept/decline reply messages the rooms were sending out had no details in the message body when viewed from Outlook 2010 or 2013.
If message preview is enabled in Outlook 2013 you can read a few lines of the body in the inbox view but it's still blank when you open the message.
Reading pane is also blank.
Opening the message from OWA or my phone shows the complete message body.
Very odd. It reminds me of the bug in Exchange 2013 CU2 where meeting invites to external users were sent blank unless they were sent as iCalendar.
Maybe this will resolve itself when I load SP1 in a few weeks.
Any one else seeing this?
We are running 2013 CU 3

Hi Scott,
I have tested in my Exchange 2013 CU1 environment and I can reproduce your issue in Outlook online mode. Please check whether the problematic users are using Outlook Online mode in Outlook 2010 and Outlook 2013.
The issue doesn’t happen in OWA and Outlook Cached mode. Therefore, I recommend users can change their Outlook client to Cached mode as a workaround. To do it, we can:
Open Outlook, click File > Account Settings > Account Settings. Double-click the account, check Use Cached Exchange Mode > Next and finish it. Restart Outlook to use it in cached mode.
Thanks,
Winnie Liang
TechNet Community Support

Some Conversations Not Grouping in Outlook 2010

I have just purchased outlook 2010 about a month ago and have already noticed that it is very quirky, and I am kind of disappointed in the performance of the program. I am a home user, and I like the functionality of Outlook as I am used to it from work
and the ability it has to hold my contacts, calendars and emails all in one place.
Anyway, the problem I am having at this current time with Outlook is that the conversation function is not working properly. For a majority of my group emails (about 70%), the conversation feature works great and groups all of my "chain" emails between friends
or family together (based on topic). However, I have been noticing a few email chains are not grouping properly. Sometimes outlook will leave one message out of the group or it just wont group the emails at all, and I am left with a cluttered and unorganized
inbox.
I have done a lot of research on this already and have found nothing. I am aware of the fact that the conversation feature works off of the email subject line, and for the emails that do not get grouped in the conversation have nothing changed at all in regards
to the subject line. All these emails are grouping properly on my iPhone as well, so Apple's software seems to be working with no problems.
Does anyone have any clue what else could be affecting some of my emails and emails chains from grouping with the conversation setting? Thanks in advance!

Hi Nalin,
Outlook 2010 doesn’t group the conversation based on subject, It uses the message header (Thread-Index:) to group the messages.
http://office.microsoft.com/en-us/outlook-help/view-e-mail-message-headers-HA001230300.aspx (Find: conversation)
Thanks, Dilip
Hi Nalin,
Thanks so much for your reply. :-)
Hi Dilip,
Thanks for your reply too. I saw some posts talking about this the other day. So in light of the conversation thread here and what you've brought up...that Blackberry devices seem to alter the Message Header, then, which in turn causes the
Blackberry reply emails to be separated from the rest of the email conversation grouping in Outlook 2010, do you know of a way to configure Blackberry devices so that they maintain the same Message Header so that a Blackberry reply email remains with the original
Outlook email conversation group?
Thanks!
Well, I've done a little more research. A
post from a guy named David Hogue led me to this tool named
MFCMAPI. You don't have to install it. You just run it. So I used it to navigate to emails in my folders where 4 emails were properly grouped and 2 emails were excluded from this conversation group (but they should have been
included).
Looking at the properties of the emails, I noticed there is a property called "Conversation ID". This seems to be the property responsible for keeping the emails properly grouped together. The problem, though, is that Outlook has the additional
complexity of showing the little orange lines and dots to display emails in the conversation at the proper level, what email the reply was in response to in the conversation thread, etc. Because of these additional features, the "Conversation ID"
is not just a standalone property value that can be adjusted. It's buried within binary information which includes all of this leveling information. So I could not find an easy way to adjust the "Conversation ID" and also have
all of this other information Outlook uses for conversation grouping level purposes.
Here's an additional test I did just to see how Outlook handles grouping. I took one of the emails that is currently excluded from the proper conversation thread. I started an email reply from it, changed the recipient to myself, and changed
the subject line to make sure that it used "Re: " before sending the reply email to myself. The email I received ended up being grouped properly with the rest of the conversation. Therefore, my conclusion is that Blackberrys are doing something
even deeper than just changing the "RE: " to "Re: " which is causing this problem. Whatever the Blackberrys are doing, they are causing Outlook to flag the email as a separate conversation and after Outlook has done this, the complexity of the email's
properties are such that trying to get this email back into the right conversation thread is not an easy task at all.

I cannot sync my contact groups from Outlook 2010 (Win 7) onto my iPad. Can anyone help please ?

I cannor sync my contact groups from Outlook 2010 (Win 7) onto my iPad. Can anyone help please ?

in Itunes, once you connect the iPad, do you see the 'info' tab? Tap that and scroll down and see if outlook is chosen as the place to sync contacts from. If not, check it and sync and see if your contacts move over.

Can't manage distribution group from Outlook with Exchange 2010 or Exchange 2013 mailbox

Hi All,
In my environment we are using exchange 2010 that contains the distribution groups which has been migrated from exchange 2003 environment .On that one of the distribution group is having an problem for the user who had an access to manage DL'S via outlook
but he can't able to manage it.When we add the new user to manage same DL and the new user tries to manage the DL via outlook it happens without any issues.
issue occurs only for the user who has already have the manage access permission on the DL where the group was on exchange 2003 before migrated to exchange 2010.
Reffered blog : http://support2.microsoft.com/kb/2586832?wa=wsignin1.0
We have done all the settings defined on the above mentioned link but still we are facing the issue.
In addition to that , we have forcefully upgraded the DL too by using the below mentioned command.
set-distributiongroup -identity "name of the problematic DL" -forceupgrade
Please all of you provide your valuable suggestions to overcome this issue .
Error message :
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Hi S.Nithyanandham,
From your description, I would like to verify if the problematic manager user is a member of security group. If yes, this issue will occur. In Exchange 2010, distribution groups can't be managed by groups, only individual users can manage groups. But in
Exchange 2003, it is possible to use groups to manage a distribution group.
For more information, here is a blog for your reference.
How to manage groups with groups in Exchange 2010
http://blogs.technet.com/b/exchange/archive/2011/05/04/how-to-manage-groups-with-groups-in-exchange-2010.aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2010 - Exchange 2013 Outlook 2010 resolves wrong server

Hello,
We are upgrading from exchange 2010 to 2013.
Now I have migrated a testmailbox, but when I try to configure it in outlook it tries to connect to the Exchange 2010 server instead of the Exchange 2013 server.
I have configured outlook manually like described on the following url:
http://www.zerohoursleep.com/2013/02/manual-outlook-configuration-with-exchange-2013/
At the "Check Name" step, it will not resolve the Exchange 2013 server guid but the Exchange 2010 server... but the mailbox is migrated to Exchange 2013...
When I try to launch outlook an error occurs: Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data
file (.ost)."
Can someone help me out please?
Thx!

Are you sure the mailbox move completed? What happens when you log into OWA? Are you having AD replication issues in your environment?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

"The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook" in Exchange 2013

In Exchange 2013, Outlook finds a new connection point made up of the user’s mailbox GUID + @ + the domain portion of the user’s primary SMTP address. This change makes
it much less likely that users will see the dreaded message “Your administrator has made a change to your mailbox.”
http://technet.microsoft.com/en-us/library/dd298114(v=exchg.150).aspx
Although the error message in the topic has been already improved a lot in Exchange 2013, the users may still encounter them in some specific scenarios. We have collected them and let’s discuss them in this thread.
Symptom
=======================================
Consider the following scenario:
Exchange 2013 was installed for a migration from Exchange 2007/2010.
The legacy Exchange server is removed after successful migration.
Exchange 2013 may be updated to Exchange 2013 SP1.
Some users were being randomly prompted with a popup in their outlook client with the following message when connecting with Exchange 2013 server:
“The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook”
Cause
=======================================
The issue may be caused due to Public Folders.
The msExchHomePublicMDB attribute on Exchange 2013 databases was set to deleted legacy public folder object.
Solution
=======================================
Removed the Public Folder from all the Exchange
2013 Databases. To do it, we can use ADSIedit.msc and remove the arrtibute - msExchHomePublicMDB from all the Databases:
1. Open ADSIEdit.
2. Connect to the Configuration container.3.
Expand Configuration, expand CN=Configuration,DC=Domain,DC=com.4. Expand CN=Services -> CN=Microsoft Exchange -> CN=Domain -> CN=Administrative Groups -> CN=Exchange
Administrative Group -> CN=Databases.5. In the right hand pane you will see a list of databases.6.
Right-click the listed database object -> Properties.7. Check whether the msExchHomePublicMDB value is set to an unavailable value. If you see reference to the old database,
please clear the value.8. Click OK.9. Check the rest of the databases to make sure
that they are not populated in the same way.
References:
https://social.technet.microsoft.com/Forums/en-US/2f736bdd-1c00-4a22-97a5-95faeadf1495/exchange-2013-sp1-users-randomly-prompted-with-the-microsoft-exchange-administrator-has-made-a?forum=exchange2010
https://social.technet.microsoft.com/Forums/lync/en-US/7a7b3cf8-8761-421c-9d55-6c84e05531c0/the-administrator-has-made-a-change?forum=exchangesvrclients
https://social.technet.microsoft.com/Forums/en-US/0d71c843-b662-493c-ab6e-30708929ef18/2013-sp1-problem-the-microsoft-exchange-administrator-has-made-a-change-that-requires-you-quit-and?forum=exchangesvrdeploy
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

This one? http://support.microsoft.com/kb/2934750

Outlook 2010 and 2013 are unable to connect but OWA (and mail routing) works fine

Hi-
Not sure why but this past Sunday (just after DST adjustment) outlook clients (using 2010 and 2013) were unable to connect to an Exchange 2013 server. OWA and mail routing (internal and external) is working fine. I've even tried on multiple machines
and all of them experience the same issue. On a new machine with a fresh version of outlook 2013 installed here is what happens:
Click on Outlook 2013
Click Next until the account setup is displayed.
Name and email is auto-populated
Established network connection is good
Searching for email address settings is good (once the self-signed exchange 2013 cert is accepted)
And then the logging onto the mail server fails. The first pop-up is:
The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicking "OK" is followed up with a window with the Microsoft Exchange connection info.
It lists Microsoft Exchange server which is populated with: GUID@<domain suffix>
Mailbox which is populated with: =SMTP:<Valid Email address>
On the Exchange Server I have noticed that the Web Management Service (WMSVC) is stopped and will not start. Starting the service outputs:
EventID 7024
"The Web Management Service terminated with the following service-specific error: Unspecified error"
Not really helpful :)
Since this is only happening with Outlook on multiple clients I'm expecting something with Exchange or the ability for outlook to connect to exchange.
Thanks in advance!

Hi
I know this is an old post, but I'm having a very similar issue. I have CU6 installed and all other client connectivity apart from internal Outlook connectivity is working fine. I have distributed the new Self-Signed Certificate and the tested to verify
the clients trust it. I have tried on multiple machine with multiple accounts and none of them connect.
I'm at the stage of reinstalling, but I would rather troubleshoot the problem, just in case ever hit the same wall in the future. I have run Test-OutlookConnectivity with the following output;
RunspaceId : 71f8d740-c499-4bbe-8baf-9cbb12566fb8
Server : PW-SC-01.companyname.local
MonitorIdentity : Outlook.Protocol\OutlookRpcDeepTestProbe\NEW2013
RequestId : 75641e34-aa49-4fce-aad7-181b56dd7b29
ExecutionStartTime : 10/11/2014 13:50:03
ExecutionEndTime : 10/11/2014 13:50:03
Error : Error 0x6ba (The RPC server is unavailable) from ClientAsyncCallState.CheckCompletion:
RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
Exception : Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC server is unavailable)
from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsyncCallState.CheckCompletion()
at Microsoft.Exchange.Rpc.ExchangeClient.ClientAsyncCallState_Connect.End(IntPtr&
contextHandle, TimeSpan& pollsMax, Int32& retryCount, TimeSpan& retryDelay, String& dn
PoisonedCount : 0
ExecutionId : 63105129
SampleValue : 33.5194
ExecutionContext : Mailbox logon verification
EMSMDB.Connect()
Task produced output:
- TaskStarted = 10/11/2014 13:50:03
- TaskFinished = 10/11/2014 13:50:03
- Exception = Microsoft.Exchange.Rpc.ServerUnavailableException: Error 0x6ba (The RPC
server is unavailable) from ClientAsyncCallState.CheckCompletion: RpcAsyncCompleteCall
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 2
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1710
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: 0 (0x00000000)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 13
EEInfo: Status: 0x000006BA
EEInfo: Detection location: 1352
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 1
EEInfo: prm[0]: Long val: -1073606646 (0xC002100A)
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0xC002100A
EEInfo: Detection location: 1380
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 12175 (0x00002F8F)
EEInfo: prm[1]: Unicode string: /rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
EEInfo: ComputerName: n/a
EEInfo: ProcessID: 14544
EEInfo: Generation Time: 2014-11-10 13:50:03.737
EEInfo: Generating component: 14
EEInfo: Status: 0x00010000
EEInfo: Detection location: 1385
EEInfo: Flags: 0
EEInfo: NumberOfParameters: 2
EEInfo: prm[0]: Long val: 8 (0x00000008)
EEInfo: prm[1]: Binary Buffer: [48-1263-10248-1262-126-9632122164676121-3988104-118-11373-61-94
-111-112-98-1217048136942-12272-122-91311550483449324830638543192311910198979999101115115461121199
91111091091154699111461171074830231349524949485349505348484990231349574949485349505348484990483449
324830638543192311910198979999101115115461121199911110910911546991114611710748-12613448136942-1227
2-122-913111503-126115048-1261102-126110-22103-15-109-16-121-119-3121-4-106119-119-9369122-5779121
719-98-24-67-32918-98-236-19-10715326827-76102-61100108-12718-438331-37109-102-57-9942-11389-10374
-77-5-4-107109-11847342222-63-48-7468-17-1067033-56111-33-54-16-105-62-76-1282011-1664-12158-4915-
88-53-9-29-2994-49-54-5211-1364-212121-12396-127-353-396185117-681229-434246070-109818119-4858-128
-106-1279248-49110-44-81-121494199-118-17-106-71106828294-93-110-110-106-415084-127126-45-12331421
-61-2757-24-128-28-25111-52113121-56-98-5821527282-47255245104-111-55-1099747-115-11172-287-12526-
79-12430-119421360-107-6430-5410282-52-51-128533354-116672757-77-75-111-72-118-10114-84484825-40-1
8-70-24-9111-61-5391-8034125-12632-16-19-128112030-8-427523101-93-127-5348-127-5648146385291511-14
4325-9648-127-110638529174-127-11848-127-121-12623119101989799991011151154611211999111109109115469
911146117107-1262211211945115994548494611211999111109109115461081119997108-12626651171161116810511
59911111810111446808767111109109115461081119997108-12626651171161116810511599111118101114468087671
11109109115469911146117107-12613808767111109109115461081119997108-12613808767111109109115469911146
11710748196385293741248106843615573148126385291911-14248048136942-12272-122-913115503-12611081-930
6613-74953718-12745-14-25-94107-80-5-45-2231536-1728-12897-8587577-1252765-892896-83-10267-7926-20
-9841-1079-12-29-4315671111357-684036-40-5129-91-24-461066-12306-65-9118-89115191071-30-20-1067161
-83-91-74105-931649-48-96126-13-71-118-8967567-40-64-104-113-31-51-102357125100-50113-103-113123-9
873-627067-25-908-10131118125122-71-115-37-1850-1055851-31410-77-7312-36848124-26104-10711043-2048
-48-12666611759121127-2960-1571-9-95-98-1036911610-74221-32-25114-108749933-7147562114-3635-101-81
-1058-73108-61-78-128-116-715155112714-37-18-84-8331-2716-1174257-76-5-1598-15-12875-98-7329632178
-10714-123-6312212-1028359-56-76-683-873987-2120-845954-7617-71-57999828110], size=926
at Microsoft.Exchange.Rpc.ClientAsy
FailureContext :
ExtensionXml :
ResultType : Failed
RetryCount : 0
ResultName : 75641e34aa494fceaad7181b56dd7b29-OutlookRpcDeepTestProbe/NEW2013
IsNotified : False
ResultId : 1748063
ServiceName : InvokeNow
StateAttribute1 : Momt
StateAttribute2 : UnknownIssue
StateAttribute3 : PW-SC-01.companyname.local
StateAttribute4 : Unknown
StateAttribute5 : {C54AD38D-1E00-4F53-ABAE-26518C3FF82F}
StateAttribute6 : 0
StateAttribute7 : 0
StateAttribute8 : 0
StateAttribute9 : 0
StateAttribute10 : 0
StateAttribute11 : Momt
StateAttribute12 :
StateAttribute13 : VgEAVAdXaW5kb3dzQwBBCEtlcmJlcm9zTA9QV0NPTU1TXG5hdGhhbmhVLlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC
0xNTQ2MTE0ODM1LTI2MzJHHQAAAAcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTEzBwAA
AAdTLTEtMS0wBwAAAAdTLTEtNS0yBwAAAAhTLTEtNS0xMQcAAAAIUy0xLTUtMTUHAADAE1MtMS01LTUtMC0zNDc3ODcxMTMHAA
AALlMtMS01LTIxLTIwNTc0OTEwMzItMzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTQxODcHAAAALVMtMS01LTIxLTIwNTc0OTEwMzIt
MzE4NDA2NDk3OC0xNTQ2MTE0ODM1LTUxMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtND
E3NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMzU3MAcAAAAuUy0xLTUtMjEtMjA1NzQ5
MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDEyMgcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMT
Q4MzUtMTE2NAcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtMTE0MQcAAAAuUy0xLTUtMjEt
MjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNDE1MwcAAAAuUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LT
E1NDYxMTQ4MzUtNDE0NQcAAAAtUy0xLTUtMjEtMjA1NzQ5MTAzMi0zMTg0MDY0OTc4LTE1NDYxMTQ4MzUtNTE4BwAAAC5TLTEt
NS0yMS0yMDU3NDkxMDMyLTMxODQwNjQ5NzgtMTU0NjEx
StateAttribute14 :
StateAttribute15 :
StateAttribute16 : 0
StateAttribute17 : 0
StateAttribute18 : 0
StateAttribute19 : 0
StateAttribute20 : 0
StateAttribute21 : /o=companyname/ou=first administrative group/cn=Recipients/cn=NathanH
StateAttribute22 : EMSMDB.Connect()
StateAttribute23 : https://pw-sc-01.companyname.local:444/rpc/rpcproxy.dll?PW-SC-01.companyname.local:6001
StateAttribute24 : Negotiate
StateAttribute25 : [33]10/11/2014 13:50:03 [FAILED!] EMSMDB.Connect();
Identity : fcd6159dd8fe42aebf10100cc4934356
IsValid : True
ObjectState : New

Bug Group by Outlook 2010 - Exchange 2013

Similar Messages

Maybe you are looking for