Option for MAPI export destination missing in CRViewer

Question

We have an application developed in C++ which includes the Crystal Reports XI RDC and previewer component.
The application is installed at a customer on a Windows Server 2003 machine. Users are working in Terminal sessions connected via Remotedesktop.
For all user accounts the CR report component in our application is working fine, especially they are all able to send documents using the MAPI option in the previewer's export function. Outlook Express is configured as the default mail handler.
There is one exception: One user doesn't have the MAPI option in the export dialogue box. We checked user rights and MAPI configuration: all seems to be the same like for the other users. Especially he also has Outlook Express as default mail client and it is possible to send documents via MAPI out of other applications (for instance the "Send..." menu item in MS Paint).
We investigated the situation with Process Explorer and found out that the "u2dmapi.dll" is not loaded when the report is opened in our application - in contrast to all other users. All other export format and destination options seem to be available for this user (and the corresponding DLLs are loaded by the application). So we believe the issue is related to the u2dmapi.dll which is not loaded.
What can be the reason? Any hint to find a solution is very appreciated!
Thanks in advance!

Answer 1

Here are some results of my "ProcessMonitor-Session". I took a look what happens when I open the export dialogue in the CR previewer under two different accounts - one account where the MAPI option is available and the account of the user who doesn't have the option.
1) There seems to be no difference when CR is browsing for the export DLLs: There is a "QueryDirectory" in the folder "C:\Program Files\Common Files\Business Objects\3.0\bin" with filter "u2d*.dll" and under both accounts the query finds the "u2dmapi.dll". So I'm guessing there is not really a problem with that DLL or its location.
2) The only difference I saw (it's hard to compare all messages line by line because I got more than 3200 event messages only for opening a single modal dialogue): CR is also querying for the "win.ini" file in the user's homepath folder which is on another shared network server. Now I found out that the user with problems has no access to this folder while the other users have access to their respective home folders. (CR queries for "
server\users1\username\WINDOWS\win.ini".) Consequently due to the missing access rights Proc.Mon. says "PATH NOT FOUND".
I remember that the "win.ini" has an entry whether MAPI is enabled ("MAPI=1") or not. Is it possible CR assumes by default that MAPI is disabled in case it doesn't find the "win.ini" and therefore doesn't offer the MAPI option in the export dialogue? (On the other hand there is also a query for "c:\windows\win.ini" on both user accounts and this win.ini has the "MAPI=1" entry, but maybe the win.ini in the homepath has higher priority or whatever ???. In the end it's the only difference I can see so far.) Perhaps CR behaves here not the same way like other applications because - as I said in the first post - mailing via MAPI is possible at least out of MS Paint.
But well, that's a lot of hypothesis and perhaps the problem has nothing to do with the missing access rights to the home path. Anyway, I've asked now the server administrators of the company to configure the account of that user the same way like the other user accounts, especially to give him access rights to his own home path (crazy setup...). I'll come back with the results after they changed it (which can mean... next year... ah no... there are always exceptions from the rule and I always hope for them )