...
A
...
lower
...
software
...
version
...
may
...
be
...
run
...
using
...
a
...
higher
...
version
...
license
...
by
...
creating
...
a
...
text
...
file
...
named
...
...
within
...
the
...
installation
...
folder
...
of
...
the
...
earlier
...
product
...
version.
...
Level.txt
...
file
...
The
...
...
text
...
file
...
should
...
have
...
two
...
lines,
...
described
...
as
...
follows:
...
- Line
...
- 1:
...
- Product
...
- Level
...
- .
...
- Depending
...
- on
...
- the
...
- product
...
- level,
...
- enter
...
- (in
...
- caps)
...
- 'BASIC',
...
- 'PLUS',
...
- 'ADVANCED'
...
- or
...
- 'ULTIMATE',
...
- etc.
...
- See
...
...
- for
...
- a
...
- list
...
- of
...
- levels
...
- for
...
- each
...
- CSI
...
- program.
...
- Line
...
- 2:
...
- Product
...
- Version
...
- .
...
- Enter
...
- only
...
- the
...
- version
...
- number
...
- of
...
- the
...
- current
...
- license,
...
- for
...
- example,
...
- '15'.
...
| Info |
|---|
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. {info} {hidden-content} *Related Incident:* * {incident:no=46677|comment=Using V14 license to run SAP2000 V11} {hidden-content} h3. Location * *Standalone installation* -- For a standalone installation, the level.txt file should be located in the program folder with the executable. Further, the license file of the current version should be copied into the installation folder of the previous version. * *Workstation installation* -- For a workstation installation, the level.txt file should be located on the server with the executable. h1. Example: Running SAP2000 v14 using a v15 license Some additional procedures which concern running [SAP2000|sap2000:home] v14 using a v15 license are listed as follows: * *Standalone installation with standalone license* -- When running a standalone installation, the SAP2000 "lservrc" file must be copied into the version 14 \*.exe folder. * *Standalone installation with network license* -- If you are running a standalone installation but getting the [network license|Network license (conventional)], the level.txt file should be copied into the SAP2000 version 14 \*.exe folder. * *Workstation installation* -- For workstation installations from the server, the level.txt file should be copied into the SAP2000 version 14 Server > License Manager folder. {info} *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. {info} {hidden-content} *Related Email:* * {email:date=11/14/2012|from=Kim|to=Mike|subject=Level.txt notes|comment=Level.txt notes on SAP2000 v14 using v15 license|id=9896232} {hidden-content} h1. See Also * [kb:Expedite software launch] * [level.txt|kb:level.txt]requested. |
Location
- Standalone installation – For a standalone installation, the level.txt file should be located in the program folder with the executable. Further, the license file of the current version should be copied into the installation folder of the previous version.
- Workstation installation – For a workstation installation, the level.txt file should be located on the server with the executable.
Example: Running SAP2000 v14 using a v15 license
Some additional procedures which concern running SAP2000 v14 using a v15 license are listed as follows:
- Standalone installation with standalone license – When running a standalone installation, the SAP2000 "lservrc" file must be copied into the version 14 *.exe folder.
- Standalone installation with network license – If you are running a standalone installation but getting the network license, the level.txt file should be copied into the SAP2000 version 14 *.exe folder.
- Workstation installation – For workstation installations from the server, the level.txt file should be copied into the SAP2000 version 14 Server > License Manager folder.
| Info |
|---|
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. |