Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Users cannot ACTIVESYNC with Exchange 2007 server to iPhone and/or Windows Mobile devices
We have just recently implemented a new Exchange 2007 server in our org. We have decommissioned and "RemoveLastLegacyExchangeS
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx
Users in the office are fine with their Outlook Clients & the new exchange server. Even OWA works fine, and users are able to download the self-issues certificate that the server distributes.
The problem that's been driving me & Microsoft Tech Support nuts it he MSExchangeActiveSync....It
" Exchange ActiveSync encountered an error. Support Code: 0x85010014" I have checked all the resources on this particulart error code, and none of the solutions work.
Furthermore, when I log onto the physical Exchange server and check the Event Viewer Application Log, I am greeted with these errors. (See 'event1008.txt' and 'evt1309.txt')
Microsoft tech suppt. seems to think it has something to do with the AppPool in the IIS Manager...since all I have to do is restart the appPool and we are fine again. However, I have a feeling that somehow the activesync service may be trying to still connect to the old storage database which was manully removed. I can't understand why the EXCEPTION TYPE is looking for mailboxes in "FIRST ADMINISTRATIVE GROUP"....doesn't that belong to the old Serv2003 Exchange??? The new storage is actually called EXCHANGE ADMINISTRATIVE GROUP (FYDIB******).
This issue has been going on for a few weeks now. Microsoft Tech suppt. is baffled, and I am too. Has anyone seen or heard of this before???
event1008.txt
evt1309.txt
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx
Users in the office are fine with their Outlook Clients & the new exchange server. Even OWA works fine, and users are able to download the self-issues certificate that the server distributes.
The problem that's been driving me & Microsoft Tech Support nuts it he MSExchangeActiveSync....It
" Exchange ActiveSync encountered an error. Support Code: 0x85010014" I have checked all the resources on this particulart error code, and none of the solutions work.
Furthermore, when I log onto the physical Exchange server and check the Event Viewer Application Log, I am greeted with these errors. (See 'event1008.txt' and 'evt1309.txt')
Microsoft tech suppt. seems to think it has something to do with the AppPool in the IIS Manager...since all I have to do is restart the appPool and we are fine again. However, I have a feeling that somehow the activesync service may be trying to still connect to the old storage database which was manully removed. I can't understand why the EXCEPTION TYPE is looking for mailboxes in "FIRST ADMINISTRATIVE GROUP"....doesn't that belong to the old Serv2003 Exchange??? The new storage is actually called EXCHANGE ADMINISTRATIVE GROUP (FYDIB******).
This issue has been going on for a few weeks now. Microsoft Tech suppt. is baffled, and I am too. Has anyone seen or heard of this before???
event1008.txt
evt1309.txt
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
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.
I have only one exchange server. NO ISA server. Everything I need is installed on this one single box. Mailbox Role, Client Access Role, & Hub Transport role are all there. IIS 7 is installed. Mobile devices connect directly to the server from outside, just like our OWA users do. THis is soooo weird..
ok
did Microsoft assisted you with all troubleshoting steps ? did they delete and recreate the Activesync virtual directory , Also did they verify the device ID restriction on the Activesync policy ?
if not try recreating the activesync folder by using command on exchange console :
remove-ActiveSyncVirtualDi
New-ActiveSyncVirtualDirec
also Test if the deviceID restriction is null, if the list is NULL, which is the default, a user can sync with any device
also try disabling your Activesync policy for testing , wait few hours then test
http://technet.microsoft.com/en-us/library/aa997160(EXCHG.80).aspx
did Microsoft assisted you with all troubleshoting steps ? did they delete and recreate the Activesync virtual directory , Also did they verify the device ID restriction on the Activesync policy ?
if not try recreating the activesync folder by using command on exchange console :
remove-ActiveSyncVirtualDi
New-ActiveSyncVirtualDirec
also Test if the deviceID restriction is null, if the list is NULL, which is the default, a user can sync with any device
also try disabling your Activesync policy for testing , wait few hours then test
http://technet.microsoft.com/en-us/library/aa997160(EXCHG.80).aspx
did Microsoft assisted you with all troubleshoting steps ? YES
did they delete and recreate the Activesync virtual directory YES, did it.
Also did they verify the device ID restriction on the Activesync policy ? YES, did it.
if not try recreating the activesync folder by using command on exchange console :
remove-ActiveSyncVirtualDi
New-ActiveSyncVirtualDirec
also Test if the deviceID restriction is null, if the list is NULL, which is the default, a user can sync with any device YES, did it.
also try disabling your Activesync policy for testing , wait few hours then test ....you mean simply turing it off altogether? Hmmmm....haven't tried this yet. Will turn off activesync for 2hours. Then will turn it back on again, & see how soon before it stops working. Not sure how this will help though???
did they delete and recreate the Activesync virtual directory YES, did it.
Also did they verify the device ID restriction on the Activesync policy ? YES, did it.
if not try recreating the activesync folder by using command on exchange console :
remove-ActiveSyncVirtualDi
New-ActiveSyncVirtualDirec
also Test if the deviceID restriction is null, if the list is NULL, which is the default, a user can sync with any device YES, did it.
also try disabling your Activesync policy for testing , wait few hours then test ....you mean simply turing it off altogether? Hmmmm....haven't tried this yet. Will turn off activesync for 2hours. Then will turn it back on again, & see how soon before it stops working. Not sure how this will help though???
Micrososft seems to think the issue is related to the IIS server's processes...specifically the W3WP.exe...However, I don't think so. We've run prodump procedures and ADPlus cscripts, to collect information. But none of the dump files show any of the w3wp instances halting or crashing. The active sync works fine for a few hours, then it simply Stops. Event viewer application log generated thousand of EVT1008 errors.....*sigh*....
Microsoft has no idea how to fix this issue. I have receive the following message:
"Thank you for the opportunity to work with you to resolve the issue you are experiencing with Microsoft Exchange. In our continued effort to expedite a resolution of your issue, we are going to bring in an additional Support Engineer. We are in the process of identifying the best resource to assist at this time. You will be contacted by this Support Engineer within one business day to continue working on this issue. "
"Thank you for the opportunity to work with you to resolve the issue you are experiencing with Microsoft Exchange. In our continued effort to expedite a resolution of your issue, we are going to bring in an additional Support Engineer. We are in the process of identifying the best resource to assist at this time. You will be contacted by this Support Engineer within one business day to continue working on this issue. "
my friend there is nothing in life which can not be solved :) , everything need commitment and time , but all can be solved . here is an idea :
first go to Microsoft "Exchange test connectivity website" , choose active sync option , choose you exchange version , follow instructions , and test active sync connection from outside . if you get all green then you ok . if you get all red then follow instructions provided by microsoft to troubleshoot .
here go here : https://www.testexchangeconnectivity.com/
Let us know what you found .
Good Luck
first go to Microsoft "Exchange test connectivity website" , choose active sync option , choose you exchange version , follow instructions , and test active sync connection from outside . if you get all green then you ok . if you get all red then follow instructions provided by microsoft to troubleshoot .
here go here : https://www.testexchangeconnectivity.com/
Let us know what you found .
Good Luck
Did the test connectivity run. It passed all except the last one. THe error is:
Connectivity Failed
Validating certificate trust for Windows Mobile Devices
When I click "tell me more about this issue and how to resolve it"....I am taken to this page: http://technet.microsoft.com/en-us/library/dd439394(EXCHG.80).aspx
Believe it or not, we have already covered all the possible causes based on this article.
Connectivity Failed
Validating certificate trust for Windows Mobile Devices
When I click "tell me more about this issue and how to resolve it"....I am taken to this page: http://technet.microsoft.com/en-us/library/dd439394(EXCHG.80).aspx
Believe it or not, we have already covered all the possible causes based on this article.
So far, it looks like something is wrong with the Apple iPhone and the way it is handling requests to the Exchange server. It is constantly hammering the IIS server every minute. This is causing the MSActiveSync Pool to crash until I physically restart the pool. We have totally removed Exchange from the iPhone and shut the device off. Now all WinMo devices are syncing just fine. I guess I need to contact Apple to find out why the device keeps sending out multiple reqests, hammering the server in that manner. Of course I am open to any suggestions from the experts here...
OK, it WAS indeed the iPhone. For some reason, the iphone was trying to connect via ExchangeLegacyDN which was, of course wrong. So , the constant hitting, and hitting this invalid AD entry was flooding the IIS, and causing the process to crash. We downloaded a free ADMODIFY tool and fixed all the AD entries that were incorrect. We also made some other modifications to the MSACtiveSync pool. Now all users are once again syncing data normally, even the iphone. Whew...this one was a nail-biter. Thanks to all the ideas and suggestions that were given. This ticket is now closed.
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 trialIt'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
Windows Server 2008
From novice to tech pro — start learning today.
-
Microsoft ApplicationsCertification: MCSA MCSE Microsoft Certified Solutions Associate & … 398 lessons
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.