PROBLEM: Receiving error "Creating Shared Memory File in Acceler8DB, 668" or "Database is older than supported by this version, 73"

The information in this article applies to:

Acceler8DB, All Versions
Windows
Security

SYMPTOMS:

Here are several symptoms:

Moving / Copying a Database
Restoring a Database
Errors Creating a Database
Changing Security Permissions in Windows Explorer on any of the files or folders where the database resides, there is an error message “Error Creating Shared Memory File, Number 668”or “Error, Database is older than supported by this version, 73”
Error "No Catalog" when you try to convert the database from v4.2 to 4.6.

CAUSE:

Here are the possible causes:

The Shared Memory File (_mdb.sys) still exists due to another ADB Engine request is currently using the database.
If you have moved, changed, restored, or updated the Database created by Acceler8DB, you may receive the error “Error Creating shared Memory file” due to no read/write Windows Security permissions on the folder or drive.
You have created a Database and specified the files / folder to exist on a Network Drive.
An Error occurred when creating a local Database (not all Acceler8DB database catalog files got installed correctly). The label shows under My Computer; however, errors persists.

RESOLUTION:

NOTE: Please coordinate with your Network Administrator or Microsoft for Windows functions.

Note: The screen pictures below are for illustrative purposes to assist you resolving your problem.

Here are some possible resolutions:

Shared Memory File: If there are no current valid ADB Engine Connections using the database, you can delete the Shared Memory File.
Errors upon creating a local DB: Create a new local database using ADB Wizard or Work with Databases dialogue. If you do receive a message that states the database is created successfully, you should no longer receive errors. Some errors are a result of the folder in which you are creating the database is not empty.
Network Drive: Create the Database and specify the files/folder to exist on the local machine.
DB was moved or copied: If the database was moved from one machine to another using Windows Explorer, make sure the database is not opened during the move or copy process. In addition to the database not being opened, make sure all of the files in the root folder where the DB exists get copied (See Figure 1).

Figure 1

Security Permissions: Check the Security Permissions in Windows Explorer (See Figure 2) on the folder that holds the Database. Make sure there is Read/Write Capabilities assigned to the “System” Account OR for the Account in which the Acceler8DB Service will run under.

NOTE: The Account in which Acceler8DB Server and the security permissions apply only to Windows NT, 2000, XP Professional with NTFS file system. If you do see a Security Tab while working with the folder's properties then you are working with NT, 2000, XP Professional with NTFS.

If you haven't created the folder that will hold this database, then we recommend creating the folder first in Windows Explorer and allow the correct Security Permissions or have the Drive available to the System Account. When you create the folder, it will inherent the security permissions defined by the drive it is created on. Creating a folder in Windows Explorer will also ensure that the folder is empty so the Database can be created successfully.

Figure 2

If that doesn’t work, you may want to also add the “Everyone” account or review the links in the MORE INFORMATION section.

STATUS:

Current.

MORE INFORMATION:

Note: Acceler8DB catalog files can't be read only files. These catalog files are in the root of the database folder (See Figure 1). For example, one of the catalog files is: "9.dta"

You can find the Shared Memory file in the root of the database folder in Windows Explorer. You will need to "Show all files" enabled.
By Default, the Acceler8DB Service runs under the System Account. The System Account will need access to the folder where the Database files will exist (See Figure 3):

Figure 3