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

Re : SafeNet Dual USB Not Recognized in Windows 7

May 17, 2018, 11:55 pm
$
0
0
Hi Tony,

Yes, it seems that the issue is with the key only, please go ahead with the replacement of the same.

Thanks,
Heena

↧
Search

Re : RNBOsproGetVersion()

May 18, 2018, 1:29 am
$
0
0

Dear Customer,

I would like to share that Gemalto Engineering has released the fixed SuperPro Library for this issue.
Please login to Gemalto Customer Support Portal (https://supportportal.gemalto.com/csm/) and click below mentioned link to download the same (KB0017524) :

https://supportportal.gemalto.com/csm/?id=kb_article&sys_id=7183c7fadb061bc4d298728dae9619a3

This package includes the Sentinel SuperPro client library version 7.1.0.12. Unzip the package to get the updated Sentinel SuperPro client libraries.
Proceed to replace the Sentinel SuperPro client libraries in your application with the Sentinel SuperPro client libraries provided in this package.

Software Compatibility:
- Visual Studio 2005 and above
- Windows 7 and above (including Windows 10 version 1803).

The enhancements in this release are:
- Supports Windows 10 in the Compatibility section of your application’s manifest file.
- Provides a new API RNBOsproGetVersionEx to return versions of both parallel and USB drivers.

Kindly refer to its Readme file for more information. Feel free to get back to us.

Thanks for the cooperation !

Regards,
Gaurav Bhanot

↧
↧

Re : List of files to distrubute

May 18, 2018, 2:05 am
$
0
0

Dear User,

Thanks for the reply and clarification.

You have mentioned about haspdnert.dll so it appears like we have .net application to be protected and deployed. Please feel free to correct me if this understanding is wrong.

Kindly find the required files and their expected locations.

>             Inside working directory of the Application:
hasp_rt.exe, haspdnert.dll and haspdnert_x64.dll, hasp_windows_<vendorID>.dll , hasp_windows_x64_<vendorID>.dll


>             Inside System32 :
apidsp_windows_x64.dll, hasp_windows_x64_<vendor-ID>.dll


>             Inside SysWow64 :
apidsp_windows.dll, hasp_windows_<vendor-ID>.dll

(for 32 bit machines)
>             inside System32
apidsp_windows.dll, hasp_windows_<vendor-ID>.dll

Feel free to share if any further clarity is needed.

Regards,
Parth Kaushik

↧

Re : Software does not recognize HASP HL dongle license information

May 18, 2018, 6:28 am
$
0
0
Hi Simon,

Kindly share some more information. The error that you mentioned is Vendor specific not sentinel one. Kindly contact your vendor so that they can contact us. Also

1- Kindly check if you can see Features in problematic dongles.
2- Also share the Admin Control Center (ACC) version in http://localhost:1947/_int_/diag.html
3- Are you able to blink your dongle's led from ACC.

Regards,
Anubhav 
↧

Sentinel LDK Runtime release history archive

May 18, 2018, 12:41 pm
$
0
0
Hi,

Where can I find archive of readme files for each new release of LDK runtime driver? I know that each new release has history of previous fixes or changes, but I'm interested in Windows OS support information.

Specifically, we wrote a utility to parse diagnostics information from user's machine sent to us for troubleshooting. This diagnostics is generated with Sentinel Admin API and contains number of useful information bits. I would like to add ability to auto-detect run-time update recommendation based on OS name and version. For example, if Windows 10 and runtime is below 7.6 recommend update.

For this reason I'd like to know minimum recommended runtime version for certain OS and at what version of runtime certain OS support was dropped. For example I see that 7.8 no longer lists Windows 2008 server.

Where can I find this information?

Thanks,
Damir
↧
↧

Re : RNBOsproGetVersion()

May 18, 2018, 7:18 pm
$
0
0
Gaurav -- Thank you. I have added the new spromeps.lib and spromeps.h.

It appears to me that the new RNBOsproGetVersionEx() function is not working correctly. 

As a test I completely removed the SuperPro drivers and then ran the Medic to verify that they are not there.

I then run the following code in my program:

PSPRO_DVR_VERSIONINFOEX spro_drvr_version;
SP_STATUS st;
st = RNBOsproGetVersionEx(spro_drvr_version);

st is coming back as SP_SUCCESS

It appears to report the drivers are there even when they are not. 

When I run the old version of the function:

RNBOsproGetVersion(ApiPacket, &a, &b, &c, &d);

It comes back with error code 12, which is correct.

Please help.

Thank you.

Luke

↧

Re : RNBOsproGetVersion()

May 20, 2018, 11:42 pm
↧

Re : RNBOsproGetVersion()

May 21, 2018, 4:08 am
$
0
0
Hi,

We're also seeing problems with Sentinel Super Pro after installing the Windows 10 1803 update.  The API Call RNBOsproFindFirstUnit returns error 12 (SP_DRIVER_NOT_INSTALLED) when called from a Java based app.    We have a C++ app using the same dongle that is still working fine.

We are using sx32w.dll version  7.1.0.5 for our C++ app and Sxjdk.dll version 7.1.0.5 for our Java app

Based on
  Sentinel SuperPro SDK 7.1.0 SP1
  Sentinel Protection Installer 7.6.9

Das

↧
Search

Re : RNBOsproGetVersion()

May 21, 2018, 6:47 am
↧
↧

Re : Sentinel LDK Runtime release history archive

May 22, 2018, 6:46 am
$
0
0

Hello Damir,

 

Thanks for raising your concern.

 

Please be informed that operating system list provided in the release notes is for tested OS versions checked for the particular RTE release.

This doesn’t necessarily mean that run-time wouldn’t be operational on OS versions not listed.

The expressed use-case doesn’t seems valid as we recommend to keep the run-time version upgraded regardless of the operating system being used.

Hence, please be suggested to modify the application to check for the version of RTE installed and should ask the user for upgrade to the latest regardless of their current OS.

 

If any further clarity is needed then please let me know.

 

Thanks,

Parth Kaushik    

↧

Re : Sentinel LDK Runtime release history archive

May 22, 2018, 5:31 pm
$
0
0
Hi Parth,

In ideal world we all want our customers to run the latest versions since there are always some bug fixes and improvements. In reality however we all know that it is impractical. Various factors such as lack of time, permissions issues, or simply following the old tried and true approach of "if it's not broken, don't fix it" play role here. The last one is especially true for companies with managed servers. The IT departments are notoriously reluctant to change anything unless absolutely critical. They don't want responsibility of license downtime affecting big $$$$ projects.

So having said that, the diagnostics parsing utility we wrote is only meant to solve a problem at hand. We do generally recommend users to install latest, but the intention here is to make a strong recommendation if there are known issues with present runtime and OS version.

At very least can you make readme files available from past few runtimes?

Thanks,
Damir

↧

Re : Sentinel LDK Runtime release history archive

May 23, 2018, 7:02 am
$
0
0
Hi Damir,

Thanks for the response.

We sincerely understand the importance of this concern for you. However, this requirement seems practically not rational.
We dont suggest to make RTE recommendations based upon the OS version/known issues as this would only complicate the situation for users. The fixes and solutions provided in any RTE version is always carried forward in the later releases.
In addition to this, the old versions of RTE are not available for public download and there could be many minor releases between a pair of major release.

However if you may like, you may raise this with our support team for more information on the same using gemalto service portal https://supportportal.gemalto.com/csm/ .

Regards,
Parth Kaushik
 
↧

Software won't detect multiple HASP keys at once (but computer does)

May 24, 2018, 3:04 pm
$
0
0
We use Geostudio in our office, and a few years back, we started running into a problem where the software wouldn't detect multiple HASP keys being used at once. This is a problem because the software has multiple different modules and you often need 2-3 things licensed at once for certain files/work.

The way the program will behave is if key A and key B are both plugged in, only key A works or is detected by the software. When key A is unplugged, the license for key B will immediately highlight/start working.

We have tried everything we can think of (uninstalling and reinstalling drivers, many different licensing options, different versions of Windows, different USB ports and hubs, even contacting Geostudio a few times) and we can't seem to find a solution for this behaviour.

The HASP version of these keys that shows up in Windows is 2.17.

Any idea on what could cause this kind of conflict or issue?
↧
↧

Re : Software won't detect multiple HASP keys at once (but computer does)

May 25, 2018, 5:22 am
↧

Re : RNBOsproGetVersion()

May 25, 2018, 3:28 pm
$
0
0
Hi!
  I've successfully used this thread to fix an issue with MecSoft's VisualCAM for Solidworks 2014. I had a similar problem to that at the top of this thread; my hardware key (a sentinel SuperPro) stopped working when the newest Windows 10 update was installed (Build 1803). I would get an error when launching SolidWorks 2017 was trying to load the add-in from MecSoft, that the dongle was not connected; this would cause the add-in to load in demo mode, and I couldn't export anything from the add-in. MecSoft told me that my software is out of support status, and suggested I buy their newest version (for $2500!!). 
  Thanks to this thread, I noticed that my issue is similar to what others have experienced after this Windows update, and that VisualCAM also uses the sx32w.dll library. I downloaded the libraries linked above by GauravBhanot, extracted them, and replaced the sx32w.dll inside the VisualCAM folder within the C:\Program Files with the one from the download. Everything works now, without paying $2500! Thank you! I hope others can use this info to solve this problem as they update their machines, as well!
Oliver
↧
Search

Re : RNBOsproGetVersion()

May 28, 2018, 2:29 am
$
0
0
Dear Oliver,

Thanks for writing in !

I am glad to know that the shared solution helped you. Please feel free to get back to us.

Regards,
Gaurav Bhanot


↧

Re : RNBOsproGetVersion()

May 29, 2018, 7:19 am
$
0
0
I have resolved my issue with help from Gemalto Customer Support.  The Java DLL sxjdk.dll has to be built using files from the Sentinel SuperPro SDK version 7.1.0 plus the above update.

In summary  - Install the Sentinel SuperPro SDK version 7.1.0 then copy the new spromeps_dual.lib files from the above 7.1.0.12 update into the appropriate folders under C:\Program Files (x86)\SafeNet Sentinel\SuperPro\7.1\Interfaces\Java JDK
Use Visual Studio to build the Sxjdk.dsw project. 
Note that I build this using Visual Studio 2017 + Java 1.8.  I have only built the 32 bit DLL versions.


I hope this is useful to anyone else with a similar problem

Das
↧
↧

Re : Sentinel LDK Runtime release history archive

May 29, 2018, 3:41 pm
$
0
0
Parth,

I think you misunderstood my intentions about this feature. The plan is not to recommend version Y to update from version X. The intention is to say version X is not supported with this OS version update to the latest.

Anyways, I saw "Release notes repository" in main downloads page. It is an archive of LDK release notes which also contain section on RTE release notes.

Regards,
Damir
↧

Re : Sentinel LDK Runtime release history archive

May 30, 2018, 7:15 am
$
0
0
Hello Damir,

Thank you for the explanation and correcting us.

We are glad to know that the needed information has been found.
We appreciate your efforts in raising discussions on forum.

Regards,
Parth Kaushik
↧

haspdinst -i returns error

May 30, 2018, 11:52 am
$
0
0
What do the parameters and status codes mean in this error?

Sentinel Run-time Environment Installer v. 7.41
Error when starting the hardlock service with parameters 1168 193 1.
This is an internal error. For assistance, contact your administrator or the software manufacturer.
Status Code: 48 5 829 193

We're experiencing this on clients that have been re-built/re-imaged, though not every time.

Can you also advise what functionality may be lost or prevented if haspdinst fails like this?  

Thank you!
↧
Viewing all 1619 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>