OCIEnvCreate causes MAPIAddress to stop working

[syi129]

Hi

we recently upgraded our systems to use oracle 10g and noticed that calls to MAPIAddress were giving an undefined error.

After doing a bit of debugging we found that the calls to MAPIAddress (in the mapi unit) stopped working was after the line OCICall(OCIEnvCreate(..)) in the method TOracleSession.GetEnv

Does anyone know why this happens ? we do not really want to roll back to using oracle 8 client to enable the application to continue working.

 

[Marco Kalter]

Perhaps you have installed the Oracle Connector for Outlook?

 

[syi129]

Nope, Oracle Connector for Outlook wasn't installed on any of the machines. We just have the basic runtime install from the oracle 10g client but the method below keeps on giving out an error code of 2.

MAPIAddress(0, 0, 'Select', 4, '', 0, lpRecip, 0, 0, @intRecips, lpRecips)

 

[Marco Kalter]

I'm not sure what else might affect a MAPI call. You could try an upgrade to an 11g client.

 

[syi129]

ok, thanks. An upgrade to 11g will not be possible across the entire estate but we are looking at replacing the MAPI calls with Extended MAPI. It is strange that the MAPIAddress method stopped working as soon as the OCIEnvCreate method was called. Do you know what the OCIEnvCreate method does underneath the hood?

 

[Marco Kalter]

I don't know any more than what is documented in the Oracle Call Interface Programmer's Guide. This does of course not provide any clue about the problem.