However, once I'm that far, I haven't a clue how to write up an example function similar to those shown in the ToolBox. 

Did you try to compile the libhasp_windows_bcc.lib file using C:\Program Files\SafeNet\Sentinel HASP\API\Runtime\Cpp\bc\mk.cmd file? If not please try the same. Make sure that bcc32 command is accessible by setting the PATH environment variable. For sample you could refer to the one available under C:\Program Files\SafeNet\Sentinel HASP\Samples\Runtime\cpp\bc. You could compile the sample also by using the mk.cmd available under same directory.

 

Regards,

Aamir

What I actually ended up doing was moving over to Delphi 7 and used the Pascal Unit instead. This seems to be much easier to work with.

I am however still a little stuck. I am attempting to define the login scope via a few XML elements. Here is what I have:

I'm not entirely sure if that's how the scope should be labeled. It seems to work OK but the status code that gets returned is 50 (Unable to locate any Feature matching scope). I have defined product ID 2000 in Business Studio, created the Provisional, the RTE Installer and followed all of the steps but it still does not seem to work. 

I did check in the Admin Control Center and I did notice that my new product hasn't shown up in the list. Is there a step I maybe missed?

Did you create an exe and used that to install the provisional license? If that is the case please try creating a v2c and apply that, then check whether you are able to see the product. I believe there might have been some issue generating the installer and that might be the reason that you are unable to see the product under ACC. Check that you have added the correct product while creating the installer for provisional product.

 

Regards,

Aamir

Yes I did that several times. I followed all of the steps in the Product Activation PDF that comes with the install. One thing I have also noticed is there seems to be a couple of products and lots of features from previous installations. Is there a way I can clear those out? I completely removed all of the components several times before to start with a clean database but the Admin Control Center still shows some leftover items.

Thanks for your help!

Hello Charlie,

 

If the bundled v2c or exe was applied successfully then the product should show under the ACC. Could you please try to apply the bundled provisional on some other machine and see whether it shows under ACC there? Moreover you could cancel the SL products which are present under ACC which would make them unusable, however this would not delete them permanently as they would still be present in the SL secure storage which can not be cleaned unless the machine if formatted completely.

 

Regards,

Aamir

I'll see if I can be verbose enough about what I'm experiencing here. I have a completely fresh copy of HASP installed (including a new database). I create a feature of ID 505 (note here that feature ID 505 exists on the two previous products that I cannot remove out of the ACC). I create a product with ID 2001 (which doesn't exist). I create a Provisional for 2001 and create the V2C and the RTE. I run the RTE against my sample Delphi project. 

Here's where the confusion begins. When I open the executable and click a button (which makes a call to feature ID 505), I get a message (that I created) that says I do not have access to that feature. In the ACC, it shows that I have a logged in session for product ID 10. Please note, the product ID should be 2001. At this point, 2001 hasn't shown up anywhere in ACC.

From here, I debug my application in Delphi to see the status code that gets returned. I get a status code of 50. According to the Pascal Unit file, this corresponds to the following: Unable to locate any Feature matching scope.

The scope I have defined is exactly the same XML as specified above (with the exception that I have changed the Product ID to 2001).

So my first question: is my XML properly formatted based on what you can tell?

Do you know why the Product ID of 2001 wouldn't be showing up in the ACC even though I have performed all of the necessary steps as shown in the Product Activation Tutorial PDF supplied with the install of HASP? Is it entirely possible that the Product ID is being installed on a different server somehow even though I'm running all of this on my laptop?

As an outline of what my sample project is doing, I created a function that simply uses the scope to determine whether or not they have access to a feature ID that I pass in. If they do, I show a success message. If they do not, I show a deny message.

Am I also correct in assuming that when using the Envelope protection, I can only protect 1 feature at a time? I ask this because we are looking to integrate this into a product that will have many different features. When a customer purchases, they will get access to multiple features. If I can only protect one feature, then should I even be using Envelope to do the protection?

Thanks for your help! I'm sorry if this seems really confusing. I do like what the product has to offer but so far, I haven't been able to get it to work like I need it to.

Please see below for the response regarding your queries:-

 

-"debug my application in Delphi to see the status code that gets returned. I get a status code of 50. According to the Pascal Unit file, this corresponds to the following: Unable to locate any Feature matching scope."

>>This is because there is no product ID 2001 (as you could not see it in ACC)

 

-"So my first question: is my XML properly formatted based on what you can tell?"

>>Yes, it seems to be correct, or else you might have received an invalid scope error

 

-"Do you know why the Product ID of 2001 wouldn't be showing up in the ACC even though I have performed all of the necessary steps as shown in the Product Activation Tutorial PDF supplied with the install of HASP? Is it entirely possible that the Product ID is being installed on a different server somehow even though I'm running all of this on my laptop?"

>>If you are running the exe for provisional product on your laptop then it should get activated on the same and not on any other machine. For more on what might be wrong let me know if I could get your contact number so that we could organize a remote session (if possible).

 

-"Am I also correct in assuming that when using the Envelope protection, I can only protect 1 feature at a time? I ask this because we are looking to integrate this into a product that will have many different features. When a customer purchases, they will get access to multiple features. If I can only protect one feature, then should I even be using Envelope to do the protection?"

>>Yes you would be able to protect your application with one feature ID, however if you want envelop to protect multiple features the features should exist in different dlls or exes that could then be protected with different feature IDs.

 

Let me know if anything is not clear regarding the above queries.

 

Regards,

Aamir

I have sent you a PM with my contact information regarding getting a time setup to do a web session to check out my problem.

Thanks!

Thanks for the phone call yesterday. This morning, I started looking at my demo project again since we were able to import the V2C file into ACC. I ran my code and tested out the two buttons I created (these just check a particular feature ID and return true if they have access and false if they don't). They continue to return false. I checked the ACC again and I noticed that the Product ID shows up just fine, however when I view the features for this product, it STILL shows that those features are tied to a completely different product number (Product ID 10). I have attached a screenshot showing this discrepancy. You saw me yesterday generate the V2C file so at this point, I'm at a complete loss as to what is happening. 

I attempted to get a screenshot of my cursor hovering over the Product itself to show which features were tied to it but I could not. I have replicated the information below:

Product ID: 2002

Vendor ID: [Demo Vendor ID]

Features: 1001, 1000

Product is not detachable

There seems to be something wrong on the machine where the product is being installed. I have sent you a PM for the same, please check it and let me know when we could look into this issue.

 

Regards,

Aamir

As discussed over the phone, changing the feature definitions and adding a new product resolved the issue. Let us know if you have any other query regarding this case.

 

Regards,

Aamir