2018 R2 and up Install Errors, No valid license found

[cappy6124]

Has anyone else seen this? Yes, the hasp is plugged in; yes, it is up to date; no, we are not trying to install through a remote connection. This has happened on 2 machines now and so far HXGN support hasn't helped at all... They told one of our guys, "Well if that's what it says, there's nothing we can do"

[Edit: Punctuation]



install error.png

[Matthew D. Hoedeman]

yeah, I thought I heard that the physical hasp was going the way of the dodo and that sooner or later, it wouldn't be able to hold enough info for the lock. Maybe you have hit that point? Nice that they are still as helpful as they have always been.

[Schrocknroll]

Earlier versions run fine?

[Matthew D. Hoedeman]

did you upgrade the computer as well (like, to Win10)?

[Sora5]

I have one offline and one online license that still uses the hasp and it is running 2018R2 in Win7 64bit. Perhaps install an earlier version and double check the license info within PCDMIS. With the hasp, you have to run the .exe file Hex sends you to update the license in it. Are you sure, sure, sure it is up to date?

[cappy6124]

The hasp is up to date, and 2018 R1 runs fine. We didn't upgrade the computer. I think its a problem with the hasp, usually when the portlock is out of date it will say that the version is too new...

yeah, I thought I heard that the physical hasp was going the way of the dodo and that sooner or later, it wouldn't be able to hold enough info for the lock. Maybe you have hit that point? Nice that they are still as helpful as they have always been.

2019R1 still works with hasp, on my machine anyway, not the one in question though.

Its weird though that its 2 machines at 2 different locations with same problem, starting at the same version of PC-DMIS

[Schrocknroll]

https://www.cipher-it.co.uk/wp-content/uploads/2017/11/ITCrow.jpg

[AndersI]

First things first - run the CUSTPROG.EXE program (in your PC-DMIS folder) and verify that the Expiry Date of your portlock is later than the issue date of your PC-DMIS version. If CUSTPROG can't read your portlock, google "Aladdin hasp hl download" and re-install the HASP driver.

With that said, I have myself experienced similar problems a number of times - everything seems to check out good, but the installation program is not cooperative. One thing that has disturbed many automatic updates is when there has been a lapse in the SMA sometime during the portlock lifetime. The Installer is not happy about this, even though PC-DMIS itself has no problem as long as the current Expiry Date is later than the PC-DMIS issue. If you have more than one machine of the same type, you can try borrowing the portlock from a working system for the installation.

If you have a valid SMA, it should be possible for your local Hexagon rep. to get you a time limited LMS license, just for the installation - then you can verify that the portlock still works with that version.

[cappy6124]

Yeah the SMA is up to date for us, it looks like the issue is stemming from some setting on our machines. Our IT likes to F everything up. The same portlock in question can be used on all but a few machines to install...

[Daywalker]

I'm guessing you definitely do not have any kind of LMS (Software license) installed??? Not an old evaluation license or something? Run the application CLM Admin and select view installed licenses.. see if it lists anything.

[Paul Sarrach]

Did the install for offline and online with no problem.

[quentin66]

why not try the software license.The New users are basically equipped with soft license in China from about 2017

[cappy6124]

LMS doesn't work either... We think it's something with our PC. IT really likes to mess up the images...

[AndersI]

Tell IT to

- Apply all pending Windows Updates - maybe some system .dll is too old.
- Verify the .NET version on the computer, possibly repair/update.
- Read https://support.microsoft.com/en-gb/help/2999226/update-for-universal-c-runtime-in-windows and maybe update that one too.
- Read the ReadMe.PDF in the PC-DMIS folder, especially Appendix B.