Project Detail

Description

This project consists of two parts:

1. I wish to acquire an existing program module written in C++ and using Extended MAPI that is capable of reading ALL calendar appointments and ALL free/busy information for ALL users on a Microsoft Exchange Server, provided the Windows account being used by the program has the necessary rights and permissions on the Exchange Server. This should be a program that has been proven in the field and works well with all possible Exchange Server setups.

2. I need your help in a specific situation where we have a customer whose Exchange Server is giving MAPI error return codes to our current program, even though the customer claims that he has given the account our program runs under the necessary rights. I need help in understanding MAPI and access rights problems so I can tell the customer "you must do this and that specific thing, and then it will work".

Background information: We already have a program written in C++ and using Extended MAPI that can read all calendar appointments and free/busy information for all users on a Microsoft Exchange Server. This program works without problem for about 80% of our new customers, plug-and-play. But this program is not robust enough for all situations, and when it fails, it does not provide sufficient diagnostic information so that we can understand what the problem is and can tell the customer which rights and permissions are needed in order to make it work. We have no in-house MAPI or Exchange Server competence.

This project requires that you have LOTS of MAPI and Exchange Server knowledge and experience, and that you have an EXISTING and proven program that can do what we want. I am not interested in bidders who say they can create a new program to do this, I want someone who already has an existing well-proven program - and who can legally sell the source code and non-exclusive rights, of course.

Additional information can be provided on request.


Additional information submitted:

11/16/2009 at 23:42 EST:
Edit (17 Nov. 2009):

Part 2 of this project is no longer applicable. We were able to get this customer's installation to work.

But it was an unfortunate and recurring problem we have with our current program. Therefore the project remains open, and I am still interested in acquiring a new program that is better than the one we currently have.