Skip to main content
tallihos
New Participant
March 23, 2017
Question

32bitmapibroker causes Outlook password popup clicking send file as e-mail attachment

  • March 23, 2017
  • 4 replies
  • 2788 views

I've got a client which uses Reader DC 2015.023.20070 which is the latest version as far as we know, they regularly (>10 times a day) use the fill and sign function and then use the 'Send file as e-mail attachment' button in the toolbar.

About 4 to 15 times a day they get a popup to enter the Outlook / Office 365 e-mail account password, if they don't there is no pop-up and the password keeps coming back. They've ticked 'save password' over 10000 times now but this doesn't seem to do the job. It's possible it doesn't ask for a password the next 5 times but it's also possible to have the pop-up 5 times in a row. In the title of the password pop-up it shows '32bitmapibroker' which is part of Adobe Reader.

They currently use a fully updated Outlook 2013 client with only 1 Office 365 account configured. Pretty straightforward in my eyes.

We've already reset all references in Windows and entered them from scratch. Do you guys have any suggestions what we could do to solve this problem?

    This topic has been closed for replies.

    4 replies

    New Participant
    February 24, 2020

    Still happening with Outlook 2019.  Profile has an internal Exchange Server account and a hotmail.com account.   Mail will be sent from the internal Exchange account, but adobe 32bitmapibroker keeps randomly prompting for the hotmail password that won't even be used to send the mail.

    sambutler
    New Participant
    May 9, 2019

    This is happening for a client running the latest version of Outlook on an Office 365 subscription, any wisdom?

    tallihos
    tallihosAuthor
    New Participant
    July 3, 2017

    This is an Outlook 2013 only problem, I've installed Outlook 2016 for this client and the problem is solved.

    tallihos
    tallihosAuthor
    New Participant
    March 23, 2017

    By the way it are all 32-bit applications so it couldn't be a 64/32 bit conversion problem or something like that.