This is a normal message given by Visio the first time ProMax is being HASP device not found.

used.
• Plug in the security device.
• Please always “Enable Macros”*. • Check that the light on the device is illuminated. If not, try
• Select the “Always trust macros from this publisher” option to plugging it into a different USB port and try ProMax again.
not repeatedly see this warning message. • Check your driver installation:
o Open Internet Explorer and type: http://localhost:1947
* You might be required to select the “Always trust macros from o If a control center opens, let us trouble-shoot.
this publisher” option before the enable choice is available. o If it doesn’t open a webpage, reinstall the device driver:
i. From the DVD, go to “HASP & NetHASP”, then
“Driver”, and then “GUI”.
ii. Run the HASPUserSetup.exe file and follow its
instructions.
Computer could not find the right SQL Database.
• Run ServicesPipeTimeout.vbs script file and try ProMax again. If it Expired security device.
still doesn’t work, • We may need to reset the device, or have you use a different
• Run FixSQLImagePath.vbs script file and try ProMax again. one.
ProMax could not start the SQL Database.
• Reboot, and install any Windows Updates that are waiting.
• Try using Local Account option for the database: Sentinel HASP License Manager service is not running.
o From the Windows Menu, click on “Run” in Windows XP, or
• Did you restart after installing ProMax? If not, it is required.
the “Search programs and files” field in Windows 7.
• Manually start the License Manager:
o In XP, type “services.msc” and hit enter. In Win7, type
o From the Windows Menu, click on “Run” in Windows XP,
“services.msc” and then right-click on the search result that
or the “Search programs and files” field in Windows 7.
matches and select “Run as Administrator”.
o In XP, type “services.msc” and hit enter. In Win7, type
o In the list of items, look for SQL Server (BRYANRES).
“services.msc” and then right-click on the search result
o Right-click on this service, and select “Properties” .
that matches and select “Run as Administrator”.
o Check that the “Path to executable” ends with:
o In the list of items, look for HASP License Manager (for
\MSSQL\Binn\secservr.exe" –sBRYANRES.
ProMax 3.0 or 3.1), or Sentinel HASP License Manager
If not, run “FixSQLImagePath.vbs” script file and try
(for ProMax 3.2).
ProMax again.
o If you cannot find it, try reinstalling from the ProMax
If it does, the select the “Log On” tab, and select
DVD:
“Local System account”. Reboot and try ProMax.
From the ProMax DVD, go to “HASP & NetHASP”,
• If you are running encryption software (such as Credent), exclude
then “Nethasp license Manager”, and then “Win32”.
both the SQL Server BRYANRES instance, and the ProMax
Run the file lmsetup.exe
database found at c:\Documents and Settings\All
o Verify that it is an “Automatic” start-up type. If not,
Users\Application Data\Bryan Research & Engineering
right-click and go to properties. Change the drop-down
Inc\ProMax3\Data.
menu to “Automatic”.
• If none of this works, reinstall ProMax: o Verify that the status is “Started”. If not, right-click and
o First, uninstall ProMax from the Add/Remove Programs list select “Start” from the options.
in the Control Panel of Windows. o If it will not start, probably the Windows firewall and/or
o Second, uninstall Microsoft SQL Server 2005 from the anti-virus software is blocking the ports necessary for the
Add/Remove Programs list. Select the “BRYANRES: driver to function. Ports 1947 and 475 should both be
Database Engine” option only. excluded from firewall blocking for both TCP and UDP
o Last, reboot and reinstall ProMax from the DVD. access. After opening these ports, you must reboot.

ProMax could not connect with the SQL Database. Company name on security device doesn’t match the installed
version of ProMax.
• Reboot and try ProMax again.
• If it still doesn’t work, start the SQL database manually: • Find the company name of your installation of ProMax from the
o From the Windows Menu, click on “Run” in Windows XP, or “About ProMax” option found in the Help menu.
the “Search programs and files” field in Windows 7. • Compare with the tag on the security device:
o In XP, type “services.msc” and hit enter. In Win7, type o If it looks like it should match, we may need to reset the
“services.msc” and then right-click on the search result that device, or have you use a different one.
matches and select “Run as Administrator”. o If it does not appear to match, we may have given you
o In the list of items, look for SQL Server (BRYANRES) . the wrong disk or the wrong security device.
o Verify that it is an “Automatic” start-up type. If not, right-
click and go to properties. Change the drop-down menu to Time or date issue.
“Automatic”. • Check the time and date on your computer, including A.M. vs.
o Verify that the status is “Started”. If not, right-click and P.M., and the current year.
select “Start” from the options. • If this doesn’t work, we may need to reset the device, or have
• Alternatively you can start the database by opening the you use a different one.
command prompt and typing: net start mssql$bryanres
 Microsoft Visio was not found on the computer. During installation, some features of MSXML and SQL did not install
correctly.
• Install Microsoft Visio.
• Install the Windows Installer Clean Up Utility, msicuu2.exe
• Run the utility to remove MSXML6.

or

• (Optional) Uninstall the utility.

Error connecting to the Update site for ProMax. Install: ‘Requires a dedicated instance of SQL 2005’.
• Select “Yes” and ProMax will continue to work as • Install ProMax from the Setup.exe file, not the ProMax.msi file.
normal. • If this does not work, we can attempt to manually install SQL
• (Optionally) “Modify” the ProMax installation to not Server Express on your computer.
include the FLEXnet Update Manager in the install.

Some scripting files required to use ProMax are not MSXML6 is installed but not correctly registered on the computer.
correctly registered on your computer.
• Close ProMax and any Microsoft Office files that are open.
• Close ProMax and any Microsoft Office files that are • Register MSXML6 on your computer:
open. o From the Windows Menu, click on “Run” in Windows XP,
• Register the mscomctl.ocx file on your computer: or the “Search programs and files” field in Windows 7.
o From the Windows Menu, click on “Run” in o In XP, type “cmd” and hit enter. In Win7, type “cmd.exe”
Windows XP, or the “Search programs and and then right-click on the search result that matches and
files” field in Windows 7. select “Run as Administrator”.
or o In XP, type “cmd” and hit enter. In Win7, type o If you have a 32-bit system, type:
“cmd.exe” and then right-click on the search regsvr32 c:\windows\system32\msxml6.dll
result that matches and select “Run as o If you have a 64-bit system, type:
Administrator”. regsvr32 c:\windows\sysWOW64\msxml6.dll
o If you have a 32-bit system, type: • Open ProMax.
regsvr32 c:\windows\system32\mscomctl.ocx
Missing ProMax Menu.
o If you have a 64-bit system, type:
regsvr32 c:\windows\sysWOW64\mscomctl.ocx • Close ProMax and Visio.
• Open ProMax. • Reset the custom VSU menus on your computer:
o Using Windows Explorer go to %AppData%\Microsoft\Visio
WMI problem on computer (error 1720). o Delete any “.vsu” file(s) you find.
• Run WMIfix.bat file and try installing ProMax again. o Using Windows Explorer go to %AppData%\Bryan Research
& Engineering Inc.\ProMax3\Data\1033
o Delete any fines named “Menu TB*.vsu”, “custom.vsu”, or
“customll.vsu”.
• Restart ProMax.