Knowledgebase
(606)NotifyLink Enterprise Server
(138)NotifyLink Device Apps
(348)NotifyLink ActiveSync Solution
(8)NotifyLink Web Server
(19)NotifyLink Database Component
(1)NotifyLink Multi-Tenant Edition
(4)NotifyLink On Demand
(4)Sales
(2)NotifySCM
(2)NotifyLink Patch Installer
(47)NotifyMDM Server
(110)NotifyMDM Device
Knowledgebase : NotifyLink Enterprise Server > GroupWise
This issue applies when using a version of GroupWise prior to 7.0. GroupWise does
not return the IMAP LIST response correctly when a folder name contains
a double quote (") character. If a folder name contains the double
quote character it will n...
When using GroupWise Client v6.5.3, v6.5.4 or v6.5.6 on the NotifyLink
messaging server, an event added to the GroupWise calendar results in
the event addition being sent to the device, followed by an update for
the event sent to the device. This erra...
GroupWise:Random delete/adds of contacts occur after an upgrade from NotifyLink Enterprise Server 4.5.2 to 4.6.0 on a GroupWise Server. The delete/adds are shown in the nlpim.log, but may be undetectable by the end user unless PIM Change Summary is enab...
GroupWise:In some situations, recurring meeting invitations synchronize incorrectly to iPhone/iPod touch devices. 1. If a recurring meeting invitation is created on an Oracle or GroupWise server with some of the instances occurring on past dates, invit...
This issue applies to NotifyLink installations that use GroupWise
Client v6.5.4 or earlier on the NotifyLink Messaging server.
When a meeting invitation is accepted from the NotifyLink user's
device, the organizer of the meeting may receive two mail
not...
GroupWise:All Day Events are handled different depending on your NotifyLink Enterprise Server version and the version of GroupWise Client installed on the NotifyLink Messaging server. When using NLES v4.5, i. If GroupWise Client v7.0 is installe...
GroupWise:
When a meeting request is created on the device for an all day event, the resulting event on the server spans from midnight to midnight. The server then sends an update to the device which causes the start/end time to be changed there as well...
This issue applies to messages that are sent internally (between users
on the same GroupWise server). If the message does not contain a body,
but does contain an html or text file as the first attachment, the
attachment text is sent as the body of the ...
When interfacing to a GroupWise v6.5.1 GWIA or POA for email, I. Attachment names are incorrect on messages sent internally. .Txt attachments have the correct name, but attachments other than the .txt file type will have the name EmailvCard.txt....
GroupWise: When
an Auto Dated appointment is created on the server, an individual
appointment item will be sent to the device for each occurrence of the
pattern. This could result in a large number of messages being sent to
your device at one time. ...
This issue occurs when contact synchronization is enabled and the NotifyLink user sends an email using the GroupWise Client. The next time NotifyLink processes the user's account, NotifyLink may detect a change for one or more of the contacts that were li...
GroupWise: This issue applies to contacts that are not in the user's Default
Address Book. The default address book is defined on the user's Contact
Sync Settings > Choose Address Books page in the NotifyLink web. If
a contact that is not part of t...
Contacts created in the GroupWise 8 client with notes added under the Notes tab, synchronize to the device without the notes. Instead, the notes are created as Reminder Notes and appear on the device as all day events. Work Around: Users may wish to ...
GroupWise: This article identifies situations that can result in contacts being duplicated on the server. I.
This situation involves existing contacts that reside in an Address
Book (category) on the server that has not been selected for processing
b...
If a contact is created in the GroupWise client with multiple email
addresses, only one email address synchronizes to the device.
There are limitations for the total number of email, contact,
calendar, and task items in GroupWise that should be followed when
using NotifyLink. Exceeding these limitations can cause issues when
processing users on the NotifyLink system. For GroupWise v...
If you are unsure of what versions of the GroupWise back end you are
running you can run the following and send us the results.
Verifying the versions of the GroupWise Agents running on NetWare.
1. From the Remote Console or at the server console type ...
On iPhone OS based devices, when viewing the meeting invitation in
the calendar or the mail application, the sender may display as
"unknown." This typically happens when using GroupWise or Meeting
Maker as the mail/pim server.
In addition, if a dev...
This issue applies to customers that are running various versions of GroupWise. Processing of some messages may results in error code 10820 and the message will not be sent to the user's device. The error will be seen in the GleanerController.log file, fo...
When GroupWise 6.5.6 Client is used with the GO!NotifyLink Messaging
Component and a user operating on a GroupWise 8.0.x account initiates
a meeting invitation from their device, PIM processing on the 6.5.6
server lags while processing of the item takes p...
Problem: After an upgrade from GroupWise 6.5.x to 7.0.x, nlpim.exe
is spiking the CPU higher than before.
Solution: Because of the changes in the limitations of the GroupWise
API in 7.0, NotifyLink may now be trying to process many more items
than e...
It is a best practice to make the IMAP connection to the POA rather
than the GWIA. This is to ensure system stability and performance
especially for companies that have more that one POA so that the IMAP
traffic will not have to be routed through the GWIA...
GroupWise client displays up to 100 characters in the subject field of a calendar event. If
the subject is longer than 100 characters and is edited from the
device, changes to any characters beyond the first 100 will not display
when synchronized to t...
This issue involves contacts added to personal address books from either the global (Novell GroupWise) address book or from a remote lookup. 1.) When a contact is copied from the global address book and added to a personal address book on the server, it ...
GROUPWISE:
If you are having an issue sending email from your device to someone
outside of your domain, first complete an SMTP telnet test to see if
you have relaying enabled. This can be accomplished by following the
steps located in the document l...
GroupWise:When you first set up NotifyLink an OTA load of contacts is required. This will remove all contacts from the device and then load the contacts you have in your Novell GroupWise client. Some users have their contacts on their device and not in ...
Problem: You see users attempting to log into your GroupWise system that are not from your company. Solution: This
is most often seen on our On Demand system as we have multiple
companies with multiple different servers. There is an issue within
th...
Issue:
I am using GroupWise and I wish to increase the number of messages
that can be downloaded via IMAP to my GO!NotifyLink account.
Solution:
Specifies in thousands the maximum number of messages that can be
downloaded by an IMAP client. Fo...
Issue:
The problem occurs when an email is sent to a GroupWise distribution
list from the device.
From your device, you send an email to a distribution list.
This includes composing a new email, forwarding an email, or perform a
reply all.
Users on the...
This issue applies to daily recurring events that are created on the device. If the interval is greater than 1 (for instance, recurring every 3rd day) and an end date is specified, the last instance may be duplicated in the GroupWise client. NOTE: If the ...
This primarily pertains to the Notifylink 4.0.1 server. User Statistics is showing Mailbox checked successfully and the Timestamp is up-to-date but no email is being found or sent to the device. Here are a couple things to check: 1. Check Folders in the...
When a meetin is created within the GroupWise Client using GroupWise
8, 2012, or the Data Synchronizer, it is not recommended that you make
changes to the meeting from the phone. Making the change on the device
will update the device, but the GroupWise Ca...
This
issue applies to meeting requests that were initiated from the device.
After the meeting has been synchronized to the server, if it is then
deleted from the device, the meeting is removed from the user's
GroupWise calendar but not from the GroupW...
GroupWise: What is “Message Availability” in the NotifyLink Admin console (User IT Policies-> Control Options) or Client console (General tab -> Control button) and what does it do? This setting is used for amount of days that an email on a devic...
Issue:
Mobile phone numbers are not syncing to my _GO!NotifyLink_ device for
contacts in the Novell GroupWise Address book.
Solution:
The only supported fields for the mobile phone number when
referencing the Novell GroupWise Address book specifically ar...
GroupWise:This was a defect in the GroupWise object API, # 183442. This happens with events, tasks, and reminder notes. It is fixed in GroupWise versions 7.0.2. http://forge.novell.com/modules/xfref_library/detail.php?tab=doc&reference_id=682&am...
This was a defect in the GroupWise object API, # 183442. This happens with events, tasks, and reminder notes. It is fixed in GroupWise versions 7.0.2. http://forge.novell.com/modules/xfref_library/detail.php?tab=doc&reference_id=682&group=11...
Port Requirements for NotifyLink Installation can be found in the NotifyLink for GroupWise Pre-Installation Guide under Pre-Installation Tasks #8, Port Requirements Port numbers used for connections with NotifyLink Enterprise Server (NLES) components ar...
Random delete/adds of contacts occur after an upgrade from NotifyLink Enterprise Server 4.5.2 to 4.6.0 on a GroupWise Server. The delete/adds are shown in the nlpim.log, but may be undetectable by the end user unless PIM Change Summary is enabled.
...
If creating a calendar event using the GroupWise 8 Web Access Client,
you do not have an option to make the event a recurring one. This is not a limitation, however, when creating the event on the device or from the desktop client.
...
If
a recurring event with no end date is created on the device, the server
will expand the series to 365 events. Adding these events to the server
may result in NLES Monitor Service restarting the PIM service or the
PIM cycle timing out for the user. ...
GroupWise:
Meetings initiated from the device with a recurrence pattern are not
supported. Currently only Windows Mobile devices allow this. The
following issues exist if such a meeting is created:After
the meeting has been synchronized to the server...
This applies when the GroupWise Client v6.5.6 is installed on the NotifyLink messaging server. If the device is used to delete a recurring series, the instances are deleted from the server, but a single new instance is added at the current time. Following...
GroupWise:
Trusted Application allows the GO!NotifyLink (GO!NL) server to login
to the user's email account without knowing the actual password to the
account. This is especially useful when your organization maintains a
password change policy, so that th...
This
issue applies to Reminder Notes, Appointments, and Tasks created in the
GroupWise Client. When these items are created by going to the File
menu, selecting New, then choosing Reminder Note, Appointment, or Task
they are created as an invitation...
GroupWise:1. Reminder notes are added to the device calendar as an All Day Event. 2. Reminder Notes are only supported when the GroupWise Client on the NotifyLink server is v6.5.1 or higher. 3. Reminder Notes cannot be created on the device, only loaded...
Problem: When a message is replied to or forwarded the message
appears "squished" and loses formatting when viewed in GroupWise. They
should look okay when switched to text view but will lose formatting
once again when a reply or forward is ...
GroupWise:NotifyLink Enterprise Server (NLES) v4.5 does not require that mail and PIM server platforms match. It is possible, therefore, to use one platform for mail processing and another for PIM processing. You might even choose to have more than one ...
When synchronizing from server to device, if a contact does not have
a first name or last name, the first name is set to the value of the
display name. If first or last name is set, the display name is not
synchronized. When adding a contact from the d...
A task created on the device that has the start date set to a date
other than the current date does not synchronize correctly. The task
will display in GroupWise on the current date, but the Start Date
property may not be set correctly.
Information: The task status field is not supported by the Groupwise Object API and therefore NLES cannot retrieve or set this property.
A tentative response sent from the device is not processed for
GO!NotifyLink ActiveSync solution users on GroupWise Mail Servers,
because GroupWise does not support the _TENTATIVE_ response for
meeting requests.
If a user responds with Tentative fr...
When viewing a forwarded email using the GroupWise 8 Web Access Client,
text added to the message does not appear in the body of the email, but
in an attached file.
Issue:
An end user is unable to synchronize the "sent items" folder between
GroupWise and GO!NotifyLink and a "sent items.dup1" folder has been
created in the folder list.
Verify the problem:
The creation of the "sent items.dup1" folder occur...
Updating the same contact from the device twice in the same PIM cycle may result in incomplete PIM processing on a GroupWise server (versions less than 8.0.1 HP1). PIM items for which processing was not completed should process in the next PIM cycle, how...
GroupWise: Problem: Upgraded your NotifyLink server from 4.0.1 to 4.5 and PIM is no longer processing for any users. Solution: If you were running with NotifyLink as a Trusted Application this is a known issue. After upgrading to 4.5, if you are runn...
GroupWise:
Creating a weekly recurring event from a device with a start date that does not correspond to its first instance results in the last instance occurring one week before it should on the server. The last instance is correct, however, on the de...
When _GO!NotifyLink_ is registered as a trusted application, users
sometimes get 11477 errors in the gleaner log. Without trusted app,
they process with no issues.
This is a GroupWise issue and will be resolved in a future release.
The only workaro...
GroupWise: If using a Windows Mobile device with encryption on, some upper ASCII
characters in Calendar, Contact, or Task fields will cause an error in
NLPIM.log, and the item will not be added/updated.
Help Desk Software by Kayako