Quantcast
Channel: Gemalto Sentinel Customer Discussions
Viewing all 1061 articles
Browse latest View live
↧

Re : Activation failed with status code :5054

November 6, 2018, 3:39 am
$
0
0
Thanks for the update.

Per shared screenshot of Admin Control Center, connected HL Max is not a driverless key. Kindly note that the Sentinel HL (HASP configuration) keys can be upgraded to Sentinel HL (Driverless configuration) keys.

To upgrade a Sentinel HL (HASP configuration) key to Sentinel HL (Driverless configuration) key:

Create a Base Product or Modification Product that contains the Upgrade to Driverless attribute. The Product can be created exclusively to upgrade the Sentinel key, or the Upgrade to Driverless attribute can be included in a Product that licenses or modifies the license for a protected application. Apply the Product to the Sentinel HL (HASP configuration) key to be upgraded.
Please be informed that this process is irreversible.

For another concern, kindly drop us an email at technical.support@gemalto.com or raise the concern through Gemalto Support Portal https://supportportal.gemalto.com/csm/ along with the code snippet/sample and brief description of the issue being faced.

Thank You !
↧
Search

HASP_SECURE_STORE_ID_MISMATCH

November 12, 2018, 2:57 am
$
0
0
Hi,
Why i'm receiving HASP_SECURE_STORE_ID_MISMATCH when trying to login the Sentinel Service using the API

my hardware did not changed, the only thing that i can see is on the attached GIF 
the Key Type is "Cloned"

any idea how to solve that?

Thaks,
Yosef
↧
↧

Re : HASP_SECURE_STORE_ID_MISMATCH

November 12, 2018, 5:24 am
$
0
0
Hello Yosef,

Thanks for raising the concern.

The error appearing usually happens when there is a substantial change in host machine's hardware that is detected by the clone detection mechanism.

However, you have mentioned that no hardware change took place on the host machine. In that case, it is advisable to reach our support team for assistance to check the cause behind the error.


You may also like try the clear clone mechanism provided with Sentinel LDK (version 7.5 or above) to avoid blocker. The procedure is mentioned in the below link :


Thanks & Regards,
Parth Kaushik
↧

Sentinel HL Not recognized in device manager

November 13, 2018, 3:54 am
$
0
0
Hi 

I have been using a Sentinel key for years and has been working correctly
I have a few different keys and all have stopped since  windows update 
Has anyone got a fix to correct this problem
I have tried to install the update up i have been unable to get it to work

Can someone please help
↧

Re : Sentinel HL Not recognized in device manager

November 13, 2018, 6:04 am
$
0
0
Hi,

Thanks for reaching out to Gemalto !

Kindly share the complete operating system details along with detail of recently installed windows update.
Please try to install the latest Sentinel HASP/LDK Windows Run-time Installer 7.81 and share the results.

To download Command Line installer, use the below link:


After downloading and extracting, use the following command to install the drivers:

haspdinst.exe -i

To download GUI installer, click:


Hope it helps !

Regards,
Gaurav Bhanot
↧
↧

Re : Sentinel HL Not recognized in device manager

November 13, 2018, 6:45 pm
$
0
0
Thanks for your email 
I downloaded the programme and followed your instruction but i still have the error
i have also attach what the error i am getting in windows also

Thanks
↧

Error when starting the Sentinel License Manager service

November 14, 2018, 6:06 am
$
0
0
Hello, i use operation system is Windows Server 2008R2. I get an error when starting the Sentinel License Manager service with parameters 1232 0 0. This is an internal error. For assistance, contact your administrator or the software manufacturer. ErrorCode: 48 5 890 0." Anyone have any ideas/suggestions? 
↧

Re : Error when starting the Sentinel License Manager service

November 15, 2018, 4:29 am
$
0
0
Dear User,

Thanks for raising the concern.

From the error code appearing, it seems that some machine level restrictions are blocking the service.
Please try to check below points and observe if it helps.

1- check if port 1947 is free for usage and not per-occupied by some other application. To see this, you use netstat -ab command in command prompt. If port appears occupied, we would require to release the port.
2- check by disabling the antivirus or firewall traffic rules that maybe conflicting with the hasp service.

If the problem still persists, please be advised to reach our support team to help you with this using the below service portal link : https://supportportal.gemalto.com/csm/

Regards,
Parth Kaushik
↧
Search

Re : Sentinel HL Not recognized in device manager

November 15, 2018, 11:36 pm
↧
↧

SuperPro doesn't work with our software

November 16, 2018, 8:23 am
$
0
0
Hi,
we are using superpro since many years. We still link our program (Windows mfc) to a spromeps.lib from 1995.
Until now that worked. We used  driver 7.6.6
With driver 7.6.9  RNBOsproInitialize() doesn't succeed. The dongle is shown correctly  in the windows device manager, but we can't read it.
Is that a known problem, and could a newer lib help, to solve it?
Thank you for answers
Dieter
↧

Re : Error when starting the Sentinel License Manager service

November 19, 2018, 6:55 am
↧

Re : SuperPro doesn't work with our software

November 19, 2018, 10:08 am
$
0
0
Hi Dieter,

Thanks for writing in !

This would require detailed investigation. Please get in touch with us through Support Portal https://supportportal.gemalto.com/csm/ or mark an email to technical.support@gemalto.com along with the following details:

- Share the Operating system details.
- Share the screenshot of device manager.
- Version of Superpro SDK/library being used.
- Share if it is working on any other machine.

Regards,
Gaurav Bhanot
↧

Re : Error when starting the Sentinel License Manager service

November 20, 2018, 12:08 am
$
0
0
Dear User,


Thank you for replying.


It seems that a detailed level investigation is needed in your environment as the generic were not helpful. For this, you should reach our support  team to work on it.

If you have already contacted the support team using the portal at https://supportportal.gemalto.com/csm/ then please share the case incident generated for the same with us to expedite the process.

You can also alternatively email your concern to our email address technical.support@gemalto.com .


Thanks & Regards,
Parth Kaushik
↧
↧

HASP envelope application does not start

December 3, 2018, 12:19 pm
$
0
0
I've got a new software product that runs on a kiosk. The OS is Windows 10 x64 (build 1607, 2016 Enterprise LTSB). I have installed the LDK runtime but the enveloped application does not start properly. With or without a key inserted, the application starts then immediately closes ... no error window or anything. Also, the key (Time HL) shows up in Device Manager as a HID device instead of a SafeNet device, but the administrative page on port 1947 does show the key connected and working. Any ideas?
↧

Re : HASP envelope application does not start

December 4, 2018, 5:41 am
↧
Search

Re : SuperPro doesn't work with our software

December 5, 2018, 4:18 am
$
0
0
Thank you,
with new libs it works also with new drivers.
But I can't read old parallel-port-dongles. With the old version, that worked.
Is it possible to do that ?

in spromeps.h is something like:

#define SP_KEY_FORM_FACTOR_PARALLEL 0
#define SP_KEY_FORM_FACTOR_USB      1
#define SP_KEY_FORM_FACTOR_SOFT     2


↧

Re : SuperPro doesn't work with our software

December 5, 2018, 6:13 am
$
0
0
Its good to know that your program works fine with new libs and latest sentinel system drivers 7.6.0.

Please note that the mentioned content of spromeps.h are key type constants.
In order to use parallel port keys, you would require to choose 'custom' as Setup type while installing the Sentinel System drivers 7.6.0. 
Then click the icon in the list for parallel drivers and install it. Refer to the attached screenshot.

Hope it helps !
↧
↧

Problems with envelope

December 10, 2018, 11:32 am
$
0
0
Hi,

When we envelope a dll's and enable core isolation in windows 10, loading the dll is very slow (+-30seconds).
How do we solve this? Or is there a new version that solves this problem.

Another problem is that loading 'hasp_windows_96490.dll' causes a crash when “ROP Exploit prevention” is enabled. Is this problem solved in a new HASP version? So we cant enable “ROP Exploit prevention” in a protected application (even without envelop).

Kind regards,
Jonas
↧

Re : Problems with envelope

December 10, 2018, 11:03 pm
$
0
0
Hi Jonas,

Please share the version of HASP/LDK Envelope and API's used along with the version of HASP/LDK runtime installed on the machine.

ROP Exploit Prevention feature is a part of some Anti Virus suites. Please confirm the exact name and version of Anti Virus used.

Please explain: "So we cant enable “ROP Exploit prevention” in a protected application (even without envelop)."
Does it mean that this problem is also faced in the application that is not protected with envelope but uses HASP API's?

Usually you protect your application with Envelope only or API + Envelope?
Also share the version and build of Windows 10 on which problem is faced.

Regards,
Ashish


↧

Re : Problems with envelope

December 13, 2018, 8:34 am
$
0
0
Hi Ashish,

We envelop and use the API's to protect our application.

The ROP problem appears when using the API (checking the license), once 'hasp_windows_96490.dll' is loaded, the application is closed.
ROP exploit prevention is a antivirus technology that is included in every modern antivirus package, it is also available as part of the michrosoft EMET 5.5 for windows 7 (but is also a problem in windows 10 and a antivirus program including the ROP).
To reproduce the problem, start with windows 7 SP1 x64 including all updates.
Install emet 5.5: https://www.microsoft.com/en-us/download/details.aspx?id=50766
Enable "ROP caller check" for the protected application that is calling functions from 'hasp_windows_xxxx.dll'

The slow loading is a problem with the envelop (not the API) in combination with core isolation.
The core isolation in windows 10 is something new and available in W10 build 1803. 

Our released software version uses;
Run-time Installer 7.81.80610.1
Sentinel License Manager 21.1.1.80248
hasp_rt.exe 18.0.1.56022 (also tested with 21.1.1.80248)
hasp_windows_vendorid.dll 7.4.1.56018
hasp_net_windows.dll 7.4.1.55825
haspnert.dll 4.20.55155.0
haspvlib_vendorId.dll 2.36.1.53591

But I tested it now with an updated HASP version (with the same problems);
Run-time Installer 7.81.80610.1
hasp_rt.exe 21.0.1.17827.6 / 7.8
hasp_windows_vendorid.dll 8.81.20251.6
hasp_net_windows.dll 7.8.17911.6
haspnert.dll 7.8.18344
haspvlib_vendorId.dll 7.80.18210.6

Kind regards,
Jonas
↧
Viewing all 1061 articles
Browse latest View live
Search