Sap2000 Student Version

Versi SAP2000 Student Version 7.40 di atas dapat anda down-load secara bebas dan digunakan sesuai dengan maksud pembuatnya yaitu untuk sarana belajar dan bukan untuk maksud komersil (misal proyek). Karena ukurannya relatif cukup besar maka dibagi dalam beberapa bagian dalam bentuk file.zip sebagai berikut. SAP2000 is general-purpose civil-engineering software ideal for the analysis and design of any type of structural system. Basic and advanced systems, ranging from 2D to 3D, of simple geometry to complex, may be modeled, analyzed, designed, and optimized using a practical and intuitive object-based modeling environment that simplifies and streamlines the engineering process. For graduate students only Software Center has SAP2000 available for installation on your desktop computer. Laptop Installation Instructions (this is a student version, and is not fully functional) The following instructions are for installing SAP2000 on a personal device. Download the installer here, and run it when it is finished downloading. Free sap2000 student version download software at UpdateStar - Installer package for driver version 11.5 and Intel PROSet/Wireless Tools version 11.5 supporting Intel(R) Wireless WiFi Link 4965AGN Mini Card and Intel(R) PRO/Wireless 3945ABG Network Connection Mini Card on Windows Vista operating. SAP Learning Hub, student edition is a online platform that provides instant access to SAP Learning Rooms where learners are free to interact with each other and SAP subject matter experts.

Skip to end of metadataGo to start of metadata

This space is devoted to SAP2000. Please visit the Technical Knowledge Base for documentation on topics common to all CSI Software.

SAP2000 is general-purpose civil-engineering software ideal for the analysis and design of any type of structural system. Basic and advanced systems, ranging from 2D to 3D, of simple geometry to complex, may be modeled, analyzed, designed, and optimized using a practical and intuitive object-based modeling environment that simplifies and streamlines the engineering process. The SAPFire ® Analysis Engine integral to SAP2000 drives a sophisticated finite-element analysis procedure. An additional suite of advanced analysis features are available to users engaging state-of-the-art practice with nonlinear and dynamic consideration. Created by engineers for effective engineering, SAP2000 is the ideal software tool for users of any experience level, designing any structural system.

Integrated modeling templates, code-based loading assignments, advanced analysis options, design-optimization procedures, and customizable output reports all coordinate across a powerful platform to make SAP2000 especially useful for practicing professionals.

SAP2000 is also an excellent medium for education. Open SAP2000 and follow the Watch & Learn video series to receive not only instruction on software use, but also insight into structural engineering philosophy and practice.

On this page:

Built-in modeling templates, a versatile and user-friendly interface, intuitive controls and features all combine to simplify and expedite a sophisticated object-based modeling process. A broad range of modeling options provide for methods and technologies at the forefront of structural engineering. Model domain may be component, system, or global-level in scope, while encompassing sub-grade components and soil-structure interaction. Grid line, snap, and replication tools are a few of the many practical features which make the modeling environment and process accessible to beginners, and sophisticated for advanced users.

Linear or curved members, cables and post-tensioned tendons, link elements to model springs, dampers, isolators, and the associated nonlinear and hysteretic behavior, framing, shell or multi-layered shell, solid elements with isoperimetric formulation and nonlinear response are all modeling options for object assembly in SAP2000. When preferred structural members are not provided in the extensive libraries of SAP2000, Section Designer is available for custom cross-section design. Users specify geometry and material composition before Section Designer automatically calculates member properties and generates biaxial-interaction and moment-curvature diagrams.

Nonlinear-fiber-hinge assignment is another advanced modeling technique available. SAP2000 implements code-based or empirical hinging behavior by modeling geometry and materials as discrete points within a cross-section, then correlating these discretized areas with their associated nonlinear behaviors. Limit-state and hysteretic considerations may also be implemented under nonlinear-static and dynamic analyses.

Once an object-based model is created, the SAPFire ® Analysis Engine automatically converts the assembly into a finite-element model by meshing the material domain with an efficient network of quadrilateral sub-elements. Joint-interpolation algorithms drive automatic edge-constraint technology to connect mesh mismatch. The Reshaper Tool is then available for mesh reshaping and refinement.

SAP2000 is the ideal tool for modeling structural systems of any complexity and any project type. Buildings, bridges, transportation infrastructure, such specialty structures as dams, sports facilities, and offshore systems are a few examples of the limitless design possibilities.

Powerful built-in templates also simplify and expedite the load-application process. Seismic, wind, vehicle, wave, and thermal forces may all be automatically generated and assigned according to a suite of code-based guidelines. Users are free to define and envelope an unlimited number of load cases and combinations.

Moving-load-generation features and a library of AASHTO vehicle applications provide for evaluation of transportation infrastructure systems. For marine systems, wave-load-generation features consider the static and dynamic response of wave, current, buoyancy, and wind while capturing inertial effects.

Enveloped load conditions may be coupled with certain advanced analysis and construction techniques (P-Delta effect, segmental construction, etc.) for additional insight into structural response.

A range of innovative analysis techniques are integrated into the capabilities of SAP2000. Users are free to supplement the standard yet sophisticated analysis process by implementing advanced features for nonlinear and dynamic consideration. This versatility makes SAP2000 a practical and productive tool for any analysis type ranging from simple static, linear-elastic to more complex dynamic, nonlinear-inelastic.

To begin, the SAPFire ® Analysis Engine drives analysis optimization with multiple 64-bit solvers. Options include Eigen analysis (with auto shifting for ill-conditioned relations) and Ritz analysis (for expedited convergence). P-delta effect captures geometric nonlinearity. Buckling analyses provide insight into structural stability through methods characterizing linear buckling (which considers multiple buckling modes under nonlinear-static or dynamic application), nonlinear buckling (which considers P-delta and large-deflection effects), snap-through buckling, and progressive collapse. Material nonlinearity capture inelastic and limit-state behavior, along with such time-dependent phenomena as creep and shrinkage behavior in reinforced-concrete systems. Plastic hinging may be specified in flexural members according to code-based standards or empirical data. Tension and compression-only springs may be assigned with limits and nonlinear attributes to simulate support plasticity.

Static and dynamic methods are available for earthquake simulation. Nonlinear-static-pushover analyses may consider modal, uniform, or user-defined lateral load patterns, plastic-hinging behavior of slender elements, inelastic response of shear walls, floor slabs, and steel plates, and then formulate demand-capacity, damping, and performance-point calculations with customizable summary reports.

Dynamic methods include response-spectrum (for likely maximum seismic response given pseudo-spectral acceleration vs. structural period curve), power-spectral-density and steady-state (for fatigue behavior with optional damping and complex-impedance properties), and time-history analyses. Time histories may follow modal or direct-integration methods, and they may be chained together and enveloped with such advanced analyses as P-delta and staged-construction procedures.

Staged-construction features are comprehensive. The construction sequence is scheduled with Gantt-chart options, enveloped with performance measures, and paired with analysis procedures. At each construction stage, evaluation may consider static or dynamic structural response, support reactions, geometric and material nonlinearity (including buckling, creep, and shrinkage), tendon and cable application with target-tensioning, etc. The Model Alive feature is available for small to medium-sized projects to analyze real or possible structural modifications.

Design is fully integrated with the analysis process, enveloping results before automatically sizing steel members and designing reinforced-concrete sections. Automatic steel, concrete, aluminum and cold-formed-framing design code checks ensure that structures meet criteria of American, Canadian, and a variety of international standards.

Output and display options are intuitive and practical. Finalized member design, deformed geometry per load combination or mode shape, moment, shear, and axial-force diagrams, section-cut response displays, and animation of time-dependent displacements outline a few of the graphics available upon conclusion of analysis. SAP2000 automatically generates reports for the presentation of images and data. Built-in and customizable templates are available to users for specialized formatting.

SAP2000 also provides a suite of interoperability features. Output reports may be transferred to Microsoft platforms in RTF file format or websites in HTML. SAP2000 models may import and export between CIS/2 STEP, SDNF, AutoCAD‏, Frameworks Plus, IGES, and Prosteel.

The SAP2000 Open Application Programming Interface (OAPI) allows developers to create custom programming applications linking related design platforms to SAP2000 function. Visual Basic and most standard languages are supported. Visit the OAPI page of the CSI Website to learn more about interoperability with SAP2000.

Several different levels of capability are offered for the SAP2000 product. Each subsequent level provides an additional set of features. Please refer to the Levels and Features page of the CSI Website for details.

Refer to the SAP2000 Tutorial page.

Refer to the SAP2000 Test Problems page.

Aviram, A., Mackie, K., Stojadinovic, B. (2008). Guidelines for Nonlinear Analysis of Bridge Structures in California. Berkeley, CA: Pacific Earthquake Engineering Research (PEER) Center.

Skip to end of metadataGo to start of metadata

A lower software version may be run using a higher version license (please see the specific examples below). See the version specific examples below. This may require creating and using a text file named level.txt within the installation folder of the earlier product version.

On this page:

To create a level.txt file, create a text file with the Product Level and Product Version of the current license (please see examples below for exact specifications). Rename the file as level.txt and copy into the location listed below.

Location of level.txt file

Standalone license – For a standalone license, the level.txt file should be located in the lower version program folder, which contains the program executable (*.exe). The license file ('lservrc' file) of the current version should also be copied into this same folder as the level.txt.

Network license (with full product installation on client machine)– The level.txt file should be located on the client machine in the lower version program folder, which contains program executable (*.exe).

Network license with workstation installation on client machine – For a workstation installation, the level.txt file should be located on the server in the lower version program folder, which contains program executable (*.exe).

NOTE: This process may not work when versions are separated by more than one major release, in which case the license file for the older version should be requested. It is not possible to run V15 using V16 license, because the licensing system has changed between program versions.

Running CSiBridge v21 using a CSiBridge v22 license

When running CSiBridge v21 using a CSiBridge v22, the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

Product level should be the level of the current license, for example: 'PLUS', 'ADVANCED' or 'ADVANCEDRATING', etc. See level.txt for a list of levels for each CSI program. Product version should be the version number of the current license.

For example:

ADVANCED 22

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- Web-Activated License:
  - License file:
    - The CSiBridge v22 license must be activated on this machine.
    - Copy the 'lservrc' file from Computers and Structures > CSiBridge 22 folder into the Computers and Structures > CSiBridge 21 folder.
    - The 'lservrc' file must be copied each time the v22 license is activated on this machine. Once v22 has been deactivated from this machine, the CSiBridge v21 product will also stop working.
  - Level.txt: The level.txt file will also be copied into the CSiBridge v21 folder (Computers and Structures > CSiBridge 21)
- Manual License (such as license locked to USB key):
  - License file: Copy the CSiBridge v22 'lservrc' file into the Computers and Structures > CSiBridge 21 folder (from Computers and Structures > CSiBridge 22 folder).
  - Level.txt: The level.txt file will also be copied into the CSiBridge v21 folder (Computers and Structures > CSiBridge 21)

Network license – The CSiBridge v22 license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the CSiBridge 21 folder which contains the CSiBridge.exe.

Running CSiBridge v20 using a CSiBridge v21 license

PLEASE NOTE: Only the latest version of CSiBridge v20.2.1 will work with the CSiBridge v21 license. Please email support (support@csiamerica.com) to download CSiBridge v20.2.1. This version is not available for download from the CSI Installation Wizard. Please uninstall your current CSiBridge v20 before installing the new v20.2.1. CSiBridge v20.2.1 is is identical to CSiBridge v20.2.0 except for the update to the licensing.

When running CSiBridge v20 using a CSiBridge v21 license, a level.txt is not required.

Please see your licensing option below for the appropriate locations for where the activated license should reside:

Standalone license –
- License file: The CSiBridge v21 license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > CSiBridge 21 folder into the Computers and Structures > CSiBridge 20 folder. The 'lservrc' file must be copied each time the v21 license is activated on this machine. Once v21 has been deactivated from this machine, CSiBridge v20 will also stop working.

Network license – The CSiBridge v21 license will reside on the server for a network license. Once the client machines have been updated to the correct version of CSiBridge v20.2.1, the client machine will automatically pick up the CSiBridge v21 network license.

Running CSiBridge 2017 (v19) using a CSiBridge v20 (2018) license

When running CSiBridge 2017 (v19) using a CSiBridge v20 (2018), the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

Product level should be the level of the current license, for example: 'PLUS', 'PLUSRATING', 'ADVANCED' or 'ADVANCEDRATING', etc. See level.txt for a list of levels for each CSI program. Product version should be the version number of the current license. Please note in this case, the product version for the current license is '2018' and not version '20'.

For example:

ADVANCED 2018

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- Web-Activated License:
  - License file:
    - The CSiBridge v20 (2018) license must be activated on this machine.
    - Copy the 'lservrc' file from Computers and Structures > CSiBridge 20 folder into the Computers and Structures > CSiBridge 2017 folder.
    - The 'lservrc' file must be copied each time the v20 license is activated on this machine. Once v20 has been deactivated from this machine, the CSiBridge 2017 (v19) product will also stop working.
  - Level.txt: The level.txt file will also be copied into the CSiBridge 2017 folder (Computers and Structures > CSiBridge 2017)
- Manual License (such as license locked to USB key):
  - License file: Copy the CSiBridge v20 (2018) 'lservrc' file into the Computers and Structures > CSiBridge 2017 folder (from Computers and Structures > CSiBridge 20 folder).
  - Level.txt: The level.txt file will also be copied into the CSiBridge 2017 folder (Computers and Structures > CSiBridge 2017)

Network license – The CSiBridge v20 (2018) license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the CSiBridge 2017 folder which contains the CSiBridge.exe.

Running CSiBridge 2016 (v18) using a CSiBridge 2017 (v19) license

When running CSiBridge 2016 (v18) using a CSiBridge 2017 (v19), the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

For example:

Sap2000 Student Version Download Free

ADVANCED 2017

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- License file: The CSiBridge 2017 (v19) license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > CSiBridge 2017 folder into the Computers and Structures > CSiBridge 2016 folder. The 'lservrc' file must be copied each time the 2017 license is activated on this machine. Once 2017 has been deactivated from this machine, CSiBridge 2016 (v18) will also stop working.
- Level.txt: The level.txt file will also be copied into the CSiBridge 2016 folder (Computers and Structures > CSiBridge 2016)

Network license – The CSiBridge 2017 (v19) license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the CSiBridge 2016 folder which contains the CSiBridge.exe.

Running CSiBridge 2015 (v17) using a CSiBridge 2016 (v18) license

PLEASE NOTE: Only the latest version of CSiBridge 2015 (v17.3.0 RMS 8.6) will work with the CSiBridge 2016 license. Please email support (support@csiamerica.com) to download CSiBridge 2015. This version is not available for download from the CSI Installation Wizard. Please uninstall your current CSiBridge 2015 before installing the new CSiBridge 2015 (v17.3.0 RMS 8.6). CSiBridge 2015 v17.3.0 RMS 8.6 is is identical to CSiBridge 2015 v17.3.0 except for the update to the licensing.

When running CSiBridge 2015 (v17) using a CSiBridge 2016 (v18), a level.txt is not required.

Please see your licensing option below for the appropriate locations for where the activated license should reside:

Standalone license –
- License file: The CSiBridge 2016 license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > CSiBridge 2016 folder into the Computers and Structures > CSiBridge 2015 folder. The 'lservrc' file must be copied each time the 2016 license is activated on this machine. Once 2016 has been deactivated from this machine, CSiBridge 2015 (v17) will also stop working.

Network license – The CSiBridge 2016 (v18) license will reside on the server for a network license. Once the client machines have been updated to the correct version of CSiBridge 2015 (v17.3.0 RMS 8.6), the client machine will automatically pick up the CSiBridge 2016 network license.

Running CSiBridge 2014 (v16) using a CSiBridge 2015 (v17) license

PLEASE NOTE: Only CSiBridge 2014 (v16.1.0/1) will work with the CSiBridge 2015 (v17) license. Please check you have upgraded to this version. CSiBridge v16.1.0/1 is identical to CSiBridge v16.1.0 except for the update to the licensing.

When running CSiBridge 2014 (v16) using a CSiBridge 2015 (v17), the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

For example:

ADVANCED 2015

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- License file: The CSiBridge 2015 (v17) license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > CSiBridge 2015 folder into the Computers and Structures > CSiBridge 2014 folder. The 'lservrc' file must be copied each time the 2015 license is activated on this machine. Once 2015 has been deactivated from this machine, CSiBridge 2014 (v16) will also stop working.
- Level.txt: The level.txt file will also be copied into the CSiBridge 2014 folder (Computers and Structures > CSiBridge 2014)

Network license – The CSiBridge 2015 (v17) license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the CSiBridge 2014 folder which contains the CSiBridge.exe.

Running ETABS v17 using an ETABS v18 license

When running ETABS v17 using an ETABS v18 license, the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

Product level should be the level of the current license, for example: 'PLUS', 'NONLINEAR', or 'ULTIMATE', etc. See level.txt for a list of levels for each CSI program. Product version should be the version number of the current license.

For example:

ULTIMATE 18

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- Web-Activated License:
  - License file:
    - The ETABS v18 license must be activated on this machine.
    - Copy the 'lservrc' file from Computers and Structures > ETABS 18 folder into the Computers and Structures > ETABS 17 folder.
    - The 'lservrc' file must be copied each time the v18 license is activated on this machine. Once v18 has been deactivated from this machine, the ETABS v17 product will also stop working.
  - Level.txt: The level.txt file will also be copied into the ETABS 17 folder (Computers and Structures > ETABS 17)
- Manual License (such as license locked to USB key):
  - License file: Copy the ETABS v18 'lservrc' file into the Computers and Structures > ETABS 17 folder (from Computers and Structures > ETABS 18 folder).
  - Level.txt: The level.txt file will also be copied into the ETABS 17 folder (Computers and Structures > ETABS 17)

Network license – The ETABS v18 license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the ETABS 17 folder which contains the ETABS.exe.

Running ETABS 2016 using an ETABS 17 license

PLEASE NOTE: Only the latest version of ETABS 2016 (v16.2.2) will work with the ETABS v17 license. Please email support (support@csiamerica.com) to download ETABS v16.2.2. This version is not available for download from the CSI Installation Wizard. ETABS v16.2.2 is functionally identical to ETABS v16.2.1 except for the update to the licensing. Model files are interchangeable between the two versions, and both versions produce identical results to within the numerical accuracy of the computer.

When running ETABS 2016 using a ETABS 17 license, a level.txt is not required.

Please see your licensing option below for the appropriate locations for where the activated license should reside:

Standalone license –
- License file: The ETABS v17 license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > ETABS 17 folder into the Computers and Structures > ETABS 2016 folder. The 'lservrc' file must be copied each time the ETABS v17 license is activated on this machine. Once the ETABS v17 license has been deactivated from this machine, ETABS 2016 product will also stop working.

Network license – The ETABS v17 license will reside on the server for a network license. Once the client machines have been updated to the correct version of ETABS 2016 (v16.2.2), the client machine will automatically pick up the ETABS v17 network license.

Running ETABS 2015 using an ETABS 2016 license

PLEASE NOTE: Only the latest version of ETABS 2015 (v15.2.3) will work with the ETABS 2016 license. Please email support (support@csiamerica.com) to download ETABS 2015 (v15.2.3). This version is not available for download from the CSI Installation Wizard. ETABS v15.2.3 is functionally identical to ETABS v15.2.2 except for the update to the licensing. Model files are interchangeable between the two versions, and both versions produce identical results to within the numerical accuracy of the computer.

When running ETABS 2015 using a ETABS 2016 license, a level.txt is not required.

Please see your licensing option below for the appropriate locations for where the activated license should reside:

Standalone license –
- License file: The ETABS 2016 license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > ETABS 2016 folder into the Computers and Structures > ETABS 2015 folder. The 'lservrc' file must be copied each time the ETABS 2016 license is activated on this machine. Once the ETABS 2016 license has been deactivated from this machine, ETABS 2015 product will also stop working.

Network license – The ETABS 2016 license will reside on the server for a network license. Once the client machines have been updated to the correct version of ETABS 2015 (v15.2.3), the client machine will automatically pick up the ETABS 2016 network license.

Running ETABS 2013 using an ETABS 2015 license

When running ETABS 2013 using a ETABS 2015 license, the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

Product level should be the level of the current license, for example: 'PLUS', 'NONLINEAR' or 'ULTIMATE', etc. See level.txt for a list of levels for each CSI program. Product version should be the version number of the current license.

For example:

NONLINEAR 2015

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- License file: The ETABS 2015 license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > ETABS 2015 folder into the Computers and Structures > ETABS 2013 folder. The 'lservrc' file must be copied each time the ETABS 2015 license is activated on this machine. Once ETABS 2015 has been deactivated from this machine, ETABS 2013 will also stop working.
- Level.txt: The level.txt file will also be copied into the ETABS 2013 folder (Computers and Structures > ETABS 2013)

Network license – The ETABS 2015 license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the ETABS 2013 folder which contains the ETABS.exe.

Running SAFE 2014 using a SAFE 2016 license

PLEASE NOTE: Only the latest version of SAFE 2014 (v14.2.1) will work with the SAFE 2016 license. This new version of SAFE 2014 (v14.2.1) can be downloaded from here (it is not available for download from the CSI Installation Wizard). SAFE v14.2.1 is functionally identical to SAFE v14.2.0 except for the update to the licensing. Model files are interchangeable between the two versions, and both versions produce identical results to within the numerical accuracy of the computer.

When running SAFE 2014 using a SAFE 2016 license, a level.txt is not required.

Please see your licensing option below for the appropriate locations for where the activated license should reside:

Standalone license –
- License file: The SAFE 2016 license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > SAFE 2016 folder into the Computers and Structures > SAFE 2014 folder. The 'lservrc' file must be copied each time the SAFE 2016 license is activated on this machine. Once the SAFE 2016 license has been deactivated from this machine, SAFE 2014 product will also stop working.

Network license – The SAFE 2016 license will reside on the server for a network license. Once the client machines have been updated to the correct version of SAFE 2014 (v14.2.1), the client machine will automatically pick up the SAFE 2014 network license.

Running SAP2000 v21 using a SAP2000 v22 license

When running SAP2000 v21 using a SAP2000 v22, the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

Product level should be the level of the current license, for example: 'BASIC', 'PLUS', 'ADVANCED' or 'ULTIMATE', etc. See level.txt for a list of levels for each CSI program. Product version should be the version number of the current license.

For example:

ADVANCED 22

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- Web-Activated License:
  - License file:
    - The SAP2000 v22 license must be activated on this machine.
    - Copy the 'lservrc' file from Computers and Structures > SAP2000 22 folder into the Computers and Structures > SAP2000 21 folder.
    - The 'lservrc' file must be copied each time the v22 license is activated on this machine. Once v22 has been deactivated from this machine, the SAP2000 v21 product will also stop working.
  - Level.txt: The level.txt file will also be copied into the SAP2000 v21 folder (Computers and Structures > SAP2000 21)
- Manual License (such as license locked to USB key):
  - License file: Copy the SAP2000 v22 'lservrc' file into the Computers and Structures > SAP2000 21 folder (from Computers and Structures > SAP2000 22 folder).
  - Level.txt: The level.txt file will also be copied into the SAP2000 v21 folder (Computers and Structures > SAP2000 21)

Network license – The SAP2000 v22 license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the SAP2000 21 folder which contains the SAP2000.exe.

Running SAP2000 v20 using a SAP2000 v21 license

PLEASE NOTE: Only the latest version of SAP2000 v20.2.1 will work with the SAP2000 v21 license. Please email support (support@csiamerica.com) to download SAP2000 v20.2.1. This version is not available for download from the CSI Installation Wizard. Please uninstall your current SAP2000 v20 before installing the new v20.2.1. SAP2000 v20.2.1 is is identical to SAP2000 v20.2.0 except for the update to the licensing.

When running SAP2000 v20 using a SAP2000 v21 license, a level.txt is not required.

Please see your licensing option below for the appropriate locations for where the activated license should reside:

Standalone license –
- License file: The SAP2000 v21 license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > SAP2000 21 folder into the Computers and Structures > SAP2000 20 folder. The 'lservrc' file must be copied each time the v21 license is activated on this machine. Once v21 has been deactivated from this machine, SAP2000 v20 will also stop working.

Network license – The SAP2000 v21 license will reside on the server for a network license. Once the client machines have been updated to the correct version of SAP2000 v20.2.1, the client machine will automatically pick up the SAP2000 v21 network license.

Running SAP2000 v19 using a SAP2000 v20 license

When running SAP2000 v19 using a SAP2000 v20 license, the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

For example:

ADVANCED 20

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- Web-Activated license:
  - License file:
    - The SAP2000 v20 license must be activated on this machine.
    - Copy the 'lservrc' file from Computers and Structures > SAP2000 20 folder into the Computers and Structures > SAP2000 19 folder.
    - The 'lservrc' file must be copied each time the v20 license is activated on this machine. Once v20 has been deactivated from this machine, the SAP2000 v19 product will also stop working.
  - Level.txt: The level.txt file will also be copied into the SAP2000 19 folder (Computers and Structures > SAP2000 19)
- Manual License (such as license locked to USB key):
  - License file: Copy the SAP2000 v20 'lservrc' file into the Computers and Structures > SAP2000 19 folder (from Computers and Structures > SAP2000 20 folder).
  - Level.txt: The level.txt file will also be copied into the SAP2000 19 folder (Computers and Structures > SAP2000 19)

Network license – The SAP2000 v20 license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the SAP2000 19 folder which contains the SAP2000.exe.

Running SAP2000 v18 using a SAP2000 v19 license

When running SAP2000 v18 using a SAP2000 v19 license, the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

For example:

ADVANCED 19

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- Web-Activated License:
  - License file:
    - The SAP2000 v19 license must be activated on this machine.
    - Copy the 'lservrc' file from Computers and Structures > SAP2000 19 folder into the Computers and Structures > SAP2000 18 folder.
    - The 'lservrc' file must be copied each time the v19 license is activated on this machine. Once v19 has been deactivated from this machine, SAP2000 v18 will also stop working.
  - Level.txt: The level.txt file will also be copied into the SAP2000 18 folder (Computers and Structures > SAP2000 18)
- Manual License (such as license locked to USB key):
  - License file: Copy the SAP2000 v19 'lservrc' file into the Computers and Structures > SAP2000 18 folder (from Computers and Structures > SAP2000 19 folder).
  - Level.txt: The level.txt file will also be copied into the SAP2000 18 folder (Computers and Structures > SAP2000 18)

Network license – The SAP2000 v19 license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the SAP2000 18 folder which contains the SAP2000.exe.

Running SAP2000 v17 using a SAP2000 v18 license

PLEASE NOTE: Only the latest version of SAP2000 v17.3.0 RMS 8.6 will work with the SAP2000 v18 license. Please email support (support@csiamerica.com) to download SAP2000 v17.3.0 RMS 8.6. This version is not available for download from the CSI Installation Wizard. Please uninstall your current SAP2000 v17 before installing the new v17.3.0 RMS 8.6. SAP2000 v17.3.0 RMS 8.6 is is identical to SAP2000 v17.3.0 except for the update to the licensing.

When running SAP2000 v17 using a SAP2000 v18 license, a level.txt is not required.

Please see your licensing option below for the appropriate locations for where the activated license should reside:

Standalone license –
- License file: The SAP2000 v18 license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > SAP2000 18 folder into the Computers and Structures > SAP2000 17 folder. The 'lservrc' file must be copied each time the v18 license is activated on this machine. Once v18 has been deactivated from this machine, SAP2000 v17 will also stop working.

Network license – The SAP2000 v18 license will reside on the server for a network license. Once the client machines have been updated to the correct version of SAP2000 v17.3.0 RMS 8.6, the client machine will automatically pick up the SAP2000 v18 network license.

Running SAP2000 v16 using a SAP2000 v17 license

When running SAP2000 v16 using a SAP2000 v17 license, the level.txt file created will contain one line with the following information:

Line 1: [Product Level] [Product Version]

For example:

ADVANCED 17

Please see your licensing option below for the appropriate locations for where the level.txt and activated license should reside:

Standalone license –
- License file: The SAP2000 v17 license must be activated on this machine. Copy the 'lservrc' file from Computers and Structures > SAP2000 17 folder into the Computers and Structures > SAP2000 16 folder. The 'lservrc' file must be copied each time the v17 license is activated on this machine. Once v17 has been deactivated from this machine, SAP2000 v16 will also stop working.
- Level.txt: The level.txt file will also be copied into the SAP2000 16 folder (Computers and Structures > SAP2000 16)

Network license – The SAP2000 v17 license will reside on the server for a network license. The level.txt file will reside on the client machine, copied into the SAP2000 16 folder which contains the SAP2000.exe.

Running SAP2000 v14 using a SAP2000 v15 license

When running SAP2000 v14 using a SAP2000 v15 Advanced license, the level.txt file created will contain the following two lines:

Line 1: Product Level. Enter the level of the current license, for example: 'BASIC', 'PLUS', 'ADVANCED' or 'ULTIMATE', etc. See level.txt for a list of levels for each CSI program.
Line 2: Product Version. Enter the version number of the current license, for example, '15'.

Sap2000 Evaluation Version

For example:

ADVANCED
15

Listed below are the installation and licensing combinations with the appropriate locations for where the level.txt and v15 'lservrc' file should reside:

Standalone installation with standalone license – If running a standalone installation with a standalone license, the SAP2000 v15 'lservrc' file must be copied into the SAP2000 14 folder containing the SAP2000.exe. The level.txt file will also be copied into this same folder (SAP2000 14 folder).

Standalone installation with network license – If running a standalone installation with a network license, the level.txt file should be copied into the SAP2000 14 folder, containing the SAP2000.exe, on the client machine.

Workstation installation – If the client machine has a workstation installation, then the level.txt file should be copied onto the server under the SAP2000 14 Server folder, which contains the SAP2000.exe.

To use SAP2000 V15 license to run SAP2000 V14 with the add-on module license (Bridge, Staged Construction, Off-Shore), the SAP2000 V14.2.5 program installation and the SAP2000 V15 Ultimate license are required.

NOTE: The *.ini file takes precedence over the level.txt file, therefore it may be best to leave the field for the program level blank in the *.ini file.

level.txt