Login/Register
  • Home
  • Community
  • Knowledge
  • Technical Docs
  • RWS Support Policy
  • Trados Studio Licensing Help
  • Login for Support
Back to Search Results

Flow service not available

000014714 |9/11/2024 6:34 PM
Scope/Environment
Flow
Symptoms/Context

When attempting to access the Flow portal there is an error:

"the service is unavailable"

Resolution
If your system is hosted by RWS, log a support case.

The instructions below are only applicable if your system is self-hosted (contact your IT department for assistance):
  1. Restart the MultiTrans Flow 64 service on the server.
  2. If restarting the Flow service does not resolve the issue, check whether any security penetration tests have been performed on the server. These security tests may corrupt Flow's installation files, in which case uninstalling/reinstalling Flow on the server should resolve the issue. To prevent this from re-occurring after the next security test, take regular backups of the server and the MultiTrans/Flow databases immediately prior to any security tests. Once the security test is completed, revert back to the latest backup when Flow was still functional.
  3. Check the "C:\Program Files\Donnelley\MultiTrans Flow 64\runtime\logs\error.log" log file on the server. If you see the following error...
    "Failed to create server shutdown socket on address [localhost] and port [8005]"
    ...then perform the following steps:
    • Open the following file in Notepad: C:\Program Files\Donnelley\MultiTrans Flow 64\JBoss - EWS\share\apache-tomcat-9.0.62\conf\server.xml
    • Look for the text
      Server port="8005" shutdown="SHUTDOWN"
      in this file.
    • Replace
      port="8005"
      to another available port number, such as
      port="8006"
    • Save your changes and restart the MultiTrans Flow 64 service.
  4. If the previous steps don't help, retrieve the Flow server logs and then log a support case for further investigation.
Root Cause
  1. There may have been a temporary network issue which interrupted the connection between the Flow server and the database server.
  2. A regular security test may have been performed on the server which corrupted Flow's installation files.
  3. Tomcat could not create a server shutdown port because the configured port was not available (default port number: 8005).
Reference
Send Article Feedback
RWS Machine Translation Translation Software Language Services Content Management
All Contents Copyright © RWS.
COPYRIGHT PRIVACY POLICY COOKIE POLICY TERMS AND CONDITIONS