Local Client Database fails to create or creation loops

The local client database may fail to be created or may loop under some (unexpected) circumstances when setting up a MONTEL Client.

If the problem occurs on only a few computers then the problem is local to that computer or user. In this case:

Creation failure of the local client database on just a few computers may be caused by:

• A badly fragmented drive (sometimes with out any error message). Run Defrag to fix
• A disk error (sometimes with out any error message). Run scan disk of a disk repair utility to fix (or test).
• No C drive being present.
• A virus checker preventing correct access to the disk.
• Not enough disk space (this will probably be reported)
• A write protected windows directory
• A write protected MONTEL.INI file, where the ApplicationDatabase does not point to a valid local client database.
• A write protected MONTEL.INI file, in conflict with a Defaults.INI file.

If the problem occurs on all computers then the problem is likely to be either problems with the users accessing the Master Client Database (check access rights and paths), or some conflict in the PABX.INI file.

Creation failure of the local client database on all computers may be caused by:

• A bad file name in PABX.INI (The following example is correct. Note that there is no .mdb in the local database name (MONTEL will add this automatically).

LocalDatabaseLocation=C:\MONTEL\LOCAL

Local32DatabaseName=MONTEL32

LocalDatabaseName=MONTELDB

• Defaults.INI specifying a bad path for in the ApplicationDatabase setting.
• ForceAllLocalDBToHaveTheSamePath=1 in the PABX.INI file, and the ApplicationDatabase Defaults.INI is not present, or is incorrect.
• ForceAllLocalDBToHaveTheSamePath=1 in the PABX.INI file, and the Local Client database path and file name from the [ClientDB] section of PABX.INI is invalid.
• Note that from Version 2.9.0 PreRelease 29: The database looping issue when a ApplicationDatabase is not specified in has been resolved with a "rule" change. Here is how it works. The local MonTel.INI file is only checked if both AlwaysUseDefaults = 0 in the program section AND ForceAllLocalDBToHaveTheSamePath = 0. Otherwise, the setting is taken straight from the file. This means that deleting the file as a way of forcing the update of the local client database will not longer work in most scenarios, though deleting it will work (of course).

Debugging:

If the computers are looping, or you are not certain why MONTEL needs to re-created the local client database every times it starts (which it should not!!!) then set DisplayMessageOnLocalUpdate = 1 in the [ClientDB] section of PABX.INI. This will display a message giving the reason for the update.

Setting ForceAllLocalDBToHaveTheSamePath = 0 in the [ClientDB] section of PABX.INI will offer a prompt giving a suggested location for the Local Client Database.

Looping may be caused by :

• File, path, or network access to the master client database (check that the mapping is correct).
• The user not having both read and write access to the Master Client Database.

The Defaults.INI file does not exist or ApplicationDatabase inside it specifying something other than the Local Client database path and file name from the [ClientDB] section of PABX.INI, and at the same time having AlwaysUseDefaults set to a non zero value in PABX.INI.

For example:

(Defaults.INI)

ApplicationDatabase=C:\MONTEL\DEMO\LOCAL\

(PABX.INI)

[Program]

AlwaysUseDefaults=1

[ClientDB]

LocalDatabaseLocation=C:\MONTEL\LOCAL

Local32DatabaseName=MONTEL32

LocalDatabaseName=MONTELDB

ForceAllLocalDBToHaveTheSamePath=1

• The Defaults.INI file file is not present yet AlwaysUseDefaults is set to a non zero value in PABX.INI.