• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1290
  • Last Modified:

Exchange 2010/2003 coexist OWA issue

I just installed 2010 Exchange into an existing 2003 forest. I did all the AD, domain, schema prep successfully, installation installled without issue.  i can see all the legacy exchange mailboxes just fine in the 2010 emc, but when trying to log into webmail on a legacy 2003 account i get " Your request couldn't be completed because no server with the correct security settings was found to handle the request. If the problem continues, contact your helpdesk" But if i create a new user on 2010 i get in just fine?
0
jasonmichel
Asked:
jasonmichel
  • 17
  • 14
  • 3
  • +1
3 Solutions
 
sunnyc7Commented:
Can you check if the mailbox you are trying to login to - is that in 2003 or 2010
0
 
jasonmichelAuthor Commented:
yes, the mailbox i am trying to login to is on the 2003 server, if i create a new mailbox on the 2010 server it works fine
0
 
Hex255Commented:
You will need to refer to this Technet Article:

http://technet.microsoft.com/en-us/library/ee332348(EXCHG.140).aspx 

Good luck!
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
sunnyc7Commented:
Jason
To clarify

a) you migrated 2003 mailbox to 2010
b) You are trying to login to OWA 2010 to the 2003 mailbox which you just migrated.
c) You get the error above ?
Your request couldn't be completed because no server with the correct security settings was found to handle the request. If the problem continues, contact your helpdesk

If this is the case, run this from 2010 shell
Update-Recipient -Identity "John Smith"

OR
a) You are trying to log into 2003 OWA and you get the above error.

please clarify.
0
 
jasonmichelAuthor Commented:
the 2010 and 2003 are coexisting at the moment, i haven't migrated the 2003 mailboxes yet because they are switching to new domain and external DNS/MX isn't in place yet.  So if i log into the 2010 OWA with any of the 2003 users, i get that error, but if i create a new user, assign it to the 2010 database on that server, i can access fine.
0
 
sunnyc7Commented:
if you login to 2010 you will get that error - because those mailboxes are not moved to 2010 yet.

If you want the users to login to 2003 mailboxes from 2010 OWA

Run
get-owavirtualdirectory | fl identity

copy the identity field content

Set-OwaVirtualDirectory -identity "Paste the identity field content" -Exchange2003Url:"https://ex2003.domain.local/exchange

where
ex2003.domain.local is your 2003 server
0
 
jasonmichelAuthor Commented:
it says   RISERVER02\owa (Default Web Site)

so i need to do

Set-OwaVirtualDirectory -identity "RISERVER02\owa" -Exchange2003Url:https://10.15.160.5/exchange

0
 
sunnyc7Commented:
Set-OwaVirtualDirectory -identity "RISERVER02\owa*" -Exchange2003Url:https://exchange2003.domain.local/exchange
0
 
jasonmichelAuthor Commented:
so i take it i can't use the ip, and have to use the FQDN?
0
 
sunnyc7Commented:
yes

Please check your internal DNS also
I hope you have separate names for 2003 and 2010 - and it doesnt point to a generic - mail.domain.local
0
 
jasonmichelAuthor Commented:
ok, i get page can't be displayed, it looks like its trying to redirect though to https://riserver01.rinet01.domain.org/exchweb/bin/auth/owaauth.dll
0
 
sunnyc7Commented:
can you ping riserver01.rinet01.domain.org

if not
then we need to change it to the FQDN of exchange 2003
let me know the FQDN of your exchange 2003 server which you can ping.

thanks
0
 
jasonmichelAuthor Commented:
yep i can ping it
0
 
sunnyc7Commented:
can you go here
https://riserver01.rinet01.domain.org/exchange

What happens when you try to login
0
 
jasonmichelAuthor Commented:
same thing, page can't be displayed but if i go http://riserver01.rinet01.domain.org/exchange

i can log in fine
0
 
sunnyc7Commented:
Is http ssl service running on exchange
0
 
jasonmichelAuthor Commented:
on 2003 yes
0
 
sunnyc7Commented:
Can you download and run this on 2003
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en

Run a health scan
Export the report as HTML
upload the report here

thanks
0
 
jasonmichelAuthor Commented:
ok, here are the results
ExBPA.201009140858593750.data.htm
0
 
sunnyc7Commented:
Unrecognized Exchange signature      Domain: RINET01
Active Directory domain 'RINET01' has an unrecognized Exchange signature. Current DomainPrep version: 12639

>> this is a report from exchange 2010

Can you get us the report for Exchange 2003 ?
0
 
jasonmichelAuthor Commented:
how would i do that?
0
 
sunnyc7Commented:
Download this tool in Exchange 2003
Can you download and run this on 2003
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=dbab201f-4bee-4943-ac22-e2ddbd258df3&displaylang=en


run a health scan

Exchange 2003 doesnt come pre-loaded with that.
2010 does.
0
 
jasonmichelAuthor Commented:
thats what i did
0
 
sunnyc7Commented:
ok - so your exchange 2003 is giving a signature of Exchange 2010 ?? :)

I thought you ran the built-in tool from exchange 2010.

Will post back.
0
 
jasonmichelAuthor Commented:
just a quick google, it seems as if this is a bug in the exbpa

http://itsolutionsdirect.com/unrecognized-exchange-signature-12639-in-exchange-2010-bpa/353/ 
0
 
sunnyc7Commented:
that bug is for pure Exchange 2010 installation
Bug is - Exchange 2010 version is 12639, and exBPA shows it as uncrecognized - whereas it should show it as Exchange 2010

Your case is different.
You are running ExBPA from exchange 2003, and its showing the signature as that of Ex 2010
0
 
jasonmichelAuthor Commented:
is it something that happened during domain prep?
0
 
jasonmichelAuthor Commented:
any luck yet?
0
 
jasonmichelAuthor Commented:
any ideas  yet ?
0
 
sunnyc7Commented:
jason I am out of office today. @endital will be able to assist you.
You can also click on request attention at the top of the page and ask other experts to join in on the case.

0
 
jasonmichelAuthor Commented:
ah..ok, thanks
0
 
George SasIT EngineerCommented:
Jason , please check this article to see why you have this problem :
http://msexchangeteam.com/archive/2009/11/20/453272.aspx

To ensure that Outlook Web Access functions correctly, you will need to enable the following URLs:

    * Outlook Web Access:
          o For environments without Exchange 2003: Set-OWAVirtualDirectory \OWA* -ExternalURL https://mail.contoso.com/OWA
          o For environments with Exchange 2003 mailbox servers: Set-OWAVirtualDirectory \OWA* -ExternalURL https://mail.contoso.com/OWA -Exchange2003URL https://legacy.contoso.com/exchange
    * Exchange Control Panel: Set-ECPVirtualDirectory \ECP* -ExternalURL https://mail.contoso.com/ECP
0
 
George SasIT EngineerCommented:
Please read the WHOLE article and follow all the steps explained.
0
 
George SasIT EngineerCommented:
Did it help ?
0
 
jasonmichelAuthor Commented:
all set now
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 17
  • 14
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now