TeamWorks 18 Release Notes

December 2017

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 Installation Notes

A successful TeamWorks deployment requires the following:

  1. A fully configured DNS service is required. See Known Issues below.

  2. Plan your deployment using the TeamWorks 18.0 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: Installation, Deployment, and Upgrade Guide.

3.0 Known Issues

  • 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:

    • db-user
    • postgres
    • 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.

  • Only One NTP Server Configured: All appliance installation wizards let you enter up to three NTP servers. However, after the appliances start, only one server is actually configured.

    Also, the 9443 console lets you type in additional servers, but the NTP configuration remains unchanged.

    Micro Focus intends to address this in a future update.

  • Account Lockout Requires Admin Intervention: If a user is locked out because of failed login attempts, the administrator must reset the password.

    Micro Focus plans to implement Captcha for password resetting 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.

4.0 Documentation

The TeamWorks documentation is posted here.