The installation package can be found on the Trimble Downloads page. While it is often associated with Tekla Structures 2020, the version 2.3/2.5 server is compatible with versions from 2017 onwards.
Users work on local cached versions of the model. When a user clicks "Save," the client machine communicates with the Multi-User Server to stream changes back to the master model database file.
+-----------------------------+ | Dedicated File Server | <--- Stores the Master Model Folder (.db1, drawings) +-----------------------------+ ^ | Read/Write saves v +-----------------------------+ Coordinates locks, +-------------------------------+ | Client Workstations | <=============================> | Tekla Multi-User Server | | (Running Tekla Structures) | queues, & numbering | (Running xs_server.exe service)| +-----------------------------+ +-------------------------------+
Add these to the server machine to increase stability: Tekla Structures Multi User Server 23 20
While the server version 2.3.20 is backward compatible with many versions of Tekla Structures (e.g., 2017 through 2021), it is vital that working on a specific model use the same version and Service Pack of Tekla Structures to avoid database conflicts. Common Troubleshooting Tips
Unlike cloud-based repositories that process file deltas independently over the internet, the local multi-user framework splits operational roles across three components:
Always check the xs_multiuser_server.log file. It provides timestamped data on who joined the session and why a save might have failed. Is Multi-User Still Relevant? The installation package can be found on the
The server merges these changes in real-time. It resolves conflicts line-by-line and object-by-object. Versions and 20 refine this process, offering specific stability patches for large assemblies.
Version 23.0 supports backward compatibility with some older clients via hotfixes, but mixing major versions (e.g., 20.0 client with 23.0 server) is not recommended and may cause database corruption.
The system operates on a architecture:
When a user clicks Save , Tekla synchronizes their local changes with the master model on the server [5]. If two people modify the same object, the first one to save takes priority [4]. Best Practices for Stability
| Symptom | Common Cause | Recommended Solution | | :--- | :--- | :--- | | | Firewall blocking the connection. | Ask IT to verify that TCP port 1238 is open on the server's firewall. Also, add xs_server.exe to the Windows Firewall exception list. | | Connection breaks intermittently | Unstable network or server name resolution. | Try using the server's static IPv4 address (e.g., 10.0.0.11 ) instead of its computer name to bypass DNS issues. | | "Model is locked" error persists | The server service may have a temporary lock on the file. | Restart the Tekla Structures Multi User Server service from the Windows Services panel. If the issue persists, delete the temporary database file tcpip_localhost_<xxxx>.db found in C:\ProgramData\TeklaStructuresServer . | | Unable to save the model | A user's session may be "stuck" on the server. | Close Tekla Structures on all connected devices, then restart the multi-user server machine entirely. This often clears orphaned user process handles. |