02.04.2013 Views

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

Sentinel Hardware Keys Developer's Guide - Customer Connection ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Solution:<br />

Problems and Solutions<br />

Contents Glossary Index Troubleshooting<br />

If any of your input files (the application executable, or any other files you<br />

have selected for encryption) have the read-only attribute set, CodeCover<br />

may not be able to protect the file. Clear the read-only attributes in the file’s<br />

Properties dialog box, then try again.<br />

Problem: Releasing a License<br />

You have closed the CodeCover-protected application on your system to free<br />

up a license. However, the <strong>Sentinel</strong> <strong>Keys</strong> License Monitor still shows the<br />

license in use.<br />

Solution:<br />

You should manually cancel the license in the <strong>Sentinel</strong> <strong>Keys</strong> License Monitor.<br />

To automatically release the license on application exit, copy the<br />

relLic.dll (for 32-bit application executable) or relLic64.dll (for 64-bit application<br />

executable) in the directory that contains the application executable.<br />

This DLL can be obtained from \<strong>Sentinel</strong> <strong>Keys</strong> Toolkit directory of the <strong>Sentinel</strong><br />

<strong>Keys</strong> SDK installation.<br />

Problem: Application fails to execute with a statically<br />

linked protected DLL<br />

When you protect the DLL that is statically linked to the application, the<br />

application fails to execute with the protected DLL. Whereas, if the DLL is<br />

linked dynamically, it executes successfully.<br />

Solution:<br />

This is a static linked DLL issue that occurs once you have protected your<br />

application. Please follow the following tips while protecting a statically<br />

linked DLL to resolve this issue.<br />

Protect both the static linked DLL, and executable instead of<br />

protecting only the DLL.<br />

Use Load Library instead of linking the DLL statically.<br />

<strong>Sentinel</strong> <strong>Hardware</strong> <strong>Keys</strong> Developer’s <strong>Guide</strong> 255

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!