Use the form below to enter your search criteria. By default, all content is searched except for document comments. If you wish to search comments as well as everything else, click "Also Search Comments" below.
[493]
Comments: 0,
Last Modified: Jul 18, 2007 2:35 PM
- Find Similar
No adjustments are made to calendar event times/dates for users traveling outside the MDaemon server time zone. The server's time zone determines the time zone of the end user. For users traveling outside the server time zone that access the MDaemon server remotely, calendar event times/dates are not adjusted. This limitation prevents NotifyLink from making these adjustments for mobile
[706]
Comments: 0,
Last Modified: Nov 29, 2007 4:55 PM
- Find Similar
Upgrade to NLES 4.5.0 for MDaemon corrects cause of problem. Procedure outlined for clearing unwanted ... ) 4.5.0 for MDaemon, an issue existed for contacts and tasks that had been edited or deleted. ... 4.5.0 for MDaemon corrects the cause of the problem, however, duplicates and undeleted items may ... MDaemon 4.3.0 to NLES 4.5.0 2. Check each user's Tasks folder on the server for any duplicates
[1206]
Comments: 0,
Last Modified: Jul 30, 2009 11:02 AM
- Find Similar
If a recurring event is created on an iPhone/iPod touch it appears correctly on the device, but ends one day early on the MDaemon server. This issue is resolved with iPhone OS 3.0. An upgrade to this version will remedy the problem.
[121]
Comments: 0,
Last Modified: Oct 30, 2006 10:49 AM
- Find Similar
Users must log into MDaemon World Client web interface at least once before PIM will process. PIM failing for a new user added to the NotifyLink server for MDaemon. Please note that before the NotifyLink PIM application can process a user, the user must have logged into the MDaemon World Client web ... .net/download/mdaemon/NLES_MDaemon_release.doc
[176]
Comments: 0,
Last Modified: Apr 22, 2008 4:03 PM
- Find Similar
Port Requirements for NotifyLink Enterprise Server - MDaemon Installation Port Requirements for NotifyLink Installation can be found in the NotifyLink for MDaemon Pre-Installation Guide under Pre-Installation Tasks #8, Port Requirements Port numbers used for connections with NotifyLink Enterprise Server (NLES) components are well-known default TCP port numbers, but are subject
[303]
Comments: 0,
Last Modified: Feb 16, 2007 1:00 PM
- Find Similar
in the calendar event being duplicated. This issue has been reported for MDaemon v9.5.4, but may apply ... processes a change from the device for the same event, a duplicate may be created on the MDaemon server. The duplicate will then be synchronized to the device. This is due to a combination of a bug in the MDaemon SyncML server and how the Outlook connector edits an item. MDaemon is aware of the issue
[703]
Comments: 0,
Last Modified: Nov 28, 2007 3:24 PM
- Find Similar
Contacts created in Outlook with just a Display Name do not sync with a First Name to the device. Contacts created in Outlook with a Display Name, but no First or Last Name, synchronize to the device without a First Name. The Display Name will not populate the First Name field, as MDaemon does not send a Display Name with its contacts from the server.
[917]
Comments: 0,
Last Modified: Jul 24, 2009 10:27 AM
- Find Similar
Switching a user's designated PIM server via the NotifyLink web, may cause PIM items to stop synchronizing to the iPhone/iPod touch. This issue is the result of a user's designated PIM server being changed via the NotifyLink Web. If the designated PIM server is switched from MDaemon or FirstClass to another server and then back again to the same MDaemon or FirstClass
[782]
Comments: 0,
Last Modified: Mar 7, 2008 3:53 PM
- Find Similar
and the user can log into the world client successfully. Solution: Get the following Mdaemon syncml log from the Mdaemon server: Syncml file from Mdaemon, located at C:\MDaemon\Logs. There is more ... ] Login failed - SyncML is not enabled for: user@domain.com Then the customer will need to enable MDaemon
[1080]
Comments: 0,
Last Modified: Mar 5, 2009 5:37 PM
- Find Similar
Information: The calendar sync range (IT Policies -> Calendar Sync Settings) is one day longer than specified in MDaemon. As such, events on that extra day will be synchronized to the device even though it seems that they are out of range.
[1103]
Comments: 0,
Last Modified: Mar 6, 2009 2:54 PM
- Find Similar
from the event itself or in Outlook, this issue does not occur. MDaemon and FirstClass Because MDaemon and FirstClass don't send invitations to the device, the Delete Invitations From Device
A Leading Provider of Enterprise Mobility Solutions
Contact Support