Known Issues for Symbian S60 3 ActiveSync Devices
Posted by Donna DeEulio on 22 September 2010 07:26 PM
NotifyLink ActiveSync Solution for Symbian S60 3rd edition devices


See also the Device Comparison Chart to learn which NotifyLink IT policies are supported and which are not supported when using the NotifyLink Symbian ActiveSync Solution.


These issues involve Nokia S60 3rd edition device users with Mail for Exchange registered against NotifyLink Enterprise Server version 4.7.0


1.)   The Device Type field displays device ID instead of the device model on the User Statistics page of the NotifyLink Administrative Web for Nokia S60 3rd edition device/ Mail for Exchange users.  This issue is due to Mail for Exchange incorrectly sending the same value for the DeviceType field as it does for the DeviceId field.  B147

2.)   This issue involves emails where the ‘Reply To’ address is different than the ‘From’ address.  A reply sent form the device, it is incorrectly sent to the “from” address.  This is expected behavior for Mail for Exchange on S60 devices.  B198

3.)   If a reload is performed for calendar events on the device,  then the device is synchronized, the calendar items will be duplicated.  This is a known issue with S60 devices using Mail for Exchange.   B205

4.)   Users will not see the deleted items folder displayed in the folders list on the device.  This is a known issue with Symbian.  B215

5.)   The phone number field is blank on the User Statistics page of the NotifyLink Administrative Web for Nokia S60 3rd edition device/ Mail for Exchange users.   This is an issue with Symbian.  B216

6.)   The device will not synchronize using the TMobile Internet. Unless the device is set to a wifi connection for access point the device will not sync.  The ability to sync with a T-Mobile sim card is possible, but only when the T-Zones access point is chosen.  However, this connection is very slow and may take more than 45 seconds to sync.  B237

7.)   Accepting a meeting invitation a second time after deleting the event from the device calendar does not re-add the event to the calendar.  B898

8.)   This issue involves emails with multiple attachments.  After each attachment is downloaded the screen view returns to the message list.  B1196

9.)   After 5 attempts to unlock the device, the following message appears, “Lock code entered incorrectly 5 times.  Code will unblock in 5 minutes.  Attempts made to unlock the device during this timeout start the 5 minutes timeout over again and do not count toward the number of Failed Unlock Attempts set on the NotifyLink server.  Therefore, if you keep entering attempts during the timeout, the device may never wipe.  If the Wipe on Failed Unlock Attempts is set to something less than five on the NotifyLink Server, this issue is not seen. B1228

10.) Nokia S60 3rd edition device with Mail for Exchange does not support creating Meeting Invitations on the device.  B1283

11.) Older E-Series devices, such as the Nokia 6120c, do not support security features that network administrators may enforce.  This can prevent Mail for Exchange from synchronizing data to the device.  If you think you are experiencing this problem, look in File Manager > MailForExchange > admin_log.txt for the text, "This device is unable to implement all requested password policies.  Currently the only solution is to reduce the server security requirements."  B1346

12.) The Mail for Exchange Calendar application has an option for creating a Meeting Request on the device, however, it is sent to the server as a .vcs attachment and does not get delivered.  This is a limitation of the device.  B1283

13.) Some devices may experience issues if more than 600 emails synchronize to the phone, such as not being able to create, reply to, or forward email.   A memory full error is displayed and the number of emails synchronized to the device needs to be reduced.

14.) When a large number of emails are deleted from the device at the same time, not all emails are deleted on the server side.

15.) If multiple tasks are created on the device and synchronized at the same time, the tasks will all have the same due date.