Support Code 0x85010004 - EAS & Windows Mobile 2005

We're running Exchange 2003/SP1 on a single server that also hosts OWA, OMA. OWA & OMA work fine (OMA works in both SSL and non-SSL mode). EAS has never worked, and I recently went through the steps of re-initializing all the virtual directories hoping that would fix it. It didn't. Any user that attempts to sync receives the Support Code 0x85010004.

Any help is appreciated, this is driving me nuts.

Jim
LVL 5
netbonesAsked:
Who is Participating?
 
RomModCommented:
Closed, 500 points refunded.

Best regards,
RomMod
Experts Exchange
Community Support Moderator
0
 
LeeDerbyshireCommented:
If you have FBA enabled or SSL required on your OWA installation, try this:

http://support.microsoft.com/default.aspx?scid=kb;en-us;817379

If not, then make sure you have Integrated Auth enabled your Exchange VDir.
0
 
netbonesAuthor Commented:
Hi,

I had already done method #2 from the KB article and it still occurs, and we never saw any of the errors in the event log that it listed.

I also turned off Forms-Based authentication and it still doesn't work.

Thanks,

Jim
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.

 
ari24Commented:
Are you using urlscan on iis?
That initially caused me the same problem you are having.
0
 
netbonesAuthor Commented:
Darn, no we aren't. I checked in Add/Remove Programs and under system32/inetsrv to make sure, and searched for urlscan.dll.

Could something else in IIS be causing this? I'm pretty sure the functionality of URLScan was included in IIS6.
0
 
ari24Commented:
After i installed exchange 2003 sp2, it was inserting a ".com" into the url and getting intercepted by urlscan as a disallowed file type. any other iis security program may finction in the same way.

Check if you have any logs in and if they are useful C:\WINDOWS\system32\inetsrv\urlscan

Review/post your iis log when one device tries to sync.
0
 
netbonesAuthor Commented:
We're not on SP2 yet, and we don't have urlscan installed, so there are no logfiles there.

Log entry from the Exchange log:

2006-05-24 20:30:27 10.10.10.30 OPTIONS /Microsoft-Server-ActiveSync User=<userid>DeviceId=1565FD93E7FAC6A32685F14005AEF1B4&DeviceType=PocketPC 443 <domain>\<userid> 66.209.31.31 MSFT-PPC/4.0 200 0 0
2006-05-24 20:30:28 10.10.10.30 POST /Microsoft-Server-ActiveSync User=<userid>&DeviceId=1565FD93E7FAC6A32685F14005AEF1B4&DeviceType=PocketPC&Cmd=GetHierarchy 443 <domain>\<userid> 66.209.31.31 MSFT-PPC/4.0 403 0 0


Jim
0
 
netbonesAuthor Commented:
We don't have Exchange SP2 installed yet, therefore we aren't using the Direct Push technology included in it. However, is this setting somewhere else? If so where?
0
 
VahikCommented:
sorry please disregard...my mistake....
0
 
SembeeCommented:
I would strongly advise that you update to service pack 2 for Exchange. Any particular reason that you haven't?
The EAS system was totally rewritten in SP2 and you may find the problem will be fixed in that update.

Simon.
0
 
netbonesAuthor Commented:
Only reason I haven't is that I can't get it to work in SP1. I don't agree with the mantra of upgrading to fix things that should be working!  If I can get this working, I'll gladly upgrade to SP2, but until then I find it ridiculous to do so with the *hope* it fixes the problem.
0
 
SembeeCommented:
You need to review your stance on service packs.

While Microsoft do provide new and improved features in a service pack, as far as I am concerned they are a bonus. They shouldn't be seen as the main reason to upgrade.

A service pack contains fixes, patches and updates for their products.
What is the point in trying to get it to work on a service pack 1 system? You are unlikely to need to do so again.
This service pack has been out for well over seven months, and is generally considered to be rock solid. Apart from a small number of vendors who are dragging their heals on supporting this service pack, there are no reasons not to upgrade.

You may find it works, you may find it doesn't. However because this particular feature is changed so heavily, the number of people willing to assist you when you are using an old revision of the application is very small and will only continue to drop. My knowledge of SP1 and older quirks is already starting to dim, as I recommend to my clients to upgrade to the latest patches as soon as possible.

Simon.
0
 
netbonesAuthor Commented:
Sembee, this isn't a question about my philosophy on service packs. We can swap stories on them in another forum, this is a question about getting something fixed.

Now, the good news - IT'S FIXED.

It turns out there is a very small change I had to make to get this working. On our mail server, we have 5 IP addresses assigned to the primary interface. I know Microsoft does not 'support' this configuration, however it was needed on this server for various unrelated reasons.

The default web site was assigned to a specific address. By changing it to "All Unassigned", it fixed the problem!! The test is to open a web browser on the server, and try to connect to "http://localhost/microsoft-server-activesync". If configured as my server was, this will fail. By changing the setting to "all unassigned", and connecting to this again, it should give you a different error (Not Implemented 501 error).

After the change was made, restarting IIS and testing OMA, all is good.

Woo Hoo!
0
 
SembeeCommented:
I haven't heard of Microsoft not supporting multiple IP addresses. I have a client with 30 IP addresses on their Exchange server, and each site is specifically set. I have four on my home Exchange server for various reasons and Exchange works fine.

In both cases, the servers are fully patched.
 
The reason that http://localhost/ doesn't work is because that has a specific IP address of 127.0.0.1 which you wouldn't have mapped to any drive. There may be a requirement with the older revision of EAS for http://localhost/exchange to be available. I do know that the latest version of EAS makes calls on to the /exchange virtual directory on port 80 to retrieve the information, so perhaps in the older version it made the call on http://localhost/exchange instead of using virtual information.

As for the argument on the stance for getting something fixed versus service packs - they are often the same.
Your problem may well have not come up at all if you had maintained current service pack status.
We have been dealing with EAS queries on this forum for many months and this is the first time this type of query and resolution has been required - I therefore suspect that both are connected to the fact that you are on the older service pack. Remember that Windows Mobile 5.0 with MSFP and Exchange 2003 SP2 were designed to work together. They were both released at around the same time. It just took a while for the devices to get in to the hands of users.

Simon.
0
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.

All Courses

From novice to tech pro — start learning today.