When a user opens a multi-user model:
Tekla Structures Multi-User Server (often associated with version
for recent releases like 2020) is a service that allows multiple users to work on the same model simultaneously. Tekla User Assistance Core Content and Functionality Centralized Connectivity
: It acts as a lightweight hub that manages traffic between different users' local copies of a model and the master model stored on a server. Networking Requirements : By default, the server communicates through TCP port 1238 . This must be open on your firewall for users to connect. Component Parts : The installation typically includes: TeklaMultiUserServer.exe : The core service file. Configuration Files : Used to define specific server settings or logs. Service Manager
: A utility to start, stop, or restart the multi-user service. Tekla User Assistance Usage and Accessibility Version Compatibility
Tekla Structures Multi-user Server 2.3.2.0 is a companion service that enables real-time collaboration by allowing multiple users to work concurrently on a single central 3D model database. Google Groups Key Features & Benefits Real-Time Synchronization
: Changes made by one user are visible to others as soon as they save, ensuring everyone works on the most recent version of the model. Conflict Prevention
: The server coordinates write access, locking the master model during critical operations like opening, saving, and numbering to prevent data corruption. Backward Compatibility
: The 2.3.2.0 installation package is generally compatible with Tekla Structures versions 17.0 and later. Optimized Workflow
: It reduces the need for manual copying and merging of models, saving time and minimizing errors. Google Groups Essential Blog Post & Resources
For a comprehensive guide, the following resources cover setup and management: Getting Started with Multi-user : A detailed walkthrough from Trimble User Assistance
on installing the server and converting models to multi-user mode. Setting Up Several Servers on One Computer
: Instructions for managing multiple server instances by assigning unique TCP ports (e.g., 1240 instead of the default 1238). Multi-user Server Setup & Usage Guide : A community post from Google Groups
detailing installation steps, firewall configurations, and model conversion. Google Groups Quick Setup Reference
: Download and install the Multi-user Server package on a dedicated machine that remains powered on. Service Status
: Verify that the "Tekla Structures Multiuser Server" is listed as "Running" in Windows Services.
Before diving into versions 23 and 20 specifically, it is crucial to understand the core concept. The Multi User Server is a separate application (not part of the standard Tekla Structures installation) that allows multiple modelers to work inside the same model simultaneously. It uses a master-client model:
Unlike file-sharing over a standard network (which corrupts models), the Multi User Server locks individual components, not entire files. This means User A can edit a steel column while User B edits a brace 10 feet away, and both save changes without conflict.
To successfully deploy the Multi User Server for versions 23 or 20, you must understand the three-tier architecture:
The server uses two distinct ports:
Crucial Note: For "Tekla Structures Multi User Server 23 20" to work, the server version must be equal to or newer than the client version. A version 20 client cannot connect to a version 23 server due to protocol changes.
Neither version 23 nor 20 has modern encryption (TLS 1.2 was not standard for the server service). Therefore:
The choice between Tekla Structures Multi User Server 23 and 20 depends entirely on your client workstations and project timeline.
Remember: The Multi User Server is not a "set and forget" tool. Regular maintenance—monitoring log files, cleaning temp folders, and rebooting weekly—ensures that your team never experiences downtime. Whether you stick with reliable version 20 or the more robust version 23, a properly configured server turns chaotic BIM coordination into a symphony of simultaneous edits.
For official support, always refer to Tekla User Assistance (user.tekla.com) for the latest service packs for version 23.0 and 20.0.
Overview
Tekla Structures Multi-User Server 23.20 is a server-based solution that enables multiple users to collaborate on the same Tekla Structures project simultaneously. It allows teams to work together more efficiently, reducing errors and improving productivity.
Key Features
Benefits
System Requirements
Technical Specifications
Release Notes
The 23.20 release of Tekla Structures Multi-User Server includes several new features and improvements, including:
Conclusion
Tekla Structures Multi-User Server 23.20 is a powerful solution for teams working on complex construction projects. Its robust features and improved collaboration tools make it an ideal choice for companies looking to improve productivity and reduce errors. With its centralized project management and enhanced security features, it provides a secure and reliable platform for teams to work together effectively.
Tekla Structures Multi-user Server 2.3.20: Technical Overview and Configuration
The Tekla Structures Multi-user Server 2.3.20 is a specialized network service designed to facilitate real-time collaboration on 3D structural models. It serves as a management hub that coordinates simultaneous access to a single "master model," allowing multiple team members to work concurrently without the need for manual model merging. 1. Core Functionality and Architecture
The multi-user system operates on a TCP/IP network and consists of three primary components: the Multi-user Server, the File Server (hosting the master model), and Client Computers.
Model Synchronization: Each user works on a local "working model." Changes are only updated to the master model—and made visible to others—when the user performs a save operation.
Operational Control: The server performs critical administrative tasks, including:
Locking the master model during saving or numbering to prevent data conflicts.
Assigning unique identification numbers to new model objects and drawings.
Tracking active users and issuing warnings if multiple users attempt to edit the same object or drawing. 2. System Requirements and Installation
While the multi-user server software is lightweight and has low CPU usage, the overall performance depends heavily on network stability and the hardware of the file server hosting the model. Tekla Structures Multi User Server 23 20 - Google Groups
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.
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."
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):
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.
Tekla Structures Multi-User Server (version 2.3.20) is an on-premises coordination service that enables multiple team members to work on a single 3D building information model simultaneously over a Local Area Network (LAN). While newer cloud-based technologies like Tekla Model Sharing
have largely superseded it for global teams, the Multi-User Server remains a stable, cost-effective choice for local, office-based teams. Tekla User Assistance 🏗️ Core Functionality
The server acts as a "traffic controller" for your project data. Master Model: One central model is stored on a file server. Working Models: Each user opens a local copy on their computer. Conflict Prevention:
The server manages write-locks, ensuring that when one person saves or runs numbering, others are momentarily queued to prevent data corruption. Real-Time Awareness:
Users can see changes made by colleagues every time they save their local model to the master. Google Groups ⚙️ Technical Specs & Requirements
A primary feature of the Tekla Structures Multi User Server 2.3.20 is its ability to facilitate real-time, simultaneous collaboration by managing centralized write access and model locking.
This service acts as a traffic controller for teams working on a shared local network (LAN). Key functionalities include:
Conflict Prevention: It automatically locks the master model when a user is saving, numbering, or editing specific objects, preventing others from making overlapping changes that could cause data loss.
Active Session Management: The server keeps a live track of all active users and their client computers, allowing team members to see who else is currently working on the project.
Automated Numbering Control: It manages the distribution of unique ID numbers for general arrangement drawings and multidrawings, ensuring consistency across all users.
Local Synchronization: Users work on a local "working model" and only synchronize their changes to the master model on the file server when saving, which helps manage network load. Multi-user system | Trimble User Assistance
Title: Keeping the Team in Sync: A Look Back at Tekla Structures Multi User Server 23 & 20
Intro In the fast-paced world of structural detailing and BIM, "collision" shouldn't just refer to rebar and ducts—it should never refer to file versions. Before the cloud became the default answer, Tekla Structures introduced a robust on-premise solution to keep teams working harmoniously: The Tekla Structures Multi User Server.
Today, we are taking a technical deep dive into versions 23 and 20. While these are not the latest releases (the current numbering has since evolved), many legacy projects and specific client workflows still rely on these stable versions.
Why Multi User (MU)? The Multi User Server allows multiple detailers to work on the same model simultaneously. Instead of "Check-out/Check-in" locks, Tekla uses a live database. When you save, your changes are immediately visible to everyone else (provided they refresh).
Version 20 (v20.0 – v20.9) Released during the "golden era" of Tekla’s transition from v19, Version 20 was a workhorse.
Version 23 (v23.0 – v23.9) Version 23 marked a maturity point. By this release, Trimble had ironed out the kinks of the previous UI overhaul.
Setting up a MU for v20/v23 (A Quick Refresher) If you are resurrecting an old server for a legacy project, remember these three rules:
The "Auto-Save" Trap One major behavior difference between v20 and v23:
Should you still use them?
Final Verdict Version 20 was the reliable diesel engine. Version 23 was the fuel-injected upgrade. Neither has the fancy web interface of today's solutions, but when you need to get 5 detailers modeling a concrete core wall on a tight deadline without paying for cloud credits, the Tekla Multi User Server 23/20 is still a legend.
Do you still have a v23 MU server running in your server room? Let us know in the comments below.
Tags: #TeklaStructures #BIM #StructuralEngineering #TeklaMU #LegacySoftware
Product Overview
Tekla Structures Multi-User Server 23.20 is a powerful software solution designed for structural steel and concrete construction projects. It's a multi-user server that enables multiple users to collaborate on the same project simultaneously, facilitating efficient teamwork and reducing errors.
Key Features
Pros
Cons
System Requirements
Target Audience
Tekla Structures Multi-User Server 23.20 is designed for:
Conclusion
Tekla Structures Multi-User Server 23.20 is a robust software solution that enables efficient collaboration and data management for structural steel and concrete construction projects. While it may have a steep learning curve and compatibility issues, its benefits, including enhanced collaboration and increased productivity, make it a valuable investment for businesses and organizations in the construction industry.
Rating: 4.5/5
Tekla Structures Multi-User Server (Version 2.3.2.0) is an essential utility for local design teams who need to collaborate on the same 3D structural model in real-time. While newer cloud-based solutions like Tekla Model Sharing are available, the Multi-User Server remains a reliable, cost-effective choice for teams working on a shared local network. Key Features & Functionality
Real-Time Synchronization: Allows multiple users to connect to a central database, enabling them to see updates from colleagues as soon as they save their work to the master model.
Centralized Master Model: The system maintains one "master model" on a server, while each user works in a local "working model." This structure minimizes the risk of data corruption.
Low Performance Requirements: The server software is lightweight and does not require high-end hardware; it can even run on the same machine as the Tekla License Server.
Multi-Instance Support: Version 2.3 allows for setting up multiple server instances on a single computer by assigning different TCP ports (default is 1238), which helps in organizing different projects or teams. Pros and Cons Getting started with multi-user | Trimble User Assistance
Tekla Structures Multiuser Server 2.3 is a software application that enables multiple users to work concurrently on the same Tekla Structures 3D model. It functions by hosting a central database on a server machine, which synchronizes real-time modifications and updates across the entire team to prevent model conflicts. Key Features & Technical Details
Real-time Collaboration: Allows team members to see modifications as soon as they are made by others.
Compatibility: The multiuser server is typically used for versions of Tekla Structures up to version 2020. For newer versions, Trimble generally recommends Tekla Model Sharing as a more advanced alternative.
Network Requirements: By default, the server uses TCP port 1238 for communication.
Conversion: You can convert a single-user model into a multi-user model through the "Open" menu in the Tekla Structures setup screen. Installation & Setup
Download: The installation package is available on the Trimble User Assistance portal under the "All Downloads" section for version 2020 and older.
Server Hosting: The software must be installed on a dedicated server or a workstation that acts as the host for the multiuser service.
Client Connection: Once the service is running, users connect to the server by entering the server's name or IP address when opening a model in Tekla Structures. Tekla Structures Multi User Server 23 20 - Google Groups
Unlocking Real-Time Collaboration: A Deep Dive into Tekla Structures Multi-User Server 2.3.20
In the world of high-stakes structural detailing and BIM, speed and coordination are everything. While many teams are moving toward cloud-based solutions, the Tekla Structures Multi-User Server 2.3.20 remains a cornerstone for firms operating on robust local networks.
This post explores how to maximize your collaborative efficiency using this version and why it’s still a vital tool in the Trimble Tekla ecosystem. Why Multi-User Mode?
The multi-user system allows several detailing professionals to access the same master model simultaneously. Unlike traditional "copy and merge" workflows, this real-time environment ensures:
Single Source of Truth: All work is saved to one master model on your file server.
No Duplicates: Eliminates the risk of controlling or tracking multiple model versions.
Instant Coordination: Users are immediately aware of others' progress, reducing onsite errors. Key Features of Version 2.3.20
Version 2.3.20 focuses on stability and seamless connectivity within a Local Area Network (LAN).
Multi-Instance Capability: You can run multiple instances of the server on a single machine by assigning different TCP ports (default is 1238).
Efficiency for Large Teams: A single service can handle multiple models, though performance is best when models are distributed across separate services if the team size is large.
Service-Based Operation: The server runs as a Windows service, meaning it starts automatically with the computer and requires no manual login to remain active. Best Practices for Peak Performance
To keep your multi-user environment running smoothly, follow these industry-standard best practices:
Version Uniformity: Ensure every user is on the exact same Tekla Structures version, service pack, and environment.
Clean Cache: Regularly synchronize and keep local cache folders updated to prevent lag.
Network Speed: Since model data is stored centrally, a fast, reliable LAN connection is mandatory for good performance.
Sequential Saves: Remember that the model locks during opening, saving, and numbering; coordinate with your team to avoid bottlenecking these operations. Multi-User Server vs. Model Sharing: Which is for you?
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.
On every client machine, the IP address or Hostname of the server must be defined.