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

Re : Unable to uninstall Sentinel v7.6

June 12, 2018, 4:22 am
$
0
0
Hi Eeyong,

Haspdinst.exe and hasp_update_x64.exe have different operations and are independent of each other.

Haspdinst can be used to install/uninstall the drivers.
Hasp_update can be used to install the license.

Uninstalling the drivers will not remove any installed license.All existing licenses will still be active when drivers are installed again.

Regards,
Ashish
↧
Search

Re : Unable to uninstall Sentinel v7.6

June 12, 2018, 4:36 am
$
0
0
Thanks again Ashish.

Is there a way to remove the installed license?

regards,
eeyong
↧
↧

Re : Unable to uninstall Sentinel v7.6

June 12, 2018, 6:40 am
$
0
0
Please share the use case why you want to remove the license.

Regards,
Ashish
↧

Re : Unable to uninstall Sentinel v7.6

June 12, 2018, 10:13 pm
$
0
0
Here's the full story:

In my computer, I installed Sentinel Runtime Driver in administration mode. Then, I updated the v2c file with hasp_update.exe in administration mode as well.

However, I found that I need to install Sentinel Runtime Driver in non administration mode. It means that I need to uninstall Sentinel Runtime Driver (haspdinst.exe -r) and re-install it in non administration mode.

I wonder if there is any impact to the license updated in administration mode. As such, I prefer to remove the updated license and update it with non admnistration mode.

↧

Re : Unable to uninstall Sentinel v7.6

June 12, 2018, 11:29 pm
$
0
0
Sorry I have one more qustion.

When I access the following page: http://localhost:1947/_int_/devices.html
I could see that my key type is "HASP SL AdminMode".
If i click on the Certificates, I could see something like this:
Now, if I click on the Show button, the certificate content will be displayed.
But if I compared the certificate content with my v2c file, I could see that the contents are different.

Does it means that my v2c file is not updated correctly in the first place?
↧
↧

Re : Unable to uninstall Sentinel v7.6

June 13, 2018, 4:44 am
$
0
0
Please confirm if the V2C is for a provisional license or activated one?
The id shown in "Certificate" can be different from the id shown in V2C. Hence it can be ignored.

Error 65 you received while applying the V2C confirms that it has already been installed.

Sentinel Runtime always has to be installed with admin rights. The installation would fail if proper permissions are not there.

Please share why do you think that it has to be installed without admin permissions.

Regards,
Ashish

↧

Re : Unable to uninstall Sentinel v7.6

June 13, 2018, 10:09 pm
$
0
0
I am sorry but I don't know how to differentiate provisional license and activated license.
Could you tell me the differences?

In fact, we have a tool to store key values and we have to run the tool without administration mode. (due to company policy)
Now, if I run the tool with administration mode, everything is fine.
However, if I run the tool without administration mode, I will receive the following error:

So, I wonder if it is due to Sentinel Runtime which installed in administration mode. If yes, is there any possibility to install it without admin mode.

By the way, if Sentinel Runtime always has to be installed with admin mode, may I know if I have to run hasp_update.exe with  admin mode as well?
I asked the question because if I run hasp_update.exe without admin mode, I will receive error message: Input/output error.

Thank you.
↧

Re : Unable to uninstall Sentinel v7.6

June 13, 2018, 11:21 pm
↧
Search

Re : Unable to uninstall Sentinel v7.6

June 14, 2018, 2:42 am
$
0
0
Hi Ashish, I attached the screenshots for devices.html and features.html.

FYI I am still using haspdint 7.4. Here's my Runtime:

↧
↧

Re : Unable to uninstall Sentinel v7.6

June 14, 2018, 3:53 am
$
0
0
Hi Eeyong,

This would need a detailed investigation.
Please report the issue with your application vendor and ask him to contact us for the same. This will be required as we need some details from vendor side.

Regards,
Ashish
↧

Re : Unable to uninstall Sentinel v7.6

June 14, 2018, 4:48 am
$
0
0
OK thanks.
By the way, may I know how can I differentiate the provision license and non-provision license.
Could you please kindly share with me?

Thanks.
↧

Re : Unable to uninstall Sentinel v7.6

June 15, 2018, 6:14 am
↧

Pc crashing, Error.log complains about driver

June 17, 2018, 3:58 pm
$
0
0
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

June 18, 2018, 1:18 am
$
0
0
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

June 18, 2018, 1:34 am
$
0
0
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_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

↧
Search

Re : Unable to uninstall Sentinel v7.6

June 18, 2018, 1:41 am
$
0
0
Yes, this is a permanent license and not a trial.

Regards,
Ashish
↧

Re : Pc crashing, Error.log complains about driver

June 18, 2018, 3:06 am
$
0
0

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

June 18, 2018, 3:33 am
$
0
0

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

June 18, 2018, 3:56 am
$
0
0
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

June 18, 2018, 3:59 am
$
0
0

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.

↧
Viewing all 1061 articles
Browse latest View live
Search