TS4136 Apple Mail ActiveSync issue during Exchange 2007 to Exchange 2010 migration

When customer configures the ActiveSync account on Apple Mail (using Exchange Server 2010 CAS array name) for the user whose mailbox is on Exchange Server 2007, they are not able to get any mail and account displays offline. It shows the mailbox empty as well, even though mailbox has the email items in it.
But when same account is configured using ActiveSync (using Exchange 2007 CAS Server name) it works fine.
ActiveSync & Web Services URLs for Exchange 2010 and Exchange 2007 are given as below:
S#
Virtual Directory
URL
Exchange Server 2010
Exchange Server 2007
1
Web Services Virtual Directory
Internal URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
2
Web Services Virtual Directory
External URL
https://email2.domain.ae/EWS/Exchange.asmx
https://email.domain.ae/EWS/Exchange.asmx
3
ActiveSync Virtual Directory
Internal URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
4
ActiveSync Virtual Directory
External URL
https://email2.domain.ae/Microsoft-Server-ActiveSync
https://email.domain.ae/Microsoft-Server-ActiveSync
Following error is logged on Console on Mac when this issue happens:
30/10/12 3:27:28.398 AM
Mail
*** Assertion failure in -[EWSConnection _fetchRootFolderId:], /SourceCache/Message/Message-1278/MessageStores.subproj/EWSConnection.m:202
EWS fetchRootFolderId: expected one folder in response, received: 0
0   Message                             0x00007fff8cdeeef8 -[MFAssertionHandler _handleFailureWithPreamble:description:arguments:] + 116
1   Message                             0x00007fff8cdef08e -[MFAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 185
2   Message                             0x00007fff8cd1c8db -[EWSConnection _fetchRootFolderId:] + 768
3   Message                             0x00007fff8cd1deba -[EWSConnection _connectAndAuthenticateUsingAccount:] + 650
4   Message                             0x00007fff8cd1c42d -[EWSConnection connectUsingAccount:] + 462
5   Message                             0x00007fff8cd1996a -[EWSAccount authenticatedConnection] + 437
6   Message                             0x00007fff8cd2c00e -[EWSGateway connection] + 55
7   Message                             0x00007fff8cd2dddf -[EWSGateway sendMessage:forRequest:] + 43
8   Message                             0x00007fff8cd3e54c -[EWSRequestOperation executeOperation] + 108
9   Message                             0x00007fff8ce0f97f -[MonitoredOperation main] + 228
10 Foundation                          0x00007fff94aae6b4 -[__NSOperationInternal start] + 705
11 Foundation                          0x00007fff94ac1912 ____NSOQSchedule_block_invoke_2 + 124
12 libdispatch.dylib                   0x00007fff8adc8a86 _dispatch_call_block_and_release + 18
13 libdispatch.dylib                   0x00007fff8adc9965 _dispatch_worker_thread2 + 255
14 libsystem_c.dylib                   0x00007fff8a32c3da _pthread_wqthread + 316
15 libsystem_c.dylib                   0x00007fff8a32db85 start_wqthread + 13

Hi Akebono,
Let's check a few things in your server:
1. From the Organization Configuration - Client Access - Exchange Activesync policies - Default: Verify if the option "Allow non-provisionable devices" is ON.
2. From Server Configuration - pointing <YourExchange2010> - Certificates: Verify if your SSL certificate is assigned to IIS. (You should also be able to see this certificate from OWA https session)
3. The problem may also reside in iPhone outdated software, try to test activesync connection from iPhone with the latest OS version.
4. Take a look at logs in C:\inetpub\logs\LogFiles\W3SVC1\ of Exchange 2010, those might give some more details on connectivity problems.
5. If you still experience such problems - post the ExRCA error report here.
▲ Vote if Helpful / Mark if Answer
MCSE: Messaging 2013 Charter / Private Cloud / Server Infrastructure
MaximumExchange.ru

Similar Messages

ActiveSync stops working after migrating from Exchange 2007 to Exchange 2013

We have started the migration from Exchange 2007 to Exchange 2013. We've followed best practices and everything is working great except ActiveSync. I've performed Exchange migrations in the past so this is nothing new for me. I've also been referring to
a great guide which has been a big help,
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part1.html.
Once a user is migrated from Exchange 2007 to 2013, ActiveSync stops working properly. Email can be pulled to the device (Nokia Lumia 625 running Windows Phone 8) by performing a manual sync. But DirectPush is not working. The strange part is it's not affecting
everyone who's been migrated. Anyone who is still on Exchange 2007 is not affected.
At first I thought it was our wildcard certificate. 99% of our users are running Outlook 2013 on Windows 7 or higher but we do have a few terminal servers still running Outlook 2010. Outlook 2010 was giving us certificate errors. I realized it was the wildcard
certificate. Rather than making changes to the OutlookProvider I simply obtained a new SAN certificate. Although that resolved the issues for Outlook 2010 users, ActiveSync was still a problem.
Rebooting the phones and removing the email account from the user's device and re-adding it didn't resolve the issue either.
Then I performed an iisreset on the CAS server. This didn't help either. I didn't know it at the time, but I was getting closer...
I tried using the cmdlet Test-ActiveSyncConnectivity but it gave me the following error:
WARNING: Test user 'extest_0d9a45b025374' isn't accessible, so this cmdlet won't be able to test Client Access server
connectivity.
Could not find or sign in with user DOMAIN.com\extest_0d9a45b025374. If this task is being run without
credentials, sign in as a Domain Administrator, and then run Scripts\new-TestCasConnectivityUser.ps1 to verify that
the user exists on Mailbox server EX02.DOMAIN.COM
I started reviewing how Exchange 2013 proxied information from the CAS to the mailbox server and realized the issue may in fact be on the mailbox server.
I performed an iisreset on the mailbox server and all of a sudden ActiveSync started working again. Awesome!
I can't explain why. The only thing I can assume is when some users were migrated from 2007 to 2013 something wasn't being triggered on the Exchange 2013 side. Resetting IIS resolved the issue. I guess I'll have to do an IIS reset after I perform a batch
of migrations. Disabling ActiveSync and re-enabling it for the affected users didn't help - only the IISRESET resolved the issue.
If anyone has any information as to why this happens, please chime in. Also, if anyone knows why I can't run the Test-ActiveSyncConnectivity cmdlet, I'd appreciate the help.
Thanks.

Hi,
In Exchange 2013, the Public Folder is changed to Public Folder mailbox instead of Public Folder in Exchange 2007 database.
Due to the changes in how public folders are stored, legacy Exchange mailboxes are unable to access the public folder hierarchy on Exchange 2013 servers. However, user mailboxes on Exchange 2013 servers or Exchange Online can connect to legacy
public folders. Exchange 2013 public folders and legacy public folders can’t exist in your Exchange organization simultaneously. This effectively means that
there’s no coexistence between versions.
For this reason, it’s recommended that prior to migrating your public folders, you should
first migrate your all legacy mailboxes to Exchange 2013. For more information about migrating public folder from previous versions, please refer to:
http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx
(Please note the What do you need to know before you begin part in this link)
Regards,
Winnie Liang
TechNet Community Support

Establish mail flow from Exchange 2007 to Exchange 2013

I am currently using Exchange 2007 into three sites in three cities and two of the sites are connected to Internet sending and receiving emails via Edge transport servers.
Now I am planning to upgrade to exchange 2013 CU1. I don't find any documentation on how to establish mail flow between Exchange 2007 and Exchange 2013. Will it be automatic or do i need to create specific connectors between them?

Was this question answered. We're in the same situation now as we're upgrading to Exchange 2013 from 2007. The latest CU certainly helped. Initially the test mailboxes on Exchange 2013 couldn't email each other - This was resolved with CU7 and
using "Custom Settings" - manually entered IPs for DNS in the Exchange Admin Center "DNS Lookups".
Issue at the moment Test mailboxes on Exchange 2013 cannot email mailboxes on 2007 or visa-versa and mail from external sources queues on the 2007 box.
Any assistance will be greatly appreciated.

Exchange 2007 to Exchange 2013 Mailbox Migration (moved twice)

I have an Exchange 2007 mailbox that I migrated to Exchange 2013 and works fine. I migrated it back to Exchange 2007 and still works fine during coexistence with Exchange 2013. I try to migrate the mailbox back to Exchange 2013 and now it won't open in
Outlook 2007. It says disconnected when it's trying to connect. I can't figure out what's causing this.

Hi,
According to your description, I understand that all mail client works fine after migrate mailbox form Exchange 2007 to Exchange 2013, however Outlook 2007 cannot connect to Exchange server when mailbox moved to Exchange 2007 then move back to Exchange 2013
If I misunderstand your concern, please do not hesitate to let me know.
Basis on previous steps testing, the mailbox and mailbox database is available in Exchange server. How about another computer with same Outlook version and problematic account?
If it works in another client, please open Control Panel\User Accounts\Credential Manager in problematic computer, then clear the remains credential and try again.
This issue may be related to the connection between Outlook and Exchange server, please click “Send/Receive All Folders” or “Update Folder” to update data. Also, run Test E-mail AutoConfiguration and Outlook Connection Status with problematic account to
narrow down issue. Please post relevant error message, it’s more helpful for further troubleshooting.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Cannot send email from Exchange 2007 to Exchange 2013 - Coexistence

Existing Exchange 2007 SP3 1 MBX, 2 CAS/HT, 2 ET servers.
I have added an Exchange 2013 server with MBX/CAS role.
Email will flow from Ex2013 server no problem. Mail from Ex2007 systems cannot deliver to Ex2013 boxes, it dies in queue with a 4.4.7 expired message after issuing a delay message.
I can telnet to ports 25, 587,717,465,475, and 2525 from Ex2007 HT role to new Exchange 2013 server. I can send email from Ex2007 HT role server to new Exchange 2013 server using telnet to port 25.
A ‘get-mailbox’ from the Ex2007 HT role server returns the server and database properly on the test users on Exchange 2013 server.
The only strange thing I am seeing is from the Ex2007 systems, a ‘get-exchange server’ command shows the new Ex2013 server as role ‘16439’ which looks to perhaps be normal.
Why is email not flowing to the new users on Exchange 2013?

You should have exchange server authentication ticked in Default Receive connector in Exchange2007.
Exchange 2007 and Exchange 2013 in the same subnet/network. if not please check any spam agent running between the networks. Are you running antispam on Exchange2013 ?
MAS

Move mailboxes and public folders from exchange 2007 to Exchange 2013

1. How do i move mailboxes from exchange 2007 to exchange 2013. I have more than 1000 mailboxes.
What is the correct way to migrate. do i need to move a single mailbox. During migration do the mailboxes get corrupted
2. I want to move public folders from Exchange 2007 to Exchange 2013.
I ran powershell commands and got these results please do guide me how to move to exchange 2013.and what are the shell commands
Get-publicfolder
Name Parent Path
IPM_SUBTREE
Get-publicfolder | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
Get-PublicFolderStatistics | select AdminDisplayName,FolderPath
AdminDisplayName FolderPath
exchangeV1 schema-root\microsoft\exchangeV1
Internet Newsgroups Internet Newsgroups
Get-PublicFolder -Recurse | fl name,replicas > c:\publicfolder.txt
Name : IPM_SUBTREE
Replicas : {}
Name : Internet Newsgroups
Replicas : {MAIL\Public Folder Storage\Public Folder Database}

I have started moving mailboxes , i have tried moving few individual mailboxes to see how things go
MAIL is my exchange 2007 and MAIL1 is my exchange 2013, please do refer the below result
PS] C:\Windows\system32>Get-MailboxDatabase -server mail
Name                           Server          Recovery
ReplicationType
Mailbox Database               MAIL            False           None
[PS] C:\Windows\system32>Get-MailboxDatabase -server mail1
Name                           Server          Recovery
ReplicationType
Mailbox Database 1460777952    MAIL1           False           None
[PS] C:\Windows\system32>New-MoveRequest -Identity '[email protected]' -TargetDatabase "Mailbox Database 1460777952"
DisplayName               StatusDetail              TotalMailboxSize
TotalArchiveSize         PercentComplete
[email protected]          Queued                    363.6 MB (381,217,115 ...
0

Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?

i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

Cannot send email from Exchange 2007 to Exchange 2013

Hello Anyone,
Anyone can help? I've prepare MS Exchange 2013 already, for Migration MS Exchange 2007 and I got the issue.
My issue is I can't send email from Exchange 2007 to Exchagen 2013, but for Exchange 2013 can send email to Exchange 2007,
is my issue only internal email for external email both Exchange server is working fine.
Regards,
Eakkasak

Thanks for your reply, when I send email from Exchange 2007 to Exchange 2013 I'm get the error message below.
Delivery is delayed to these recipients or distribution lists:
Eakkasak Buajan
Subject:
This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.
Delivery of this message will be attempted until 8/29/2014 8:30:29 PM (GMT+07:00) Bangkok, Hanoi, Jakarta. Microsoft Exchange will notify you if the message can't be delivered by that time."
I'm already tick "Exchange server Authentication" in the Default Receive connector properties of Exchange 2013"
I'm restart services and restart all Exchange Server but doesn't work.
Thanks,
Eakkasak
Sent by Microsoft Exchange Server 2007

Help With Migration From Exchange 2007 To Exchange 2013

We have an Exchange 2007 Server with Service Pack 3 and Rollup 12 applied.
I installed a new Exchange 2013 Server and then immediately applied CU3.
I am following this Technet article:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
The only deviation from the instruction I have had to do is in Part 2, section 4 “Configure offline address book (OAB)”.
Instead of entering:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2013)"
I had to enter:
Get-MailboxDatabase | Set-MailboxDatabase -OfflineAddressBook "\Default Offline Address Book (Ex2012)"
I believe this is due to the fact that the writer installed from an Exchange 2013 CU1 disk and I only had Exchange 2013.
Also when I tried to run:
Move-OfflineAddressBook -Identity "Default Offline Address Book" -Server SRV-EX2013
I get the following error:
Move-OfflineAddressBook : Failed to create the 'ExchangeOAB' folder on the target server 'SRV-EX2013'. Two possible reasons for the failure are that the System Attendant Service is not running or you do not have permission to perform
this operation. Error message : 'Catastrophic failure (Exception from RESULT: 0x8000FFFF (E_UNEXPECTED))'.At line:1 char:24+ Move-OfflineAddressBook <<<<
-Identity "Default Offline Address Book" -Server SRV-ex2013+ CategoryInfo
: InvalidResult: (Default Offline Address Book:OfflineAddressBookIdParameter) [Move-OfflineAddressBook], LocalizedException
+ FullyQualifiedErrorId : 9250969C,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveOfflineAddressBook
However when I looked at the address books in EAC I could see that “Default Offline Address Book (Ex2012)” was the default and that it contained a copy of the Global Address List. So I did nothing else about it.
I am now at Part 3, section 7 “Move Mailboxes” and it keeps failing.
I am using the EAC so that I at least see the error as using the powershell brings back no results.
Anyway it Syncs the 18 items in the mailbox then fails with:
Data migrated: 936.7 KB ‎(959,145 bytes)‎
Migration rate: 0 B ‎(0 bytes)‎
Error: MigrationPermanentException: Error: An error occurred while updating a user object after the move operation. --> Unable to generate the e-mail address. Unable to load address module ‎'C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\address\SMTP\AMD64\inproxy.dll‎'
for address type ‎'SMTP‎'. Additional message: ‎'Access is denied‎'.
Help??
Tony

Hi,
You can't configure Exchange 2013 to generate other OAB versions, and the OAB generation occurs on the Mailbox server on which the organization mailbox resides.Therefore, to move OAB generation in Exchange 2013, you must move the organization mailbox. You
can only move the OAB generation to another Exchange 2013 mailbox database. You can’t move OAB generation to a previous version of Exchange.
And please refer to the following articles :
Moving OABs between Exchange versions
If you want to upgrade from exchange 2007 to exchange 2013,I recommend you refer to the following article:
Upgrade from Exchange 2007 to Exchange 2013
Exchange version
Exchange organization coexistence
Exchange 2007
Supported with the following versions of Exchange:
Update Rollup 10 for Exchange        2007 Service Pack 3 (SP3) on all Exchange 2007 servers in the
organization, including Edge Transport servers.
Exchange 2013 Cumulative        Update 2 (CU2) or later on all Exchange 2013 servers in the
organization.
Install Exchange 2013 in an Existing Exchange 2007 Organization
You can install a Microsoft Exchange Server 2013 server into an existing Exchange Server 2007 organization, and then move the Exchange resources, such as mailboxes, public folders, and connectors, to Exchange 2013. However, you can't perform an in-place
upgrade from Exchange 2007 to Exchange 2013.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support

Public folders from exchange 2007 to exchange 2013

HI I am new to exchange, i am planning to do the migration of Exchange 2007SP3 UR10 to Exchange 2013 CU7, I want to move public folders from exchange 2007 to exchange 2013. wht is the procedure to move and wht are the commands to know how many public folders
i have.I just want to be aware before the installation so that later i can avoid issues.please do guide me

Hi Quiett,
please find how to move public folders on ttp://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/migrating-public-folders-exchange-2013-part1.html
You can replace your servers names and follow exactly the proedure that is shown there. I strongly suggest to read also the 2nd page (replication) before you start. Please be aware of
Set-OrganizationConfig –PublicFoldersLockedForMigration $True , so you cannot change the source side whle migrating.
Regards,
Martin

Mailbox Move from Exchange 2007 to Exchange 2013

I was surpprised to see that when I move mailboxes from exchange 2007 to Exchange 2013, that the mailbox being moved does not get disconnected during the move process (client Outlook connection). That is great news but supprising to me. I know
moving from 2010 - 2013 or 2013 - 2013 is a background process. Did something change with this recently or has it always been this way? Does the mailbox move flag inside the mailbox just jet ignored?
Thanks

When you do a mailbox move it stays connected during the initial sync. Once the initial sync is performed, there is another phase where it completes the mailbox move (basically updates some AD attributes) when this piece happens users will not be able
to access their mailboxes.
You can control this behavior by setting the SuspendWhenReadyToComplete
switch either by command line when creating the move request via the EMS
https://technet.microsoft.com/en-us/library/dd351123%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Or if you are doing this via the the EAC select "Manually Complete the batch" option before starting the move.
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

Move Mailboxes from Exchange 2007 to Exchange 2013 (Could not find a valid mailbox migration for esta organization)

Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
"Could not find a valid mailbox migration for this organization"
Do you know that you can be?
regards
Microsoft Certified IT Professional Server Administrator

Hi,
From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
Migration.8f3e7716-2011-43e4-96b1-aba62d229136
If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
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

Migration from Exchange 2007 to Exchange 2013

We are migrating from Exchange 2007 to Exchange 2013. We have a new Exchange 2013 server will all of the roles installed, but none of the mailboxes have even been moved yet. We are seeing some of our users getting prompted to accept the self signed certificate
on the exchange 2013 server. Exchange 2007 server is still handling all of the mail flow and connectors. Any reason why some of our users would be prompted with the certificate for the exchange 2013 server even though their mailbox is still on exchange 2007.
Our users are on outlook 2010.
Ed
Ed

Hi,
Could you show us what is the prompt details?
According to your desciption,I recommend you refer to the following methods to troubleshoot:
1.Please check if outlook anywhere been configured to connect exchange 2013.
2.Ctrl+Right click outlook, use “Test E-mail AutoConfiguration” to check all the settings .
Thanks.
Niko Cheng
TechNet Community Support

Upgrade exchange 2007 to exchange 2013 on SBS 2008

Hi,
I need to upgrade EX07 to EX13 on small business server 2008, So I am looking for the documents or steps which will help in Implementation.
Thanks in advance!
-av

Hi,
Any update about the issue?
In-place upgrade is not possible. According to the MS article:
When you're upgrading your existing Exchange 2007 organization to Exchange 2013, there's a period of time when Exchange 2007 and Exchange 2013 servers will coexist within your organization. You can maintain this mode for an indefinite period of time, or
you can immediately complete the upgrade to Exchange 2013 by moving all resources from Exchange 2007 to Exchange 2013, and then decommissioning the Exchange 2007 servers. You have a coexistence scenario if the following conditions are true:
Exchange 2013 is deployed in an existing Exchange organization.
More than one version of Microsoft Exchange provides messaging services to the organization
Upgrade from Exchange 2007 to Exchange 2013
https://technet.microsoft.com/en-us/library/jj898581%28v=exchg.150%29.aspx?f=255&MSPPError=-2147217396
Regards.
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Exchange 2007 and exchange 2010 Federation

Hi all I am trying to federate between Three organisations
org A exchange 2007 with exchange 2010 cas
org B exchange 2010.
org C exchange 2010.
I cannot share my calendar from org A to Org B
I can share Org B to Org A and Org B to Org C.
when I try from Org A to Org B or Org C
When I try to share free/busy fro the exchange 2007 with exchange 2010 cas. The user gets an error
"calendar sharing is not available with the following entries because of permission settings on your network."
-availabilityaddressspace. Autodiscover works TXT works. I have added a user from Org B as a contact in exchange.
The exchange 2010 server is not the CAS server for the exchange environment and I is not a proxy for exchange 2007. Is this where I am failing ?
Heeeelp

Hi Nigel,
How is the impact, just one user or all users, Outlook or OWA?
If just one user, it seems like an issue on the Outlook Client side.
Please trying to re-create new profile to fresh the caches.
Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
Found a similar thread for your reference:
Calendar Sharing not available error message
http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

TS4136 Apple Mail ActiveSync issue during Exchange 2007 to Exchange 2010 migration

Similar Messages

Maybe you are looking for