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

Re : Problem accessing Sentinel EMS

May 11, 2017, 7:06 am
$
0
0
Thanks for your fast answer.

The service "Sentinel EMS" is not runnint (I have one called "Sentinel LDK License Manager")

The service "SQL Server (EMSDATABASE)" is running.

When manually launching "ems-startservice.bat" go no error

d:\Program Files (x86)\Gemalto\Sentinel EMS>ems-startservice.bat
stopping Sentinel EMS Service....
starting Sentinel EMS Service....
↧
Search

Re : Problem accessing Sentinel EMS

May 11, 2017, 9:01 am
$
0
0
Trying uninstall/reinstall.

Here is the log of failing installation

2017-04-25 09:55:58,507 DEBUG main LocalDBConnection - ARG Database info: 127.0.0.1:17476:EMSDB
2017-04-25 09:55:58,508 DEBUG main LocalDBConnection - ARG Database upgrade & File Path info:   : local
2017-04-25 09:55:58,600 DEBUG main LocalDBConnection - status:  1
2017-04-25 09:55:58,806 DEBUG main EMSPingDatabase - ARG Database info: 127.0.0.1:17476:EMSDB:1
2017-04-25 09:55:58,807 DEBUG main EMSPingDatabase - ARG Database upgrade & File Path info: 0  :   :   :   : newDB  : local
2017-04-25 09:55:58,877 DEBUG main EMSPingDatabase - WA url:  jdbc:jtds:sqlserver://127.0.0.1:17476;instance=EMSDATABASE;useNTLMv2=true
2017-04-25 09:55:58,878 DEBUG main EMSPingDatabase - WA SQLException:  
2017-04-25 09:55:58,878 DEBUG main EMSPingDatabase - JDBC connection attempted 
2017-04-25 09:55:58,904 DEBUG main EMSPingDatabase - permissionLevel:  1
2017-04-25 09:55:58,907 ERROR main EMSPingDatabase - SQLException:  
java.sql.SQLException: Database 'EMSDB' does not exist. Make sure that the name is entered correctly.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:368)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2820)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2258)
at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:632)
at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:723)
at net.sourceforge.jtds.jdbc.JtdsStatement.execute(JtdsStatement.java:1160)
at EMSPingDatabase.checkEMSSchema(EMSPingDatabase.java:159)
at EMSPingDatabase.main(EMSPingDatabase.java:105)
2017-04-25 09:55:58,908 DEBUG main EMSPingDatabase - status:  3
2017-04-25 09:56:35,889 DEBUG main EMSDatabaseSetup - Entered EMSDatabaseSetup class
2017-04-25 09:56:35,890 DEBUG main EMSDatabaseSetup - ARG Database info: 127.0.0.1:17476:EMSDB:true
2017-04-25 09:56:35,890 DEBUG main EMSDatabaseSetup - ARG Database File Path info: D:\Program Files (x86)\Gemalto\Sentinel EMS:C:\Program Files\Microsoft SQL Server\MSSQL10_50.EMSDATABASE\MSSQL\Data:newDB:local
2017-04-25 09:56:35,969 DEBUG main EMSDatabaseSetup - WA url:  jdbc:jtds:sqlserver://127.0.0.1:17476;instance=EMSDATABASE;useNTLMv2=true
2017-04-25 09:56:35,969 DEBUG main EMSDatabaseSetup - WA SQLException:  
2017-04-25 09:56:35,969 DEBUG main EMSDatabaseSetup - JDBC connection attempted 
2017-04-25 09:56:35,997 DEBUG main EMSDatabaseSetup - Got Connection
2017-04-25 09:56:35,997 DEBUG main EMSDatabaseSetup - dbTypeOption newDB
2017-04-25 09:56:35,997 DEBUG main EMSDatabaseSetup - *************** Creating database for EMS 7.4 ****************
2017-04-25 09:56:35,997 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath  : \Database\SQL Scripts\EMS_CreateEMSDb.sql
2017-04-25 09:56:35,997 DEBUG main EMSDatabaseSetup - ARG params  : [Ljava.lang.String;@4534b60d
2017-04-25 09:56:35,997 DEBUG main EMSDatabaseSetup - ARG checkReq  : true
2017-04-25 09:56:36,006 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath read 
2017-04-25 09:56:36,007 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executing
2017-04-25 09:56:36,576 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executed 
2017-04-25 09:56:36,576 DEBUG main EMSDatabaseSetup - ARG EMSCreateNew status : 0
2017-04-25 09:56:36,576 DEBUG main EMSDatabaseSetup - ARG status : 0
2017-04-25 09:56:36,576 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath  : \Database\SQL Scripts\EMS_DB.sql
2017-04-25 09:56:36,576 DEBUG main EMSDatabaseSetup - ARG params  : null
2017-04-25 09:56:36,576 DEBUG main EMSDatabaseSetup - ARG checkReq  : false
2017-04-25 09:56:36,595 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath read 
2017-04-25 09:56:36,602 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executing
2017-04-25 09:56:41,106 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executed 
2017-04-25 09:56:41,106 DEBUG main EMSDatabaseSetup - ARG status EMSDbSqlPath : 0
2017-04-25 09:56:41,106 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath  : \Database\SQL Scripts\EMS_DB_SEED.sql
2017-04-25 09:56:41,106 DEBUG main EMSDatabaseSetup - ARG params  : null
2017-04-25 09:56:41,106 DEBUG main EMSDatabaseSetup - ARG checkReq  : false
2017-04-25 09:56:41,112 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath read 
2017-04-25 09:56:41,117 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executing
2017-04-25 09:56:41,280 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executed 
2017-04-25 09:56:41,280 DEBUG main EMSDatabaseSetup - ARG status EMSDBSeedSqlPath : 0
2017-04-25 09:56:41,280 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath  : \Database\SQL Scripts\EMS_DB_SEED_HASP50.sql
2017-04-25 09:56:41,280 DEBUG main EMSDatabaseSetup - ARG params  : null
2017-04-25 09:56:41,280 DEBUG main EMSDatabaseSetup - ARG checkReq  : false
2017-04-25 09:56:41,281 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath read 
2017-04-25 09:56:41,282 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executing
2017-04-25 09:56:41,327 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executed 
2017-04-25 09:56:41,327 DEBUG main EMSDatabaseSetup - ARG status EMSDBSeedHASPSqlPath : 0
2017-04-25 09:56:41,327 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath  : \Database\SQL Scripts\CONTACT_TEMPLATE_SEED.sql
2017-04-25 09:56:41,328 DEBUG main EMSDatabaseSetup - ARG params  : null
2017-04-25 09:56:41,328 DEBUG main EMSDatabaseSetup - ARG checkReq  : false
2017-04-25 09:56:41,328 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath read 
2017-04-25 09:56:41,328 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executing
2017-04-25 09:56:41,338 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executed 
2017-04-25 09:56:41,338 DEBUG main EMSDatabaseSetup - ARG status EMSDBContactTemplateSeedPath : 0
2017-04-25 09:56:41,338 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath  : \Database\SQL Scripts\EMS_DEMO_SEED.sql
2017-04-25 09:56:41,338 DEBUG main EMSDatabaseSetup - ARG params  : null
2017-04-25 09:56:41,338 DEBUG main EMSDatabaseSetup - ARG checkReq  : false
2017-04-25 09:56:41,343 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath read 
2017-04-25 09:56:41,346 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executing
2017-04-25 09:56:43,426 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executed 
2017-04-25 09:56:43,426 DEBUG main EMSDatabaseSetup - ARG status EMSDBSeedDemoPath : 0
2017-04-25 09:56:43,426 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath  : \Database\SQL Scripts\EMS_DB_SEED_SAAS.sql
2017-04-25 09:56:43,426 DEBUG main EMSDatabaseSetup - ARG params  : null
2017-04-25 09:56:43,426 DEBUG main EMSDatabaseSetup - ARG checkReq  : false
2017-04-25 09:56:43,427 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath read 
2017-04-25 09:56:43,428 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executing
2017-04-25 09:56:43,532 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executed 
2017-04-25 09:56:43,532 DEBUG main EMSDatabaseSetup - ARG status SaaSScript : 0
2017-04-25 09:56:43,532 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath  : \Database\SQL Scripts\EMS_DB_SEED_LDKSAAS.sql
2017-04-25 09:56:43,532 DEBUG main EMSDatabaseSetup - ARG params  : null
2017-04-25 09:56:43,532 DEBUG main EMSDatabaseSetup - ARG checkReq  : false
2017-04-25 09:56:43,532 DEBUG main EMSDatabaseSetup - ARG sqlScriptPath read 
2017-04-25 09:56:43,532 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executing
2017-04-25 09:56:43,537 DEBUG main EMSDatabaseSetup - ARG EMSDatabasePS executed 
2017-04-25 09:56:43,537 DEBUG main EMSDatabaseSetup - ARG status EMSDBSeedLDKSAASSqlPath : 0
2017-04-25 09:56:43,537 DEBUG main EMSDatabaseSetup - Inside updatenodeIdentifier
2017-04-25 09:56:43,538 DEBUG main EMSDatabaseSetup - VendorId=1
2017-04-25 09:56:43,538 DEBUG main EMSDatabaseSetup - nodeIdentifier=null
2017-04-25 09:56:43,538 DEBUG main EMSDatabaseSetup - Updataing nodeIdentifier for vendor Id 1
2017-04-25 09:56:43,642 DEBUG main EMSDatabaseSetup - Inside updatenodeIdentifier
2017-04-25 09:56:43,643 DEBUG main EMSDatabaseSetup - ARG finally 
2017-04-25 09:56:44,583 DEBUG main PropertyReplace - WA SQLException:  
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - JDBC connection attempted 
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - Got Connection
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: D:\Program Files (x86)\Gemalto\Sentinel EMS\EMSServer\webapps\ems
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: 127.0.0.1
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: 17476
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: EMSDB
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: 
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: 
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: 
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: 25
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: ems@entitlementpublisher.com
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: false
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: 8080
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: 8443
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: true
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: false
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: local
2017-04-25 09:56:44,584 DEBUG main PropertyReplace - ARG: sqlInstance2.2
2017-04-25 09:57:08,059 DEBUG main EMSDatabaseMWUpdate - ARG finally 
2017-04-25 09:57:09,583 DEBUG main EMSDatabaseMWUpdate - ARG finally 
2017-04-25 09:57:09,583 DEBUG main EMSDatabaseMWUpdate - ARG finally 
2017-04-25 09:57:10,905 DEBUG main EMSWSCall - Entered EMSWSCall class
2017-04-25 09:57:10,930 DEBUG main EMSWSCall - contextFilePath->D:\Program Files (x86)\Gemalto\Sentinel EMS\EMSServer\webapps\ems\META-INF\context.xml::dbServer->127.0.0.1::dbPort->17476::dbName->dbName::dbUsername->sa::emsUrl->http://127.0.0.1:8080/ems/
2017-04-25 09:57:10,931 DEBUG main EMSWSCall - inside fresh block
2017-04-25 09:57:20,931 DEBUG main EMSWSCall - calling login webservice
2017-04-25 09:57:21,952 DEBUG main EMSWSCall - IOException-java.net.ConnectException: Connection refused: connect
2017-04-25 09:57:41,952 DEBUG main EMSWSCall - calling login webservice
2017-04-25 09:57:42,958 DEBUG main EMSWSCall - IOException-java.net.ConnectException: Connection refused: connect
2017-04-25 09:58:12,958 DEBUG main EMSWSCall - calling login webservice
2017-04-25 09:58:13,964 DEBUG main EMSWSCall - IOException-java.net.ConnectException: Connection refused: connect
2017-04-25 09:58:23,964 DEBUG main EMSWSCall - calling login webservice
2017-04-25 09:58:24,969 DEBUG main EMSWSCall - IOException-java.net.ConnectException: Connection refused: connect
2017-04-25 09:58:24,969 DEBUG main EMSWSCall - login unsuccesful
2017-04-26 14:37:09,723 DEBUG main EMSDBUpgradeForPatch - Entered EMSDBUpgradeForPatch class
2017-04-26 14:37:09,724 DEBUG main EMSDBUpgradeForPatch - ******** EMS 7.5 Found ********
2017-04-26 14:37:09,724 DEBUG main EMSDBUpgradeForPatch - EMSDatabase 7.5 upgrading to 7.5.4
2017-04-26 14:37:09,799 DEBUG main EMSDBUpgradeForPatch - ARG Database info: 127.0.0.1:17476:EMSDB
2017-04-26 14:37:09,799 DEBUG main EMSDBUpgradeForPatch - ARG Database File Path info: D:\Program Files (x86)\Gemalto\Sentinel EMS:D:\Program Files (x86)\Gemalto\Sentinel EMS\EMSServer\webapps\ems\META-INF\context.xml
2017-04-26 14:37:09,988 DEBUG main EMSDBUpgradeForPatch - Got Connection
2017-04-26 14:37:09,988 DEBUG main EMSDBUpgradeForPatch - ARG sqlScriptPath  : \Database\SQL Scripts\UpdateValuesFrom753to754.sql
2017-04-26 14:37:09,988 DEBUG main EMSDBUpgradeForPatch - ARG params  : null
2017-04-26 14:37:09,989 DEBUG main EMSDBUpgradeForPatch - ARG checkReq  : false
2017-04-26 14:37:10,000 DEBUG main EMSDBUpgradeForPatch - ARG sqlScriptPath read 
2017-04-26 14:37:10,001 DEBUG main EMSDBUpgradeForPatch - ARG EMSDatabasePS executing
2017-04-26 14:37:10,187 DEBUG main EMSDBUpgradeForPatch - ARG EMSDatabasePS executed 
2017-04-26 14:37:10,187 DEBUG main EMSDBUpgradeForPatch - ARG error status - Upgrade : 0
2017-04-26 14:37:10,187 DEBUG main EMSDBUpgradeForPatch - ARG finally 

↧
↧

Re : Problem accessing Sentinel EMS

May 11, 2017, 9:10 am
$
0
0
Same error at second installation.
↧

Re : Problem accessing Sentinel EMS

May 15, 2017, 3:12 am
$
0
0
Problem solved by technical support team.

The problem was a previous JAVA installation not recognized by Sentinel EMS installer. 
↧

Re : Problem accessing Sentinel EMS

May 15, 2017, 4:59 am
$
0
0
Hi Christophe,

Thanks for sharing the information!

Glad to know issue has been fixed by our Technical Support team. Feel free to reach back to us in case of any concern in future.

Regards,
Gemalto Support.
↧
↧

Sentinel EMS, best OS

May 17, 2017, 8:06 am
$
0
0
We are new to Gemalto protection solution. After reading the docs, we have some high level questions.

We currently have no netwrok infrastructure and we are checking to get one.

As far as I understand, we need to have a server for managing/generating licence. It is "Sentinel EMS".
I've seen that Sentinel EMS only work on Windows servers ??
 Is is right. (for security purpose I would have tought that linux servers were better).

So we need to setup somewhere a windows server. Which windows version is the best for that ? (Window8 seem not a good choice to me. I've read that the windows server version were better. Which version can you suggest ?)
↧

Re : Sentinel EMS, best OS

May 17, 2017, 11:41 pm
$
0
0
Hello Christophe,

Thanks for raising your concern.

Please help us know which EMS are you using.

We have two different flavors of EMS as mentioned below: 

1- Sentinel EMS Enterprise.
2- Sentinel LDK-EMS, which is a component of LDK software development kit.

Also please share the version details to guide you better.

Regards,
Parth
↧

Re : Sentinel EMS, best OS

May 18, 2017, 3:24 am
$
0
0
We received a box labelled "Sentinel LDK"

↧
Search

Re : Sentinel EMS, best OS

May 18, 2017, 7:23 am
$
0
0
Hello Christophe,

Thanks for the response.

Sentinel LDK-EMS is supported for operating systems releases from windows 7 to windows 10 (without device guard enabled) as per the released guidelines.

However, it is advised to reach our support  at technical.support@gemalto.com for any help in integrating the solution as per your specific requirement.  

Regards,
Parth
↧
↧

Re : Sentinel EMS, best OS

May 18, 2017, 8:49 am
$
0
0
Do any "Windows Server" versions would be better for security purpose  ?
We are used to Linux servers.

We already contacted the technical support, but no answer since monday :(
↧

Re : Sentinel EMS, best OS

May 19, 2017, 12:02 am
$
0
0
Hello Christophe,

Thanks for the reply.

The supported versions for windows servers are Windows Server 2003 SP2, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012 R2.

However, the implementation of security infrastructure would be more on the side of IT team integrating the solution as per their policies.

Just keeping in notice that we also provide hosted instances of Sentinel EMS to the customers which are managed by our team for its security and other maintenance.

For more information on hosted instance, you can get in touch with our sales team.

Kindly help us get the support incident ID you have opened so that we shall notify the assigned technician to get back to you over the same.


Regards,
Parth



↧

How to attach a usb master key on windows xp(virtualbox)

May 21, 2017, 10:09 am
$
0
0
Master,

I bought a starter kit and now I want to attach master key on windows xp.
**The widnows xp was installed on virtualbox 5.1.22(host: Mac 10.12.4)**

I encountered a problem.
widdows xp cannot attach the master key (take a look attached image). 
I think maybe the host os (mac) is holding the master key even I unload driver(kextunload -b  com.aladdin.kext.aksfridge).

Could you give me an advice?
thanks



↧

Re : How to attach a usb master key on windows xp(virtualbox)

May 22, 2017, 4:00 am
$
0
0
Hello Diuming,

Thanks for the query.

Keeping in notice that Windows XP operating system has been declared end of support by Microsoft.

However, this particular issue seems to be related to connecting any USB device over the guest on virtual box hosted on a MAC OSX.

Could you please confirm if you are able to use any other USB device (like pen-drives etc) over the guest OS or not ?

This could help us narrow down if the issue is specific to Master Key.

Looking forward for the reply.

Regards,
Parth


 
↧
↧

Re : How to attach a usb master key on windows xp(virtualbox)

May 22, 2017, 5:03 am
$
0
0
Hi Master,

Yes. I can attach protection key on guest windows xp(virtualbox).
take a look attached images, please

thanks
↧

Re : How to attach a usb master key on windows xp(virtualbox)

May 22, 2017, 5:31 am
$
0
0
Hi Master,

update:
Only the protection key was configured as driverless that can attach to guest windows xp.

thanks for helping me
↧
Search

Re : How to attach a usb master key on windows xp(virtualbox)

May 23, 2017, 3:07 am
$
0
0
Hello Diuming,

Thanks for the response.

We recommend to kindly get in touch with our support team at technical.support@gemalto.com for detailed investigation on the concern.

Regards,
Parth
↧

Re : Is there a 64-bit delphi static object for LDK sentinel 7.1 API?

May 23, 2017, 5:19 am
$
0
0
Dear Peter, Dear customers,

We have now fully integrated the generation of the "vendorised" Sentinel LDK Delphi Static Libraries (32 & 64 bit) into our Gemalto Servers.


Please use the “Sentinel LDK Master Wizard” tool, to generated and download the latest LDK Delphi Runtime Libraries (.OBJ) and associated LDK VendorCode file.

 

For evaluation of Sentinel LDK, please download "Sentinel LDK 7.5": https://sentinelcustomer.gemalto.com/DownloadNotice.aspx?dID=64424541086


After installation of Sentinel LDK Vendor Suite, you can go to :

C:\Program Files (x86)\Gemalto Sentinel\Sentinel LDK\API\Runtime\Delphi\


To find :

“hasp_unit.pas” for definition of fonctions & error code.

“hasp_windows_delphixe_demo.obj” Win32 COFF object for the DEMOMA batch code.

“hasp_windows_x64_delphixe_demo.obj” x64 COFF object for the DEMOMA batch code.

 

For the compiled samples and sample source code:

C:\Program Files (x86)\Gemalto Sentinel\Sentinel LDK\Samples\Runtime\Delphi\x64

C:\Program Files (x86)\Gemalto Sentinel\Sentinel LDK\Samples\Runtime\Delphi\win32

 

See attached “readme” PDF file for usage of samples.

 

Regards,

Olivier

↧
↧

Is it possible upgrade protection key and master key to driverless?

May 23, 2017, 11:22 pm
$
0
0
Hi Master,

I have some questions about Sentinel HASP.
Q1)Is it possible to upgrade protection key and master key to driverless?
Q2)Do you provide some tools to do this action except Sentinel EMS?

thanks 
↧

Re : Is it possible upgrade protection key and master key to driverless?

May 24, 2017, 1:49 am
$
0
0
Hello Diuming,

Thanks for the query.

Please find the answers below on the raised points.

Q1)Is it possible to upgrade protection key and master key to driverless?

Ans : Yes, the protection keys can be upgraded to driver-less by the help of creating a modification over the existing product. In this, we would require to select the option for "upgrade to driver-less" and then the entitlement created for that modification would be for driver-less keys.

Please keep a caution that upgrade for driver-less keys is irreversible process. Hence, the keys which are made HL-driverless can be reconverted back to driver dependent configuration.

The new Sentinel LDK Master keys are per-configured to create HL-driverless keys. However for old configuration,  you may need to do an online reintroduction to get the feature in the master key.


Q2)Do you provide some tools to do this action except Sentinel EMS?

Ans : you can alternatively use LicGen API for the same operation. The Sentinel ToolBox contains license generation  API which can be used for practicing license generation using APIs.

For upgrade to driver-less configuration, we would need to parse the respective XML while license generation.

<?xml version="1.0" encoding="utf-8"?> <sentinel_ldk:license schema_version="1.0"         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"         xmlns:sentinel_ldk="http://www.safenet-inc.com/sentinelldk">    <enforcement_type>HL</enforcement_type>    <upgrade_to_driverless>Yes</upgrade_to_driverless> </sentinel_ldk:license>


For better understanding, you can take refence of the API documentaion in the ToolBox > "Help".

If you need any technical assistance then you are always invited to raise your concerns with our support technical.support@gemalto.com .

Regards,
Parth
↧

sentinel HL key driver problem

May 24, 2017, 10:18 pm
$
0
0

Hi

I am facing problem on my dongle, it was working perfectly on TEMS 16  but suddenly stopped working, when I insert it the driver failed to installed, I try the following:

1.       Download the latest driver version (Sentinel_LDK_Run-time_setup)

2.       Install latest USB drivers

3.       Install fresh copy of windows

4.       Try another laptop

5.       Update the driver from windows update

But still the driver failed to install, note that the red light is stable not blinking

Check below photos please:




↧
Viewing all 1619 articles
Browse latest View live
Search