Re : Deadlock in sentinel ldk api and envelope

September 2, 2016, 3:38 am

≫ Next: hasp_login() hangs on Dell computer

≪ Previous: Deadlock in sentinel ldk api and envelope

Hi David,

Hope you are doing good.

For the mentioned query, kindly confirm the LDK version you are using at your end.

Also, kindly place the hasp_rt.exe (generated while Envelope protection) in the same folder as exe, and it should manage the task of deadlock occurred in case when you make a hasp_login() and you free library without hasp_logout().

For the other deadlock received in WaitForSingleObject() please make sure that before quitting the exe, proper logout from the respective dll is called.

Thanks,
Heena

↧

hasp_login() hangs on Dell computer

September 2, 2016, 10:11 am

≫ Next: Re : hasp_login() hangs on Dell computer

≪ Previous: Re : Deadlock in sentinel ldk api and envelope

Hi all,

I have a new DELL 5810 computer installed with Windows7/64-bit. On this computer the hasp_login() API function does never return with or without a valid key present. So there is no error message or return code, the function simply never returns. Envelope protected programs also do not work.

We have seen this problem before, but never found a solution. It seems to happen only on DELL computers with National Instruments software (Labview) installed.

Any ideas for a solution or how to investigate ?

↧

Re : hasp_login() hangs on Dell computer

September 2, 2016, 11:34 am

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

≪ Previous: hasp_login() hangs on Dell computer

Hi Fibonacci,

Hope you are keeping well.

We need to investigate on this issue further. Kindly send one email with all the information to "support@safenet-inc.com".

Regards,

Anubhav

↧

Re : Problem with releasing module licenses on network dongle

September 4, 2016, 11:21 pm

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

≪ Previous: Re : hasp_login() hangs on Dell computer

Hi,

Regrading the mentioned scenario, there is a feature called Application timeout. In this the server can disconnect a user, and release the license for use by other users, after a pre-determined amount of time has elapsed without a Sentinel SuperPro query or heartbeat message. This helps prevent idle users from tying up licenses, and permits recovery of licenses used by aborted programs or workstations that are unexpectedly disconnected from the network.

This time is by default 120 secs. Using SuperPro APIs ( RNBOsproSetHeartBeat) or configuration file, you can define other period to override the default seconds.

For eg, RNBOsproSetHeartBeat( packet, MIN_HEARTBEAT * 3 ); gives you 60x3 = 180 secs
MIN_HEARTBEAT=60sec, so the sever will wait 180secs before releasing the license back to the pool.

Please feel free to get back in case of any query.

Thanks,
Heena

↧

Re : Problem with releasing module licenses on network dongle

September 5, 2016, 3:39 am

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

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

Hi Heena

I understand about the heartbeat and I am using that. Maybe I didn't explain my scenario very well.

Lets say there are 2 modules in the application module A and B. A client has 3 licences for module A and 1 for module B. On the network dongle we have created a rawdata feature for each module which stores the number of licences available for the module and how many have been used so far. The modules are used by certain functions in the application not always when opening the application. So if the user opens module A the feature for module A is updated to have 1 licence used and then the user opens module B the feature for module B on the dongle is updated with 1 licence used for module B. Then if the user loses connection to the network, the core dongle license is released when the heartbeat times out but the module A and B features still show that a license is used.

Is there a way to implement this solution with modules that will allow the release of these licenses when the heartbeat times out?

Thanks

↧

Re : Problem with releasing module licenses on network dongle

September 6, 2016, 5:24 am

≫ Next: Re : hasp_login() hangs on Dell computer

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

Hi,

This cannot be achieved at Module level. For the same you need to get your own implementation to count the no. of licenses from each module that are consumed or free. Now if the application is timed out all the module level licenses should also get refreshed into the pool.

Thanks,
Heena

↧

Re : hasp_login() hangs on Dell computer

September 7, 2016, 8:50 am

≫ Next: Re : hasp_login() hangs on Dell computer

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

Thank you,

Problem was solved by support.

Appeared to be a software version issue.

Regards.

↧

Re : hasp_login() hangs on Dell computer

September 8, 2016, 6:03 am

≫ Next: Using Envelope for protection Visual FoxPro program

≪ Previous: Re : hasp_login() hangs on Dell computer

Hi Fibonacci,

Thank you for reply.

Please feel free to contact us whenever you have any issue.

Regards,

Anubhav

↧

Using Envelope for protection Visual FoxPro program

September 13, 2016, 7:35 am

≫ Next: Re : Using Envelope for protection Visual FoxPro program

≪ Previous: Re : hasp_login() hangs on Dell computer

I was used envelope from LDK 7.4 for protect Microsoft VisualFoxpro 9.0 SP2 exe file.

I received messages:

0006   2016-09-13 11:57:34   Windows - Starting Protection Process - C:/Users/Public/Documents/oper_vok.exe
0007   2016-09-13 11:57:34   The file contains unknown extender data. It will be removed (872)
0008   2016-09-13 11:57:38   Windows - Finished Protection Process - C:\Users\Programmer\Documents\SafeNet\Sentinel LDK 7.4\VendorTools\VendorSuite\Protected\oper_vok.exe

Message 0007: The file contains unknown extender data. It will be removed (872)

What mean this message ? Will be fullfunction my protected program after such message?

Help me please.

Alexander

↧

Re : Using Envelope for protection Visual FoxPro program

September 14, 2016, 6:09 am

≫ Next: Re : Using Envelope for protection Visual FoxPro program

≪ Previous: Using Envelope for protection Visual FoxPro program

Hello Alexander,

Thanks for your query.

Please be informed that this warning can be ignored if it is not causing issue. Kindly confirm by executing the protected application if any problem is being faced.

This warning comes when the unprotected application contains certain data that needs to be taken care before encrypting. It may appear when the executable file being protected is a launcher file for other libraries.

Kindly uncheck the overlay support option in sentinel envelope and let us know if that helps removing the warning.

Regards,

Parth

↧

Re : Using Envelope for protection Visual FoxPro program

September 14, 2016, 9:31 am

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

≪ Previous: Re : Using Envelope for protection Visual FoxPro program

Hello Parth

I execute protection with checked the overlay support option and with unchecked the overlay support option.

Messages from sentinel envelope see below:

checked the overlay support option

0001   2016-09-14 16:21:50   Project АРМы-базовая версия-overlay-on.prjx loaded successfully
0002   2016-09-14 16:22:31   Windows - Starting Protection Process - C:/Users/Public/Documents/oper_vok.exe
0003   2016-09-14 16:22:31   The file contains unknown extender data. It will be removed (872)
0004   2016-09-14 16:22:37   Windows - Finished Protection Process - C:\Users\Programmer\Documents\SafeNet\Sentinel LDK 7.4\VendorTools\VendorSuite\Protected\oper_vok.exe

unchecked the overlay support option

0005   2016-09-14 16:22:42   Windows - Starting Protection Process - C:/Users/Public/Documents/oper_vok.exe
0006   2016-09-14 16:22:42   The file contains unknown extender data. It will be removed (872)
0007   2016-09-14 16:22:42   Warning : The file contains unknown extender data. Overlay Protection should be enabled.
0008   2016-09-14 16:22:48   Windows - Finished Protection Process - C:\Users\Programmer\Documents\SafeNet\Sentinel LDK 7.4\VendorTools\VendorSuite\Protected\oper_vok.exe

Now I will execute protected application for finding any problem.

Alexander

↧

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

September 14, 2016, 10:58 am

≫ Next: Re : Using Envelope for protection Visual FoxPro program

≪ Previous: Re : Using Envelope for protection Visual FoxPro program

We have installed RMS on three Windows servers and configured them with a redundant license file lsrvrlf (there is no standalone license file lservrc).

When rebooted two of them start in "standalone" mode and one in "redundant" mode which we know because VLSgetLeaderServerName() is returning VLS_NON_REDUNDANT_SRVR on one system and LS_SUCCESS on the other two.

However, if we simply stop and restart the services of the two "standalone" RMS servers they then correctly restart in "redundant" mode.

This problem is reproducible every time.

Any ideas ?

↧

Re : Using Envelope for protection Visual FoxPro program

September 15, 2016, 12:57 am

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

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

Hello Alexander,

Thanks for the update.

Please check and let us know if any problem occurs in execution of protected application.

Regards,
Parth

↧

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

September 15, 2016, 9:10 am

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

≪ Previous: Re : Using Envelope for protection Visual FoxPro program

Hi Mr Steele,

Hope you are doing well!

As per the concern you shared there are few things which we need to know\test before starting the troubleshooting process.

1. As you said one of the Servers work as Redundant, do we know which of them always works redundant? Is that our Leader\Primary server?

2. In case of Redundant Servers we need to make sure to Keep "lsrvrlf" file in WinNT location of every server. Please share if did we keep "lsrvrlf" file in every RMS server's location. Once the file is place in all the Server's location, kindly restart the servers in the same order in which "lsrvrlf" file is created.

Hope that helps. Please share if there is anything else I may help you for?

Regards,

Ashish Kumar

↧

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

September 15, 2016, 9:29 am

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

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

Hi Ashish,

Thanks for getting back to me,

The primary and secondary servers always start in standalone mode and the tertiary always starts in redundant mode after a Windows reboot.

The lsrvrlf files are definitely correctly located and there are no lservrc files anywhere. The problem ONLY occurs after a Windows restart and we find that when we manually stop and start the RMS service it functions correctly (i.e. the primary and secondary then start in redundant mode). For clarification I have detailed the steps below....

1. Reboot Windows on all three servers.

2. Log on to each server.

3. Check the status of RMS on each server:

(a) On the primary server the RMS service is in standalone mode.

(b) On the secondary server the RMS service is in standalone mode,

4. On the primary server stop the RMS service and restart it: after it has restarted it is in redundant mode.

5. On the secondary server stop the RMS service and restart it: after it has restarted it is in redundant mode.

6. After steps 4 and 5 the redundant server array then behaves as it is supposed to - we can do fail-overs etc..

This behaviour occurs every time.

Best regards,

Ian.

↧

Re : Problem with releasing module licenses on network dongle

September 20, 2016, 4:27 am

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

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

Thanks for your response.

We have been looking into developing something on our side for this - can you tell me if there is a recommended way of doing this.

We would need to know from the dongle which host PC/user has which core dongle licence so that we can release the modules requested by that host if needed. Is there an API call we can use to get this information. It is possible to see the host names that are connected to the dongle using the Sentinel monitoring tool so I assume there will be a way of getting that information - I just can't see anything in the documentation for it.

Please advise.

Thanks

↧

Re : Problem with releasing module licenses on network dongle

September 20, 2016, 5:48 am

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

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

Hi,

For further assistance kindly send an Email to support@safenet-inc.com.

We would be happy to assist you.

Thanks,
Heena

↧

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

September 20, 2016, 8:26 am

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

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

Hi Ian,

There is a catch in the process in which redundant servers should be managed. Looks like the concern we are getting is because of the order in which we are restarting the RMS Servers (not machine).

Please follow below steps:

===========================

1. Once the "lsrvrlf" file is placed in the RMS Server's installed directory in all the three Server machines.

2. Restart the RMS Server(not machine) in the same order in which the RMS Server's order is set in "lsrvrlf" file.

This should fix the concern we have. However to know more about the process kindly refer to the Sentinel RMS Admin Guide.

If the above solution did not help. Feel free to e-mail us at: "support@safenet-inc.com".

Regards,

Ashish Kumar

↧

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

September 20, 2016, 8:33 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.

Hi Ashish,

Are you saying that the RMS redundant server functionality will only work if the servers are started up in a specific order ?

How can that considered to be a reasonable redundant server implementation when the whole point of having redundant servers is that they can go offline and come back online arbitrarily ? Please confirm that this is genuinely the case.

Regards,

Ian.

↧

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

September 20, 2016, 9:10 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.

Hi Ian,

This is the part of the process we follow while setting up the Redundant server's. Yes Sentinel RMS Server's may go down in any order in future. But to setup the Redundant server this is the process to follow.

All the information of How to Setup Redundant server is documented in Sentinel RMS System Administrator's Guide - Chapter "Redundant License Manager".

Regards,

Ashish Kumar

↧

Latest Images