QA4/1, QA7/2 & QA11/3 - wNote v4.

1 (29-Jul-08)

Product Release Latest Update

AVEVA Licensing System 1.1.1
Full Release 30368-1
This Letter is updated after the product release has been locked down. It contains last minute
news for the release and information about any issues or workarounds found since the release
has been locked.

(For a Full Release only)

This letter also contains information about subsequent partial fix releases.

Customers are advised to subscribe to the Support news of the relevant product group for
information about any changes.

Latest News
There is no latest news for this product release at present.

Fault Corrections
The following problems requiring your attention have been found in Acceptance Testing or after
Release but have not yet been corrected in a subsequent release:

See next page for Known defects and workarounds.

Fix Releases Available

None.

Incident Defect Description Recommended

number number Workaround

Revision History
Date Comment
02 Jul 2013 First release, to accompany product release letter

For further information please contact your local AVEVA support office, which can be found at
http://www.aveva.com/products/support/support.html
File: w30368.doc
Last saved: 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 1 of 11
 Product Release Latest Update
.

Defect No 1
When just after installing AVEVA License System 1.0 and via the START menus
you try and run the AVEVA License System Console you get the following error :-

This is a Windows timing problem, The install has set an environment variable but its value has
not yet populated to the menus, so there are two workarounds.
1 . Wait for a few minutes and try again or ( reboot) machine.
2. Navigate to the environment variable the installer has set AVEVA_LICENSING and manually
set it and then try again.

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 2 of 11

 Product Release Latest Update
.

Defect No 2
When running any product for the first time you get the following error message :-

There could be several reasons for this.

1. This could mean that the Specific license key that the product is trying to use is NOT
installed in the ARMS license server which is running. A common reason is running
AVEVA Administration with a license file with just an AVEVA Everything3D seat and not
one with AVEVA Administration.
2. This could also be due to the new license file being linked to either the wrong locking
criteria or there has been a mistake copying and pasting.
3. Or you just have not installed the license file in the server yet. (Page3 release letter).

Download and run the .bat file as documented in aareadme.txt file as in this ServerInfo.zip AVEVA
Support site.
And send that (AVEVA-Server-info.txt), along with your license.xml file back to the Administrator
who gave you the license, with a screen shot of the product/version you are attempting to run that
gives the error.

Defect No 3
If an old Flex 5 license file is placed into the Flex part of the AVEVA Licensing System server, the
following error message will appear. This example is from running a PDMS application as below.

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 3 of 11

 Product Release Latest Update
.
Defect No 4
If a new Flex 6 licenses.lic part from an installed AVEVA Licensing System server is placed into
an old Flexman5.2 server The following error message will appear. This is for example from a
PDMS application as below.

Defect No 5
If the license server has all the Flex license keys expired, what happens is the Cadcentre.exe
process dies but the lmgrd.exe process is still running. So when an attempt to install a new license
file on that server, the AVEVA license System Console thinks that the servers are down, but in
fact the Flex server/service is still running. When this happens this error is displayed.
Error in shutdown the licensing system. Aborting installation.

To overcome this error the Flex service (lmgrd.exe) programs must be stopped. This can be done
by manually stopping the Flex service (AVEVA DLS Flex Server) or by stopping the lmgrd.exe
processes . Once the service is stopped the new license can be installed.

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 4 of 11

 Product Release Latest Update
.
Defect No 6
If when installing the license file using the AVEVA License System Console, the error message
below appears.

This usually happens on laptop installs, and what is means is that the license servers state has
changed since requesting the license servers locking criteria , and now when attempting to start
the license server. For example when running the AVEVA-Locking.bat file the laptop was using
the LAN network card, and now when attempting to start the license server the laptop is using the
wireless network adaptor.
For example here is the contents of my AVEVA-Server-info.txt file when a server is connected via
the LAN with wireless network card disabled.
IP address : 10.0.101.38
Disk ID : 0x8771CA45
Host name : UKCAML4161
Ethernet address[1] : 2C-41-38-08-01-9F
Hard Disk Serial[1] : J3360081G1KVBC
CPU Info String : GenuineIntel Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz 6 10 7
UUID : 008E337B-321F-11E1-9716-6CC25F06A060

Same machine with Wireless network active. ( see two Ethernet addresses now)
IP address : 10.0.101.38
Disk ID : 0x8771CA45
Host name : UKCAML4161
Ethernet address[1] : AC-81-12-97-F1-1C
Hard Disk Serial[1] : J3360081G1KVBC
CPU Info String : GenuineIntel Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz 6 10 7
UUID : 008E337B-321F-11E1-9716-6CC25F06A060

Locking Code 1 [1] : 381E-*15S SFAW CGQ8 XADQ

---------------------------------------------------------------------

Ethernet address[2] : 2C-41-38-08-01-9F

Hard Disk Serial[1] : J3360081G1KVBC

You have two workarounds.

1. Place the license server into the same state that you ran the (.bat) file when the license
was requested. Then install the license. (see note)
2. Run the (.bat) again now and request a new license file with the new [1] locking criteria
And when you have the license install it, without changing the server state.

Note Once the license file has been installed it will then work which ever network card is
being used, so long as the original card is active/enabled.

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 5 of 11

 Product Release Latest Update
.

Defect No 7
When setting up a client to use an AVEVA Licensing server you get the following error when
running, the ASL Client Configuration Tool .

This means that the program needs to be elevated to be run as an adminstrator.

Right mouse , properties ALS Client Configuration Tool on Start menu and on Compatibility tab
Set Privilege Level to, Run this program as an administrator.

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 6 of 11

 Product Release Latest Update
.

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 7 of 11

 Product Release Latest Update
.
Defect No 8
If using a local AVEVA Licensing server and a VPN client , when stopping the VPN client the
license server stops, or your route to your license server is not restored, and after 8-10 minutes
your applications give you server lost prompts.
The only way continue and to restart your license
server is to re-boot your machine.

This can be fixed if you point both your RMS

and your Flex parts of the AVEVA Licensing
System to localhost.
This can be done by editing the Flex
licenses.lic file found in the following folder:-

C:\AVEVA\AVEVA Licensing System\Flex\ licenses.lic

Change the SERVER line to read :- SERVER localhost ANY 744

Note- This will have to be done manually after everytime a new license is installed. As at the
moment the AVEVA License System Console tool does not enable this facility.

Save the licenses.lic file and see next page, how to set your clients to see this new server .

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 8 of 11

 Product Release Latest Update
.
Point your client to this (localhost) server using the ALS Client Configuration Tool. After this is
done stop and restart your license server before using VPN.

If wanting to use WlmAdmin tool to check on your license server usage, after using VPN or during
using VPN software you might have to define your own (localhost) server.

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 9 of 11

 Product Release Latest Update
.
Defect No 9
When running the AVEVA-locking.bat file the AVEVA-Server-name-info.txt file does NOT
Have an Ethernet address listed. As example below.

Sentinel RMS Development Kit 8.5.3.0020 Host Locking Code Information Utility
Copyright (C) 2012 SafeNet, Inc.
IP address : 192.168.200.56
Disk ID : 0xCD341ADF
Host name : ITGENLLSCR7
Ethernet address[1] : ( this is blank no value returned )
Hard Disk Serial[1] : WD-WXE1A7078783
CPU Info String : GenuineIntel Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz 6 14 5
UUID : 4C4C4544-0053-4B10-8047-C7C04F5A4E31

Locking Code 1 [1] : 381E-*1N8 FVL9 B82C R6AG

---------------------------------------------------------------------

What has happened is that in the registry the first network card listed has a blank in it, or is a
network card that RMS does not use, for example a Phone card/mini network card.
When this happens instead of looking for the next entry echoid/wechoid stops and returns a blank.
To fix this problem what the user must do is carefully edit the registry and move the first network
card entry to the bottom of the list, thus enabling the echoid/wechoid programs to pick up a valid
ethernet address and list it.
Carefully open the machines registry and navigate to here:-
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkCards
This example shows a blank entry :-

See next page for how to move it to bottom of list.

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 10 of 11

 Product Release Latest Update
.
To move the blank or problem network card to the bottom of the list rename the number
To a higher network card number than the last one in the list .
In this example I have renamed it to 91 , but it could of been 12 .

Once the entry has been changed and the list refreshed and the registry closed, when
the AVEVA-locking.bat file was run, the AVEVA-Server-name-info.txt file output
contained an Ethernet address listed. As example below.

Sentinel RMS Development Kit 8.5.3.0020 Host Locking Code Information Utility
Copyright (C) 2012 SafeNet, Inc.
IP address : 192.168.200.56
Disk ID : 0xCD341ADF
Host name : ITGENLLSCR7
Ethernet address[1] : 18-A9-05-C2-37-21
Hard Disk Serial[1] : WD-WXE1A7078783
CPU Info String : GenuineIntel Intel(R) Core(TM) i7 CPU Q 740 @ 1.73GHz 6 14 5
UUID : 4C4C4544-0053-4B10-8047-C7C04F5A4E31

Locking Code 1 [1] : 381E-*1N8 FVL9 B82C R6AG

Now a license file can be requested using that Ethernet address.

Note If the license file is requested with that network card active, when the returned license.xml
file is to be installed, it MUST be installed with that same network card active (See defect No 6),
Once installed the server will work when any network is used.

w30368.doc 10-Oct-2013 Copyright 2013 AVEVA Solutions Limited Page 11 of 11