Codeunit 397 and NS Outlook Synchronization Handler problem

blusky75

We have a 4.0 SP3 environment and have some processes to send mail via outlook. We're trying to get this working for a new workstation but we're getting the following error when codeunit 397 is called from one user's machine:

Could not create an instance of the OLE control or Automation server
identified by GUID={03BC4F50-2ABB-48B3-B2A6-3F08EB1D013E} 1.7:{F3B45F48-1F4A-40C9-8DE6-5CC377BF4F82}:'NS Outlook Synchronization Handler'.OSendMail.

After some researching, we went through the necessary steps - install the outlook toolbar via the SP3 installation (client install), ran regsvr32 olhandler.dll, but Navision still refuses to create an instance of that object at run-time.

When we log in as a superuser on the affected workstation and compile codeunit 397, we have no issues. When the superuser windows account calls that codeunit, everything appears to work. When we log in the affected user however, we get the above error. It's as if the automation object (olhandler.dll) is registered for some users, but not others (the affected user by the way is a member of the machine's local admin group so I don't believe it to be permissions-related).

Any idea why this object is behaving so erratically?