Exchange 2003/2010 Coexistance - User login Issue

Hello
We have deployed Exchange 2010 SP3 in coexistance with 2003 and created connectors.
2003/2010 both Users are not able to login on 2010 OWA and error showing that username/PW is wrong although they are working on OWA 2003 perfectly.
When i add the same user to the local admin group on the Ex2010 server, it works fine with email send/receive. i am confused please suggest what i am missing....Regards
Waseem

Hello
This is the error that occured during that time.
SACL Watcher servicelet encountered an error while monitoring SACL change.
Got error 1722 opening group policy on system SERVER.DOMAIN in domain MYDOMAIN.
Event ID 6003
Source : MSExchange SACL Watcher
i am not sure if its related to this problem.
Secondly i have also tested to run the "Microsoft Exchange Active Directory Topology Service" with a new user having all the rights of exchange & AD groups but its showing giving the error that it cant run the dependency
services. currently this service is running with the local account rights.
I just add the test users (moved from 2003 and new user created in 2010) to the local admin group and it works fine, please give any idea what may be the problem in rights or something else ??
Regards
Waseem

Similar Messages

Exchange 2003/2010 Co-Existence - Distribution Group Management

We're running both exchange 2010 and Exchange 2003. I have an issue where some distribution groups were upgraded to Exchange 2010 (v14.0.100) and the manager of those lists who are on Exchange 2003 can no longer modify members, they get the error:
"Changes to the distribution list membership cannot be saved. You do not have sufficient permission to perform this operation on this object".
We've already implemented the myDistributionGroupsManagement role with success to allow Exchange 2010 users to manage their own list without allowing them to create new ones.
http://blogs.technet.com/b/exchange/archive/2009/11/18/3408844.aspx
Trying to apply the "Default Role Policy Assignement" to the exchange 2003 users returns an error. Is there any way Exchange 2003 users can manage Exchange 2010 Distribution list they owned without being upgraded to Exchange 2010? If not, is
there any way to downgrade distribution group to Exchange 2003 once they've been upgraded?

Hi,
From my lab, legacy exchange user can manage the distribution group which has been upgrade to Exchange 2010.
Exchange 2010 sp2, Exchange 2003 with sp2.
I can add/remove member for distribution group from address book via outlook.
Xiu Zhang
TechNet Community Support

Exchange 2003 -2010 cross forest (NDR 5.4.6)

Hi.
Have: Exchange 2003+2010 in source forest. Exchange 2010 in target forest.
Successful migrate mailbox to target forest (in source forest this mailbox convert to mailuser).
When try send e-mail to this mailbox (it`s in target forest) from Exchange 2003 mailbox get this:
A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients.
If send from Exchange 2010 (source/target) - all mail ok.
If delete this mailuser (in source forest) - all set to ok.
x500?
Please, help.
Thanks.

Hi,
In the error event, 5.4.6 means "Routing loop detected" (RFC1893).
This issue occurs if the source Exchange organization is authoritative for the target domain. Because the source Exchange organization is responsible for mail delivery to target, the categorizer tries to find locally a recipient for
that message. The categorizer does not succeed, and then you receive the NDR.
More details in the following KB:
You receive an NDR with a 5.4.6 status code when you send a message to a specific domain in Exchange
http://support.microsoft.com/kb/324732/en-us
Hope it is the solution.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2003 /2010 Co-existence plus 2010 migration to new hardware

Hi,
Here is our current scenario;
Exchange 2003/2010 co-existence. This has been running perfectly for a couple of months now.
Exchange 2003 - exch1.domain.lan
Exchange 2010 (SP3) - exch2.domain.lan (local domain name) / mail.domain.com.au (external domain name)
ActiveSync, autodiscover, legacy etc are all working. Our UAC certificate from GoDaddy has all the required names for exch2 - except it doesn't have the local domain name as they don't allow certificates with that anymore. I've configured all the required
services to be the external domain name and am running split DNS.
The first Exchange 2010 server I installed was lower spec'd and only has about 25 users on it. I now need to install a second Exchange 2010 server (exch3.domain.local), which is properly spec'd and will host the entire company. I won't be running DAG as
I need to repurpose the first Exchange 2010 server once it's removed.
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange
organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
Any guidance on the above is helpful.
Thanks.
Steve

Hi Steve I will try my best to answer each of these
My high level questions are;
1) Should I migrate everyone off Exchange 2003 onto Exchange 2010, decommission the 2003 server, and then install the second 2010 server? OR
2) Should I install the second Exchange 2010 server, migrate everyone from the first Exchange 2010 server, decommission that one, then do the migration from 2003 to 2010?
OR does it matter which way I do it?
doesn't matter at all. Since you want to move to a new hardware you can setup a new Server CASH/HUB/Mailbox. Once installed start migrating the mailboxes from Exchange 2003 to this mailbox server. This way you will not have to redo the migration from 2010
to new 2010 sever -- like you mentioned in 1) it will save you a lot of time and repeating procedure.
I've read what I can find about installing the second Exchange 2010 server into the organisation. It seems to be pretty simple at first. Just install Exchange 2010 with HT, mailbox and CAS roles which will automatically configure it into the same Exchange organisation.
1) Do I configure CAS to be externally facing right from the get go or do I do that later?
Keep your existing 2010 internet facing for now. Once you finished migrating the mailboxes then you will need to do it.
2) As soon as I install the second Exchange 2010 server, will I encounter any mail flow problems? Will mail be trying to flow out of the second Exchange 2010 server as well as the first?
Mail will not flow to 2ndry server unless you add that server as a source serve in the transport.
In regards to SSL, so obviously the second Exchange 2010 server will have a different local domain name than the first, but ultimately, I want it to have the same external domain name, eg mail.domain.com.au. As my certificate doesn't contain any local domain
names, can I export the certificate from exch1 and import it into exch2, or should I just generate a new CSR from exch2 and get GoDaddy to reissue it?
You can always export the certificate and then import it to the newly installed Exchange 2010.
OR should I look at creating a CAS Array from exch1 and adding exch2 to it. (I don't fully understand the workings of this at the moment).
You will only need to setup the CAS array if you are going to use both the server which can be done later.
Hope that help
Where Technology Meets Talent

Exchange 2003-2010 co-existence environment

i have exchange 2003 -2010 co-existence environment .
Everything works fine accept below;weird issue,i tried to re-create routing group connector but issue is same.
My issue is very simple,The mail flow as below:
exchange 2003 to outside............
exchange 2010 to outside ...........works
exchange 2010 to 2003 ...............works
exchange 2003 to 2010................is not

Hi Huzefa,
Can you try creating a new bidirectional RGConnector and check?
New-RoutingGroupConnector -Name "NameOfRG" -SourceTransportServers "Ex2010.contoso.com" -TargetTransportServers "Ex2003.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true
http://technet.microsoft.com/en-us/library/aa997292(v=exchg.141).aspx
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013
Detected Problems:
- Access denied for attached mailbox (department mailbox)
- Access denied for delete or move messages on own mailbox
- Can't send new messages with error (Error: [0x80004005-00000000-00000000])
Solution:
- Rollback to Exchange 2010 SP3 - Rollup 7
- You can rollback to Exchange 2010 SP3 - RollUp 7 in 30 min
Algunos de los destinatarios no recibieron su mensaje.
Asunto: Hola
Enviado el: 11/12/2014 8:35
No se puede localizar a los destinatarios siguientes:
'[email protected]' en 11/12/2014 8:35
Este mensaje no se pudo enviar. Inténtelo de nuevo más tarde, o póngase en contacto con el administrador de red.
Error: [0x80004005-00000000-00000000].

See the following forum thread:
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8

Exchange 2003 - 2010 Local Mail box move Error

Hey everyone,
I have just finished a transition from Microsoft Exchange 2003 to 2010, and I am having problem with moving the Legacy mailboxes over.
I have managed to move all the mail boxes over bar 2, using the " New local move Request".
So the problem is just these 2 mail boxes with the same error as below.
Any Advice?
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:39
Sifiso Mguni
Failed
Error:
Service 'net.tcp://tvt-exchange.vtrust.local/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=131]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x80040111
    Lid: 26937
    Lid: 21921   StoreEc: 0x80040111
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0x80040111
    Lid: 26297
    Lid: 16585   StoreEc: 0x80040111
    Lid: 32441
    Lid: 1706    StoreEc: 0x80040111
    Lid: 24761
    Lid: 20665   StoreEc: 0x80040111
    Lid: 25785
    Lid: 29881   StoreEc: 0x80040111
Exception details: MapiExceptionLogonFailed (80040111): MapiExceptionLogonFailed: Unable to open message store. (hr=0x80040111, ec=-2147221231)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=131]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropLogon [254]
    Lid: 17082   ROP Error: 0x80040111
    Lid: 26937
    Lid: 21921   StoreEc: 0x80040111
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0x80040111
    Lid: 26297
    Lid: 16585   StoreEc: 0x80040111
    Lid: 32441
    Lid: 1706    StoreEc: 0x80040111
    Lid: 24761
    Lid: 20665   StoreEc: 0x80040111
    Lid: 25785
    Lid: 29881   StoreEc: 0x80040111
Exchange Management Shell command attempted:
'vtrust.local/Valley Trust Users/Users/Staff/Sifiso Mguni' | New-MoveRequest -TargetDatabase 'Mailbox Database 0271422377'
Elapsed Time: 00:00:39

HI. I had the same problem while trying to migrate a user from Exchange 2003 to 2010. And the same error as you have appeared. I tried to skip more e-mails in case some fails but couldn't get successful.
Check if the user have accessed the mail at all on Exchange 2003 because if the user didn't accessed it it may contain many mails and when we try to migrate the mailbox, the mailbox size on Exchange 2003 may be grater than on the 2010.
On my case after many reading we just see that the user didn't access the mail at all on our Exchange 2003. (Let me know if you need to know how you can check if the user accessed the mail or not or you can just google it). So what we have done is we just
reset the user password on Active Directory. Because as you can see the error is related with Logon Failure.
This solved the issue for me. Can you check this way
Thanks

Namespace for Exchange 2003 == 2010 == 2013 Migration

Hi
Hope someone can help. I am working on an Exchange 2003 to 2010 migration, which will then quickly move onto a 2010 to 2013 migration and need some clarification on the namespaces to use. I am aware that if I do not do this right at the 2003
to 2010 migration, this will cause a headache at the 2010 to 2013 migration.
Some background:
2003 Functional Level Domain - 2 x 2008 DC's
Currently users are on a 2003 exchange cluster with a mix of RPC (internal users) and RPC over HTTP connections (roaming users)
We will be installing Exchange 2010 on a single server, with CAS, HUB and Mailbox roles and no load balancer, as we will be moving quickly to 2013.
We have two Kemp load balancers ready for Exchange 2013.
Exchange 2010 is installed on a single server (exh2010.domain.local) and configured with an CAS array name (exh-cas.domain.local) which is resolvable internally only.
Currently we have multiple smtp namespaces e.g. @company.com, @company2.com.
Our main website etc is www.company.com
Our public facing services are at https://service.mycompany.com
Our 2003 RPC address is https://webmail.mycompany.com
I understand that the 2010 RPC CAS array name should be separated from the Outlook Anywhere (RPC over HTTPS) address so that when 2013 takes over the HTTPS address, the RPC connections are not broken.
Two Questions:
Do we have to use the HTTPS same namespace for 2013 as we do in 2010? Its just I would want to test the Kemp load balancers before making them live (slow careful transition), and giving them a different namespace, e.g.
https://mail.mycompany.com would allow a migration, rather then a cutover.
Can we use the *.mycompany.com address rather then the company.com address, even though we have no SMTP addresses at mycompany.com? Can autodiscover still work?
Thanks in advance for any guidance
Cheers
Steve

1. No, but you can. Exchange 2013 will proxy all services for Exchange 2010, so if you set up everything right, you should be able to simply swing the name from Exchange 2010 to 2013.
2. Your web services can be published with any domain as long as the hostname is in the certificate. Only Autodiscover needs to match the e-mail domain(s). So in your example, you could publish OWA, ECP, ActiveSync, Web Services and OAB
at owa.mycompany.com. You would need autodiscover.company.com, autodiscover.company2.com, etc., but if you don't have e-mail addresses with mycompany.com, you don't need autodiscover.mycompany.com. If all users have a company.com e-mail address,
the you only need autodiscover.company.com as long as users know to enter that e-mail address when configuring profiles on PCs or devices. If you're going to have to have Autodiscover for multiple domains, then you might consider using an SRV record
instead because it can greatly simplify your certificate requirements.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Providing voicemail in a trusted-domain Exchange 2003 - 2010 upgrade

As a result of a merger, we are upgrading from Exchange 2003 in the same domain as a Unity 5.0 server to an Exchange 2010 server in a trusted domain in a different forest. The Exchange 2003 server is still up, but mailboxes are being moved to the 2010 server. The goal of getting Unity to somehow deliver voicemail to the users who have been moved to the 2010 server in the other domain is only temporary, as we will be replacing our on-premesis system with a hosted solution in a couple of months. So I'm looking for something quick, but it doesn't have to be elegant or permanent.
As Unity cannot connect to a partner Exchange server in a different forest, I see the most likely options as:
Move Unity to the new domain. Wanted to see how easy it would be to do this, as Cisco recommends that the same version of Unity be installed on a server in the new domain as is currently running the server in the old domain. I believe I have the original install disks, but can't speak to whether or not upgrades have been applied to the current (old) server since it went in 5 years ago.
Convert current subscribers into "Internet Subscribers" - This is not currently working, I believe, because Unity's partner server is the 2003 server, which lives in the same domain as the Unity server, but is also a part of the same Exchange group as the 2010 server in the new domain. When I create an "internet subscriber", I'm creating a contact with an email address that already exists in the domain.
For 1., Cisco says I have to install the same version of Unity in the new domain and then restore the database to it. Would I need to roll back items like the Engineering Special that I just installed? As long as the install disk is for 5.0(1) and the server's currently running 5.0(1), am I OK?
For 2., Is it possible to do anything with Internet subscribers? This seems like it would be easier, but also seems like it's not working because of the fact that the partner server is not recognizing addresses for the Internet subscribers as external.
Any assistance or insights would be greatly appreciated.
Kevin

Hi,
We can move the mailbox from Exchange 2003 to Exchange 2010 as a linked mailbox in Exchange 2010. The moved mailbox would be a disabled User Object which is linked to a separate enabled user object in an Account Forest (Exchange 2003 forest).
We can use the Prepare-MoveRequest.ps1 script in the Shell to prepare the cross-forest mailbox moves:
https://technet.microsoft.com/en-us/library/ee861103(v=exchg.141).aspx
Then we can create a remote legacy move request to move mailbox:
https://technet.microsoft.com/en-us/library/dd876952(v=exchg.141).aspx
Additionally, for more information about migration from Exchange 2003 to Exchange 2010, please read:
http://blogs.technet.com/b/schadinio/archive/2010/08/11/exchange-2010-cross-forest-mailbox-moves.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2003 - 2010. Moving public folders one at a time

Hi all,
I'm in the process of decomisioning our old Exchange 2003 server (long overdue after what has been a relativly smooth and trouble free transition to 2010). As the first step in the decomisioning process, I'm looking to move the public folders from the 2003
box to the 2010 box. From my understanding there are a couple of ways to achieve this (please correct me if I'm wrong). The first is to add the Exchange 2010 server as a new replication partner, allow for replication of the PFs to occur, and then remove the
2003 partner from the replication partnership. The other option is to use MoveAllReplicas.ps1.
I opted for the first option, but the problem I have is that the initial replication process started to generate a very large number of transaction logs on the Exchange 2010 server, to the point I was slightly conccerned I was going to run out of space on
the volume (our server is backed up nightly at which point the transaction logs are normally flushed).Whilst I know I could potentially increase the size of the volume or turn on cicular logging for the duration of the migration (neither of which is appealing
as it will involve down time), I was wondering if there was a way to move a smaller set of Public folders one at a time with a powershell command, or is it an all or nothing operation? My other option may be to replicate a small subset of folders everyday,
but that just a little painful as there are a large number of child folders with in the structure. Any other suggestions welcome!
Many thanks,
Rob

Hi,
If your Public Folder Database is large, you can use tool like Exfolders or ESM to add replica folder by folder.
A related article for your reference.
http://careexchange.in/moving-public-folders-from-exchange-2003-to-exchange-2010/
Note: 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.
And it is recommended to replicate public folders off business hours.
Best regards,
Belinda Ma
TechNet Community Support

AD users login issue.

Hi All,
We are getting login issue on our UAT server. AD users are not able to login into share point,it again prompting login box after entering correct username and password.
When we add that user to local admin group then it works.

May be you are try it on same sharepoint machine. If you try some other machine it will work fine. You need to create a registry key for that. This is a known issue with sharepoint
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
DWORD DisableLoopbackCheck
Value. 1
http://support.microsoft.com/kb/896861

Exchange 2003/2010 2003 AD to 2008 R2 AD

Setup:
DC's
2003 - 2, 2008 R2 -1 Domain functional level is Windows 2003.
Exchange
1 - 2003 SP2 running Exchange 2003, 1 - 2008 R2 running Exchange 2010 SP3.
All mail comes in through the Exchange 2003 server.
Question:
Both of our 2003 Domain Controllers are in bad shape and need to be replaced. We are going to replace them with 2008 R2 domain controllers. Can we change the domain functional level to 2008 R2 and leave the Exchange servers
alone or do we have to remove the Exchange 2003 server as well? Thanks for any help.

Hi
I would install the new DC, let replication take place and then seize the rolls to the new server. After that once you happy with everything then decommission the 2008 server. Are you running SBS with 2003 installed? if so you will need to first move all
your mailboxes over etc. before you decommission that DC.
It shouldnt be a problem to raise your domain level to 2008 R2 at all. I would plan this as you making big changes to your environment.
http://technet.microsoft.com/en-us/library/ff728623(EXCHG.141).aspx

Exchange 2003: Collab/Notification email relay issues

We use Exchange 2003 SMTP email server which is open internally and has relaying disabled.
The portal is installed on internal servers yet is having a problem sending notifications to external email addresses.
In the notification config file there are settings for email servers that have relaying disabled however this functionality doesn't work and the bug ticket for it has been opened for 4 years I'm told.
I'm wondering how smaller companies (<2000 employees) handle this issue.
Do you:
*enable relaying on your main email servers?
*setup a notification specific SMTP server?
*use a 3rd party email company?
What steps are there to reduce the threat of spammers and blacklists while still allowing email to be relayed?
I'm trying to work through this with our IT department but the idea of enabling relaying is a very touchy subject here as we have been burned by being blacklisted a few times in the past.
Thanks for any help!
Geoff

After going back and forth with Plumtree support for about 3 weeks we have solved the problem.
The problem came from a misunderstanding on what needed to be relayed. It turns out that external relaying is not needed, but internal relaying is.
Explicitly granting trust to the notification server allowed emails to begin flowing.
Geoff

Exchange 2007 2010 coexist autodiscover fails

We are migrating from 2007 to 2010. Autodiscover is not working on the 2010 CAS servers (4 of them).
SMTP=[email protected]
Attempting URL
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml found through SCP
Autodiscover to
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml starting
GetLastError=o; httpStatus=500
Autodiscover request completed with http status code 500
Autodiscover to
https://autodiscover.domain.com/Autodiscover/Autodiscover.xml Failed (0x80004005)
If I browse to the page, it returns the normal XML - error 600 Invalid request page.
The AutoDiscoverServiceInternalUri is set to
https://autodiscover.newpagecorp.com/Autodiscover/Autodiscover.xml on both the 2007 and 2010 CAS servers.
If we point our autodiscover DNS record to the 2007 CAS servers, 2007 mail users function just fine. If we point it to 2010 CAS servers, autodiscover fails, for both 2007 mail users and 2010 mail users (we only have 3 test users migrated)
Please help!
Thank you!

Just noticed this in the event log:
Log Name:      Application
Source:        System.ServiceModel 3.0.0.0
Date:          4/24/2014 7:06:02 PM
Event ID:      3
Task Category: WebHost
Level:         Error
Keywords:      Classic
User:          SYSTEM
Computer:      server.domain.com
Description:
WebHost failed to process a request.
Sender Information: System.ServiceModel.ServiceHostingEnvironment+HostingManager/32001227
Exception: System.ServiceModel.ServiceActivationException: The service '/Autodiscover/autodiscover.xml' cannot be activated due to an exception during compilation. The exception message is: A binding instance has already been associated to listen
URI 'http://server.domain.com/Autodiscover/Autodiscover.xml'. If two endpoints want to share the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a
config file, or a combination of AddServiceEndpoint() and config. . ---> System.InvalidOperationException: A binding instance has already been associated to listen URI 'http://server.domain.com/Autodiscover/Autodiscover.xml'. If two endpoints want to share
the same ListenUri, they must also share the same binding object instance. The two conflicting endpoints were either specified in AddServiceEndpoint() calls, in a config file, or a combination of AddServiceEndpoint() and config.
   at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
   at System.ServiceModel.ServiceHostBase.InitializeRuntime()
   at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.ActivateService(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   --- End of inner exception stack trace ---
   at System.ServiceModel.ServiceHostingEnvironment.HostingManager.EnsureServiceAvailable(String normalizedVirtualPath)
   at System.ServiceModel.ServiceHostingEnvironment.EnsureServiceAvailableFast(String relativeVirtualPath)
Process Name: w3wp
Process ID: 8256

Exchange Server 2003/2010 Coexistence Mail-flow Issues

I've installed Exchange 2010 in a 2003 coexistence scenario.
2010 was deployed with CAS,HUB, and Mailbox roles.
The installation went through smoothly, and the default RGC was created.
On the 2010 Server, when I create a new users with mailbox, that user is no able to send or receive mail from anywhere.
2010 user to 2010 user does not work
2003 user to 2010 user does not work
Mail delivery between 2003 users works fine.
The RGC message queue in ESM 2003 shows that the messages are queued and keep retrying.
I have deleted the RGC twice and created new ones, I have un-installed the HUB and CAS roles and re-installed them, and I have also re-run setup /preparead and setup /preparelegacyexchangepermissions
I'm not able to make any sense of the message tracking on the 2010 side. It just shows a bunch of entries:
EventID: NOTIFYMAPI
Source: STOREDRIV
When I use the best practices analyzer to test mailflow to a 2010 user from the outside, the test comes back with a pass even though the message itself isn't delivered to the specified mailbox.
There is no smart host defined on the default SMTP virtual server on 2003.
There is no SMTP Send Connector for External or Internal mail configured on 2003 besides the 2010 RGC
Any ideas?
Here is the mail flow analyzer result:
Testing inbound SMTP mail flow for domain '[email protected]'.
     Inbound SMTP mail flow was verified successfully.
     Additional Details
Elapsed Time: 3437 ms.
     Test Steps
     Attempting to retrieve DNS MX records for domain 'test.com'.
     One or more MX records were successfully retrieved from DNS.
     Additional Details
MX Records Host mail.test.com, Preference 0
, Host test.com, Preference 10
Elapsed Time: 110 ms.
     Testing Mail Exchanger mail.test.com.
     This Mail Exchanger was tested successfully.
     Additional Details
     Test Steps
     Attempting to resolve the host name mail.test.com in DNS.
     The host name resolved successfully.
     Additional Details
     Testing TCP port 25 on host mail.test.com to ensure it's listening and open.
     The port was opened successfully.
     Additional Details
Banner received: 220 EX2K3w2K3.test.net Microsoft ESMTP MAIL Service, Version: 6.0.3790.3959 ready at Wed, 5 Feb 2014 14:40:44 -0500
Elapsed Time: 368 ms.
     Analyzing SMTP Capabilities for server mail.test.com:25
     SMTP Capabilities were analyzed successfuly.
     Additional Details
     Attempting to send a test email message to [email protected] using MX mail.test.com.
     The test email message was delivered successfully.
     Additional Details
Elapsed Time: 621 ms.
     Testing the MX mail.test.com for open relay by trying to relay to user [email protected].
     The Open Relay test passed. This MX isn't an open relay.
     Additional Details
     Testing Mail Exchanger test.com.
     This Mail Exchanger was tested successfully.
     Additional Details
     Test Steps
     Attempting to resolve the host name test.com in DNS.
     The host name resolved successfully.
     Additional Details
     Testing TCP port 25 on host test.com to ensure it's listening and open.
     The port was opened successfully.
     Additional Details
     Analyzing SMTP Capabilities for server test.com:25
     SMTP Capabilities were analyzed successfuly.
     Additional Details
     Attempting to send a test email message to [email protected] using MX test.com.
     The test email message was delivered successfully.
     Additional Details
     Testing the MX test.com for open relay by trying to relay to user [email protected].
     The Open Relay test passed. This MX isn't an open relay.
     Additional Details

No duplicate security groups. I did notice Exchange 2010 is not in the Exchange Domain Servers group, but 2k3 is. Not sure if that matters.
In the Application event log I'm seeing this error a lot.
Log Name: Application
Source: MSExchangeMailSubmission
Date: 05/02/2014 3:02:31 PM
Event ID: 1009
Task Category: MSExchangeMailSubmission
Level: Error
Keywords: Classic
User: N/A
Computer: ex2010w2k8.test.net
Description:
The Microsoft Exchange Mail Submission service is currently unable to contact any Hub Transport servers in the local Active Directory site. The servers may be too busy to accept new connections at this time.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeMailSubmission" />
<EventID Qualifiers="49156">1009</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-02-05T20:02:31.000000000Z" />
<EventRecordID>6530</EventRecordID>
<Channel>Application</Channel>
<Computer>ex2010w2k8.test.net</Computer>
<Security />
</System>
<EventData>
<Data>HubTransport</Data>
</EventData>
</Event>
As long as you cannot send email between ex2010 users this has nothing to do with connectors/smtp config..
I had the same issue one year ago and solved adding both sevrers to old/new exchange sevrers security groups.
Looks like for some missing security entry (not sure why) mailbox is unable to conact HUB  (MSExchangeMailSubmission) I expect you seing items stuck in draft for owa (outbok for outlook)
I saw in some blogs similar cases solved by setting static DNS servers for HUB severs config.
Yes that is similar to what I'm experiencing.
When using the Outlook client with a 2010 mailbox the mail leaves the outbox fine. When using OWA new messages just get saved as drafts when I try to send them.
I will try your suggestions. I see two groups. Exchange Domain Servers, and Exchange Enterprise Servers of which Exchange Domain Servers is a member.

Exchange 2003/2010 Coexistance - User login Issue

Similar Messages

Maybe you are looking for