Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

September 20, 2016, 9:19 am

≫ Next: Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

≪ Previous: Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

$

0

0

Hi Ashish,

When you say "setting up the Redundant server's" are you referring to the initial installation of the license file from scratch or are you referring to the process of starting licenses servers from a state when there are no license servers running in the array ?

Regards,

Ian.

---

Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

September 20, 2016, 9:37 am

≫ Next: Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

≪ Previous: Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

$

0

0

Hi Ashish,

There is a far more serious consequence of this behaviour that has just occurred to me: if server#1 in a three-redundant server setup fails then it will not be possible to run with server#2 and server#3 after a restart.  This in effect makes the RMS redundant server technology LESS redundant than a SINGLE server because there are more points of failure i.e. if ANY of the three servers has a hardware failure then the entire array will be non-functional after a restart.

Please can you confirm the above ?

Regards,

Ian.

Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

September 20, 2016, 9:37 am

≫ Next: Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

≪ Previous: Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

$

0

0

Hi Ian,

Yes I meant to say when we are setting up the Redundant server which refers to the initial installation of the license file.

Regards,

Ashish Kumar

Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

September 20, 2016, 9:41 am

≫ Next: linuxenv with Ubuntu 16.04LTS - linuxenv: fatal E0001: internal error (hint 0x000007DB)

≪ Previous: Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

$

0

0

Hi Ian,

To discuss more on the concern or to troubleshoot the same further, Kindly send us the details on: "support@safenet-inc.com". So that we can investigate bit more on the same.

Regards,

Ashish kumar

linuxenv with Ubuntu 16.04LTS - linuxenv: fatal E0001: internal error (hint 0x000007DB)

September 21, 2016, 7:27 pm

≫ Next: Re : linuxenv with Ubuntu 16.04LTS - linuxenv: fatal E0001: internal error (hint 0x000007DB)

≪ Previous: Re : RMS 8.6.1 servers start in standalone mode when configured with redundant license file.

$

0

0

We have an application that when compiled under Ubuntu 14.04.3 LTS can be enveloped just fine with the linuxenv tool.  Compiled under Ubuntu 16.04LTS, the same application fails to be enveloped and results in:

$ ./linuxenv -f:0 -b:0 -e:4 --msg-out:0 -v:OODAR.hvc app app_secured

LINUXENV, Sentinel LDK Envelope for Linux (ELF x86 and x86_64) applications, Version 1.1.54891

(c) 2015 SafeNet, Inc. All rights reserved.

linuxenv: fatal E0001: internal error (hint 0x000007DB)

The build environment is as follows:

• HASP daemon : Sentinel LDK SDK v7.4
• linuxenv : Version 1.1.54891 (from LDK SDK v7.4)
• distribution : Ubuntu 16.04LTS
• kernel : 4.4.0-36-generic
• gcc : 5.4.0 20160609

A simple application that just prints "hello world!" can be enveloped in this environment.

Any suggestions?

Thanks,

Kevin

Re : linuxenv with Ubuntu 16.04LTS - linuxenv: fatal E0001: internal error (hint 0x000007DB)

September 22, 2016, 6:56 am

≫ Next: Aladdin HASP Driver Installation Issue

≪ Previous: linuxenv with Ubuntu 16.04LTS - linuxenv: fatal E0001: internal error (hint 0x000007DB)

$

0

0

Hi Kevin,

Hope you are keeping well.

Please note that the Sentinel LDK 7.4 is not officially tested over Ubuntu 16.04 LTS. However, the same behavior has already been reported to our RnD Team.

As per the update from the team, this would be fixed in our upcoming release Sentinel LDK 7.5 which is tentatively scheduled for October. 

Thank you,

Gaurav Bhanot

Aladdin HASP Driver Installation Issue

September 30, 2016, 9:07 am

≫ Next: Re : Aladdin HASP Driver Installation Issue

≪ Previous: Re : linuxenv with Ubuntu 16.04LTS - linuxenv: fatal E0001: internal error (hint 0x000007DB)

$

0

0

When installing Aladdin Hasp drivers on a Windows 7 computer I receive the following message: Error when starting the Sentinel License Manager service with parameters 1168 1053 1.  Any ideas?

Re : Aladdin HASP Driver Installation Issue

September 30, 2016, 10:02 am

≫ Next: Sentinel Superpro BSOD Windows 8.1 x64 Embedded

≪ Previous: Aladdin HASP Driver Installation Issue

$

0

0

Hi Robert,

Thanks for sharing the concern!

In order to troubleshoot the shared error kindly provide\try below information:

1. Which version of Driver are we trying to install?

2. Did we try installing the Drivers by Turning Off Firewall/Anti-Virus?

3. Please try installing the Drivers with Admin rights.

4. If we are not trying to install the latest(7.50) version of driver. Kindly download it from                                 http://www.sentinelcustomer.safenet-inc.com/DownloadNotice.aspx?dID=8589947873 

      location and install it.

5. If above steps did not work, Kindly share the error screenshot in order to analyse it further.

Regards,

Ashish Kumar

---

Sentinel Superpro BSOD Windows 8.1 x64 Embedded

October 1, 2016, 2:11 am

≫ Next: Re : Sentinel Superpro BSOD Windows 8.1 x64 Embedded

≪ Previous: Re : Aladdin HASP Driver Installation Issue

$

0

0

Hi,

We are using Sentinel Superpro keys, and when using it with a new PC, the PC always crash.

Error says: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (SNTUSB64.SYS)

The crash happens when I attach the USB key to any of the USB plugs. If I remove the Sentinel driver the PC works fine, the USB plugs are working with Pen-drives, and mouse.

PC will not start correctly until the key is plugged into the USB.

I tried the Sentinel driver 7.5.7 first, then tried the 7.6.6, the error is the same. Tried with another older key, the PC crashes with that also, and tested both keys in another machine, where both work fine.

Windows 8.1 has the latest updates up to yesterday.

Any help would be appreciated.

Re : Sentinel Superpro BSOD Windows 8.1 x64 Embedded

October 3, 2016, 6:17 am

≫ Next: Sentinel USB Dongle

≪ Previous: Sentinel Superpro BSOD Windows 8.1 x64 Embedded

$

0

0

Hi Viktor,

Hope you are keeping well.

You are trying to install older drivers on Windows 8.1 machine. Please install latest Sentinel Protection Installer 7.6.8 from " http://sentinelcustomer.safenet-inc.com/DownloadNotice.aspx?dID=34359738400 " and share your findings. 

Also let me know, are you facing this issue on physical or virtual machine? If VM then did you enable any extra settings in VM?   

If you get same BSOD error then send one email to "support@safenet-inc.com" with kernel level crash dump.

Regards,

Anubhav 

Sentinel USB Dongle

October 4, 2016, 3:38 am

≫ Next: Re : Sentinel USB Dongle

≪ Previous: Re : Sentinel Superpro BSOD Windows 8.1 x64 Embedded

$

0

0

Hello Guys

i found a USB Dongle on which it says "SafeNet Sentinel". If i install it on Windows, the USB Name is "SafeNet USB SuperPro/UltraPro".

Is there a way to see which license is on the dongle? I mean, for which Software.

Is these Information on the dongle or only a key?

Best regards

Dorian

Re : Sentinel USB Dongle

October 4, 2016, 6:49 am

≫ Next: Re : Sentinel USB Dongle

≪ Previous: Sentinel USB Dongle

$

0

0

Hello Dorian,


Thanks for the query.


There is no way to get the license related information from the SuperPro USB dongle.

This can only be confirmed from the vendor from which the specified SuperPro key has been purchased.

Kindly contact your vendor to get detailed information.

with regards,
Parth
Associate Engineer - Client Services SM
Support-line (Global) : +1-410-931-7520
Gemalto Inc

https://sentinel.gemalto.com

http://www.gemalto.com/software-monetization

Re : Sentinel USB Dongle

October 4, 2016, 9:11 am

≫ Next: Re : Sentinel USB Dongle

≪ Previous: Re : Sentinel USB Dongle

$

0

0

Hello Parth

thank you very much for the answer. Thats what i thought.

I'll contact the supplier (iar) of the dongle.

Best regards

Dorian

Re : Sentinel USB Dongle

October 5, 2016, 12:33 am

≫ Next: Re : Problem with releasing module licenses on network dongle

≪ Previous: Re : Sentinel USB Dongle

$

0

0

Hello Dorian,

Thanks for the update.

Feel free to get back to us for any future concerns.

Regards,
Parth

Re : Problem with releasing module licenses on network dongle

October 5, 2016, 3:45 am

≫ Next: Re : Problem with releasing module licenses on network dongle

≪ Previous: Re : Sentinel USB Dongle

$

0

0

Good day 

I have emailed support@safenet-inc.com, I was informed via email that Service Request # 1-1406857287 was opened but I have not received any correspondence since then - it has been 2 weeks.  I have emailed 3 times asking how I can track this service request but have had no response.  Can you please advise how I can track this.

Thanks

 

---

Re : Problem with releasing module licenses on network dongle

October 6, 2016, 4:00 am

≫ Next: Re : Problem with releasing module licenses on network dongle

≪ Previous: Re : Problem with releasing module licenses on network dongle

$

0

0

Hi,

We have forwarded the request to our assigned Engineer. He will get back to you.

Thanks,
Heena

Re : Problem with releasing module licenses on network dongle

October 6, 2016, 6:40 am

≫ Next: SHK problem on Windows 10

≪ Previous: Re : Problem with releasing module licenses on network dongle

$

0

0

Can you please tell me if there is any way to track the request that doesn't involve waiting for an email?

SHK problem on Windows 10

October 6, 2016, 12:46 pm

≫ Next: Re : SHK problem on Windows 10

≪ Previous: Re : Problem with releasing module licenses on network dongle

$

0

0

Years ago my company developed a .NET application and protected it using SHK (API protection and envelope).
The application works fine on Windows 7 and we delivered it to many customers.

But when the application is installed on Windows 10, it takes more than 40 seconds to start and this is very annoying.
The problem does not arise if we run the executable without the envelope protection, but we don't want to distribute it to avoid reverse engineering.

Is there any workaround to solve this problem on Windows 10 ?

Thank you for any help you can provide.

Re : SHK problem on Windows 10

October 6, 2016, 11:36 pm

≫ Next: Error 203 when running application that accesses dongle from Visual Studio 2012

≪ Previous: SHK problem on Windows 10

$

0

0

Hi,

Hope you are doing good.

The issue mentioned by you above, require some detail investigation.

Therefore, it is requested to send an Email to support@safenet-inc.com with all the details.

We would be happy to assist you.

Thanks,
Heena

Error 203 when running application that accesses dongle from Visual Studio 2012

October 7, 2016, 6:59 am

≫ Next: Re : Error 203 when running application that accesses dongle from Visual Studio 2012

≪ Previous: Re : SHK problem on Windows 10

$

0

0

Hi

When we build our application as 64 bit, we get an error 203 when reading the dongle - this only happens when running the app from Visual studio, if we run the exe it doesn't give the error.

We are using the 64bit Sentinel dlls. It works fine in 32 bit.

This is for the the Sentinal Dual dongle network and standalone.

Is there something we can do to correct this.