Check the below links
http://support.microsoft.c
http://support.microsoft.c
Main Topics
Browse All TopicsI'm trying to get an iPhone 3G to sync with my Exchange 2003 SP2 server using Activesync, and I'm running into some problems. I've read a lot of other posts on this site and none of the solutions have worked. Here's where I am:
Going to https://mydomain.com/oma results in an error (both internally and on the iPhone) of "A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator." This also results in the following error in the Event Viewer:
Event Type: Error
Event Source: MSExchangeOMA
Event Category: (1000)
Event ID: 1503
Date: 8/7/2008
Time: 10:51:03 AM
User: N/A
Computer: Server
Description:
An unknown error occurred while processing the current request:
Message: The remote server returned an error: (501) Not Implemented.
Source: Microsoft.Exchange.OMA.Exc
Stack trace:
at Microsoft.Exchange.OMA.Exc
at Microsoft.Exchange.OMA.Exc
at Microsoft.Exchange.OMA.Exc
Message: Exception has been thrown by the target of an invocation.
Source: mscorlib
Stack trace:
at System.Reflection.RuntimeC
at System.Reflection.RuntimeC
at System.RuntimeType.CreateI
at System.Activator.CreateIns
at Microsoft.Exchange.OMA.Use
Message: Exception of type Microsoft.Exchange.OMA.Dat
EventMessage:
UserMessage: A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.
Source: Microsoft.Exchange.OMA.Use
Stack trace:
at Microsoft.Exchange.OMA.Use
at System.Web.SessionState.Se
at System.Web.SessionState.Se
at System.Web.SessionState.Se
at System.Web.AsyncEventExecu
at System.Web.HttpApplication
Also, whenever my phone tries to sync and check email, a different error is created in the Event Viewer:
Event Type: Error
Event Source: Server ActiveSync
Event Category: None
Event ID: 3005
Date: 8/7/2008
Time: 10:51:10 AM
User: Domain/User
Computer: Server
Description:
Unexpected Exchange mailbox Server error: Server: [diserver.DI.local] User: [user@domain.com] HTTP status code: [501]. Verify that the Exchange mailbox Server is working correctly.
Here's some other things I've tried:
- I have an SSL cert installed and it works fine with OWA. SSL is enabled (but not required) for OMA.
- I've checked that IP security is granting access to all IP's for all relevant Exchange, OMA, and Activesync sites.
- I've installed service pack 2 for exchange.
Any ideas?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Check the below links
http://support.microsoft.c
http://support.microsoft.c
Ok, I've made some progress using the first link that ach_patil posted (KB898131). I added a multiple identity for the default web site (port 80) with my server's NetBIOS name. Now when I go to http://mydomain.com/oma on my PC, I get the following message:
The device type you are using is not supported. Press Ok to continue.
Ok
Ok, and do not warn me again
User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080702 Firefox/2.0.0.16
This is a step in the right direction, I think. However, I get the same message when I go to mydomain.com/oma on the iPhone's web browser. Also, the iPhone is still not syncing with Exchange. I continue to get the error 3005 in the Event Viewer whenever my phone tries to sync.
I'm going to try the second KB article now.
I got it working guys, just follow the activesync white paper!
If you are using a single Exchange 2003 server:
Verify that Exchange 2003 Outlook® Web Access is working.
If you are using devices with Windows Mobile 2002 software or using devices with Windows Mobile 2003 software with SSL, make sure that a certificate is installed on the Exchange server unless the SSL session is terminated before the Exchange server.
If you are not using SSL, launch Internet Explorer on the desktop and verify that http://servername/Microsof
If you are using SSL, launch Internet Explorer on the desktop and verify that https://servername/Microso
Verify that massync.dll is listed as an Application map on the Microsoft-Server-ActiveSyn
Verify that Exchange ActiveSync is enabled globally using Exchange System Manager. This is the default setting.
Verify that the user is enabled for Exchange ActiveSync using AD Users and Computers. This is the default setting.
On the Exchange server, verify that the authentication settings on the Exchange virtual directory include Integrated Windows Authentication.
Exchange ActiveSync uses Kerberos authentication when communicating with the Exchange server and therefore requires that Integrated Windows authentication be checked on the Exchange virtual directory.
If you are using a single Exchange 2003 server and have either configured your Exchange virtual directory to Require SSL or have turned on Forms Based Authentication (FBA), then follow the procedure below to create an alternate Exchange virtual directory for ActiveSync to use.
The new virtual directory needs to be created through Internet Services Manager for Exchange ActiveSync to work.
If you are using Microsoft Windows Server" 2003 or later, follow these instructions:
1. Start Internet Information Services (IIS) Manager
2. Locate the \exchange virtual directory (default location is Web Sites\Default Web Site\Exchange)
3. Right click on the Exchange virtual directory, choose All Tasks, Save Configuration to a File.
4. Type a name in the File name: text box (for example, ExchangeVDir).
5. Click OK.
6. Right click the root of this Web site (Default Web Site), choose New, Virtual Directory (from file).
7. On the Import Configuration dialog box, select the Browse button and locate the file from step #4, then click Open.
8. Next, select the Read File button.
9. In the Select a configuration to import text box, select Exchange and press OK.
10. A dialog box will appear stating the virtual directory already exists. In the Alias text box, type a name for the new virtual directory that you want the Exchange Server ActiveSync and Outlook Mobile Access processes to use. For example, type Exchange-OMA.
11. Click OK.
12. Right click on the new virtual directory and choose Properties, in this example, Exchange-OMA.
13. Select the Directory Security tab.
14. Click the Edit button in the Authentication and access control section.
15. Verify only the following authentication methods are enabled:
" Integrated Windows authentication
" Basic authentication
16. Click OK.
17. Click Edit under IP address and domain name restrictions.
18. Click Denied access, and then click Add.
19. Click Single computer (if this option is not already selected), type the IP address of the server that you are configuring, and then click OK.
20. Click the Edit button in the secure communications section.
21. Verify require secure channel (SSL) is not enabled and click OK.
22. Click OK, and then quit IIS Manager.
23. Click Start, click Run, type regedit in the Open box, and then click OK.
24. Locate the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\
25. Right-click Parameters, point to New, and then click String Value.
26. In the New Value #1 box, type ExchangeVDir, and then press ENTER.
27. Right-click ExchangeVDir, and then click Modify.
28. In the Value data box, type a forward slash (/) followed by the name of the new virtual directory that you created in step 10. For example, type /Exchange-OMA.
29. Click OK, and then quit Registry Editor.
30. Restart the IIS Admin Service. To do this:
" Click Start, click Run, type services.msc in the Open box, and then click OK.
" In the Name list, right-click IIS Admin, and then click Restart.
Which part of this solution solved your problem?
I checked everything on my server and it all seems to jive with the information above. I've seen the instructions for creating a new virtual server, but in the KB articl with these instructions, at the end it says that the new virtual server has to be named exchange-oma if you are using SBS2003 (which I am), and there is already a virtual server named exchange-oma, and an entry in the registry equivalent to the one the instructions are telling me to create.
I noticed that Apple's configuration instructions include this tidbit:
"On the ISA Server, create a Web listener as well as an Exchange Web client access
publishing rule according to Microsoft documentation. This is a necessary step in enabling Exchange ActiveSync."
I have no idea what this means, but I don't even have an ISA Server installed... Is that a problem, and if so, how do I fix it?
Yes, I've rebooted IIS Admin after every change I make. I've done it a dozen times today alone. I just wish there was somewhere I could look up and see precisely what error 3005 means. I've already followed Microsoft's directions for resolving error 3005 and it didn't work. Although, Microsoft also lists an alternate solution for this error, in case the other solution didn't work. It might be the only solution that ends up working:
"If these user actions do not let the user synchronize calendar items, move the mailbox of the user specified in the event description to a different Exchange Server computer."
If only I had another Exchange Server computer at my disposal.
But seriously though, can anyone think of anything else I can check that might be triggering this error?
If I try to send an email from my iPhone, it just gives a generic error like "An error occured while delivering this message." However, it just silently fails when trying to sync.
There were no errors displayed when I was configuring the iPhone. I don't put the domain in front of my username though. I've tried it before, but everytime I do that it gives me an error saying that my username or password is incorrect and asks for the correct password. I took that as a sign that it didn't like the domain in front of my username.
I noticed that you used a backslash between your domain and username, so I just tried that and it doesn't give me an incorrect username/password error, but it still fails like before (and still generates a 3005 error in the event viewer).
Ya, you need to have the yourdomain\username exactly the way i typed it. it even shows you to type it that way on the iphone itself.
Delete your exchange email account and try again. Do not just edit your settings on the iphone. After each step pay close attention to the message at the top of the screen every time you hit "next".
The exact same thing was happening to me to where you just get an inbox with nothing in it until i followed the 30 steps I sent you.
I think you are very close to solving it.
Mine is working with a self-signed certificate, make sure your self-signed is current. I am getting mine using the microsoft cert server.
I tried recreating my account on the iPhone instead of just modifying it, and I used the domain\user format for my username. The messages at the top of the screen said that the exchange account was verified, no errors, everything is great. But, still no sync when I go to the mail program. And, still a 3005 error in the event viewer.
I'm wondering... the iPhone is using wifi right now, and the wireless router it's connecting to is on the same local LAN as the mail server... could that be a problem? I'm going to try turning off wifi on the iPhone and see if that makes a difference.
to recap?
is http:\\localhost\oma working
is http:\\mail.company.com\om
stupid question perhaps but..i assume you phone can browse the internet?
is outlook web access working - i have read rumours that the iphone uses web access - but i doubt this - but you may as well confirm this functionality.
All of the following sites work, both from inside and outside the network:
http://mail.domain.com/oma
https://mail.domain.com/om
http://mail.domain.com/exc
https://mail.domain.com/ex
The phone definitely can browse the internet. I've tried configuring the phone's exchange account while connected to wifi and while connected to 3G.
Everything results in the same error: 3005.
I have resolved this issue. For future reference, here are the instructions I followed (after following all of the KB articles noted above):
http://www.ureader.com/mes
Just in case anyone else finds the same problem, I followed the directions above and in doing so found the IP address that was already configured in (see step 19) was wrong - once corrected everything worked immediately. My mistake, as I built the server with a different IP then changed it to it's production IP - leaving the incorrect IP address in certain IIS default settings.
Andy
I added an iPhone 3GS to our SBS 2003 network with Exchange Server 2003 SP2 and struggled at first to get the iPhone to work. I had other Windows phones working fine. For me, the issue was the configuration on the phone - in particular the "Domain" entry. When I entered the Domain, not luck. When I left it blank, everything works. Hope this helps.
iPhone 3Gs settings:
Email: username@domainname.com
Ser
Domain: (No entry)
Username: (network user name)
Password: (Current network password)
Description: Whatever
Use SSL: On
Good luck.
Business Accounts
Answer for Membership
by: wolfcamelPosted on 2008-08-07 at 08:17:37ID: 22181795
ok..
until you can get http:\\localhost\oma to work on the server there isnt much point playing with the phone.
forget the https it is typically not turned on for oma
I had this recently at one client and SP2 solved it.
If this is SBS I would rerun the internet connection wizard as this will reset most of the IIS settings.