TeamWorks 18.1.1 Release Notes

March 2019

TeamWorks helps your teams communicate and collaborate more effectively using their mobile phones, web browsers, and the Micro Focus GroupWise email client.

1.0 Product Overview

TeamWorks lets your organization’s teams

  • Initiate project-based, team-oriented discussions.

  • Hold real-time conversations.

  • Share files dynamically.

2.0 What’s New in TeamWorks 18

2.1 New in 18.1.1

In addition to bug fixes, TeamWorks 18.1.1 includes the following:

2.2 New in 18.1

In addition to bug fixes, TeamWorks 18.1 includes the following:

  • Mentioning/Tagging users so that they are notified of posts.

  • Key architecture updates.

  • Refined email notifications.

  • Support for SLES 15.

  • Performance improvements.

3.0 Installation Notes

A successful TeamWorks deployment requires that you:

  1. Have a fully configured DNS service on the network. See Known Issues below.

  2. Plan your deployment using the TeamWorks 18.1.1 Planning Your TeamWorks Deployment—Best Practices guide in combination with the TeamWorks 18.0 Planning Worksheets.

  3. Deploy TeamWorks using the instructions in the GroupWise TeamWorks 18.1.1: Installation and Deployment Guide.

4.0 Known Issues

  • /var Partition Expansion Requires Manual Intervention: The Port 9443 Storage Expansion dialog doesn’t expand the /var partition without additional manual steps, as follows:

    1. Access the Port 9443 console and shut down the appliance.

    2. Using the VMware tools, expand the size of the appliance’s third disk (dev/sdc1).

    3. Restart the appliance, then in the Port 9443 console, expand the /var partition to match what you did in VMware.

    4. At the command prompt, edit the /etc/fstab file and remove the following line.

      /dev/sdc1/var ext rw 0 0

    5. Restart the appliance.

    6. At the command prompt, edit the /etc/fstab file and restore the following line.

      /dev/sdc1/var ext rw 0 0

    7. At the command prompt, enter the following command:

      /opt/novell/base_config/va_expand_disk

      The partition expands and /dev/sdc1 mounts as /var.

    8. Restart the appliance.

  • DNS Services Must Be Running on the Network: Before deploying TeamWorks, you must have a fully configured DNS server running on the network that TeamWorks uses. Otherwise, initial system configuration will fail.

  • Search and All-in-One DNS names Cannot Begin with a Number: During initial appliance deployment of Search and All-in-One appliances, if you enter a DNS name that begins with a number, appliance installation will fail and must then be redone.

    Micro Focus intends to address this in a future update.

  • Services Account Users’ Passwords Require ASCII Characters: During initial TeamWorks service setup, when you set passwords for the TeamWorks services accounts listed below, you must use only ASCII characters for the following users:

    • svcs-user
    • svcs-admin

    Micro Focus intends to address this in a future update.

  • Database Name–Do Not Include a Dash: If you include a dash in the database name, database creation will fail.

    You must then use the Back button to return to the field and change the name.

  • Account Lockout Resolution: If a user is locked out because of failed login attempts, the administrator can reset the password and restart TeamWorks as described in this TID.

    Alternatively, the user can retry after 30 minutes.

    Micro Focus plans to implement Captcha for resetting passwords in a future release.

  • Users Unable to Authenticate: If your users are not able to authenticate and if you see entries similar to the errors below in the appserver.log, then check your PostgreSQL database access. Also check the disk free space on /vastorage.

    2017-07-10 11:08:41,789 WARN [http-nio-8443-exec-6] [org.hibernate.util.JDBCExceptionReporter] - SQL Error: 0, SQLState: 53100
    2017-07-10 11:08:41,789 ERROR [http-nio-8443-exec-6] [org.hibernate.util.JDBCExceptionReporter] - ERROR: could not access status of transaction 0
    Detail: Could not write to file "pg_subtrans/000A" at offset 237568: No space left on device.
    2017-07-10 11:08:41,790 ERROR [http-nio-8443-exec-6] [com.novell.teaming.module.authentication.impl.PlusAuthenticationProviderModule] - Authentication failure for [mclark]
    org.springframework.dao.DataAccessResourceFailureException: Hibernate operation: could not get next sequence value; SQL [select nextval ('ss_loginaudit_id_sequence')]; ERROR: could not access status of transaction 0
    Detail: Could not write to file "pg_subtrans/000A" at offset 237568: No space left on device.; nested exception is org.postgresql.util.PSQLException: ERROR: could not access status of transaction 0
    Detail: Could not write to file "pg_subtrans/000A" at offset 237568: No space left on device.
  • Attached File Uploads—Name Limitations: For the TeamWorks web client, an attachment fails to upload if the filename contains any of the following:

    • Pound sign or hashtag (#)

    • Caret (^)

    • Ampersand (&)

    • Forward slash (/) (Macintosh only because Windows filenames cannot contain this)

  • Microsoft Edge Browser–Administrative Limitations: Many of the Port 9443 Administrative Console functions don’t work on the Edge browser.

    Edge is only supported for administrative tasks that use the Port 8443 Administrative Console.

5.0 Documentation

The TeamWorks documentation is posted here.