Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved mailResolveRecipient returning mailReturnFailure!

  1. Advice
0
Votes
Undo
  1. David Peace (Powersoft)
    David Peace (Powersoft)
  2. PowerBuilder
  3. Monday, 2 March 2020 14:20 PM UTC

Hi Guys

We have a problem with mailResolveRecipient returning mailReturnFailure!

This is code that is 20 years old has worked consistently forever. Clearly it is something environmental that is occurring but the symptoms are as follows:

1. Some users work other do not same code same functions.

2. The number of users not working is increasing so the disease is spreading like coronvirus.....

Environment is:

Various windows version PCs & through to 10, Outlook Version 2016, Exchange Server 2013. PB Version 12.5, not yet rolled out the PB2017R3 yet.

My question is what exactly does the mailResolveRecipient actually do what calls do, what calls does it make on the MAPI client? If I can understand this we can give that into to the IT support for them to diagnose the problem.

Perhaps someone knows the underlying details or Appeon dev can take a look for me please.

Thanks in advance

 

David

 

Looking for a buyer for my PB software-based busin...
sql / dw updates
Responses (2)
Miguel Leeuwe
Miguel Leeuwe Accepted Answer Pending Moderation
  1. Monday, 2 March 2020 15:09 PM UTC
  2. PowerBuilder
  3. # 1

Hi David,

 First of all, I realise this is not an answer to your question, but ...

If you are on 2017 or 2019, try setting PBUseSimpleMapi=No in the pb.ini.

If you are on 12.6 leave the default.

On 12.5 we never had any problems.

 

What we do (since 12.6), is only use Mapi to popup the addressbook of outlook, as that one doesn't keep flashing in the taskbar. Since after sending the email, we still have to use OLE with outlook to empty the outbox (see: https://docs.microsoft.com/en-us/office/vba/api/Outlook.NameSpace.SendAndReceive ), we decided to use OLE and Outlook for all the rest (send, resolve recipients, etc.)

After having obtained the recipients with MAPI, we assign them to OLE recipients. If PBUseSimpleMapi=No that OLE-resolve works. If not it doesn't.

Also, when double clicking on a recipient in the mapi address book, we've had a period in which the email addressees would be preceded with a "; ", depending on the pb.ini setting. (now that bug seems to have been resolved by either MS or Appeon?).

HIH

NOTE: 
Have you checked if they might be on Office 64 bits? That would cause problems with MAPI.

 

Comment
David Peace (Powersoft)
  1. David Peace (Powersoft)
  2. Monday, 2 March 2020 15:24 PM UTC
Thanks for the feedback, yes our PB2017r3 version is using the pb.ini setting. Unfortunately this has occurred on a system that has been running successfully for months. I really need to understand what the mailResolveRecipient actually does with the MAPI client.



It's not an Outlook 64Bit issue as the version of Outlook has not changed, it might have something to do with the latest MS Update for outlook but that is not clear as the IT support forced the update on a user that had not yet had it installed and their system continued to work.

  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Monday, 2 March 2020 15:39 PM UTC
Now that I remember, I tried not to long ago with MAPI and "resolveAll()". That did not work. Resolving the recipients one -by-one did work.

Also make sure your ani-virus is up to date and maybe see if this "permission asking dialog of outlook" is popping up somewhere in the background.
  1. Helpful
There are no comments made yet.
David Peace (Powersoft)
David Peace (Powersoft) Accepted Answer Pending Moderation
  1. Friday, 10 September 2021 14:38 PM UTC
  2. PowerBuilder
  3. # 2

Never did find out what caused this, but it went away. Weird stuff happens!

Comment
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Friday, 10 September 2021 15:20 PM UTC
Office updates, I see things break and get fixed constantly.

regards
  1. Helpful 1
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.