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: 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.