Recent Control & Safety Systems Discussions
Similar Posts
“AMS Device Manager could not be licensed. Possible reasons include: can’t open license file, license file is invalid, or could not move license file to specified directory” when performing AMS licensing after origin machine is crash.
Problem: Delta V virtual controller parameters change upon run of first timestep after loading snapshot when connected to Unisim dynamic simulation model for OTS
Base Station License will not load, no errors
New Intuitive, Scalable PACSystems™︎ Edge Solutions in Fit-for-purpose Packages Simplify Creation of Advanced IIoT Applications
Error whenSTART button in pressed in BOI after successful loading of Phase
Share

Simulate DV11 - No way to load license file after new database creation

Hi

That's the second times that happend on different Simulate machine and don't know how to solve it :
- The Simulate machine works fine
- Creating a new Database
- Set active this new database
- ShutDown the DB server
- Start the ReRun utility + type the correct password at the end of procedure + restart the machine
- logging the machine
- Flexlock "DeltaV loggon"
... but the current (windows logging) user (that is the same as before) does'nt appears in the list; only got "Administrator, Configure and Maintainer"

The only user that accept loggin is Administrator.
When I start DV Explorer and try to load the license file, the item menus "File + Licensing" are greyed : "Load License File" and "Create License File".
If I select back to the previous Database, the problem is the same : License assignment disappears and the menu to load the license file is greyed.

The user exists in "user managment" account list.
If I rename the user in the "user management" + recreate a new one with the same name (as the window user) + reboot, then the windows desktop is reinitialized and I definitively lost access to anything.
The "WatchIt DongleDriver" says "RT_FAILURE" (error 7) - but works fine previously.

Questions :
- Is there another way to load license file than from the explorer menu ?
- Is there a reason why the user rights disappear after a ReRun ?

By the way, I only have the solution to reinstall completly Windows and DV to be able to build a new database
If someone have an idea ...
Some more details that could be important :
- This simulate machine runs under VMWare Player 5.0.2
- my dongle is supported on a parallel port LPT1 (and usualy works fine)

Jack_France
  • Maarten van der Waal
    Jack, Loading the license can only be done when the dongle is attached.
    After you restarted the VM (forced by the ReRun facility), the link between
    the Dongle and the VM is broken. So from the menu, reattach the dongle and I
    would guess you are up and running. Maarten.

    -----Oorspronkelijk bericht-----
    Van: Jack_France [mailto:bounce-Jack_France@community.emerson.com]
    Verzonden: maandag 06 mei 2013 13:18
    Aan: DeltaV@community.emerson.com
    Onderwerp: [EE365 DeltaV Track] Simulate DV11 - No way to load license file
    after new database creation

    Hi

    That's the second times that happend on different Simulate machine and don't
    know how to solve it :
    - The Simulate machine works fine
    - Creating a new Database
    - Set active this new database
    - ShutDown the DB server
    - Start the ReRun utility + type the correct password at the end of
    procedure + restart the machine
    - logging the machine
    - Flexlock "DeltaV loggon"
    ... but the current (windows logging) user (that is the same as before)
    does'nt appears in the list; only got "Administrator, Configure and
    Maintainer"

    The only user that accept loggin is Administrator.
    When I start DV Explorer and try to load the license file, the item menus
    "File + Licensing" are greyed : "Load License File" and "Create License
    File".
    If I select back to the previous Database, the problem is the same : License
    assignment disappears and the menu to load the license file is greyed.

    The user exists in "user managment" account list.
    If I rename the user in the "user management" + recreate a new one with the
    same name (as the window user) + reboot, then the windows desktop is
    reinitialized and I definitively lost access to anything.
    The "WatchIt DongleDriver" says "RT_FAILURE" (error 7) - but works fine
    previously.

    Questions :
    - Is there another way to load license file than from the explorer menu ?
    - Is there a reason why the user rights disappear after a ReRun ?

    By the way, I only have the solution to reinstall completly Windows and DV
    to be able to build a new database If someone have an idea ...
    Some more details that could be important :
    - This simulate machine runs under VMWare Player 5.0.2
    - my dongle is supported on a parallel port LPT1 (and usualy works fine)

  • Jack_France

    In reply to Maarten van der Waal:

    Hi Maarten

    You'r right !

    I have never been surprised by the dongle deconnection during loggon/off and you are right : After logoff, the parallel port status is not connected.

    I've connected it before re-loggin, Flexlock only provides "adminstrator" loggon, but I was able to load the license, attribute it to the PP node and then, after the download, the default user reappears in the available users list in the FlexLock.

    Many, many thanx, Maarten.

    The first time i've encountered this problem I was forced to create a new Simulate machine.

    Ouf. Merci

  • Kartik29

    In reply to Maarten van der Waal:

    I'm facing similar kind of situation , dongle is attached however i cant see the option for license load in DeltaV Exp File menu.Is there any other way to load the license ?

    Karma doesn't have any menu, you get serve what you deserve.

  • Andre Dicaire

    In reply to Kartik29:

    Using WATCHIT, type in the path and tell us what the response is. Saying the Dongle is attached, could mean various things, but specifically, we need to know that the dongle is actually being read successfully and that it is not expired. Simulate Standalone Dongles do not expire, but Development licenses do. WATCHIT window will confirm the Dongle ID number and that it can read it successfully, and that it is not expired.

    For a VM, the physical USB port where the dongle is connected must be attached to the VM. I've had one customer with windows 10 running the windows HyperV VM and the DeltaV License Dongle could not be read, though he was able to "attach" it to the VM. They loaded up a VMWARE Workstation VM and the Dongle attached successfully and could be read. So if the Dongle is attached, but WATCHIT cannot read it, we have to investigate this as it is not a DeltaV Database or Explorer issue, but a Hardlock driver/USB connection issue.

    The only way to load a license is through Explorer. Since the license is bound to the Dongle, the Dongle must be available to confirm the license file is valid. For the load license file options to be unavailable, the dongle must not be visible to DeltaV, or you are using an SI Dongle which does not have any licensing. A Simulate Stand alone dongle will have a license file and the dongle does not expire.

    Let us know what Windows OS you are using and whether you are running a VM on VMware or Hyper V, or Virtual PC. And also what version of DeltaV, just so we know...

    Andre Dicaire

  • Pieter Degier

    In reply to Andre Dicaire:

    When using hyper-V on windows server 2008R2 a USB dongle will work with a USB through Ethernet. I have good experience with Eltima (eltima.com)

    A good way to check if your dongle is recognized by DeltaV is to open 'about DeltaV explorer' in the help menu of the DeltaV explorer. The dongle number and the expiry date should be on the SystemID line.
  • Kartik29

    In reply to Andre Dicaire:

    Thanks Andre for the reply.
    From the watchit when checked shows that dongle have expired and also confirmed from the DeltaV Exp ->Help-> about deltav explorer shows no System ID.Requested the distributor for the required dongle license.Hopefully after renewal of dongle license will allow to load license.Will keep you updated.

    Karma doesn't have any menu, you get serve what you deserve.

  • ctgarvey

    In reply to Andre Dicaire:

    Hi Folks,
    great thread, just bringing it right up to date with V14 simulate on Windows server / Hyper-V using the AnywhereUSB IP-to-USB device.

    Folks, we just purchased Deltav simulate V14, cant get it to work.Cannot boot deltav explorer to assign the licenses. Am using Hyper-V with Windows 2019 server and USB anywhere device in order to bind the dongle to the VM. The VM can read the dongle according to AnywhereUSB manager. Watchit reports nothing at all. Is there a Sentinel HL driver that must be installed on the VM? Dongle info reads as: Gemalto / Sentinel HL on the VM.
    Any help most appreciated!
    Thanks,
    Cormac

    Automation IT MES Engineer.

  • Andre Dicaire

    In reply to ctgarvey:

    Not clear if you are using Hyper-V 2019 Host server or that your VM is Windows Server 2019. V14 requires Server 2016 for the VM operating system.

    Assuming you have the correct VM OS, you should still be able to launch DeltaV Explorer without the Dongle present. Confirm that the DeltaV services are running. You need to first get DeltaV Explorer to open. Once that happens, you can look to see if you actually have an issue with the IP to USB device. Let us know the VM windows OS. Did you use a Virtual Studio VM Template or did you create your own VM using Hyper V Manager?

    Andre Dicaire

  • ctgarvey

    In reply to Andre Dicaire:

    Thanks Andre.
    The physical host is Win2019 server datacenter. The guest OS is win2019 server standard. So if all else fails, i will begin the process again on Win2016 server. ( i am aware win 2019 is not supported). I can install on a win2016 VM , but wanted to try and get it working on win2019 first. (This is DV simulate for training only) I didnt see any installation guidelines for DV14, on the DVDs. Is there one? I created my own VM using hyper-v manager.So it is patched with the most recent windows OS patches, not the Emerson -tested patches. I cannot get DeltaV explorer to open. In the past i have run DeltaV on VMware workstation ( not Hyper-V) without problems other than poor performance.

    Here is the list of running services:

    The services that are running are:

    deltaV
    deltaV addb config service
    deltaV api broker service
    deltav configuration manager
    deltav database server
    deltaV diagnostics information service host
    deltav do session server
    deltaV file server
    deltaV oe web service
    deltaV opc .net discovery
    deltaV opc .net server
    deltaV opc ua server
    deltav RET service
    Deltav site host
    DeltaV task service
    fix
    SQL server (deltav_adv_cntrl)
    SQL server (deltav_instance)
    SQL server (emerson2014)


    The deltav services that are NOT running are:

    deltav batch manager
    deltaV campaign manager
    SQL server (deltav_chronicle)



    Are there any missing?

    i installed a hardlock dongle driver that i found , in an attempt to provide device driver for HL dongle so that is also running;

    digi anywhereusb manager is runnning
    HL-Server is running
    sentinel keys server is running


    Thanks again,
    Cormac

    Automation IT MES Engineer.

  • Andre Dicaire

    In reply to ctgarvey:

    I'm surprised DeltaV Installed on server 2019. There is usually an OS verification that stops installation on non-supported OS. The services look correct as the batch and event chronicle are only needed if you are running those on this machine. You might look into the windows logs to see what messages are being generated when DeltaV Explorer fails to start. But wandering off the valid OS does not usually turn out well. If you solve this, you will likely run into something else and again. I'd recommend cutting your losses and installing on VM with valid OS. that at least allows you to get assistance from GSC.

    Andre Dicaire

  • ctgarvey

    In reply to Andre Dicaire:

    Thanks Andre, yes i cut my losses and re installed on Win2016 server VM. This time the system Id /dongle is read correctly and i can also open DV explorer now. However, i dont appear to have the rights to assign licenses or even logon to Deltav or open user manager right now. i am assuming these are just 'newbie' install queries, since its been a long time since i last actually installed deltav.. Is there a guideline for v14 installation on windows 2016 server workgroup/standalone? I am not doing something right regarding the deltav users as i cannot login and dont know their passwords. Thanks again!
    Cormac

    Automation IT MES Engineer.

  • ctgarvey

    In reply to ctgarvey:

    In addition to above....
    The DeltaV isntall routine explicitly recommends that you disable the Administrator account and provides capability to do so. So i did that and installed deltav in the context of an administrator with a different name (deltavadmin). This seems to be a bad idea however ,as the default deltaV database still has an administrator account (that is mapped to windows a local administrator account) and it appears to be the only way to actually logon to deltav before downloading the workstation or adding users in DV user manager. Even after adding users in DV manager they will not appear in dropdown selection until a workstation download , apparently. Something that i cannot do now that dvexplorer has been removed from my desktop.

    In the meantime, something else has happened and the deltav DVexplorer icons are no longer available to any of the declared DV administrator accounts. At a guess, i would say this is somehow related to applocker and/or deltav logon functionality.

    Am i better off going back to original 'before deltav' snapshot and just re installing again, from scratch ? and this time ignoring all requests to disable the 'Administrator' windows server account? There really needs to be an installation guide for the simulate software on the supplied DVDs..

    thanks again,
    c

    Automation IT MES Engineer.

  • Andre Dicaire

    In reply to ctgarvey:

    Try Enabling the ADMINISTRATOR account if you can, and set a known password. This account is in the list of default DeltaV accounts and that should let you logon, load licenses and download. Then, create your new Windows Administration account as well as your day to day worker account.

    The Default Administrator account is disabled because this account poses cyber security risks. You do need an administrator account for all the Windows related activities, like software installation and User management, setting file security etc. Your first step is to create this new Admin User as an administrator and log on with that user to install DeltaV. Note that DeltaV creates a services account called DeltaVAdmin and your user account should not use this name.

    For day to day DeltaV configuration and DeltaV level administration, you are not logged on as a Windows Administrator and any compromise to your account does not give malware Admin credentials.

    If you installed using an account called DeltaVAdmin, this is likely part of your issue.

    As for the DeltaV Icons on the start menu, I did see a KBA on that. The programs disappear from the drop down categories. I'm on WS18 and the icons have returned. I don't know what the root cause was. When it happened, I pinned the programs to the Program bar after launching them from the DeltaV/Bin directory.

    Andre Dicaire

  • ctgarvey

    In reply to Andre Dicaire:

    Thanks Andre, success! I re-enabled administator account and was able to continue and download licenses and start configuring. So the lesson here, is do NOT disable administrator account immediately, and do NOT create a windows admin level account called 'deltavadmin' either to install DeltaV !.

    I still have an OPCUA server licensing issue. I thought i recall Sales team telling me that OPCUA server & OPCUA client was enabled as part of deltaV simulate standalone, but i get the message 'error: software licenses do not match the system identifier, or the system identifier is missing or absent'. Any thoughts on OPCUA server working in DeltaV simulate V14.3.1 standalone? Maybe i should start a new thread for this..

    Thanks for the great help. Almost up and running :->
    Cormac

    Automation IT MES Engineer.

This is the official online community site of the Emerson Global Users Exchange, a forum for the free exchange of non-proprietary information among the global user community of all Emerson Automation Solution's products and services. Our goal is to improve the efficiency and use of automation systems and solutions employed at members’ facilities by sharing our knowledge, experiences, and application information.

User Groups | World Areas | Community Guidelines | Legal Information | Privacy Policy | Contact Community Manager

Website translation provided by Website Translator

© 2015-2022 Emerson Global Users Exchange. All rights reserved.