Why Won’t My Mapi OCX Work On A Server Without VB Installed?

I have an app that sends email using the Microsoft Mapi Controls 6.0 (msmapi32.ocx).
This app runs fine on my machine that has VB and Office as well as Outlook on it.

I’m trying to run it from a machine that only has Outlook on it (configured identical to mine), and its not working.
Outlook can send emails from that machine just fine on it’s own.
I registered msmapi32.ocx on that machine successfully.
And even created a setup.exe using the Setup Wizard included in VB6, and ran it on the client machine successfully.

The error I get is "ActiveX component can't create object"

On this line: Set m_objMapiSession = CreateObject("MSMAPI.MAPISession")

Shouldn’t I be able to use the msmapi32.ocx with only Outlook installed on the computer considering all my VB components have been copied over, and registered?

mcvbm60.dll must be in the system directory and registered for your OCX to work.

It's the VB virtual machine.

Quote:

---

Originally posted by jim mcnamara
mcvbm60.dll must be in the system directory and registered for your OCX to work.

It's the VB virtual machine.

---

He wouldn't be getting the error he is getting if he didn't have the VB runtime files. If he didn't have msvbvm60.dll file installed and registered, then he wouldn't even get the program to run. Plus he said he used the P&D wizard, which also needs the vb runtimes to run. It usually installs them automatically.

A similar thing happened to me. Twice, with different programs on different machines.
I installed my prog (using P&D Wizard) on a clean win 98 instalation.
When I started the program, the same error occured.

I first thougth that it was a problem with DAO so I registered it manualy. I eventualy tried to register all components and activex dlls manualy and still nothing. I installed MDAC, DCOM, and idontknowhatelse, and nothing.
So I ended up installing VB, and then deleting the vb directory.

Both programs and instalations were previously tested on clean instalations of all target systems.
I haven't got a clue why the error occured :confused:

I am interested in what you have to say about that.

Anyone know how to solve this WITHOUT installing any more applications on the server?

nobody found a solution for this?