Administering Boss

Troubleshooting BOSS 2.5 Installations

 

 

 

Error Msg: Run Time Error 217

Situation: When trying to load any of the Boss modules from an NT workstation, especially after installing on a new machine

Solution 1:

  • Reboot the local machine

Solution 2:

  • Logon to the local machine as the Administrator
  • Go to Start | Run… Type regedt32
  • Select HKEY_LOCAL_MACHINE on Local Machine
  • Double-click SOFTWARE
  • Click once on BORLAND
  • From the menu at the top, select Security | Permission…
  • Check Replace Permission on Existing Subkeys
  • Click on Add…
  • Double-click Domain Users
  • Under Type of Access:, select Full Control and click OK
  • Click OK to exit the Registry Key Permissions dialogue box
  • Exit the Registry Editor window
  • Log off as Administrator and log back in as the user


Error Msg: Admin.exe has generated errors and will be closed by Windows. You will need to restart the program. an error log is being generated

Situation: When trying to load any of the Boss modules from a Windows 2000 or XP workstation, especially after installing on a new machine

Solution 1:

  • Reboot the local machine

Solution 2:

  • Logon to the local machine as the Administrator
  • Go to Start | Run… Type regedt32
  • Select HKEY_LOCAL_MACHINE on Local Machine
  • Double-click SOFTWARE
  • Click once on BORLAND
  • From the menu at the top, select Security | Permission…
  • Check Replace Permission on Existing Subkeys
  • Click on Add…
  • Double-click Domain Users
  • Under Type of Access:, select Full Control and click OK
  • Click OK to exit the Registry Key Permissions dialogue box
  • Exit the Registry Editor window
  • Log off as Administrator and log back in as the user

Error Msg: Exception EDBE Error … vcl50.bpl… Class not registered

Situation: When trying to load the Sales module (Sales.exe) after a new install

Solution:

  • Install the MS Agents on the local machine (found on the server in Boss25\MS Agents). Order of installation: tv_enua.exe, Msagent.exe, and the 4 agents in no particular order.


Error Msg: Exception EDBE Error … vcl50.bpl… Driver not known to system

Situation: When trying to load any of the Boss modules

Solution:

  • Verify the settings of the Idapi32.cfg file using the BDE Administrator (bdeadmin.exe) on the server.
  • Once the BDE Admin is opened, what is the path to the right of BDE Administrator in the title bar? It should read \\ServerName\BDE\IDAPI32.CFG. Verify the OMS and OQS aliases. Both should be of type MSSQL with the following entries: Database Name, Server Name and User Name having the correct information entered. Double-click each alias to verify the connection (right-clicking and closing the connection if successful).
  • Is the BOSS user in Enterprise Manager set up correctly (including rights: db_datareader). Otherwise, we are having connectivity problems. The local machine is not seeing the Idapi32.cfg file on the server correctly. If possible, delete the Borland directory from the local machine. Using regedit (Start | Run, type regedit), delete the Borland key (Hkey_local_machine | Software | Borland). Verify the settings in the Boss.ini file on the server.


Error Msg: Exception EDBE Error … vcl50.bpl…
Cannot access directory
Share violation Paradox.lck
File already exists Pdoxuser.lck

Situation: When using or loading any of the Boss modules

Solution:

  • All users have to exit the various Boss modules. Once this is done, on the server, search for P*.lck and P*.net in the Boss directory. We are looking for the following 3 files: Paradox.lck, Pdoxusrs.lck and Pdoxusrs.net. If any of these are found, they are to be deleted.


Error Msg: Cannot locate or connect to SQL Server.
Unable to connect: SQL Server is unavailable or does not exist.
Specified SQL Server not found alias: OQS

Situation: When using or loading any of the Boss modules

Solution:

  • In the BDE Administrator (bdeadmin.exe), verify the Database name and Server name entries for the OQS alias.



Error Msg: Unable to connect to the Boss Server.
Unknown username or password.
Login failed for user ‘BOSS’
Login incorrect.
Alias: OQS_DB.

Situation: When trying to load any of the Boss modules.

Solution:

  • Verify that a user with a login of 'BOSS' is entered in SQL Server (Security folder). If a BOSS user is not present, one must be added to the SQL Server. The user should be added as per the normal method of adding users to a SQL Server. If you are unable to enter the BOSS user (the system tells you there is already a BOSS user but none show on the user list), open SQL Server Query Analyzer. Change the DB (in the right-hand corner to the <OQS Database>). Enter the following: sp_dropuser BOSS and F5 to execute. You should now be able to enter the BOSS user in SQL Server. Contact OQS support @ 613.566.7074 to obtain the password used for the user name "BOSS".

Error Msg: Unable to locate server directory.

Situation: When trying to load any BOSS modules after a new installation.

Solution:

  • Enter the server path to the BOSS modules in the input box and click on OK.
  • If the error repeats, highlight the path you have entered and press Ctrl + C. Go down to start and choose run, paste (Ctrl + V) the server path and click on OK. You should now see directory on your server where the BOSS modules reside : an explorer window with all the executables (Sales.exe, Warehouse.exe, etc). If not, you may have typed the server path incorrectly. Locate the proper directory on the server and enter the full path in the error prompt.
  • If the error still repeats and you are certain that you have entered the server path correctly, search for the file ?Boss.ini? on your server and contact OQS support @ 613.566.7074.
Copyright 2002 OQS Software Design Inc.