Move this topic
We have a server that sometimes we get the following error:
Unable to access Sentinel HASP Run-time Environment (H0033)
It happened in the last 3 weeks.
We are solving the problem by installing hasp runtime again, But this solution only good for a few days.
We are not facing the problem on other servers with the same definitions.
Plesae help us solve the problem, The customers are loosing their Patience.
I see you already logged a case in our support portal.
I'm going to answer your query from there.
Leave a comment on smac's reply
Greetings of the day!!
Hope you’re keeping well.
Description: This error means “Communication error between the program and the local license manager.” This error can be caused by a number of things including the HASP SRM runtime is not installed properly, Personal Firewall Software blocking communication with the HASP LMS service, or another piece of software is using the same port that the HASP License License uses (port 1947)
To troubleshooting the error follow the steps below till the cause for the error is found:
o This is the HASP SRM Admin Control Center. If it’s possible to connect to this then the SRM Runtime is installed OK and the problem lies elsewhere and you can disregard the rest of this document
o If you get a message “page cannot be displayed” then it’s possible the SRM Runtime is not installed (go to step 2) or blocked (go to step 3 and 4)
2. Go to Start --> Run --> and type “services.msc” and press OK
o The list is alphabetical. Search for 'Sentinel Local/LDK/HASP License Manager' in the table and then check that it’s status is “Started”
o If this entry is not listed then the HASP SRM Runtime is not installed. Please reinstall it
o If the status is not “Started” check the event log for entries relating to the HASP License Manager service that will give an error message and further diagnostic information
3. Check your personal firewall software. There are many types of personal firewall software including Norton Internet Security (the Firewall is one component of this software), Zonealarm and others.
o By default most personal firewall software will request permission to allow access for the HASP Licence Manager the first time it is run. If access is allowed there will be no problems.
o If access is denied you will encounter communication problems. To resolve such problems either disable the Firewall completely (Note: this option has risks. Please contact your firewall vendor for details) or create a rule/exception in the firewall to allow the HASP Licence Manager (if there is an option to create a rule/exception based on a port number, allow port 1947)
As there are many personal firewall products on the market it is not possible to list all the ways to configure each piece of software here. Please contact your firewall vendor for details of create exceptions or rules as detailed above.
4. Check that there isn't any other application that uses HASP registered port (Port 1947). If you find such a program, disable it and run the HASP application again.
5. Also, try uninstalling/reinstalling the HASP Driver (v6.55) [Kindly refer to the attached doc.]
To check which service uses port 1947 do the following:
1- Open command-prompt.
2- Type: CDocuments and Settingsuame>netstat -a -b
3- Right-Click --> Find --> 1947
4- Check if 'hasplms.exe' is using port 1947 or not.
Hope this helps.
I’ll wait for you to update me with your findings.
Thanks and Regards,
Engineer - Technical Services
Engineer - Technical Services
Leave a comment on Tanuj Kumar's reply
Thanks for your detailed reply. I am facing the same problem but my case is slightly different.
I have an application to be protected for which I am evaluating Sentinel HASP HL. My application has a launching exe and several other supporting DLLs. When I envelop my exe, it works fine. However when I wrap one of the DDLs, I get H0033. To see if this was indeed an issue with DLL, I made a simple Hello World application in two parts: 1) An exe containing Main func 2) A DLL containing Hello World functions. In this case enveloping the DLL works fine.
What could possibility be the issue with my application's DLL's? Any ideas/suggestions are appreciated.
Raj Kiran Joshi
Leave a comment on rajkjosh's reply
Could you please download the LDK 7.0.3 and just install the LDK vendor Suite.
Here is the link:
As far I as know, the LDK 7.0 Envelope do not have this problem anymore.
Leave a comment on olivier_safenet's reply
We have the same issue/problem.
Intermittent crashes of our application with H0033 errors.
We've tried wrapping with LDK 7.n and still get the error.
It seems to happen slightly more when a dll has been wrapped - but it also happens to .exe files which we've wrapped.
Please get a solution to this problem!
Leave a comment on mikej's reply
if you havent done this yet, I'd suggest you to contact us via email at email@example.com
so we'll create a ticket and request you more details about the protection you implement and about your application in order to find a solution.
Leave a comment on Ilaria's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic
Reply to limorr's problem
- 6 Replies
- 48199 Views
- 2 Followers