Tekla Structures Multi User Server 23 20 May 2026

Mastering Collaboration: A Guide to Tekla Structures Multi-User Server 2.3.20

In the world of Building Information Modeling (BIM), seamless collaboration isn’t just a luxury—it’s a necessity. For structural engineers, detailers, and fabricators using Tekla Structures, the Multi-User Server 2.3.20 remains a foundational tool for teams working simultaneously on a single model.

While newer cloud-based solutions like Tekla Model Sharing have gained popularity, many firms continue to rely on the Multi-User Server for its stability within local area networks (LAN) and its straightforward setup. What is Tekla Structures Multi-User Server 2.3.20?

The Multi-User Server is a small service application that runs on a central computer (server) and manages access to a Tekla Structures model. Version 2.3.20 is a specific update designed to ensure compatibility across various Tekla versions while fixing critical bugs related to model locking and synchronization.

Essentially, it acts as a "traffic cop." When multiple detailers are working on the same high-rise or industrial project, the server ensures that two people don't try to modify the exact same part at the exact same time, preventing data corruption. Key Benefits of Version 2.3.20

Low Latency Performance: Because the server operates on your internal network, data transfer is incredibly fast compared to cloud syncing, making it ideal for large, complex models.

Model Integrity: Version 2.3.20 includes refined protocols for "saving" and "refreshing," ensuring that when a user saves their work, all other users receive the update without the model crashing.

No Subscription Fees: Unlike Tekla Model Sharing, which often requires a per-user license or "credits," the Multi-User Server is generally included with your Tekla Structures license, making it a cost-effective choice for localized teams. Installation and Setup Best Practices

To get the most out of Multi-User Server 2.3.20, your IT environment should be optimized. Here is the standard workflow for a successful deployment: 1. Server Requirements

The server application is lightweight. You don't need a high-end workstation to run it; a dedicated "always-on" PC or a standard Windows Server instance will suffice. Ensure the server has a static IP address to prevent connection drops. 2. Port Configuration

The Multi-User Server typically communicates through Port 1238. You must ensure that this port is open in your server’s firewall and that the client workstations can "ping" the server over this port. 3. Version Consistency 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 all detailers working on a specific model use the same version and Service Pack of Tekla Structures to avoid database conflicts. Common Troubleshooting Tips

Even with a stable version like 2.3.20, users may encounter "Locked Model" errors. Here is how to handle them:

The "Ghost" User: If a user’s computer crashes, the server might still think they are active. In the Multi-User Server administration tool, you can manually disconnect inactive users to release the locks.

Active Directory Issues: Ensure that all users have Read/Write/Modify permissions to the folder where the model is stored. The Multi-User Server manages the logic of the model, but Windows manages the file access.

Log Files: 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?

With the rise of Tekla Model Sharing (Cloud), some wonder if the Multi-User Server is obsolete. The answer is no. For projects where data security prevents cloud storage, or for offices with high-speed internal networks but inconsistent external internet, the Multi-User Server 2.3.20 remains the most reliable way to deliver a project on time. Conclusion

The Tekla Structures Multi-User Server 2.3.20 is a "set-it-and-forget-it" tool that powers high-intensity detailing environments. By centralizing your model management and following basic network protocols, your team can focus on what matters most: accurate detailing and clash-free construction.

Title: The Great Clash of the 23.20 Bridge

It was 3 PM on a Friday. The Millbrook Bridge project was already two weeks behind. Four structural engineers—Mia, Carlos, Leo, and Priya—sat in different corners of the same open-plan office, each staring at their own screen. Their deadline: Monday morning.

They were using Tekla Structures 23.20 with the Multi User Server (MUS). When it worked, it was magic. When it failed, it was a silent disaster. Title: The Great Clash of the 23

The Setup (Friday, 2:30 PM) Their IT guy, Sam, had set up the MUS on a local server: 192.168.1.105:2307. The master model, Millbrook_Bridge_23.20, was stored there. The rule was simple: Always save to the server, never locally. But as deadlines loom, rules bend.

Mia worked on the main girders. Carlos was detailing the cross-frames. Leo handled the bearings. Priya was running clash detection.

The Incident (Friday, 2:47 PM) Carlos, impatient with a lag caused by a VPN background process, decided to work detached—he saved a local copy, made 47 changes, and then tried to merge back.

Tekla MUS 23.20 was robust, but not psychic. When Carlos forced his local model back into the master, the server paused. A pop-up appeared on everyone's screen:

"Conflicting modifications detected. Object ID 18473. Please reconcile."

Panic set in.

The Twist (Friday, 3:00 PM) While Carlos and Mia argued over who moved a bolt group, the MUS did something unexpected—it entered auto-recovery mode. This was a hidden feature of version 23.20: when a critical object ID conflict occurs, the server doesn't crash. Instead, it forks the conflicting objects into a separate "quarantine" layer.

The team didn't know this. They thought the model was corrupt.

The Discovery (Friday, 3:15 PM) Sam the IT guy opened the Multi User Server Administrator tool (version 23.20’s interface was clean but intimidating). He saw the log:

[WARNING] Object 18473 locked by user CARLOS (write)
[WARNING] Object 18473 also modified by user MIA (write)
[INFO] Auto-quarantine activated. New layer "_CONFLICT_18473" created.
[INFO] Server stability maintained. No rollback performed.

Sam shouted across the room: "Nobody panic! Version 23.20 quarantined the conflict. Your main model is safe." "Conflicting modifications detected

The Resolution (Friday, 3:30 PM) Using Tekla’s built-in Compare and Merge tool (greatly improved in 23.20), Mia and Carlos opened the quarantine layer side-by-side. They saw the issue: Carlos had shifted a bolt pattern by 5mm to match a shop drawing, while Mia had locked it to a global rule.

They agreed on Carlos’s fix. Mia deleted her version, Carlos saved his to the server, and the quarantine layer vanished.

The MUS logged:

[INFO] Conflict resolved. Quarantine layer purged.
[INFO] All users synchronized. Last save: 15:32:01.

The Happy Ending (Monday, 8:00 AM) The team submitted the Millbrook Bridge model on time. No corrupt files. No weekend overtime. Sam received a $50 coffee card from the project manager.

And the Multi User Server 23.20—unseen, unthanked, but rock-solid—kept humming on 192.168.1.105:2307, ready for the next clash.

Why 23.20 was special (technical footnote for story lovers):

  • Stability over features: Version 23.20 was the last of the 23.x cycle, meaning it was the most patched and reliable MUS before Tekla moved to version 24.
  • Auto-quarantine: Not officially documented as "quarantine," but conflict isolation was a hidden gem.
  • No cloud dependency: Pure on-premise, which made it a favorite for government and infrastructure projects where security is paramount.

If you’d like a different angle—like a disaster story, a migration tale, or a performance tuning saga with MUS 23.20—just let me know.

Why versions 23 and 20 specifically?

In the Tekla release cycle, version 20 (2015) and version 23 (2017) are considered "Long Term Stability" (LTS) releases. Many fabrication shops still refuse to upgrade past version 23.0 because later versions changed the database schema. Consequently, Tekla Structures Multi User Server 23 20 environments are the most common hybrid setups found in active fabrication shops today.

Part 3: Step-by-Step Installation Guide

Here is the exact procedure to set up the Multi User Server for versions 23 and 20 simultaneously (dual-environment).

Part 4: Connecting Clients (How to point to the server)

Once the server is running, your detailers need to connect. In Tekla Structures 23 or 20:

  1. Go to File > Open > Model.
  2. At the bottom of the dialog, change the "Model location" dropdown from Single-user model folder to Multi-user model.
  3. In the "Server address" field, enter the IP of your server followed by the port.
    • For Version 23: 192.168.1.100:27000
    • For Version 20: 192.168.1.100:27002
  4. Click Show models. If configured correctly, the shared models will appear.

6. Troubleshooting Common Issues

Even with proper setup, network issues can arise. Here are common solutions for Multi-User Server 23:

3. System Requirements & Prerequisites

Before installing Multi-User Server 23, ensure your hardware and network meet the following baseline requirements:

Troubleshooting Tips

  • Use expanded server logs in 23.20 to trace slow commits or conflicts.
  • Monitor CPU, memory, and disk IO during peak collaboration to identify bottlenecks.
  • If users experience frequent conflicts, review object-locking patterns and train teams on smaller, more frequent commits.
  • For WAN deployments, test latency and packet-loss; consider deploying a local MUS instance and synchronizing models between sites if latency is high.

Error 3: Database corruption – "History differs"

  • Cause: A user lost power while saving their local cache (the .db files).
  • Fix: The Server Admin must use the "Rollback" feature in the Server Management Console to revert the model to a previous snapshot (located in model\history).