Best Practices for maximumports in TM1: Avoiding PAW Connection Failures

Problem Summary:

Users encounter a "Logging on to the server failed" error when opening PAW reports when their }clientproperties have maximumports set to non-zero values (1-10).

Root Cause:

The issue stems from PA Workspace's modern architecture 2.1.5:

• The client makes multiple simultaneous requests to the TM1 Server for improved throughput
• Each request requires a separate connection
• The application uses asynchronous processing to enhance performance and user experience

When maximumports is set too low (1-10), it restricts the number of concurrent connections the client can establish, causing connection failures during report loading.

Recommended Solutions:

• Removes any artificial limit on connections
• Allows the client to establish as many connections as needed
• Recommended unless there are specific reasons to limit connections
  

• Try values like 10, 50, or 100
• Requires testing to determine the optimal value for your environment
• Note that the optimal value may vary based on:
  

  Report complexity

  Data payload size

  Server capacity

  Network conditions

Implementation Considerations:

• There's no universal "correct" value for maximum ports, as connection needs vary by usage pattern
• Higher values consume more server resources but prevent connection starvation
• Lower values conserve resources but may cause performance issues or failures

The documentation suggests that setting maximum ports to 0 (unlimited) is generally the best approach unless specific constraints require limiting connections.