home

auralia

musition

downloads

support

contact

buy


Network and Database Problems and Solutions

Table of Contents

Borland Database Engine Problems

  1. "Directory is controlled by another .NET file"
  2. "Runtime error 217" on starting Auralia/Musition
  3. "Error initialising the Borland Database Engine" (error 2109 or similar)
  4. "Invalid file name" in some topics
  5. "Interface error" or "Engine version mismatch"
  6. Index or table is out of date

Download the latest instructions for installing Auralia 2.0 or Musition 1.0 on your network. [Download the Adobe Acrobat Reader]


"Directory is controlled by another .NET file ..."

To correct this error, use the BDE Administrator in the Control Panel on each computer. Select Configuration, double click on Drivers, Native, Paradox, and then "NET DIR". Set the NET DIR setting to a path located on your Windows 95 network server. All computers must have this setting set to the same path. Then double-click System, then INIT, and change "Local Share" to TRUE. Finally, close the BDE Administrator. The updated network instructions describe this process also.

If the error occurs after checking all the BDE Administrator settings, there may be some old network control files on your workstation and/or server. Ensure that there there are no workstations with Auralia or Musition active and delete any files called 'PDOXUSRS.NET' and 'PDOXUSRS.LCK' on the server and workstations.


"Runtime error 217"

This error occurs when some of the registry entries for Musition or Auralia are missing.

We recommend you reinstall your Rising Software product. If possible, first remove the registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Borland using the registry editor REGEDIT.

The following information applies only to Musition 1.0.0: When Musition is first run on a particular computer it must add some entries to the registry for the Borland Database Engine which is used to access databases in Musition. These entries are read from the file RISNET.INI which must live in the directory \Program Files\Rising Software (or the parent directory to the directory containing MUSITION.EXE if you have changed the name). Please contact Rising Software for an upgrade to Musition.


"Error initialising the Borland Database Engine"

(This information applies only to Musition 1.0.0.)

When Musition is first run on a particular computer it must add some entries to the registry for the Borland Database Engine which is used to access databases in Musition. If this error message is seen, the registry entries may be corrupt or incorrect.

To check the entries, run REGEDIT (found in the Windows directory), select HKEY_LOCAL_MACHINE, then SOFTWARE, then Borland, then BLW32. The registry keys should point to your \Program Files\Rising Software\BDE directory, or another directory containing the Borland Database Engine if you own other products which use it.

You may need to delete the entire Borland section to correct this problem. Musition will recreate these entries when next run. However, Rising Software cannot take responsibility for any problems occurring with other software if you attempt this.

Please contact Rising Software for an upgrade to Musition.


"Invalid file name"

If you receive an Invalid filename message when logging in to Musition or when starting the chords, concepts, terms, symbols, instrument range or instrument transposition topics, and you are running Musition from a network, you may need to rename the directories containing Musition to names not containing any spaces. We have observed that, on Netware, Invalid filename messages may be received if the pathname contains spaces.

For example, you may wish to rename \Program Files\Rising Software to \ProgramF\RisingSo.

This problem may also occur if Musition is installed into the root directory; that is, Musition.EXE is \Musition\Musition.EXE. Please move theses directories to a subdirectory of the root.

These problems are caused by the Borland Database Engine and may be corrected in a future maintenance update of Musition. (This applies to all versions of Musition and Auralia 2.0).


"Interface error" or "Engine version mismatch"

This problem occurs when some other software installed on your computer has already installed an older version of the database software used in Musition and Auralia, the Borland Database Engine. This older version of the BDE (Borland Database Engine) is not compatible with the version shipped with Musition. We recommend that you uninstall the other software, uninstall Musition, then reinstall Musition first and then your other software. Your other software should be compatible with the version shipped with Musition. (Note that Musition 1.0.1 ships with a newer version of the BDE than Musition 1.0.0; please contact us if you need to upgrade.)

You may also be able to correct this problem by downloading and installing the BDE 4.51 upgrade from Borland, at this web site. You can also download this directly from us. Please note that this upgrade is quite large (10mb).

However, Rising Software cannot take responsibility for any problems occurring with other software if you attempt this.


Index or table is out of date

This message may occur for several reasons.

Firstly, you must have LOCAL SHARE set to TRUE in the BDE Administrator if using Auralia or Musition on a network. In the BDE Administrator, go to System, then INIT, and ensure that LOCAL SHARE is set to TRUE.

Secondly, this error may occur if students do not shut down the computer properly. For example, if a student switches off the computer without leaving Auralia or Musition, mild database corruption can occur. You can download our DBREPAIR utility which will attempt to correct the problem. This utility will work with both Auralia 2.0/Musition 1.0 and Auralia 2.1/Musition 2.0.

There may be other circumstances where this problem occurs. Please contact us if you need assistance.


Go to: Auralia 2.0 support, Musition 1.0 support, support index, main index.

Copyright © 2002 - 2008 Rising Software Australia Pty Ltd ACN 077 057 213. Last updated Sunday, November 23, 2008 .
In case of difficulty, please contact the webmaster.