Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

Hello,
we are having a problem with a few Outlook 2010 Clients that have two Exchange accounts setup in one profile. One account is connecting to the company's Exchange 2013 Server, the second account is connecting to an external provider's Exchange 2007 infrastructure
using Outlook Anywhere.
The companies Exchange 2013 was recently migrated from Exchange 2010 and this is the point where the problem started.
Some users are no longer able to send using the external Exchange 2007 account. When they try they are receiving an NDR with the following error message:
#554 5.6.0 STOREDRV.Deliver; Corrupt message content## from the external provider's servers.
When I setup a profile containing only the external provider's mailbox everything works fine until I am adding the company's Exchange 2013 back in at which point the same error appears.
We have no problems using the company's Exchange 2013 servers.
Does anyone have an idea what causes this and how to resolve it? The external provider is uncooperative in troubleshooting so we are left with the problem.
Thank you
Sascha

Hi,
The problem should be related to the External Exchange 2007.
Please refer to this kb below:
http://support.microsoft.com/kb/2203381/en-us
This problem occurs when the email message is a multipart/mixed MIME message which contains a text/plain body and an application/applefile body. If the corresponding body is not a real application/applefile body, the Exchange Server 2007 server considers
that the email message is invalid. Therefore, it generates the NDR. However, Exchange Server 2010 can deliver this kind of email message successfully.
To resolve this problem, you should let the External Provider install the following update rollup:
2279665 Description of Update Rollup 1 for Exchange Server 2007 Service Pack 3
Hope this helps.
Thanks,
Melon Chen
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

Similar Messages

Outlook 2010 connected to Exchange 2013 prior to coexistence

I installed Exchange 2013 into the environment (Exchange 2010 SP3) and left it at that (ie no additional config). I noticed Outlook 2010 client connected to Exchange 2013 somehow (it got a cert warning). Why would Outlook connect to the new
Exchange 2013 server like that? Although I enabled Outlook Anywhere, it is not trying RPC/HTTP first, but rather RPC/TCP.

Hi,
By design, if the user mailbox located in Exchange 2010 server, the Outlook client will connect to Exchange 2010 server automatically.
According to your description, I found that we have nothing additional configuration on Exchange 2013. So, only server name and internal services' URLs are configured automatically during the Exchange 2013 server installation.
If it has no mailbox located in Exchange 2013, it is odd that Outlook client connect Exchange 2013 first.
I suggest running "Test E-mail AutoConfiguration" in Outlook to verify which Exchange server the Outlook connected.
Thanks
Mavis
Mavis Huang
TechNet Community Support

First timeout, push retry and then succesfull connect?! Starting Outlook 2010 connect to Exchange 2013

Hi!
Some info:
2x AD/DC Windows 2003 Native.
Previous Exchange 2003 installed, but now cleanly as it gets uninstalled.
Exchange 2013CU2v2 Aka Version 15.0 (Build 712.24)
Office 2010 with Outlook 2010 (Latest SP, and WU)
Outlook-prf configured for Outlook Anywhere. (i've also tried to configure manually, no difference)
Exchange: SAN Cert. GUI requested from ECP. This one covers all possible host names the server can use. autodiscover, owa, mail, "netbios"-name. Self issued from the internal CA. CA distributed to clients with GPO. I get NO certificate warnings
surfing to OWA, ECP.
Exchange: ECP/Server/Outlook Anywhere; Auth set to NTLM (not Negotiate)
Ping inside host names resolves to the Exchange server.
Starting Outlook.exe with /rpcdiag show two connections for a while. One of the type catalog and one of the type redirect.
Problem:
When starting Outlook you see "Loading profile" for about 30-40 seconds. /rpcdiag show two connections CID "9","11"; SERVERNAME "---","[GUID]@thedomain", AUTH and ENCRYPT is empty.
The the a dialog comes up that says that the server isn't available?!
Clicking "Retry" makes Outlook connect as it should. Everything from there works like a charm! /rpcdiag windows show that it has connection as it should.
Tried to click "Reconnect" in /rpcdiag. It also takes about 30 sec before it regains the conneciton. The part hanging there is the Type: Redirect.
So, does anyone have a clue for why it doesn't work and then does?
Can it be something wrong with the autodiscover?

Hello,
Do you mean the issue occurs when you select manually configure outlook exchange account or automatically configure outlook exchange account? If so, please make sure whether all users have the issue.
I recommend you check if there exists redirection on your rpc virtual directory.
I recommend you use "test e-mail autoconfiguration" tool to check if your autodiscover is correct.
Besides, I recommend you to enable global and advanced logging for outlook to check RPC trace events.
How to enable global and advanced logging for Outlook 2010 and Outlook 2013
http://support.microsoft.com/kb/2260527
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2013 and 2007 coexistence and redirects

Hi all,
I'm settings up the coexistence but i've got a problem.
I've got 3 sites:
Site A: Exchange 2013 cas and mailbox
Site B: Exchange 2007 hub/cas and mailbox
Site C: Exchange 2007 hub/cas and mailbox
The problem is the owa and active sync redirect. I can open a mailbox located in site B where the legacy.domain.com dns record points, but i cannot open a mailbox from the exchange 2013 nor 2007 owa from site B to C.
I configured only the internal url leaving the external one blank.
How do i redirect all the requests to a mailbox located in site C from site A and B?
Thanks,
D.

You need to have External URL too, so that redirection can take place.
http://blogs.technet.com/b/mbaher/archive/2009/12/17/exchange-2010-proxy-or-redirect.aspx
http://technet.microsoft.com/en-us/library/bb310763(v=exchg.141).aspx
http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Autodiscover exchange 2013 and 2007

hello,
i am in the process of setting up autodiscover properly for a coexistence environment of exchange 2007 and 2013.
currently, exchange 2007 has the active CAS server role. let's call it server1.contoso.com. Exchange 2013 is installed with the CAS and Mailbox role. let's call that server server2.contoso.com
Assuming all certificates have been installed, i assume that server2.contoso.com has to point to the autodiscover of server1.contoso.com until i have fully moved all mailboxes over to 2013 CAS, correct?
the powershell command i used to set autodiscover on server2 is as follows,
Set-ClientAccessServer -AutodiscoverServiceInternalUri https://server2.contoso.com/Autodiscover/Autodiscover.xml
it then asks for identity and i enter "server2.contoso.com".
Currently, when i type "get-clientaccess server | fl server,*uri I get the follow results,
AutoDiscoverServiceInternalUri : https://server1.contoso.com/autodiscover/autodiscover.xml
AutoDiscoverServiceInternalUri : https://server2.contoso.com/autodiscover/autodiscover.xml
Should they both be "AutoDiscoverServiceInternalUri : https://server1.contoso.com/autodiscover/autodiscover.xml" since server1 is the active CAS server?
Again, once everything has been migrate i will then change the CAS server to server2.contoso.com
Thanks!!

Apologies if I have confused everyone here.
we need 2 urls for Owa and EWS in 2007 and 2013. My this blog should help
http://msexchangeguru.com/2013/12/31/e20132007-urlsauth/
Undying: Answers are in line.
1. What I understand from the post marked as Answer is there is no need for legacy namespace for Exchange2007/Exchange2013 co-existence, meaning after the installation of Exchange 2013 in the environment there is no need to modify the virtual dirs on exchange
2007 side. Both 2013 and 2007 will be using the mail.domain.com namespace for all the services and once the virtual directories have been configured on the Exchange 2013 CAS it will redirect the request to Exchange2007 CAS for the Exchange2007 mailboxes. And
since there's no need for legacy namespace, it should also mean that there would be no need for any additional publishing rule in the reverse proxy (ISA/TMG), just modifying the current one (mail.domain.com) to point to the Exchange 2013 CAS should do the
trick. Am I correct?
Just to summarize, all the redirection from Exchange 2013 to Exchange 2007 will be done without the need of legacy namespace and without modifying any URls on the Exchange 2007 side.
PN Answer:
You need 2 urls for OWA and EWS.
legacy.domain.com and mail.domain.com
Also need
autodiscover.domain.com
Basically you need to change these urls on 2007 side to legacy.domain.com
This means you need to get this url added into the cert.
On TMG side direct all the traffic to 2013 and it will redirect to 2007.
you would need a new public host record for the legacy url.
2. If all that is indeed correct then why the Technet article still make it sound like that the legacy host name is mandatory? http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
(Step 7)
PN Answer: Yes we need legacy url
Regards, Prabhat Nigam XHG and AD Architect and DR Expert Website: msexchangeguru.com VBC: https://www.mcpvirtualbusinesscard.com/VBCServer/wizkid/card

Outlook 2010 disconnects from Exchange 2013

One of the users running Outlook 2010 (14.0.7108.5000) randomly gets disconnected from her mailbox on Exchange 2013. The disconnect lasts about 5 min and then connection reestablishes. While outlook gets disconnected, computer does not have any problems
accessing any other network resources. Event 25 gets logged on the client when outlook disconnects and states the following. "Network problems are preventing connection to Microsoft Exchange."
Other users in the same mailbox database don't experience or notice the same issue.
The error message states that the mailbox database is offline, but it's probably misleading as the database remains online and mounted while the disconnect happens. The problems seems to follow the user no matter what mailbox database she is in.
The following information gets logged in exchange RCP Client Access log Listed in chronological order.
RopHandler: OpenFolder: [StoragePermanentException] There was an error parsing the entry ID. -> [MapiExceptionInvalidParameter] Unable to obtain the FID and MID from the entry id. (hr=0x80070057, ec=0)
ClientRPCCount=42;AvgClientLatency=00:00:00.0022142;ServerRPCCount=8;AvgCasRPCProcessingTime=00:00:00.0057500;AvgMbxProcessingTime=00:00:00;MaxCasRPCProcessingTime=00:00:00.0460000;20%ClientPercentile=10;40%ClientPercentile=10;60%ClientPercentile=10;80%ClientPercentile=10;90%ClientPercentile=10;95%ClientPercentile=20;99%ClientPercentile=20;100%ClientPercentile=50;20%CasPercentile=10;40%CasPercentile=10;60%CasPercentile=10;80%CasPercentile=10;90%CasPercentile=10;95%CasPercentile=10;99%CasPercentile=10;100%CasPercentile=50;20%MbxPercentile=10;40%MbxPercentile=10;60%MbxPercentile=10;80%MbxPercentile=10;90%MbxPercentile=10;95%MbxPercentile=10;99%MbxPercentile=10;100%MbxPercentile=10;ClientRpcFailureData:
RpcEndPoint: [ServerUnavailableException] Connection must be re-established -> [SessionDeadException] Connection is severed (ConnectionFailedTransientException). Client needs to reconnect. -> [ConnectionFailedTransientException] Cannot get row count.
-> [MapiExceptionNetworkError] Unable to get table row count. (hr=0x80040115, ec=0)
RopHandler: Logon: [RopExecutionException] Mailbox is temporarily unavailable. Error code = MdbOffline (0x00000476) -> [MailboxOfflineException] Cannot open mailbox /o=CORP/ou=Office/cn=Recipients/cn=Banger. -> [MapiExceptionMdbOffline] Unable to make
connection to the server. (hr=0x80004005, ec=1142)
RpcEndPoint: [ServerUnavailableException] Connection must be re-established -> [SessionDeadException] The primary owner logon has failed. Dropping a connection. -> [RopExecutionException] Mailbox is temporarily unavailable. Error code = MdbOffline
(0x00000476) -> [MailboxOfflineException] Cannot open mailbox /o=CORP/ou=Office/cn=Recipients/cn=Banger. -> [MapiExceptionMdbOffline] Unable to make connection to the server. (hr=0x80004005, ec=1142)
Any help would be greatly appreciated

After reviewing the entire RCP Client log on the server, I am ruling out the client PC at this moment.
The disconnect seems to be getting triggered by a Healthmailbox check that starts right before users gets disconnected.
Here is a similar problem with exchange 2010 with no answer.
http://serverfault.com/questions/474123/one-email-user-keeps-disconnecting-from-our-exchange-server
Healthmailbox associated with user's mailbox database preforms the following operations at 19:00:05.899Z
Connect
OwnerLogon
OwnerLogoff
Disconnect
a minute later, at 19:01:43.526Z Healthmailbox associated with initial mailbox database preforms the following operations
Connect
ArchiveLogon
ArchiveLogoff
Disconnect
and then at 19:01:46.479Z server logs RopHandler: OpenFolder: [StoragePermanentException] There was an error parsing the entry ID. -> [MapiExceptionInvalidParameter] Unable to obtain the FID and MID from the entry id. (hr=0x80070057, ec=0) for the
client connection and client notices the disconnect.

Exchange 2013 and 2007 - Coexistence and ActiveSync

Good morning all,
We're currently in the process of migrating our Exchange server from 2007 to 2013, and am experiencing a few problems. At the moment, OWA redirection works fine, but ActiveSync does not. At the moment the 2013 Server isn't public facing, it's internal until
all testing is complete. However despite being on the LAN, when an iPhone is configured to target the 2013 server, it isn't proxying to the 2007 CAS, but instead provides a vague error of being Unable to Verify account information. No mail is retrieved.
Has there been a step I've missed to allow this to work seamlessly?

Generally, both the internal and external Exchange 2007 ActiveSync URL should be pointing to the legacy namespace - legacy.yourdomain.com. If you've set correctly the internal name resolution (resolving the legacy namespace to the internal Exchange 2007
IP address), ActiveSync should be working fine.
Have you tried Android phones as well?
Alternatively, you can set the Exchange 2007 ActiveSync External and Internal URL to $NULL, forcing Exchange 2013 CAS to proxy all requests to the Exchange 2007 CAS. This way devices are not affected by a redirect.

Connection beetween Exchange 2013 with outlook client 2007 SP3

Hi All,
My company reinstall exchange 2013 when the previous mailbox DB error. When I implemeted a new server. I configured step by step carefully. if we use outlook 2010 connect to exchange server, send/receive work normally. But someone, uses outlook 2007 SP3,
they have somer error. They work with "cached mode", the connection from outlook to exchange server connected normally, but mail items sometime disappear in outlook client, when i check in the OWA, the mailbox item appear on this.
I tested with "online mode", the mailbox items push into outlook.I switched to "cached mode", this items haven't in outlook. Everybody who's meet the problem, please help me the solution can resolve the problem? Many thanks.
Quoc Dao

Hi,
Would you please let me know edition information of the Windows Server? Is it a Windows Server 2012, Windows
Server 2012 R2 or other?
On current situation, please refer to following KB and check if can help you.
Sometimes e-mail messages do not appear in your
Cached mode Inbox even though they were synchronized down from your mailbox
By the way. Based on your description, this issue seems to be more related to Outlook 2007. If this issue still
exists, I suggest that you should post in
Outlook forum. I believe we will get a better assistance there.
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]

Outlook 2010 Syncing With iPod Touch and iPad

I have a PC with Outlook 2003 that sync’s with iPod Touch and iPad. I plan to buy a new PC with Windows 7 and Outlook 2010. Comcast tells me they don’t support Outlook (They support Outlook Express) but Outlook 2003 currently works fine on my PC with Windows XP. I have the following questions:
- . Is there an alternative to Outlook 2010 that will sync with my iPod Touch and iPad?
- Will Outlook Express sync with my iPod Touch and iPad and is Outlook Express still available?
- What is Microsoft Exchange?
Thanks for your help. LCP

Just look at page 26 of the new US) users guide. It specifically says that the iPad syncs with Outlook 2010 (as well as 2003 and 2007). However, Comcast's mail help page only lists OL 2000, 2002, 2003 and 2007.
http://customer.comcast.com/Pages/FAQListViewer.aspx?topic=Internet&folder=b2aa4 a3a-53eb-4730-832f-89764b6a03b9

Outlook 2007 - single profile connecting to Exchange 2013 / 2007 mailboxes

Hi,
I am in the early part of a migration from Exchange 2007 to Exchange 2013. So far I have 2013 installed and running in a DAG and just moved my own mailbox to the new server.
I set up a new profile in Outlook 2007 which connects to my mailbox on Exchange 2013. The problem is that I need to add additional mailboxes to my profile which are still hosted on Exchange 2007, however this is not working.
I thought at one stage I tested this and was able to get it work with a test mailbox also hosted on Exchange 2013.. but maybe I never did.
Does anyone know if this is possible at all (single Outlook profile, primary mailbox hosted on Exchange 2013 and other mailboxes on Exchange 2007). Most of our users have an additional mailbox mapped in their profile so I hope there is some way around this.
Thank you!

Hi,
It is possible to open a shared mailboxes on a legacy server.
Your problem could be caused by:
Not having one of the later CU installed (read CU4 or CU5)
Incorrect authentication methods configured (see link below)
Outlook is not at the latest patch level
Users of Exchange Server 2013 can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139
Martina Miskovic

Exchange 2013 and Outlook 2007

Is there a new way to connect EX2013 to Outlook 2007 SP3?
MSB

Hi Baker,
According to the description, I notice that you want to migrate from Exchange 2010 to Exchange 2013 and want to know how to connect Exchange 2013 with Outlook Client 2007.
Following is an article about the migration, for your reference:
Upgrade from Exchange 2010 to Exchange 2013
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Outlook client uses Autodiscover and Outlook Anywhere to connect to Exchange server, please make sure services’ URLs configured correctly.
If you want to communicate with external users, you need to apply a certificate issued from a Public CA.
After configuring all the points above, please run “Get-Mailbox –Identity allen | FL *GUID*” in EMS to get mailbox GUID of allen’. Input the GUID into server name filed.
More details on “Manual configuration guide for Outlook 2010 (Exchange 2013)” for your reference:
http://support.sherweb.com/Faqs/show/manual-configuration-guide-for-outlook-2010-exchange-2013
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Allen Wang

Unable to connect to Exchange 2013 using Outlook 2010/2013 with latest patch

Dear All,
I'm setting up Exchange 2013 CU2 coexist with Exchange 2010 SP3. Since we are still planning and testing, the internet is still pointing to 2010 for send/receive mails.
The 2013 environment are:-
2 X CAS server with MS NLB configured
2X MBX server with DA
Internal NLB/licent access: excas2013.int.my.domain
External access (current set on 2010 as well): webmail.my.domain
Certificate with valid subject name has been import to 2013 and 2010:
CN: webmail.mydomain
SAN: excas2013.int.my.domain
SAN: excas.int.my.domain (for 2010)
I am able to connect to my Exchange 2010 user thru 2013 CAS server and proxy to exhcnage 2010 by outlook. However, I cannot connect to Exchange 2013 user by outlook. During mail profile create of Exchange 2013 user by autodiscover (pointed to exchange 2013),
the process looks good:-
Establish network connection (checked)
Searching for [email protected] server settings (checked)
Log on to server
The process stop at "Log on to server" and a windows prompt, saying:
The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
Clicked OK, I can see:-
MS Exchange Server:
[email protected]
Mailbox:
=SMPT:[email protected]
WHen I click "Check Name", it said The name cannot be resolved.
I have no idea of what is going on. Just want some help~

I have checked the iis log:-
2013-09-23 06:58:29 10.144.144.71 POST /autodiscover/autodiscover.xml &cafeReqId=99ed5467-a294-481c-95eb-9b21d6530404; 443 mydomain\training101 10.144.85.4 Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7106;+Pro) 200 0 0 8018
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f4652a19-2e8e-4652-a007-0cf0b7fb792e&cafeReqId=f4652a19-2e8e-4652-a007-0cf0b7fb792e; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c48cda77-6008-423b-8e8b-d6d40f4d1b39&cafeReqId=c48cda77-6008-423b-8e8b-d6d40f4d1b39; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:29 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=033f1ce4-43ba-49b1-b226-f4cc357e7702&cafeReqId=033f1ce4-43ba-49b1-b226-f4cc357e7702; 443 - 10.144.85.4 MSRPC 401 1 2148074252
15
2013-09-23 06:58:29 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=d2424d25-ca9e-4867-922f-e527b041d9db&cafeReqId=d2424d25-ca9e-4867-922f-e527b041d9db; 443 - 10.144.85.4 MSRPC 401 1 64 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=ff35f49b-e418-4d55-b66c-dbae509cc12f; 443 - 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 401 1 2148074254 0
2013-09-23 06:58:31 10.144.144.73 POST /autodiscover/autodiscover.xml &cafeReqId=033f8ed6-d7ce-41b2-8ed2-e275e22e53be; 443 mydomain\tkchung 10.144.92.17 Microsoft+Office/12.0+(Windows+NT+5.1;+Microsoft+Office+Outlook+12.0.6662;+Pro) 200 0 64 15
2013-09-23 06:58:37 10.144.144.71 POST /powershell serializationLevel=Full;ExchClientVer=15.0.712.24;clientApplication=ManagementShell;TargetServer=;PSVersion=3.0&sessionID=Version_15.0_(Build_711.24)=rJqNiZqNgbqnsr3Py9GWkYvRlZqc0ZyQkoHOxsvOxsbJzczNgcbQzczQzc/OzN/Ixc/KxczI376y&cafeReqId=5350aa81-6668-489e-b099-3b3647115f10;
80 mydomain\Administrator 10.144.144.71 Microsoft+WinRM+Client 500 0 0 180040
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f961c596-efff-4696-9188-611a0d151601&cafeReqId=f961c596-efff-4696-9188-611a0d151601; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=753d8852-ce19-459c-ac78-849c3e51e0a1&cafeReqId=753d8852-ce19-459c-ac78-849c3e51e0a1; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=c9e86049-c883-4b03-8546-143909361a80&cafeReqId=c9e86049-c883-4b03-8546-143909361a80; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 78
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=327ace4c-b2c8-44c1-95ba-7871727f60ef&cafeReqId=327ace4c-b2c8-44c1-95ba-7871727f60ef; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 109
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=a7c8daa9-e458-4f2d-b388-7300e8679dcd&cafeReqId=a7c8daa9-e458-4f2d-b388-7300e8679dcd; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=c40afede-dd8f-4ac7-a3dd-827872bb2e76&cafeReqId=c40afede-dd8f-4ac7-a3dd-827872bb2e76; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=2dc56148-1900-4044-b72a-4b13e5e871f0&cafeReqId=2dc56148-1900-4044-b72a-4b13e5e871f0; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 64 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=9475aad3-9537-4dac-86cb-6fdb187fa148&cafeReqId=9475aad3-9537-4dac-86cb-6fdb187fa148; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d&cafeReqId=11a54e96-d8d8-4649-8e01-f8138ebf7b8d; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=b1a3e503-1077-4144-84df-fcdb65a7eea4&cafeReqId=b1a3e503-1077-4144-84df-fcdb65a7eea4; 443 - 10.144.85.4 MSRPC 401 1 2148074254
15
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=5b5639ba-4c91-4351-bda6-bcec46d6b218&cafeReqId=5b5639ba-4c91-4351-bda6-bcec46d6b218; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 15
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6002&RequestId=f200806f-3294-4210-8940-e3fee0385ccd&cafeReqId=f200806f-3294-4210-8940-e3fee0385ccd; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=675d6515-85da-43fa-9cd8-0a18ac06a71f&cafeReqId=675d6515-85da-43fa-9cd8-0a18ac06a71f; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b97b2c3e-5309-4927-8330-fe0f339b5930&cafeReqId=b97b2c3e-5309-4927-8330-fe0f339b5930; 443 - 10.144.85.4 MSRPC 401 1 2148074254
0
2013-09-23 06:58:46 10.144.144.71 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=504d462a-db21-4e4b-8568-79e4099d78c1&cafeReqId=504d462a-db21-4e4b-8568-79e4099d78c1; 443 mydomain\training101 10.144.85.4
MSRPC 404 0 0 31
2013-09-23 06:58:46 10.144.144.71 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6004&RequestId=b4757b1e-8428-454a-91df-ca0a2153144f&cafeReqId=b4757b1e-8428-454a-91df-ca0a2153144f; 443 mydomain\training101 10.144.85.4
MSRPC 200 0 64 46

Outlook 2007 SP3 can't connect to Exchange 2013

Outlok 2007 with latest hotfixes
Freshly migrated mailboxes
Gives the error
Can't open outlook-The set of folders cannot be opened
Cert has internal FQDN name. Encryption is disabled
Any pointers?

Does the certificate have the server name?
That was apparently the solution here:
http://social.technet.microsoft.com/Forums/exchange/en-US/1ae67f48-d1ba-44b5-a3c7-4e9a5e955f3e/outlook-2007-cannot-connect-to-exchange-2013?forum=exchangesvrclients
Please 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.

Unbale to install November update on Outlook 2007 SP3 for connecting to Exchange 2013

Hi
I was trying to upgrade my outlook 2007 clients for connecting to Exchange 2013 environment. First I have installed Office SP3 (kb2526086). Outlook version after that is 12.0.6607.1000. Later I tried to install nNovember 2012 update which is a
prerequisite for connecting to Exchange 2013 clients (support.microsoft.com/kb/2687404/en-us) but it shows me a message "Expected version of the product was not found on the system". No idea how to proceed now, expecting help.

I recommend that you post this in the Outlook Forum: http://social.technet.microsoft.com/Forums/en-US/outlook/threads
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Am trying to connect my icloud to my outlook account. Icloud says I have two versions of Outlook running. I installed Outlook 2013 but Outlook 2010 is a trial version and I can't seem to be able to delete it without deleting all of Windows Office 2010

Am trying to connect my icloud to my outlook account. Icloud says I have two versions of Outlook running. I installed Outlook 2013 but Outlook 2010 is a trial version and I can't seem to be able to delete it without deleting all of Windows Office 2010

You will have to remove one of the two versions, which one is your choice.

Outlook 2010 connecting to Exchange 2013 and 2007 ... delivery fails

Similar Messages

Maybe you are looking for