Network and Database Problems and Solutions

Table of Contents

1. "Auralia/Musition files could not be found on the network"
2. "Directory is controlled by another .NET file"
3. "Index or table is out of date"
4. "Runtime error 217" on starting Auralia/Musition
5. "Error initialising the Borland Database Engine" (error 2109 or similar)
6. "Invalid filename"
7. "Interface error" or "Engine version mismatch"

Download the latest instructions for installing Auralia 2.1 or Musition 2.0 on your network.

Auralia/Musition files could not be found on the network message

If you get this message, then Auralia/Musition have been setup to talk to network databases that aren't presently available. You can then work with Auralia/Musition on the local computer, using the local 'auralia.ini' / 'musition.ini' file, and the local set of databases. You will notice that the 'Network' option under the 'Administration' menu is greyed out, for security reasons.

If your network files have been deleted and you need to change the location that Auralia is using, then you will need to use 'regedit', the Registry Editor. Under 'HKEY_LOCAL_MACHINE', browse to 'SOFTWARE', and then 'Rising Software Shared 2.0'. Change the keys 'useSharedAuralia' / 'useSharedMusition' and 'useSharedData' to '0' (zero), and the key useLocalINIFile to '1'. You will then be able to access the Network menu from within Auralia/Musition, and choose the correct path on your network.

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

This error can be caused by incorrect settings, or the failure to shutdown a workstation before turning it off. Firstly, check that the Network Directory setting found under the 'Administration -> Network' screen is the same on each computer. This is described in the installation guide in more detail.

Secondly, check that all computers have the correct Database Engine settings. Use the BDE Administrator in the Control Panel on each computer. Select Configuration, double-click System, then select INIT, and ensure that "Local Share" is set to TRUE. Close the BDE Administrator. The updated network instructions describe this process also.

If the error occurs after checking the Network settings and the BDE Administrator settings, there may be some old network control files on your workstations 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.

"Index or table is out of date"

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. The DBREPAIR utility will attempt to repair any database corruption. Note that we recommend backing up your data before using this utility as we do not guarantee it.

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

"Runtime error 217"

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.

"Error initialising the Borland Database Engine"

This error may occur if you didn't restart your workstation after installing Musition or Auralia. Restart your workstation and try loading the software again.

If the program isn't resolved, we recommend you reinstall your Rising Software product.

If a reinstall doesn't solve the problem, delete the registry entries under 'HKEY_LOCAL_MACHINE\SOFTWARE\Borland' using the registry editor REGEDIT. Then reinstall the software again. Deleting these registry keys may affect other software installed on your computer.

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

"Invalid filename"

For example, you may wish to rename "\Program Files\Rising Software" to "\Programs\Rising".

This problem may also occur if Musition or Auralia is installed into the root directory. For example, Musition.EXE is \Musition\Musition.EXE. Please move the directories to a subdirectory of the root. Using the example given, move the 'Musition' directory into another directory stemming from the root directory; '\Program Files\Musition" would work fine.

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 2.0 and Auralia 2.1).

"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 or Auralia.

We recommend that you uninstall the other software, uninstall Musition and/or Auralia, then reinstall Musition and/or Auralia first and then your other software. Your other software should be compatible with the version shipped with Musition and Auralia.

You may also be able to correct this problem by downloading and installing the BDE 5.11 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.