Provisional license is the the trial license given for specific number of days.
It will show number of remaining days under "Restrictions" column in http://localhost:1947/_int_/features.html
Regards,
Ashish
Ashish
↧
Re : Unable to uninstall Sentinel v7.6
↧
Pc crashing, Error.log complains about driver
I have a problem with two identical systems, both have the same problems but not at the same time.
The PC's are equiped with 3 dongles, in the access.log only two dongles are continuously checked.
From a certain moment, the dongles are not being able to be read.
Could it be a threading issue in the license manager (hasmlms.exe).
If the logging is correct, the second application is connecting when the first has just logged out:
2018-06-12 17:18:25 127.0.0.1:61308 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)2018-06-12 17:18:25 127.0.0.1:61310 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)2018-06-12 17:18:25 127.0.0.1:61308 Administrator@CO1289-02 POST /api/loginex LOGIN_EX(lm=local,haspid=833652937,productid=2,feat=1,sess=00030C5B,api=7.50) result(0)2018-06-12 17:18:25 127.0.0.1:61308 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)2018-06-12 17:18:25 127.0.0.1:61308 Administrator@CO1289-02 POST /api/logout LOGOUT(lm=local,haspid=833652937,productid=2,feat=1,sess=00030C5B,duration=0) result(0)2018-06-12 17:18:26 127.0.0.1:61321 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)2018-06-12 17:18:26 127.0.0.1:61323 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)2018-06-12 17:18:26 127.0.0.1:61321 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)2018-06-12 17:18:26 127.0.0.1:61321 SYSTEM@CO1289-02 POST /api/loginex LOGIN_EX(lm=local,haspid=1008429944,productid=0,feat=0,sess=00030C5C,api=7.50) result(0)2018-06-12 17:18:26 127.0.0.1:61321 @127.0.0.1 POST /api/API_GET_INFO_XML GET_INFO_XML(XML) result(0)2018-06-12 17:18:26 127.0.0.1:61321 SYSTEM@CO1289-02 POST /api/logout LOGOUT(lm=local,haspid=1008429944,productid=0,feat=0,sess=00030C5C,duration=0) result(0)2018-06-12 17:18:26 127.0.0.1:61321 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)2018-06-12 17:18:26 127.0.0.1:61321 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)2018-06-12 17:18:26 127.0.0.1:61321 SYSTEM@CO1289-02 POST /api/loginex LOGIN_EX(lm=local,haspid=1008429944,productid=0,feat=0,sess=00030C5D,api=7.50) result(0)2018-06-12 17:18:26 127.0.0.1:61321 @127.0.0.1 POST /api/API_GET_INFO_XML GET_INFO_XML(XML) result(0)2018-06-12 17:18:26 127.0.0.1:61321 SYSTEM@CO1289-02 POST /api/logout LOGOUT(lm=local,haspid=1008429944,productid=0,feat=0,sess=00030C5D,duration=0) result(0)
I think I read somewhere we could make the different application listen to a separate port, in stead of all using the 1947 port number.
Error.log says:
2018-06-12 17:18:25 [2632] Failed to call driver (error 0xe000000c)
....
2018-06-15 07:30:37 [2632] Failed to call driver (error 0xe000000c)
Then:
2018-06-15 07:31:41 [2948] Local-only mode enabled (bind_local_only = 1)
2018-06-15 07:31:41 [2948] Local-only mode enabled (bind_local_only = 1)
2018-06-15 07:54:43 [2832] Local-only mode enabled (bind_local_only = 1)
2018-06-15 07:54:43 [2832] Local-only mode enabled (bind_local_only = 1)
2018-06-15 08:07:13 [2464] Local-only mode enabled (bind_local_only = 1)
2018-06-15 08:07:13 [2464] Local-only mode enabled (bind_local_only = 1)
Server machines are crashing every 5 days or so. This is a real problem for our customer, since these server show the userinterface of the plant of a dredging ship.
PS:
screenshot of the dongles is to show the types, the screenshot is made on sever1, while the logfiles are from server2
↧
↧
Re : Unable to uninstall Sentinel v7.6
Thank you Ashish.
It is written perpetual under the Restrictions column, so I believe I am not using the provisional license.
↧
Re : Pc crashing, Error.log complains about driver
Hi Edgar,
The logs show that all API calls have returned "result (0)" which means success. Hence the problem does not seem to be on the licensing side.
Your screenshot shows that all three keys have different batch codes.
Please check if the correct batch code is implemented in each application.
The license manager works on port 1947. The application does not define the port on their side. The linked libraries communicate directly with the license manager port as required.
It may be possible that some other application on the machine is using the same port due to which license manager is getting blocked.
Share the screenshot/details about the error faced when second application is launched while first is still running.
Please follow these steps for some additional logs-
1. Create 3 files in the following location as the given name-
C:\Users\<user name>\AppData\Local\SafeNet Sentinel\Sentinel LDK\hasp_48395.ini
C:\Users\<user name>\AppData\Local\SafeNet Sentinel\Sentinel LDK\hasp_48395.ini
C:\Users\<user name>\AppData\Local\SafeNet Sentinel\Sentinel LDK\hasp_59147.ini
C:\Users\<user name>\AppData\Local\SafeNet Sentinel\Sentinel LDK\hasp_61320.ini
2. Contents of each file should be below lines-
requestlog=1
errorlog=1
3. Enable "shows extensions of known file types" to confirm the file extension is ".ini" and not ".ini.txt"
4. Run your applications to replicate the issue
5. Share the log files created in the same folder
Regards,
Ashish
Ashish
↧
Re : Unable to uninstall Sentinel v7.6
Yes, this is a permanent license and not a trial.
Regards,
Ashish
Ashish
↧
↧
Re : Pc crashing, Error.log complains about driver
thanks for the info.
The error.log is also showing problems. This is small part of the log file:
2018-06-15 07:30:07 [2632] Failed to call driver (error 0xe000000c)
2018-06-15 07:30:07 [2632] Failed to call driver (error 0xe000000c)
2018-06-15 07:30:07 [2632] Failed to call driver (error 0xe000000c)
2018-06-15 07:30:35 [2632] Failed to call driver (error 0xe000000c)
2018-06-15 07:30:37 [2632] Failed to call driver (error 0xe000000c)
2018-06-15 07:30:37 [2632] Failed to call driver (error 0xe000000c)
2018-06-15 07:30:37 [2632] Failed to call driver (error 0xe000000c)
2018-06-15 07:31:41 [2948] Local-only mode enabled (bind_local_only = 1)
2018-06-15 07:31:41 [2948] Local-only mode enabled (bind_local_only = 1)
2018-06-15 07:54:43 [2832] Local-only mode enabled (bind_local_only = 1)
2018-06-15 07:54:43 [2832] Local-only mode enabled (bind_local_only = 1)
2018-06-15 08:07:13 [2464] Local-only mode enabled (bind_local_only = 1)
2018-06-15 08:07:13 [2464] Local-only mode enabled (bind_local_only = 1)
Our application is also logging HASP errors, we are logging the following. So maybe it is a problem in the library we linked to our application. But the other applications also don;t see their dongle info.
10-05-2018 11:53:41 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 11:55:07 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 11:56:21 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 11:57:15 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 11:58:07 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 11:59:16 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:00:00 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:01:17 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:01:59 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:02:49 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:03:52 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:04:29 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:04:59 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:05:50 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:06:36 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:07:27 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:08:25 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:09:49 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:11:06 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:12:03 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:12:56 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:14:10 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:15:18 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:16:10 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:16:43 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:17:22 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:18:04 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:18:42 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:19:20 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:20:16 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
10-05-2018 12:20:49 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
↧
Re : Pc crashing, Error.log complains about driver
two of the appplications are running using the service "System" account, which folder should I place their .ini file
↧
Re : Pc crashing, Error.log complains about driver
If the current logged in user is Administrator then you can put in the same user folder.
Otherwise use the Administrator folder.
If logs are not created then try in a different user folder.
Thanks,
Ashish
↧
Re : Pc crashing, Error.log complains about driver
Error.log
2018-06-15 07:30:37 [2632] Failed to call driver (error 0xe000000c)
Access log, thinks everything is OK???
2018-06-15 07:30:35 127.0.0.1:63243 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)
2018-06-15 07:30:35 127.0.0.1:63245 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)
2018-06-15 07:30:35 127.0.0.1:63243 Administrator@CO1289-02 POST /api/loginex LOGIN_EX(lm=local,haspid=833652937,productid=2,feat=1,sess=0003AA49,api=7.50) result(0)
2018-06-15 07:30:35 127.0.0.1:63243 [SRM]@127.0.0.1 POST /api/GET_FEATURES GETFEATURES() result(0)
2018-06-15 07:30:35 127.0.0.1:63243 Administrator@CO1289-02 POST /api/logout LOGOUT(lm=local,haspid=833652937,productid=2,feat=1,sess=0003AA49,duration=0) result(0)
Our application log
15-06-2018 07:29:30 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
15-06-2018 07:30:35 Warning DigiDlg ReCheckLicense MemoHasp: Error in ReadBlock - Internal error occurred in API.
↧
↧
Re : Pc crashing, Error.log complains about driver
I only get an accesslog of the application running under the Administrator account.
Possibly the other .ini files are not in the correct folder.
Can I check in a log file where the application will search for this .ini file?
↧
SmartKey (formerly Aladdin Knowledge, formerly Eutron) unreadable key
We are using driver 12.0.0. for USB key, and the sample software provided in the SDK (GenericWin32Dll\smartdem.c) to test several keys which have an issue. While some keys can be read from the beginning to the end of the test software, several other keys are not found and software reports
- ST_NONE_KEY : Key Not Found.
If we insist with that key, it may show up but it fails in the scrambling test:
- SmartKey found with protocol LOCAL
- Scrambling 3132333435363738 : ST_NONE_KEY : Key Not Found
This issue seems only to affect several keys, but not all of our keys, so it can't be said that is a system specific issue. Even trying the same keys on different hardware gives the same results: faulty keys are faulty on other system at the same way.
The strange thing is that the Smartke Programming Central (SPC) seems to find the faulty key ad it's able to reset it to defaults. Even when reset to defaults, the behavior is the same in the test application. SPC test feature does not report any issue with the faulty key.
Your help would be appreciated.
Thanks in advance and regards,
Stefano
↧
Customizing the EMS interface -feature name
Hi,
We want 'feature name' and 'RefID 1' to be displayed together everywhere where we need to display feature - eg. in Catalog-Feature list, entitlement ..Can we customize the EMS 4.1 interface?
Regards,
Surafel
↧
Re : SmartKey (formerly Aladdin Knowledge, formerly Eutron) unreadable key
Hello Stefano,
Thanks for raising the concern.
However, the SmartKey product has been discontinued long ago. Hence, the keys are not covered under support warranty as for now.
Regards,
Parth Kaushik
↧
↧
Re : SmartKey (formerly Aladdin Knowledge, formerly Eutron) unreadable key
Is there any way to retrieve the latest available driver and SDK, just to be sure that we are using the correct software versions? SPC reports version 12.1.0, while driver seems to be stuck at 12.0.0, as for skeylink.dll.
Thanks and regards
Stefano
↧
Re : SmartKey (formerly Aladdin Knowledge, formerly Eutron) unreadable key
Hello Stefano,
Thanks for the reply.
However, there is no way to provide the same as the product itself is out of production and support.
You may like to get in touch with gemalto sales representatives to check for the other product options available to meet your requirement.
Regards,
Parth Kaushik
↧
Re : SmartKey (formerly Aladdin Knowledge, formerly Eutron) unreadable key
Hello Parth,
we already migrated our product to Gemalto licensing solution, but unfortunately we still have to provide support for this oldest platform to our customers. I was just finding a way to detect if these keys need to be replaced and if so I need a way to justify it to the customer.
Thanks for your attention and regards,
Stefano
↧
Re : SmartKey (formerly Aladdin Knowledge, formerly Eutron) unreadable key
Hi Stefano,
Thanks for the response.
The version mentioned is the latest and was last updated on 2010. Since then, we have no further updated components or drivers. We didn't test the components since then on later platforms.
Hence, the error appearing could be due to faulty dongles or unsupported platform.
Unfortunately, there is no way to proceed with the query.
We appreciate your participation over the channel.
Regards,
Parth
↧
↧
Re : Pc crashing, Error.log complains about driver
Hi Edgar,
It seems that this issue will need detailed investigation.
Please contact our support team via Customer Portal https://supportportal.gemalto.com/csm/
Regards,
Ashish
Ashish
↧
Error code H0053
Hi!
When starting our application, we got the following message:
Does anybody knows what the problem could be?
I de-installed and installed the application and HASP again, but with no result.
↧
Re : Error code H0053
Dear Customer,
Thanks for writing in !
Please share the following detail:
- Open the Admin Control Center (http://localhost:1947/_int_/devices.html) on the license server from where the application is accessing the license key. Same machine in case of standalone license.
- Click on 'Configuration' option available on the left, then click 'Users' tab and share its screenshot.
Additionally, share the version of Sentinel HASP/LDK RTE which is being used?
Regards,
Gaurav Bhanot
↧