85010001 Error Trying to Sync with WM5.0 Device/ActiveSync4.1/ISA2004

Well, this is a new one.  Pull out ERR and look up 85010001 !  The configuration was SBS2003 Premium with ISA2004 installed and a Treo 700 with ActiveSync 4.1 on 2 separate Windows XP Pro laptops.  It was an "upgrade" from ISA2000 to ISA2004.  The Treo 700 sync'ed perfectly over the air.  Only in the cradle did it have a problem.


Here were the symptoms:


1.  Trying to sync with the Firewall Client enabled, it hangs at connecting or synchronizing...most of the time it popped up with an error "85010001 you do not have permissions to sync with your current settings...".

2.  Disable the Firewall Client and it sync'ed.

3.  We noticed some flaky behavior when we swapped the device between using SSL and not using SSL.

4.  A PocketPC2003 device with ActiveSync 3.8 worked perfectly on another computer.

4.  Trying the same device on another computer (laptop) gave almost the exact symptoms.

5.  One laptop had the ISA2000 Firewall Client, the other had the ISA2004 Firewall Client.

6.  We noticed a bit different behavior between the laptop with the ISA2000 client and the one with the ISA2004 client. 


Ok, so what's up with that!!  What's busted?  Is it the laptop(s)?  One of the laptops had a wireless connection, a wired connection and BlueTooth!  Was it networking?  Was it ActiveSync?  Was it the server?  Was it the certificate?  Well, I started working on the assumption that the server was fine due to another device sync'ing fine through ActiveSync (ActiveSync 3.8) and both devices sync'ed perfectly "over the air".  I took a quick look at ISA's logging features and didn't notice anything too out of the ordinary.  I did not spend too much time in Monitoring, just looking for "denied" at this point.  The device appeared to have the correct certificate installed. 


I did some research and found out that ActiveSync 4.1 makes "special" networking calls that the ISA2000/ISA2004 Firewall Client(s) don't respond well to.


We ended up setting up exceptions in the Firewall Client settings on the SBS box.  Here is what we set:


1.  WCESCOMM - Disabled - 0

2.  WCESMGR - Disabled - 0

3.  REPIMGR - Disabled - 0


These can be defined in ISA2004->Servername->Configuration->General->Define Firewall Client Settings->Application Settings->New.  After defining the above, we rebooted the clients to get the new Firewall Client settings pushed to the client.  We still have an ongoing issue with the laptop's going "offline" (they have offline folders configured) whenever the device sync's while in the cradle.


Stay tuned for the solution to that one!


Comments (4)

  1. Anonymous says:

    Information on Devices:  http://www.xda-developers.com/

    And Vlad’s wiki on Mobility and Exchange

  2. Bill Kitchen says:

    I tried this change on my SBS2003 SP1 Premium setup and it still doesn’t synch inside the firewall – works fine outside over GPRS – but it would be nice to be able to synch to Exchange inside as well – Maybe its related to the offline folders issue? Has anyone been able to get this config working? I posted to the SBS2K Yahoo group last week and drew a nil resonse.
    Thanks for all the great Podcasts!



  3. Dave B says:

    Hi and thanks for the information but I have a question as to your settings.  I saw a similar post somewhere else regarding ISA traffic and WM5 and rather than your use of

    1.  WCESCOMM – Disabled – 0

    2.  WCESMGR – Disabled – 0

    3.  REPIMGR – Disabled – 0

    He suggested a value of ‘1’ rather than ‘0’.

    Help in ISA2000 shows the values as:

    Entry Description

    Disable Possible values: 0 or 1. When the value is set to 1, the Firewall service is disabled for the specific client application.

    Wouldn’t you want the firewall disabled for that traffic?  It seems that ‘0’ would just turn the firewall on as default.  Am I missing the purpose of setting these apps up in ISA?

    Thanks for any guidance you can give me on this… I’ve been banging away at it for a few days and keep ending up to what I think is close but haven’t had one successful sync yet.




Skip to main content