Error: 1733: Class definition TELEMAGIC.DOWNTIMEMONITOR is not found

This error has to do with the user access rights.

This generally occurs with a new PC, attempting to run TM5 for the first
time. It’s looking for DTMON.DLL in the System32 folder.

[protected]

Make sure the user has Power User rights and it should work fine.

Either manually copy it into the System32 directory on the PC in question from the server or do this:

  1. Log into the local machine with administrator
  2. Run DBUTIL on the local machine and run Register System Files
  3. Exit out of DBUTIL
  4. Run TeleMagic v5
  5. Exit out of TeleMagic
  6. Log off Administrator and log in as the user
  7. Run TeleMagic v5

When all else fails install an eval copy of TM to a different directory (c:\tm5delete) once installed try running the client again.  Sometimes the eval install seems to do a better job of getting the files registered and setup correctly than copy and register system files does

[/protected]

Error: “an unknown error occurred while loading Tm.exe. shutting down”

I have a client who just bought a laptop with Win 7-32-bit and he gets ‘an unknown error occurred loading TeleMagic. Shutting down.’

[protected]

Most common error has to do with the fax driver, or the fact that the user doesn’t have rights to update files in the system32 folder.

Check to make sure you have admin rights on the machine, for the first time you run TM.

Log in as the administrator, and run  the copy/register. After that is done, try it again.

When you install TM5 on a W7 or W Server 2008 you must copy from somewhere the telemagic folder that is in c:\program files\telemagic

There are fax files and folder in there that does not get created on install.  If it is a 64 bit OS you would copy it over to the c:\program files (x86) folder.

This telemagic folder is often overlooked because on a XP install we never notice it is there.

If this is a Terminal Services installation, set the Check System Files to N in TM.INI

[/protected]

Error: C0000005

This is generally caused by a failing network switch, card, or router.
Replacement or the bad component is the solution.

It has also been caused by anti-virus / anti-spyware programs aggressively
checking every file. This causes system slowness to the point where this
message appears. We suggest that you set your av software programs to skip
.DBF, .CDX, .FTP and .TXT files as a test should you receive this message.

Error: 1104 / 1105 – Proc

The large majority of 1104 / 1105 errors experienced have been network related.

“The error message indicates that the specified file is not available. There are several possible causes, but the most likely would be that the file is being locked by some other operation, or that the paths are incorrectly mapped.”

  • Check components like hubs, nic card on the server, switches. Also check to see that TCP is the only protocol running. NETBEUI & IPX have caused this problem in isolated cases.
  • In Windows 2000 environments, missing patches to Terminal Services have proven to cause this error as well.
  • This is a general Error Reading File message. You need to check the typical things (server error log, disk space, temporary files, permissions, etc). You might try copying the installation to your local system, doing a Path Update, and then seeing if you can create the problem on the local system.
  • One thing to be aware of in Win7. I’m not sure if this is all the time, but if you run something “as administrator”, it won’t pick up the drive mappings you have in place. I don’t know if that would effect this or not.
  • Could a virus scanner be running and locking the file?
  • You have a bad port on the switch.  Plug the network cable from that machine into a different port.
  • Make sure they are running from a node install. Try running some network tests, to see if there are errors occurring.
  • I had that problem with a machine in my office recently.  I replaced the network cable from the machine to the wall and its worked perfectly since then.

Error: C0000006

Unknown Error C0000006

This is generally caused by the Terminal Services problem for which there is a patch offered by Microsoft. This appears to be the fix that prevents corruption to the Visual Fox Pro DLL files held on the server in the \SYSTEM32\ folder. The files in question are vfp6r.dll and vfp6renu.dll.

If you are getting this error, you need to fix it and then prevent it from recurring by applying the MS patch.

The fix is to delete those files from \SYSTEM32\ and replace them with those stored within TM. To be safe you might want to rename rather than delete these files. We suggest that you perform a full backup before proceeding.

  • All users need to be out of the system
  • A Rebuild is not required.
  • Log in as a network operating system supervisor
  • Delete (or rename) vfp6r.dll and vfp6renu.dll in \SYSTEM32\ using Windows Explorer
  • Launch T:\TM5\PROGRAMS\DBUTIL.EXE
  • Select SYSTEM & COPY & REGISTER SYSTEM FILES
  • Close DBUTIL.
  • Test for the error

Note that you can work around the problem by having ALL TS users log off TS & return to TS & TM. This works for a random period depending on usage of TS.

Error: Ambiguous Name Detected. tmpDDE

This message might be displayed when sending a fax or printing a letter using mail merge.

Solutions:

  • Rename or Delete all instances of Normal.dot on the workstation, it will be re-created the next time you use Word, any formatting in normal.dot need to be re-created.
  • In Word go to Tools/Macros and Remove the Word macro called TMPDDE.
  • Scan the computer for viruses.