TROUBLE SHOOT: What to check if the MonTel client won't start correctly

There are a number of potentials reasons why the MonTel client won't start or start correctly. These can be divided into a number of areas to consider:

(In this list, problems likely to affect the greatest number of computers start at the top. If only one computer in the office is affected, it might be worth starting from the bottom of the list and working back up.)

Failure to find various files, and the Local call record database. This could be because:

• The File Server is off line or there is a general network failure.
• Drive mappings have changed or are incorrect.
• The users home directory has been incorrectly specified (see the [Users] section of the PABX.INI file especially (DIR) Users Home Directory).
• MonTel is configured to detect the wrong type of network (See The Network Server type was changed and now MonTel appears to start and then exits immediately )

PABX.INI or DEFAULTS.INI settings. Make sure that:

• In the [Network] section The NetworkCheckOrder is correct. For Windows based servers on a TCP/IP network the correct value is 4.
• In the [Program] section AllowOnlyAdminToUseMontel is set to zero and DontStartMonTelClient is set to zero.
• The user has the correct login name and home directory if applicable in the [Users] section.
  
• Check that you have also modified any DEFAULTS FOR INDIVIDUAL USERS correctly (see: How to force local default or background options in the MonTel Client).

Problems connecting to the Master Client database. (If the master client database is still the jet engine it should be immediately upgraded to MSDE or SQL).

• Details of this and solutions can be found at Some MonTel clients cannot connect to the SQL Server or appear to hang on start up.
• Occasionally MonTel clients fail to connect to MSDE or SQL Server with Error 71

Various problems with the local client database:

• See Errors such as Error 91, 3265, 3078 and others on only one or a few of the computers running MonTel.
• See Various errors and problems connecting to the client database that occur on only one users computer.
• See ForceUpdateLocalDBDailyOnStart left undefined would in some circumstance force a local update when none was required.
• See Local Client Database fails to create or creation loops.

A conflict with other software or out of date system files. This problem is very rare and other steps should be considered first

• Has new software modified any system DLL's, especially the Jet database files or the VB Runtime files (and installed older versions?)
• See MonTel Client runs slowly on some Win9x systems with early versions of Norton's Anti-Virus
• An older version of MDAC or a Windows service pack is being used on the client computer.
• See A few Client Computers with MonTel run slowly.
• On older MonTel client has previously been installed. Re-run setup.exe to update the system to the VB runtime Service pack 5.

Hardware or Software system faults or installation issues

• Check that other applications are also running correctly. If they are, it would be sensible to assume that one of the above issues is correct.
• See the fixes for TROUBLE SHOOT: Unable to Run the MonTel Client 32bit Setup on First Windows 95 Version.
• Try re-installing the client (use Setup32). Delete the C:\MonTel folder, the MonTel.INI and SETUP32.EXE file (in the Windows folder). Switch off any virus checkers, and close all open programs, and as much as it possible that might be running in the background. See How to set up the MonTel 32 bit Client on each computer.