![Safenet Safenet](http://2.bp.blogspot.com/-UHOiJIbl6Ok/VJZNMJipXJI/AAAAAAAAATo/fsB_bYCBxOg/s1600/dumper.jpg)
Attention, Internet Explorer UserAnnouncement: Jive has discontinued support for Internet Explorer 7 and below.In order to provide the best platform for continued innovation, Jive no longer supports Internet Explorer 7.Jive will not function with this version of Internet Explorer. Please consider upgrading to a more recent version of Internet Explorer, or trying another browser such as Firefox, Safari, or Google Chrome.(Please remember to honor your company's IT policies before installing new software!).
![Safenet missing dongle windows 7 Safenet missing dongle windows 7](http://hydrocompinc.com/wp-content/uploads/images/SentinelKeys.jpg)
I had an interesting case that I want to share in the event anyone else experiences this problem. In this case a Symantec certificate stored on a SafeNet USB dongle was being used to sign a Windows Store app in Visual Studio. The signing was failing. Visual Studio reported: “SignTool Error: An unexpected internal error has occurred”.
These guidelines were followed and everything seemed in order:During packaging, Visual Studio validates the specified certificate in the following ways: Verifies the presence of the Basic Constraints extension and its value, which must be either Subject Type=End Entity or unspecified. Verifies the value of the Enhanced Key Usage property, which must contain Code Signing and may also contain Lifetime Signing. Any other EKUs are prohibited. Verifies the value of the KeyUsage (KU) property, which must be either Unset or DigitalSignature. Verifies the existence of a private key exists. Verifies whether the certificate is active, hasn’t expired, and hasn't been revoked. SolutionI used Process Monitor (Procmon) to determine the command line that was being used and then using the command line SignTool.exe to issue the same command, saw that it was returning this: Error: SignerSign failed.'
(-/0xc0000225)SafeNet had the solution for this problem. Using the SafeNet Client Authentication tools it was found that there were ‘Orphan Objects’ on the device.
HASP Key Device Driver - HDD32.EXE. The HASP Device Driver interfaces between HASP-protected applications and the HASP key. In other words, protected applications communicate with the HASP key through the HASP Device Driver. The HASP device driver is also required for the Customer.exe and HaspCheck.exe programs. Initialize Safenet eToken 5110 cc for Qualified Certificates 3. How to Manually Update the Adobe Approved Trust List (AATL) in Adobe Acrobat Reader 4. Timestamping Intermediate Certificates View recent system alerts and subscribe to receive realtime updates. View Alerts Tools SSL Configuration Test.
Removing these resulted in being able to use this device to sign the application successfully!Let me know if this helps you out! This might be an issue with the way SafeNet gets registered. See this StackOverflow answer:.Quoting from that answer:'I had the exact same problem a few days ago and the Digicert after-sales service has been able to to solve it.
Try to check the value of this register key (in regedit):HKEYLOCALMACHINE/SYSTEM/CurrentControlSet/Control/Cryptography/Providers/SafeNEt Smart Card Key Storage Provider/AliasesThe value should be 'eToken Base Cryptographic Provider' and not 'eToken Base Cryctographic Provider' ('p' instead of 'c').'