mrubinsk Wed, 23 Jul 2014 16:09:22 +0000
Modified page: http://wiki.horde.org/ActiveSync
New Revision: 266
Change log: Make this line more obvious.
@@ -276,9 +276,9 @@
If all else fails and you can't figure out the issue, we will be
happy to try to help you work it out, but you should be able to
check/provide us with the following:
* Be sure to check the notes in the chart above for your specific
device. This might be a known issue, or a workaround may be known.
* Check the web server error logs and see if there are any PHP
errors being logged.
-* Configure Horde to send !ActiveSync log messages to a separate
logfile. This is configured on the !ActiveSync tab of Horde's
configuration screen.
+* **Configure Horde to send !ActiveSync log messages to a separate
logfile. This is configured on the !ActiveSync tab of Horde's
configuration screen.**
* If you are able to, it would also be useful to run a wireshark
session to capture the network communication.
* In some cases, it might be useful for us to see the affected
device's state records in the database.
++++ Using tshark (command line wireshark) to obtain a network capture
--
commits mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: [email protected]
