A lower software version may be run using a higher version license (please see the specific examples below). This may require creating and using a text file named level.txt within the installation folder of the earlier product version. However, this is not applicable between current web-activated licenses and previous conventional licenses (therefore, for example, the SAP2000 v15 product cannot use a SAP2000 v16 license).

Level.txt file

Create a level.txt file by creating 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).
   

Example: 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]

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 19 

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 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)

• 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.

Example: 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]

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. 

For example:

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.

Example: Running ETABS 2015 using a ETABS 2016 license

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. 

Example: Running SAP2000 v17 using a SAP2000 v18 license

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. 

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

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.

Example: 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.

Example: 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]

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 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.

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

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]

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. 

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.

Example: 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'.

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.

See Also

• Expedite software launch
• level.txt