Exchange Activesync error for only one user

I have one user that is having problems using Activesync. This issue is consistent for the user on any device that is attempted. The Device is receiving a 500 Internal Server error message. I have turned on verbose logging, and not much else useful really comes back. I deleted the user and the mailbox and recreated him. The problem still persisted.

Since Activesync uses the Pre-Windows 2000 username, i thought that perhaps it was getting truncated on the devices somehow.  The usersname was 'impact.moor5567'.  I Changed the pre-windows account name and the mailbox alias to 'moor' instead.

I still recieve the error.  Since my understanding is that Activesync is part of the OMA functionality, I decided to try to log in to OMA and see what happened. I receive an error when i attempt to log in here as well. The page comes back with a message saying: "  Network problems are preventing OMA from working properly. Please try again later. If this problem persists contact your administrator."

The front-end server also throws a message in the Application Event log, and cannot find any other information. Here is the information:

Event Type: Error
Event Source: MSExchangeOMA
Event Category: (1000)
Event ID: 1904
Date:  2006-04-17
Time:  20:05:03
User:  N/A
Computer: EXFE02
Description:
Unable to connect to the global catalog server. To fix this problem, verify that network connectivity exists between this server and the global catalog servers. Also, verify that the global catalog servers are working properly.


Again, OMA and Activesync work fine for all of my other users, just this one user has issues.
LVL 9
atheluAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SembeeCommented:
If you have deleted the account and the problem continues, then I would tend to think it is the device.
Try this user's account with the emulator: http://www.amset.info/pocketpc/wm5emulator.asp
If the problem doesn't follow, then hard reset the device and then configure it again.

Simon.
0
atheluAuthor Commented:
I configure the device with my own account and it works just fine. I have tried the account on two other devices as well ( known working ones) and still have the problem.
0
SembeeCommented:
When you recreated the account, did you bring anything over from the old account?
It is very odd for anything to survive account recreation.

Simon.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

atheluAuthor Commented:
No. I even purged the old Mailbox before creating the new account.

Actually, i think that i have discovered that ANY new user that I create is having this issue. The only thing that has changed (recently) was for me to change my exchange environment to native mode instead of mixed-mode.
0
SembeeCommented:
The change in mode shouldn't have affected it either.
Does OMA work?

Simon.
0
atheluAuthor Commented:
not for these users.  I posted the results of this testing in my original message.
0
SembeeCommented:
The error message you have posted in the original message isn't much help.
Browse to the OMA virtual directory using a regular machine and internet explorer with show friendly HTTP error messages turned off.

Simon.
0
atheluAuthor Commented:
ok

Turns out that this is a hosted related issue. Microsoft tells me that the activesync service cannot cope with a user whose UPN does not match his Primary email domain. There is an SMTPproxy value that can be created in the registry to correct this, but they could not tell me whether this value could store multiple domains or only one.

This makes a little bit of sense, since recently we changed our structure from creating new UPN domains for hosted companies to using the same UPN domain across the board. This was still a while ago however, but most likely someone just hadn't tried setting up Activesync on a new account since the change.  What I don't get though is that we changed the UPN on ALL the users, even the pre-existing ones. These older accounts still work. I can only assume it has something to do with creating the account initially with the other UPN value or some such.

Anyway, i was instructed by Microsoft that SP2 for exchange accomodates the differeing UPN domain/Email domain issue. So looks like I get to install Windows SP1 and exchange SP2 soon....
0
SembeeCommented:
You might also want to look at this article as well.

http://support.microsoft.com/default.aspx?kbid=886346

I kinda assumed that you were already on the latest service packs, because most people who are trying to do EAS connections want push, and for push you need the latest Exchange Service Pack.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.