[horde] Activesync | WP7 cannot sync

Sun Jan 29 16:20:51 UTC 2012

Quoting Martin Hochreiter <linuxbox at wavenet.at>:

> Hi!
>
> I have a massive problem with one user and its wp 7(.5) phone.
>
> If I configure active sync, as I did on the iphone, wm 6.5 and android
> it ends in that error message on the phone:
>
>
> xxx.xxxx.xxx requires that certain security policies be enforced  
> before you can sync your information. Contact a support person or  
> your service provider. Last tried x minutes ago. Error code:
> The error code is 0x85010013.
>
> I tried to force provision - to turn of provision (but still if  
> provision is turned off completely

You should only get that message if you have forced provisioning and  
either the phone doesn't support the configured security requirements  
(unlikely since this is a Windows phone), or the user didn't  
enable/refused to enable the requested features. Another possibility  
is that maybe these newer phones don't fully support the older EAS 2.5  
style of provisioning rules. The newer protocol versions use a  
different format when pushing out the rules to the device. I'll have  
to look into that when I get back home. Horde currently only supports  
up to version EAS 2.5.

> there is this line "PROVISION request received for user user_user"  
> in the log)

Was this log generated while provisioning support was completely  
disabled? It doesn't look like it was; If you look at the entry where  
it is "checking policykey for...", the user should not be immediately  
logged off after that check if provisioning is disabled. Additionally,  
the device should NEVER send a PROVISION request unless told to do so  
by the server and this should never happen with provisioning support  
disabled.

Otherwise, if this was done during "Allow"  provisioning, this issue  
sounds similar to an issue early android devices had, in that they  
would incorrectly send a POLICYKEY of zero, even though the device did  
not support PROVISION. We work around this in code by sniffing  
versions and device strings. Though I would really be surprised that  
this is the issue, seeing how it's a Windows phone and, presumably,  
designed to work well with other Microsoft technology.

Can you provide a wireshark trace or tcpdump of the conversation? I  
don't have access to a Windows phone and it's the only way I can see  
exactly what is being sent.

> Is there a solution or workaround for that?
>
> -------------- log -------------------------
> 2012-01-29T14:33:23+01:00 INFO: Horde_ActiveSync_Driver_Horde::logon  
> attempt for: user_user
> 2012-01-29T14:33:24+01:00 DEBUG: [] OPTIONS request received for  
> user user_user
> 2012-01-29T14:33:26+01:00 INFO: Horde_ActiveSync_Driver_Horde::logon  
> attempt for: user_user
> 2012-01-29T14:33:26+01:00 DEBUG: [8BCFCF4D1B57DEA7E3C2FA17703BC03C]  
> FOLDERSYNC request received for user user_user
> 2012-01-29T14:33:26+01:00 DEBUG: [8BCFCF4D1B57DEA7E3C2FA17703BC03C]  
> Device entry does not exist, creating it.
> 2012-01-29T14:33:26+01:00 DEBUG: [8BCFCF4D1B57DEA7E3C2FA17703BC03C]  
> Device entry does not exist for user user_user, creating it.
> 2012-01-29T14:33:26+01:00 INFO: Request being handled for device:  
> 8BCFCF4D1B57DEA7E3C2FA17703BC03C Supporting protocol version: 2.5
> 2012-01-29T14:33:26+01:00 INFO: [Horde_ActiveSync::handleFolderSync]  
> Beginning FOLDERSYNC
> 2012-01-29T14:33:26+01:00 DEBUG: [8BCFCF4D1B57DEA7E3C2FA17703BC03C]  
> Checking policykey for device  Key: 0 User: user_user
> 2012-01-29T14:33:26+01:00 DEBUG: [8BCFCF4D1B57DEA7E3C2FA17703BC03C]  
> loadDeviceInfo: user_user
> 2012-01-29T14:33:26+01:00 DEBUG: [8BCFCF4D1B57DEA7E3C2FA17703BC03C]  
> Stored key: 0
> 2012-01-29T14:33:26+01:00 INFO: User user_user logged off
> 2012-01-29T14:33:27+01:00 INFO: Horde_ActiveSync_Driver_Horde::logon  
> attempt for: user_user
> 2012-01-29T14:33:27+01:00 DEBUG: [8BCFCF4D1B57DEA7E3C2FA17703BC03C]  
> PROVISION request received for user user_user
> 2012-01-29T14:33:27+01:00 DEBUG: [8BCFCF4D1B57DEA7E3C2FA17703BC03C]  
> loadDeviceInfo: user_user
> 2012-01-29T14:33:27+01:00 DEBUG: Resetting PING state
> 2012-01-29T14:33:27+01:00 INFO: Request being handled for device:  
> 8BCFCF4D1B57DEA7E3C2FA17703BC03C Supporting protocol version: 2.5
> 2012-01-29T14:33:27+01:00 DEBUG: I <Provision:Provision>
> 2012-01-29T14:33:27+01:00 DEBUG: I <Provision:Policies>
> 2012-01-29T14:33:27+01:00 DEBUG: I <Provision:Policy>
> 2012-01-29T14:33:27+01:00 DEBUG: I <Provision:PolicyType>
> 2012-01-29T14:33:27+01:00 DEBUG: I      MS-WAP-Provisioning-XML
> 2012-01-29T14:33:27+01:00 DEBUG: I </Provision:PolicyType>
> 2012-01-29T14:33:27+01:00 DEBUG: I </Provision:Policy>
> 2012-01-29T14:33:27+01:00 DEBUG: I </Provision:Policies>
> 2012-01-29T14:33:27+01:00 DEBUG: I </Provision:Provision>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Provision>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Status>
> 2012-01-29T14:33:27+01:00 DEBUG: O    1
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Status/>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Policies>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Policy>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:PolicyType>
> 2012-01-29T14:33:27+01:00 DEBUG: O      MS-WAP-Provisioning-XML
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:PolicyType/>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Status>
> 2012-01-29T14:33:27+01:00 DEBUG: O      1
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Status/>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:PolicyKey>
> 2012-01-29T14:33:27+01:00 DEBUG: O      5887728924
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:PolicyKey/>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Data>
> 2012-01-29T14:33:27+01:00 DEBUG: O  
> <wap-provisioningdoc><characteristic type="SecurityPolicy"><parm  
> name="4131" value="0"/><parm name="4133"  
> value="1"/></characteristic><characteristic  
> type="Registry"><characteristic  
> type="HKLM\Comm\Security\Policy\LASSD\AE\{50C13377-C66D-400C-889E-C316FC4AB374}"><parm name="AEFrequencyType" value="1"/></characteristic><characteristic type="HKLM\Comm\Security\Policy\LASSD"><parm name="DeviceWipeThreshold" value="10"/></characteristic><characteristic type="HKLM\Comm\Security\Policy\LASSD"><parm name="CodewordFrequency" value="5"/></characteristic><characteristic type="HKLM\Comm\Security\Policy\LASSD\LAP\lap_pw"><parm name="MinimumPasswordLength" value="5"/></characteristic><characteristic type="HKLM\Comm\Security\Policy\LASSD\LAP\lap_pw"><parm name="PasswordComplexity"  
> value="1"/></characteristic></characteristic></wap-provisioningdoc>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Data/>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Policy/>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Policies/>
> 2012-01-29T14:33:27+01:00 DEBUG: O <Provision:Provision/>
> 2012-01-29T14:33:27+01:00 INFO: User user_user logged off
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: horde-unsubscribe at lists.horde.org

-- 
mike

The Horde Project (www.horde.org)
mrubinsk at horde.org