FAQKeyfiles

[vc_row][vc_column width=”1/2″][vc_column_text] [/vc_column_text][/vc_column][vc_column width=”1/2″][vc_column_text]Frage:
How do I get the MedSecID, Host ID?

Antwort:
The program lmhostid is available on the MEDUSA 2003200 CD.
It is possible to request this ID with an operating system command:

– on Windows in the DOS-BOX with IPCONFIG -ALL (under physical address)
– on VMS with MC NCP SH KNOWN LINE CHAR
– on SUN with: hostid
– on HP with : echo `uname-i` l60p | dc

In most cases, that will allow you to successfully obtain the correct address. With specific configurations the result can be false! In any case, it is better to use the LMUTIL tool with the LMHOSTID option, delivered with MEDUSA.

It is located in MEDUSA under: product MEDSYS, in the subdirectory ->MED->LICENSE.

For example:

Windows : C:MEDUSAMEDSYSMEDLICENSELMUTIL lmhostid
VMS : $ LMUTIL:==$MED:[MEDSYS.MED.LICENSE]LMUTIL $ LMUTIL LMHOSTID
Unix : /medusa/medsys/med/license/lmutil lmhostid

In the older versions of MEDUSA-Classic, the Tool used to be named MEDSECID and was started without parameters.
(Depending on the version, either in the subdirectory RUN instead of LICENSE, it can also be started via MEDUTIL)
If MEDUSA is not yet installed, the tool should be copied from another data processor or the FLEXLM-system should be installed from the MEDUSA-CD. (MEDUSA itself is not required in order to do so)

Frage:
Which version of the License Manager is needed for my MEDUSA version?

Antwort:
The table below shows the License Manager version for the different MEDUSA versions:

12.2.2 FEATURE med2d_draft medusa_lmd 12.000 …
12.2.3 FEATURE med2d_draft medusa_lmd 12.000 …
12.2.4 FEATURE med2d_draft medusa_lmd 12.000 …
12.2.5 FEATURE med2d_draft medusa_lmd 12.000 …
12.3 FEATURE med2d_draft medusa_lmd 12.000 …
14.0 FEATURE med2d_draft medusa_lmd 14.000 …
14.1 FEATURE med2d_draft epd 1.000 …
14.1.1 FEATURE med2d_draft epd 1.000 …
NG 1.1 FEATURE med2d_draft medusa_lmd 13.000 …
NG 1.1.1 FEATURE med2d_draft medusa_lmd 13.000 …
NG 1.2 FEATURE med2d_draft medusa_lmd 13.000 …
NG 2.0 FEATURE med2d_draft medusa_lmd 15.000 …
NG 3.0 beta FEATURE med2d_draft medusa_lmd 16.000 …
NG 3.0 FEATURE med2d_draft epd 1.000 …
NG 3.0.1 FEATURE med2d_draft epd 1.000 …
NG 3.1 FEATURE med2d_draft epd 3.000 …
NG 3.2 FEATURE med2d_draft epd 3.000 …
NG 4.0 FEATURE med2d_draft epd 4.000 …
2000i FEATURE med2d_draft epd 5.000 …
2000i2 FEATURE med2d_draft epd 6.000 …
2001 Datecode 2001100 FEATURE med2d_draft epd 7.000
2001 Datecode 2001200 FEATURE med2d_draft CSGLMD 1.000
2003 Datecode 2003100 FEATURE med2d_draft CSGLMD 2.000
2003 Datecode 2003200 FEATURE med2d_draft CSGLMD 2.200
MEDUSA4 V1.0 FEATURE med2d_draft CSGLMD 4.000
2003 Datecode 2003300 FEATURE med2d_draft CSGLMD 4.100
MEDUSA4 V2.0 FEATURE med2d_draft CSGLMD 4.200 (FlexLM 10.1.3)
MEDUSA4 V2.1 FEATURE med2d_draft CSGLMD 4.300 (FlexLM 10.1.3)
MEDUSA4 V2.2 FEATURE med2d_draft CSGLMD 4.400 (FlexLM 10.1.3)
MEDUSA4 V2.2.1 FEATURE med2d_draft CSGLMD 4.400 (FlexLM 10.1.3)
MEDUSA4 V3.0 FEATURE med2d_draft CSGLMD 4.500 (FlexLM 11.4.0)

Frage:
Which version of the License Manager is needed for my STHENO/PRO Version?

Antwort:
The table below shows the License Manager version for the different STHENO/PRO versions:

1.0 FEATURE STHENO_pro CSGLMD 1.000
1.1 FEATURE STHENO_pro CSGLMD 1.000
1.2 FEATURE STHENO_pro CSGLMD 1.200
1.2.1 FEATURE STHENO_pro CSGLMD 1.200
1.3.1 FEATURE STHENO_pro CSGLMD 1.300
2.0 FEATURE STHENO_pro CSGLMD 4.200 (FlexLM 10.1.3)
2.1 FEATURE STHENO_pro CSGLMD 4.300 (FlexLM 10.1.3)
2.2 FEATURE STHENO_pro CSGLMD 4.400 (FlexLM 10.1.3)
2.2.1 FEATURE STHENO_pro CSGLMD 4.400 (FlexLM 10.1.3)
3.0 FEATURE STHENO_pro CSGLMD 4.500 (FlexLM 11.4.0)

Frage:
What is the meaning of the error codes in the CSG License system?

Antwort:
Error Codes of the License Management:

1 No entry in Env, Reg, Path
2 Keyfile is not existing (Env)
3 Keyfile is not existing (Registry)
4 Keyfile is not existing (Path)
10 Keyfile does not contain Module
11 Major Version is not correct
12 Ethernetaddress (ETA) is not correct
20 Checksum Error
21 License is not yet valid (date)
22 License is expired (date)

Additional MEDUSA errors:

101 MEDAS license.dat is not existing
102 Environment Variable (csg.license_file) can not be found
103 MEDUSA_LICENSE_PATH can not be found
104 CSG_key is not suitable with the MEDUSA-Keyfile
105 Demo Key has to be applied for
110 Check failed

Frage:
How should the MEDUSA LICENSE-File look like?

Antwort:
In it’s original state (as sent by PTC at the time), the Keyfile contains many comments, starting with: #.
Those comments are without meaning for the function itself and can be eliminated as needed.
Warning: If carriage returns become involved during transfer, the Keyfile will not function!
Additionaly the Keyfile contains 2 blocks existing of one SERVER and one DAEMON block and several FEATURE-lines.
The older Keyfiles used to contain 2 blocks (EPD and MEDUSA_LMD), consisting of a server-, a DAEMON- and several FEATURE-lines.
It may only contain one block, the block not used must be deleted or commented out (#). There are 3 different DEAMON-names by now:
CSGLMD
EPD
MEDUSA_LMD
See under FAQ "Which version of the License Manager is needed for my MEDUSA version?"

The DEAMON-name is the 2nd parameter of the DEAMON-line and in the feature-lines.
The SERVER/DAEMON-line has to be adapted as following:

-under NT:

SERVER SRV47 0004711a007 1730
DAEMON CSGLMD C:MEDUSAMEDSYSMEDLICENSECSGLMD

-under VMS :

SERVER SRV47 0004711a007
DAEMON CSGLMD MED:[MEDSYS.MED.LICENSE]CSGLMD 0

-under Unix :

SERVER SRV47 0004711a007 1730
DAEMON CSGLMD/medusa/medsys/med/license/CSGLMD

Please consider that:

SRV47
must be the Host name of the Keyfile-Server.(can be edited)
0004711a007
must be the IP-Address of the KeyfileServer. Can NOT be edited- Keyfile may has to be applied for again, if applicable.
1730
Is the Port-number for the inquiries between Client and Server. Should only be changed if already used by another application! (unnecessary with VMS)
CSGLMD
(or medusa_lmd or epd with older versions) is the NAME of the DEAMONS, must not be changed!
C:MEDUSAMEDSYSMEDLICENSECSGLMD oder MED:
[MEDSYS.MED.LICENSE]CSGLMD or /medusa/medsys/med/license/CSGLMD is the name of the Path for CSGLMD.EXE (or EPD.EXE/MEDUSA_LMD.EXE) and not to the Keyfile, as often presumed! This Path must be adjusted
0
(Only with VMS) this is the DECNET-Object number. Necessary with VMS!
Sample of a FEATURE-line
( these may not be edited!)
FEATURE
med2d_draft CSGLMD 1.000 1-jan-0 5 4C682E7861399BB7E3D6 ""

Please consider that:

med2d_draft
Name of the Module
CSGLMD
Name of the Daemons
1.000
The version (see under:FAQ" Which version of the License Manger is needed for my MEDUSA version?")
1-jan-0
The final date, the year "0" means unlimited.
5
Number of Licenses.
4C682E7861399BB7E3D6 ""
Checksum (including a reference to the Server-line and a starting date)

Frage:
How do I install my final MEDUSA-Keyfile (EPD-version) under NT?

Antwort:
Please take the ‘Reference for the Licence system for MEDUSA version 2001200’ into account with the CSGLMD-keyfiles.
Proceed as following with the EPD-keyfiles.
1.) The Keyfile needs to be edited under: C:CVSWLMEPDEPD.LIC
———————————————————————
see also under: FAQ "How should the MEDUSA LICENSE-File look like?"

2.) Set up:
————————-
Log in as the Administrator at the KeyfileServer and execute the following script:
C:CVSWLMBININSTALLEPD.BAT

3.) Start:
———————-
As Administrator search for the entry under: " FLEXlm License Server " START>SETTING>SYSTEMCONTROL>SERVICE and then start.
Should the service not start then usually the entries in the Keyfile are not all right, see under 1.)

4.) Check the MEDUSA-License-Path
———————————
The Environment-Variable is set at the LOGIN.BAT of the project, for example:
C:MEDUSAMASTER_PROJECTLOGIN.BAT
Set up:
MEDUSA_LICENSE_PATH=C:MEDUSAMEDSYSmedlicenseepd.dat
This Path has to either:
– – direct to the same Keyfile that the License Server uses
– – or direct to a 1:1 copie of the Keyfile. This would make sense in a Network, if the License-Management is installed on the local c:-plattform on the server, but this not visible to the client is.

5.) Starting MEDUSA
—————–

To consider:
==========

a)In general the Path for the License-SW and the name of the Keyfiles are free to choose, but:
-The Path/Names (has) have to be universal changed at: INSTALLEPD.BAT, all LOGIN.BAT’s of the projects and in the Deamon-line of the License-Files.
-The License Server must have the CVSWLM-Directory on a local disk and has to be able to directly access it.
The reason: all services are started BEFORE the network!
The clients are able to access the Keyfile through the network.

b)During the Update of the Keyfile it is usually sufficient to simply switch the Keyfile and then finish and re-start.
In case of using different Path names, the old service must be removed in a DOS-Box:

C:CVSWLMBINLMGRDINSTALL -REMOVE

You can then set up different Path names: See under 2.)

c) Step 1 and 3 can be droped with the DEMO-Keyfile. A FlexLm-service is not needed.

Frage:
Why do I not receive a License when I start MEDUSA?

Antwort:
1.) When working with DEMO-Keyfile:
=====================
1.1) Is the, mostly written over two lines, Feature-line in accordance with the original?
Is the line completed with a line feed?
Are all other lines commented?

1.2) Does the environment variable MEDUSA_LICENSE_PATH, set in LOGIN.BAT of the project, point to the Demo-Key?
Check the variable like : execute LOGIN.BAT within a DOS-Box and subsequent control with the command: SET MEDUSA ( it will show all environmental variables starting with MEDUSA).

1.3) Has the User process reading rights with the Keyfile?

1.4) Has the final date been exceeded or the starting date ( contained coded in the Keyfile, usually complies with the creation date) expired ?

2.) with the final Keyfile and although the server is running?
==========================================
2.1) Is the File on which the environmental variable MEDUSA_LICENSE_PATH (see under 1.2), points, identical with the Keyfile the server is using? It has to either be physicaly the same File or a 1:1 copie of the same.

2.2) Does the TCP/IP connection between client and server function?
Control: Enter the command PING OTTO in a DOS-Box (OTTO being used as a sample name for the registered name of the server in the Keyfile). If this doesn’t function ( or only over the IP-address), it can either mean that the TCP/IP protocol is not configurated or the question after the DHCP-server was answered with "yes", even though it is not existend. It could also mean that the DHCP (or DNS-)-server is having problems, or…..
In any case it would be a network- and not a MEDUSA problem.

2.3) Is the date of the client and the server right and even more important: the same?

2.4) Do client and server have different software versions of MEDUSA/FLEXLM?

2.5) Is there an error message in the Logfile of the server
(< inst-path >MEDSYSMEDCVSWLM.LOG resp. C:CVSWLMEPDCVSWLM.Log)?

3.) The FLEXLM-Server doesn’t start with the final Keyfile.
============================================
3.1) Have SERVER- and DEAMON-line been accordingly adapted?
(see FAQ: "How does the MEDUSA LICENSE-File has to look like?")

3.2) Has the TCP/IP protocol been installed and is the "simple TCP/IP service" started?

3.3) Has the FLEXLM-service been installed/started including (with) the administration rights?

3.4) Does the administrator have the right to create a directory (C:FLEXLM ) on the system disk?

3.5) Is the CVSWLM-Software on a local disk? Network disks are not permissible!

3.6) Are the Logfiles < inst-path >MEDSYSMEDCVSWLM.LOG resp. C:CVSWLMEPDCVSWLM.LOG and do they contain error messages?

3.7) Tip: To find errors you can also try to start the License server directly (not the service).
To do so: open a DOS-Box and then start the LMGRD.EXE with the parameters "-APP" and "-c< keyfile >" .
For example: C:MEDUSAMEDSYSMEDLICENSELMGRD.EXE -app -c C:MEDUSAMEDSYSMEDLICENSECSGLMD.LIC (or C:CVswlminImgrd.exe -app -c C:CVswlmepdepd.lic with older versions)
Error messages are now more visible.
Everything seems to be functioning if the process starts without errors ( the DOS-Box can be closed by closing the window).
Finaly you need to remove the old service, install the new one and re-start (see FAQ "How do I install my final MEDUSA-Keyfile under NT?").

Frage:
Why does the MEDUSA Keyfile not work under WINDOWS 2000/XP without a network connection?

Antwort:
Deactivate Media Sense ( win2k and winXP )
This concerns installations on a Laptop or
stand-alone PC in perticular!

The network card will be deactivated if MediaSense is turned on (default) and there is no physical network connected!
For this reason, MEDUSA can not retrieve a valid Host-ID
and a licence can not be activated.
This is also documented under e.g.: Q239924 in the Microsoft Knowledge Base.
This entry can be created manually or with the help of a registration file.

Sample of a registration file: see ‘Download’
This registration will be extended when double clicking the file in the Explorer.

Manually: see ‘Download’
Start the registration-editor as local administrator.

Please select: HKEY_LOCAL_MACHINESystemCurrentControlSetServicesTcpipParameters
You may now enter the parameter with value.

DisableDHCPMediaSense REG_DWORD 1

This action should only be used for the above mentioned problem.
Please note, these specifications are without warranty!
Please use the MS KDB for more information.
The system should be backed up before executing this action.
If the network card is automaticaly disabled by BIOS and no network attached when booting your pc, you should disable this BIOS functionality.

Download[/vc_column_text][/vc_column][vc_row][vc_column width=”1/2″][vc_column_text]

Project Data Control (PDC)

Project Data Control (PDC) ist eine optionale in MEDUSA4 und MPDS4 integrierte Datenmanagement Lösung für Konstruktionsdaten und die damit verwendeten Dokumente. Durch die offene Architektur bietet PDC vielseitige Integrationsmöglichkeiten. Dadurch können die Daten sowohl für andere PLM-, PDM- und ERP-Systeme zur Verfügung gestellt oder gar über das Web für andere Nutzergruppen zugänglich gemacht werden.
PDC erlaubt die Generierung einer an die Kundenanforderungen angepassten Datenbankstruktur, wobei entweder eine Oracle- oder andere Datenbank-Architektur verwendet werden kann. Der Zugriff auf die Datenbank erfolgt dabei aus MPDS4, MEDUSA4 oder dem Web. PDC erlaubt dabei die Verwaltung von allen konstruktionsnahen Daten, wie 3D-Modellen (DXF, STL, IGES, STEP, VRML, MOD), 2D-Zeichnungen, Tabellen oder Rohrleitungsisometrien. Natürlich werden auch alle zum Dokument dazugehörigen Daten, wie benutzerspezifische Attribute, Verweise, Stücklisten oder aktueller Bearbeitungsstatus vom System mit verwaltet.

PDC ermöglicht die Zusammenarbeit zwischen weltweit verteilten Teams, mit einer einfachen Implementierung und Administration. Die Vernetzung verschiedener Standorte erlaubt einen kontrollierten Datenaustausch bis hin zur kompletten Synchronisation gesamter Projektdatenbanken.[/vc_column_text][/vc_column][/vc_row][vc_row][vc_column][vc_column_text][/vc_column_text][/vc_column][/vc_row]

[vc_row][vc_column][vc_column_text][/vc_column_text][/vc_column][/vc_row]