Contents

• Introduction

• Upgrade Alerts

• New in Scalix 11.0

• Packaging

• Supported Environments

• Known Issues and Workarounds

Introduction

Back to top

Upgrade Alerts

Back to top

Please read the following alerts carefully, as failing to adhere to any one of them could cause loss of data or destabilize your Scalix system.

New in Scalix 11.0

Back to top

Packaging

Back to top

Supported Environments

Back to top

Known Issues and Workarounds

Back to top

Back to top

Issue

Workaround

During installation of Scalix Web applications, the Apache Web server may not register all workers after the installer restarts it.

In this case, some Web applications will not come up. The error reported in the Apache error log looks like:

To resolve this issue, restart the Apache Web server manually with following CLI commands:

• On RedHat or Fedora Core: "service httpd restart"
• On SUSE: "/etc/init.d/apache2 restart"

If you installed SLES 9 on the Scalix Server host, the python-gtk-2.0.0-215.1 package automatically installs. This version of the package forces the Scalix Installer to display the following error message:

Error: Please upgrade python-gtk package to version 2.0.0-215.3 or newer, currently installed version 2.0.0-215.1 contains a bug that affects Scalix Installer.

Exit the Scalix installer and use YaST to upgrade the python-gtk package by the means provided by SLES 9.

After installation, the automatic launch of the Scalix Management Console can sometimes be accompanied by a series of error messages saying, "Shell-init: error retrieving current directory: getcwd: cannot access parent directories: No such file or directory." Ignore these messages. The browser launches anyway. (bug 4754)

None.

The installer fails at the point of system verification if there is no eth0 interface. The eth0 is the network interface the NETBIOS server uses. (Bug 8528)

Do a manual command line installation.

On a 64-bit SUSE Linux Enterprise Server 10, installation may abort. (Bug 13998 and 13948)

None

On a 64-bit machine with JRE 1.5_05 already installed, installation may abort. (Bug 13948)

Remove JRE 1.5_05 before installing or upgrading and allow the installation wizard to install its own, updated version of JRE 1.5_06.

If installing on a 64-bit SUSE Linux Enterprise Server 10, you must have the package glic-locale-32bit installed.

None

If a pre-existing version or instance of Tomcat is running, the installer may log an error. This does not cause any problems and installation continues normally. (Bug 13619)

None needed

Reconfiguring the Messaging Services or the PostgreSQL Database Integration with the Installation Wizard upgrade process can, in some cases, cause users to be locked out when they later try to sign in to the Scalix Mobile Web Client. (Bug 13947)

If the PostgreSQL database password changes, it must also be changed in the file, platform.properties, which is located at <instance>/platform/platform.properties. This requires a restart of Tomcat. If the database is on a separate server from the platform, this change must be done manually.

If no default gateway is configured, the installer aborts with a network check error. (Bug 11771)

Configure a default gateway, even on an isolated network. With an isolated network, use the server itself as the default gateway. For instructions, consult the Linux distribution's documentation.

Scalix installation fails if /var/opt/scalix/temp is on a different mount point than /var/opt/scalix. (Bug 14294)

For installation only, unmount /var/opt/scalix/temp and create a /var/opt/scalix/temp directory. After installation, recreate the temp directory on its own mount point as /var/opt/scalix/sys/instance_initials/s/temp.

Windows-based installer for Scalix Connect for Outlook crashes at the end of installation when starting setup.exe from inside a Windows compressed folder even though installation completed successfully. (Bug 14281)

Extract setup.exe from the compressed folder and execute it directly from a normal folder.

Back to top

Issue

Workaround

After upgrading Scalix Server from 10.0 to 11.0, users with a large number of messages in their email client folders might notice reduced client/server performance when they access the message store. This is caused by upgrades to the message store container file structure that occur when they are next accessed by a user (through the client UAL process or the local delivery service).

To control when the upgrading of the message store happens so that it doesn't slow down mailbox access, shut down the Scalix Server after upgrade and with only the daemons running (omrc -n), run the commands omtidyu and omscan without the fixmode (-f) option. For example, enter: omtidyallu -M and omscan -Aa. Note 1: The first time it runs after an upgrade, omscan can take twice as long as is typical because it is upgrading message store containers. Scalix recommends that you perform this task in off hours (nights or weekends) to minimize impact on the Scalix Server.

If you've installed your Scalix system on host(s) running SUSE Linux Enterprise 9, your Outlook users will not be able to take advantage of Single Sign On, due to a flawed Kerberos interaction between SUSE and Microsoft.

Solution: There is no workaround or solution at this time.

SSO fails if the time stamps for domain controller, mail server and the workstation are not in sync.

The critical prerequisite to setting up successful SSO and Kerberos authentication is synchronization of time zone, date and time between the domain controller, mail server, and the client user's workstation. The timestamp difference between the mail server and the domain controller should not be greater than the "maximum tolerance for computer clock synchronization setting" of the domain controller.

On Scalix 10.0 servers only, the synchronization command, omldapsync, does not create a new Scalix mailbox for an Active Directory user whose "friendly name" includes accented characters. This has been fixed for the 11.0 release, but if you have old 10.0 servers in your system, you may encounter this problem.

Use a mapping table entry that includes the custom map function:

!CUSTOM=TX_IA_TO_QP_IA

For example:
mail|INTERNET-ADDR|*,1,512|!CUSTOM=TX_IA_TO_QP_IA

The result is that:'"c?nt" <ia>' becomes '=?UTF8?Qc=C3=B6mm=C3=ABnt?= <ia>'

[iCal Information] --

• Exchange 5.5 does not support iCal, therefore SWA-generated meeting requests and meeting requests sent from Outlook/Exchange using the "Forward as iCalendar" do not work correctly.
• A cancelled meeting scheduled via iCal shows as "Tentative" rather than "Free".
• Outlook 2002 (Outlook 10) with an IMAP profile does not recognize iCal messages. The only way Outlook XP will render iCal is if the content type is text/calendar and is the only body type. Most iCal messages are formatted as multipart/alternative. The same messages viewed with OL11/IMAP are correctly processed. Therefore you cannot use Outlook 10 in IMAP mode to connect to a Scalix server and process iCal type meetings.
• All-day events across time zones appear in local time and are not marked specifically as all-day.
• Advanced recurrence patterns are not supported, e.g. every 2 weeks, Tuesday and Sunday (where the week starts on a Monday) or yearly recurrence of the first weekend day of December.
• Responding to an iCal meeting request and proposing a new time is not supported. Scalix does not currently support the COUNTER method of iCal.
• Updating text for a series of recurring meetings may fail to display the update where the recurring meeting previously had exceptions.
• Sending a meeting request from Evolution to Outlook with Scalix loses the "Optional" attendee status. As a result, all attendees appear as "Required".

[iCal Workarounds] --

• To get full calendaring interoperability between Scalix and Exchange 5.5, use the TNEF route and Outlook as the client.
• To make a time slot display as "free," manually remove the meeting from the calendar when accepting a cancellation request.
• This is a Microsoft issue with Outlook 10.

• None

• None

• None

• None

The access URL for Webcal has changed. It is now http://my.scalix.server/api/name@domain.com/mailbox/Calendar?output=ical.

None

If you modify an email user's name while the user is actively connected to the server, the user may not be able to sign on again using SWA or Outlook/Connect. This applies to modifications made both in the Scalix Management Console or the ommodu command on the CLI.

Use SAC or the CLI to verify that the user is logged off before making any modifications. You can then use SAC to modify the user record, or use CLI and issue the following command:

ommodu --requireSignoff -o "<name> "

Where <name> is the user's Scalix name.

German umlauts (and other non 7 bit characters) can cause problems with misfiring rules created with the Web Rules Wizard.

If umlauts (and other non 7 bit characters) are causing problems with misfiring rules created in the Scalix Web Rules Wizard, update the Wizard configuration with 'omwebconf -ra -l lang' (where lang is ENGLISH, AMERICAN or GERMAN). The problematic rules must then be re-edited.

If the Apache/Tomcat connector has not been installed, the server cannot contact the Search and Index Service (SIS) using the default port (80).

Change the SIS port from 80 (the default) to 8080 on the server and all individual users.

1. Edit ~/sys/general.cfg and add the following lines:

   USRL_SIS_URL=sxidx://fqdn:8080/%u
   USRL_BB_SIS_URL=sxidx://fqdn:8080/BB@fqdn

   where fqdn is the fully qualified hostname of the machine.

To change every existing user's entry:

1. Run the command omshowu -n <username> and look for the line:
   SIS URL : sxidx://fqdn/guid

2. Run the command ommodu -n <username> -index sxidx://fqdn:8080/guid
   where fqdn is the fully qualified hostname of the machine and guid is a unique identifier.

The above can also be automated using a simple shell script.

If a user's account is moved from one server to another when SmartCache is enabled, local caches do not update with the user's new internal server address.

When a user is moved to a different server, the cache must be recreated.

If using SmartCache in SmartCache mode, when a user's mailbox is moved from one server to another within a multi-Server Scalix Enterprise Edition environment, you must create a new profile on the user's desktop and re-initialize the user's cache.

Create a new profile on the user's desktop and re-initialize the user's cache.

If you use DDVs to store ISO bulletin board subjects, any DDVs that contain 80-bit ISO characters should be moved to the DDVn-TX variants before upgrading to 11.0. Otherwise, upgrade and/or directory synchronization may fail for these entries.

DDVs that contain 8-bit ISO characters should be moved to the DDVn-TX variants before upgrading to 11.0. On the system where the directory entry is locally owned, use omsearch to extract (e.g. omsearch -e S=bb1 -m DDV1) and ommodent to 'move' it. For example: ommodent -e S=bb1 -n DDV1=/DDV1-TX=<ddv1_value>.

After migrating a user in to Scalix from Exchange via the Scalix Migration Tool (SMT), you may see some that some messages using internationalized character sets such as Japanese show garble in the subject and message fields if you are running against a Scalix 10.0 server. This is because 10.0 does not support internationalization.

Upgrade all servers to Scalix 11.0

With the 11.0 release, the interchange character set used for storing ORN's has been changed from T61 to UTF8. This means that when communicating with legacy Scalix machines (Scalix 10.0 and earlier) via the Sendmail Interface (SMINTFC), character set conversion needs to take place.

To achieve interoperability with legacy machines, the SMINTFC routes need to be flagged with a new "Version Number" field, which can be set with a new "-v" option to omaddrt/ommodrt and which can be viewed with the pre-existing "-f" option to omshowrt. When creating a NEW route to a Scalix 1.0.x machine, the version number should be set to "0" or "1". If creating a SendMail interface route to another 11.0 machine, the route version should be set to "2". In multi-server environment, if a machine is upgraded to 11.0, initially all interface routes will remain as version 0. But as soon as it receives a message on one of those routes which it detects to be an 11.0 message, then the Sendmail Interface Service automatically upgrades that route to version 2. This way, as other machines in the network are upgraded, Sendmail interface communication continues to work.

Any custom scripts with hard-coded references to /var/opt/scalix must be updated because this file structure has been changed.

The binary /opt/scalix/bin/omrealpath can return the correct path to the mount point as follows:

/opt/scalix/bin/omrealpath "~/"

should return

/var/opt/scalix/<nn>/s

where <nn> is a two-character reference based on the hostname. Other examples are:

/opt/scalix/bin/omrealpath "~/sys"
/opt/scalix/bin/omrealpath "~/logs"

to return specific directories.

To use this in a script:

SCALIX_PATH=$(omrealpath "~/")

After an Equinox upgrade, all directory entries (both new and existing) set up to allow mailing to a Public Folder require manual entry of a common name (CN) value, or the sendmail interface reports the user as unknown. (Bug 14017)

Run the following command on a one-time, per folder basis: ommodent -e S=+BB/IA-FORMAL=public.folder@domain.com -n "CN=Public Folder Name", where the IA-FORMAL value is the Internet address of the public folder and the CN value is the name of the Public Folder.

If upgrading from an RC1 version of Scalix 11.0, clean out the IMAP cache. (Bug 14119)

Run the following command on the Scalix Server: cd $(omrealpath \~/user) find -name imap-cache | xargs rm -rf . It is best to run this command when nobody is signed on to the system (when the rci and IMAP services are off).

In some cases, you may be able to log in to SAC using administrative privileges from a server not registered with SAC. (Bug 14088)

On each server, use a different password for the user named sxqueryadmin so that they do not match.

Back to top

Issue

Workaround

Indexing stops working with a "Too many files" error reported in the log, /opt/scalix-tomcat/log/scalix-sis-indexer.log

Consider increasing the number of file descriptors per process using the command ulimit -n 10000 or larger.

Back to top

Issue

Workaround

Restarting Tomcat on machines where the Management Agent (aka Remote Execution Service or RES) is deployed takes several seconds.

Allow Tomcat to shut down properly and wait several seconds before restarting it.

Users created in the Management Console whose passwords contain umlauts cannot log in to Scalix Web Access. (Bug 4108)

Change user passwords to text entries without diacritical marks.

Users who exceed their mailbox size limits do not receive messages even after you remove the limits. (Bug 4971)

After removing the mailbox size limit, restart the Client Interface, Service Router, and Local Delivery services.

In environments that have the Management Agent (RES) operating in Kerberos mode on the server alongside other large applications, Tomcat must be running on the RES server before starting Tomcat on any other server that runs the Management Console.

Ensure that the Management Agent is deployed first in Tomcat (before other large applications) and that all Tomcat instances are started before you start the Management Console service.

A user whose name is modified while he/she is actively connected to the server may not be able to sign on again using SWA or Outlook.

Verify that the user is logged off before changing his name. Or use the command line to forcibly sign them off with the following command:

ommodu --requireSignoff -o "<user_name>"

If an administrative user has a pre-expired password (requiring that they change their password upon next login), the user cannot log on to the management console until the password is reset. (Bug 13881)

Have administrative users change their passwords in their clients before accessing the management console, remove the pre-set flag on the command line (ommodu with a -E option) or avoid the use of pre-expired passwords entirely.

In a multi-server installation with the Management Console on one server (A) but not another (B), the Management Console may not be able to perform actions on the other server (B). (Bug 13633)

Install the Management Console on all servers.

Back to top

Issue

Workaround

OLE objects embedded in the body of an email message may not be usable by the message recipient. (Bug 723)

Transfer OLE data as an attached file.

In Outlook 2002, enabling the instant messaging feature impacts response time when viewing messages in the Preview pane.

Disable this option.

When using the German-language version of Outlook (with Scalix Connect), opening and using the Scalix Rules Wizard may result in a rule, but the process triggers an I-E script error, referring to "sclxresDE.dll". (Bug 10370)

The script error is triggered by clicking through the Wizard to the exceptions screen, whether any exception is chosen or not. The rule is, however, created successfully and works as configured by the user.

If users create additional folders using existing standard folder names ("Inbox", etc), they will not be able to open or use them in SWA or other IMAP clients that do not utilize MAPI.

Solution: Don't create folders named "Inbox" (or "Draft" or "Junk E-mail", etc.) if you want to use SWA to check your mailbox.

Once SmartCache is enabled, you cannot revert to non-SmartCache mode.

If you wish to discontinue caching, create a new profile without the SmartCache feature enabled.

The use of non-ASCII characters in display or common names to log in to SWA and Outlook is not supported.

None

In rare circumstances, a delegate can see a new folder created by his or her "principal" but cannot open it. This happens if the principal creates a new folder shortly after the delegate adds the principal's mailbox to his own profile.

Restart Outlook and the new folders become accessible to the delegate.

If you are trying to sync a Blackberry device with the Microsoft Outlook client, you must replace the Intellisync file ilxolk.fil with a customized Scalix version. The customized version is located in the .tar.gz file under software/scalix_connect_outlook.

To install the patch file for Scalix/Intellisync:

1. Using the Windows browsing UI, locate the BlackBerry Desktop Manager installation directory, which is usually "C:\Program Files\Research In Motion\BlackBerry".
2. Under the BBDM installation directory, open the folder "Connectors\MS Outlook Connector".
3. Right-click the file "ilxolk.fil" to bring up the pop-up context menu.
4. Select "Properties," then in the Properties dialog box that appears, select the "Version" tab.
5. Verify that the file version number begins with "5.3.4". For BBDM 4.1.0.6, the version number is 5.3.4.12.
6. Dismiss the Properties dialog box.
7. Rename the file "ilxolk.fil" to something else, for example, "ilxolk.fil.original".
8. Copy the replacement connector file ilxolk.fil from the delivery disk (or wherever you have stored it) into the connector folder.
9. Verify the version number of the new file by following steps 3-5 above. The new file version should be "5.3.4.27".
   

If the Calendar folder is set to display first when launching Outlook, the Scalix Rules Wizard fails to load and the connection to the server is lost. (Bug 8284)

Only specify the Inbox folder as the initial display mode.

On Outlook 2003 with Active Virus Shield installed and enabled, Outlook deadlocks when sending mail. (Bug 13690)

Disable the 'Scan on delivery' for Active Virus Shield.

1. Start Outlook.
2. From the Tools menu, select "Options". The Options dialog appears.
3. Click the "Active Virus Shield" tab.
4. In the "Settings" section, uncheck the "Scan on read," "Scan on Send" and "Scan on delivery" checkboxes.
5. Click "Ok".

The Outlook Connector setup procedure does not properly extract the sxpro.exe when the /e switch is used. Because this .exe file creates Outlook profiles on Scalix, it is essential that it run properly and complete its function. (Bug 13965)

To launch the sxpro.exe function manually, install the MAPI SP and it extracts under the directory \Program Files\Scalix\Connect. Launch it from there.

Use of the sxpro command line program to auto-create Outlook profiles for new users can cause cache initialization to continue indefinitely upon first login. (Bug 14180)

Avoid use of the sxpro profile creation feature and instead, create Outlook profiles manually.

Unicode is functional in Outlook 11, but not Outlook 10. (Bug 13324)

If Unicode is needed, use Outlook 11.

Back to top

Issue

Workaround

When using Internet Explorer with high-resolution displays, users with dpi settings other than 96 dpi may experience that certain modal dialogs within Scalix Web Access do not display all of the information that the dialog contains.

Set dpi setting to Normal size (96 dpi) through Windows Control Panel > Display Properties.

Popup-blocking software installed on your machine might prevent SWA from starting up.

You need to either disable pop-up blocking or add the Scalix Web Access URL to the list of allowed sites.

The use of non-ASCII characters in display or common names to log in to SWA and Outlook is not supported.

None

When upgrading SWA, customizations to the login page are not retained.

Prior to upgrade, save a copy of index.html and web.xml, which are where login customizations are made, and use these as a guide to make the same changes once the update has completed successfully.

Umlauts created from an English keyboard (alt+0228 or alt+0252) on Internet Explorer 7 do not display properly in the contacts list if the URL used to access SWA is not on the list of trusted sites. They do display properly in email or calendar items.

Use a German language keyboard.

SWA does not accept resource bookings made with global character sets.

None

A large number of concurrent SWA sessions can trigger a file descriptor limit, causing an error message in the SWA log that says, "Too many open files."

Configure the ulimit setting appropriately depending on how many SWA users are expected. For RHEL, add the "ulimit -HSn <number>" to /etc/rc.d/init.d/scalix-tomcat.

For RHEL:

if [ "$DISTRIBUTION" = "redhat" ] ; then

start() {

ulimit -SHn 9000

action $"Starting Tomcat service: " $startup

RETVAL=$?

}

For SuSe:

elif [ "$DISTRIBUTION" = "suse" ] ; then

start() {

ulimit -SHn=9000

echo -n "Starting Tomcat service"

$startup

rc_status -v

}

If upgrading directly from 10.0.1 or later to 11.0, the event services may not start, which can cause the Scalix Mobile client to fail and SWA performance to deteriorate. (Bug 14133)

After completing upgrade to 11.0, the xinetd process needs to be signalled to reload its configuration. Run the following command: "/etc/init.d/xinetd reload". Then restart the Scalix mail server (omshut/omrc).

In Firefox, resizing the message list pane shrinks the entire pane to only one pixel, obscuring the message list. (Bug 10397)

At the top of the preview pane, pull the border repeatedly until it reaches the desired size. This may take a few repetitions as the border bounces back.

In some cases, the Drafts folder may have multiple copies of the same message. (Bug 14194)

Delete the extras after sending.

Folders designated as shared may not appear in SWA. (Bug 13398)

Restart Tomcat and the IMAP process

Users managed through Active Directory and other external directories cannot use Advanced Search functionality within SWA. Also, with large mailboxes, mailbox load performance is equivalent to what it was in Scalix 10. In scalix-api.log, the following error message is logged:
FATAL [DbUtils.getSession:57] org.postgresql.util.PSQLException:
ERROR: syntax error at or near "==" (Bug 14277)

To enable simple search functionality, disable use of the Scalix Messaging Services by SWA. In the file swa.properties, set the following parameter to false: "swa.platform.enabled=false" (default: true) and restart scalix-tomcat.

SWA search doesn't work with locale set to German. (Bug 14325)

On RHEL4, go to /etc/sysconfig/i18n and change the language setting from de_DE.UTF-8 to en_US.UTF-8, then reboot the server.

Back to top

Issue

Workaround

Recurring appointments "Every Xth Y of month M every year" cannot be created or edited in Evolution

You can create recurring appointments with the pattern "Every Xth Y of month M every year" in Outlook and SWA but not in Evolution. If created in SWA or Outlook, though, it displays correctly in Evolution although you cannot edit them.

Nested PDLs (address-lists)

You cannot create nested PDLs in Evolution. When created in Outlook, nested PDLs only show with their top-level members in Evolution.

Freebusy data of organizer not displayed

The "Scheduling" section of the meeting editor does not show the free/busy data for the organizer.

Offline mode

Only mail features are currently supported in offline mode. While certain calendar and contacts operations do work, they are not officially supported.

Message filters

Message-filters do not file new messages automatically although the "apply filters to new messages in the Inbox" option in the account profile is checked. "Apply Filters" from the Message menu however works.

SMTP configuration

You cannot configure the SMTP and IMAP servers separately. They are always the same and the SMTP port is always 25. If you need a different configuration, manually change your account profile settings through gconf-editor:

• Run gconf-editor
• Expand /apps/evolution
• Select mail
• Double-click on accounts in the right-hand pane
• Select the relevant account and click "Edit"
• In the text box, find the XML element <url> inside the <transport> element and add ":###" after the hostname, where ### is the port of your SMTP server.

Modifying an existing Scalix account in Evolution to a new account does not update the calendar and contact data for the new user.

Delete the existing Scalix account by choosing Edit ->Preferences in Evolution and then create a replacement ("New") Scalix account.

When accepting a meeting request in Evolution, adding a comment results in an empty message attachment in the response when viewed by an Exchange user in the Outlook client.

None

Evolution users cannot accept updated instances of recurring meetings sent from Outlook.

None

Additional invitees to a recurring meeting may not display when the appointment is viewed in Evolution.

None

Resource booking is not supported in Evolution.

None

Evolution does not display priority or sensitivity levels set in SWA or Outlook.

None

Evolution does not show message formats as saved in the Outlook Drafts folder.

None

Messages sent to PDLs arrive in Evolution as "Undisclosed-Recipient."

None

Back to top

Back to top

Issue

Workaround

Microsoft Exchange out-of-office settings do not transfer during migration. So if a user's out-of-office assistant is activated during migration, it stops responding.

After migration, reset out-of-office notifications in Scalix.

When migrating a user with the Scalix Migration Tool, the Outlook rules are not preserved because Microsoft rules are not compatible with Scalix.

None

Back to top

Issue

Workaround

Replying to emails results in an error message. (Bug 13747)

None

Reconfiguring the Messaging Services or the PostgreSQL Database Integration with the Installation Wizard upgrade process can, in some cases, cause users to be locked out when they later try to sign in to the Scalix Mobile Web Client. (Bug 13947)

If the PostgreSQL database password changes, it must also be changed in the file, platform.properties, which is located at <instance>/platform/platform.properties. This requires a restart of Tomcat. If the database is on a separate server from the platform, this change must be done manually.

Users managed through Active Directory and other external directories cannot log in to the Mobile Web Client. In scalix-api.log, the following error message is logged: FATAL [DbUtils.getSession:57] org.postgresql.util.PSQLException: ERROR: syntax error at or near "==" (Bug 14277)

None. This is caused by the format of the unique user ID string provided by AD. Users managed through an external directory cannot use the Mobile Web Client at this time.

Back to top