Contents 1 Downloads 2 Installation 3 Key codes 4 Key updates 5 Error Message Popups 5.1 Cannot open file... 5.2 "Error 7: ..." 5.2.1 Using local dongles 5.2.2 Using networked dongles 5.2.3 Used in conjunction with Fusion 5.3 "Error 25: ..." 5.4 "Error 31: ..." 5.5 "Error 41: ..." 5.6 "HASP key not found" 5.7 "HASP: Invalid vendor code" 5.8 "HASP: Impossible to call hasp_get_size: 10" 5.9 "HASP: Vendor code is not recognized" 5.10 "Loading of HASP interface (hasp_windows.haspdll) failed" 5.11 "Sentinel HASP session broken (H0039)" 6 Blue crash screen (BSOD) upon start

HASP-specific troubleshooting forum: https://forums.bisimulations.com/viewforum.php?f=74

If using networked authorization, make sure that the authorization server is fully booted up, and any client PCs have a working network connection, before attempting to start VBS2.

Downloads

You can download the latest drivers from one of these sources:

• http://www3.safenet-inc.com/support/hasp/enduser.aspx
• http://distribution.bisimulations.com/release/support/haspDriver/HASP_6.00.zip (Beta)

Installation

To uninstall the HASP drivers, run the following command from the drivers\HASP folder under the VBS2 installation directory:

haspdinst.exe -r -kp -purge

To (re-)install the drivers, execute the command

haspdinst.exe -i

Key codes

The software and the HASP key are encoded for specific user groups and functionality. Both have to match, in order to work. The currently used codes are:

• EYEWE - USSF
• EZDER - ADF
• EZYQC - UK
• GYBBK - Educational, Personal
• MTOOG - US Army, USMC
• WOCRM - Developer
• XOYXO - Lasershot
• YIMWI - Trial
• YYMEA - General

Key updates

If your installation is time-limited, the license needs to be updated when it expires (which can be indicated by an Error 31: Feature not found error).

To create a license file open the folder optional\support under the installation directory, and run the executable hasprus_xxxxx.exe (the value of "xxxxx" depends on the type of installation/licence you have, e.g. hasprus_YYMEA.exe). This brings up a window, where you can click "Collect Information" to create your license file.
This file (which has the extension C2V) should then be sent to license@bisimulations.com, along with your personal/orginizational and license information.
Once you received an updated license file (which has the extension V2C), open this executable again, go to the "Apply License Update" tab, and select the updated file.
After the program updated the license your purchased VBS2 features should be available again.

Error Message Popups

Cannot open file...

some XBO file

Cause:

• Some files were not properly closed when VBS2 was last exited (most likely to happen with crashes under 64 bit Windows).

Solution:

• Log off the current Windows user.
• If that doesn't help, reboot Windows.

"Error 7: ..."

HASP HL key not found or VBS2 USB key not found

Causes:

• License wasn't found.
• Used installation doesn't match the installed dongle.
  

Using local dongles

Solutions:

• Ensure that the HASP key is inserted in the computer you are trying to run VBS2 on, and that its LED is lit.

• Reinstall HASP drivers:

1. Remove the USB key from the computer
2. Open the \driver\HASP folder in your VBS2 installation directory.
3. Run manualinstall.bat
4. Re-insert the USB key
5. Attempt to start VBS2 once again.

• Also ensure that the correct version of VBS2 is installed for the license dongle you are using.

1. Check the five letter code printed on the side of the HASP dongle Eg: YYMEA, YIMWI, GYBBK
2. Navigate to your VBS2 install directory Eg: C:\Programs\Bohemia Interactive\VBS2 VTK 1.40
3. Locate the following file: hasp_windows_XXXXX.haspdll
4. Ensure that the 5 letter code printed on your Hasp dongle matches the name of the .haspdll file for Eg: hasp_windows_YYMEA.haspdll matches a YYMEA license

• If the .haspdll file does not match the 5 letter code on the hasp dongle you will need to install the correct version.

Using networked dongles

Solutions:

• Ensure that a HASP License Manager is running on the authorization server (and a red network USB key is inserted on that machine).

• Reinstall HASP drivers (see instructions above)

• Check that the firewall software on both the host (http://localhost:1947/_int_/config_from.html) and client computers (http://localhost:1947/_int_/config_to.html) is not blocking VBS2. Note that Windows has a native firewall that may cause these types of problems.

• Ensure that the host computer can be 'seen' by the client machines. The following technique can be used to check if the host machine is visible:

1. On the host computer, click Start, click Run and then type 'cmd'. Press Enter.
2. At the command prompt type 'ipconfig' and press enter. Note the IP address.
3. On a client computer, click Start, click Run and then type 'cmd'. Press Enter.
4. Type 'ping <IP>' where <IP> is the IP address of the host machine. Press Enter. You should see a message similar to: Reply from <IP>: ...
5. If there a different message is displayed then the problem is most likely your network configuration or firewall.

• If the error persists, contact BI Simulations with a screenshot of the error message and your contract details.

Used in conjunction with Fusion

Cause:

• Correct version of VBS2.EXE might be overwritten by Flare installation.
  

Solution:

1. Install VTK
2. Save VBS2.EXE to a different location
3. Install Fusion
4. Restore the saved version of VBS2.EXE

"Error 25: ..."

Clock has no power

Cause:

• Dongle most likely physically damaged.
  

Solution:

• Contact BI Simulations, to request replacement.

"Error 31: ..."

Feature not supported or Feature not found

Cause:

• Used installation doesn't match the installed dongle.
  

Solutions:

• Verify that the 5-digit key on the dongle (e.g. EZYQC) matches the installed version of the software.
• If the license is time-limited, this error could indicate an expired usage period. Ensure that any received license updates have been installed. If so, follow the instructions for Key updates to renew your license.

"Error 41: ..."

Feature has expired

Cause:

• The trial period for the product has expired.
  

Solution:

• Contact BI Simulations, to extend the trial, or to purchase a full version.

"HASP key not found"

(After is has been working for a while)
Cause:

• Server may have shut down power to USB hub.
  

Solution:

• Make sure that the power settings on the licensing server never shut down the USB hub, by disabling the option to turn off this device to save power.

"HASP: Invalid vendor code"

Cause:

• Mismatch of resource files.
  

Solution:

• Verify that the following files are all for the same HASP code:

• hasp_windows_?????.haspdll (????? must match HASP code, e.g. YYMEA)
• VBS2.exe
• dta\product.bin
• vbs2\addons(\core)\customer.ebo

"HASP: Impossible to call hasp_get_size: 10"

Cause:

• New license format (introduced in 1.50) cannot be read.
  

Solution:

• Update the licensing functions via a hotfix available here.

"HASP: Vendor code is not recognized"

Cause:

• Incorrect, missing or multiple HASP_Windows_<Version>.haspdll in installation folder (<Version> must match HASP type, e.g. YYMEA, and only one should be present).
  

Solutions:

• Verify that correct haspdll is installed.

"Loading of HASP interface (hasp_windows.haspdll) failed"

Cause:

• File HASP_Windows_<Version>.haspdll is missing.
  

Solution:

• Try to locate another copy of this file, and place it into the appropriate folder (either from tools\buldozer into the main VBS2 install folder, or the other way round).

"Sentinel HASP session broken (H0039)"

Cause:

• Mismatch of versions between client and server.
  

Solution:

• Update all attached machines to the same version. (Download URL at top of page.)

Blue crash screen (BSOD) upon start

Cause:

• Conflict with virus scanner.
  

Solution:

• Reboot, after shutting down your anti-virus software, and try again.
  If running Microsoft's Security Essentials, also explicitly disable the service "MsMpSvc".
  

A new (beta) HASP driver may alleviate the issue (see this discussion).