Office 2016 Integration

Options
Hi,


I was wondering if anyone has been successful in getting Outlook integration to work with RE (we're on v7.95) in Office 2016. We had a 64 bit version of Office 2016 installed and when we went to install the RE7Outlook.dll file we got a popup saying the file is not a valid Office Add-in. We were told through BB back channels that it *should* work with the 32 bit version so we installed that and now don't get the same error message, but the file is still not installing - nothing happens. Our IT person suspects it is more of a DLL permissions issue than a BB issue. Since BB doesn't support Office 2016 I was hoping some fellow users might be able to point us in the right, or any, direction.


Thanks!

Comments

  • Paul Mulligan:

    Hi,


    I was wondering if anyone has been successful in getting Outlook integration to work with RE (we're on v7.95) in Office 2016. We had a 64 bit version of Office 2016 installed and when we went to install the RE7Outlook.dll file we got a popup saying the file is not a valid Office Add-in. We were told through BB back channels that it *should* work with the 32 bit version so we installed that and now don't get the same error message, but the file is still not installing - nothing happens. Our IT person suspects it is more of a DLL permissions issue than a BB issue. Since BB doesn't support Office 2016 I was hoping some fellow users might be able to point us in the right, or any, direction.


    Thanks!



    Paul, we are experiencing the same issue at our organization. Similar to you, when I try to add the RE7Outlook.dll to my Outlook 2016 add-in screen, nothing happens. have you found a fix since over the last couple of months?

  • Paul Mulligan:

    Hi,


    I was wondering if anyone has been successful in getting Outlook integration to work with RE (we're on v7.95) in Office 2016. We had a 64 bit version of Office 2016 installed and when we went to install the RE7Outlook.dll file we got a popup saying the file is not a valid Office Add-in. We were told through BB back channels that it *should* work with the 32 bit version so we installed that and now don't get the same error message, but the file is still not installing - nothing happens. Our IT person suspects it is more of a DLL permissions issue than a BB issue. Since BB doesn't support Office 2016 I was hoping some fellow users might be able to point us in the right, or any, direction.


    Thanks!

    Good Morning,


    I am having the same issue. If we had the integration tool before upgrading to Office 2016 it seems to still work, but if we did not have the add-in prior to installing Office 2016 I get an error message. I reached out to support for help and was given this reply: 

    Communities is where our programmers go to look for enhancements.  Have all your colleagues and Blackbaud friends go vote on the topic.  The more votes a topic receives, the more likely it will come to fruition.  You know it will eventually come, we just want it sooner rather than later. 


    This answer is unacceptable. This should be on the priority list for eTapestry development. Trying to get enough votes for a function that should be readily available is ridiculous.


    This functionality needs to be addressed NOW!!!!


    Patty Eagon

    Kingdom Workers

  • Nate Laning:

    Paul Mulligan:

    Hi,


    I was wondering if anyone has been successful in getting Outlook integration to work with RE (we're on v7.95) in Office 2016. We had a 64 bit version of Office 2016 installed and when we went to install the RE7Outlook.dll file we got a popup saying the file is not a valid Office Add-in. We were told through BB back channels that it *should* work with the 32 bit version so we installed that and now don't get the same error message, but the file is still not installing - nothing happens. Our IT person suspects it is more of a DLL permissions issue than a BB issue. Since BB doesn't support Office 2016 I was hoping some fellow users might be able to point us in the right, or any, direction.


    Thanks!



    Paul, we are experiencing the same issue at our organization. Similar to you, when I try to add the RE7Outlook.dll to my Outlook 2016 add-in screen, nothing happens. have you found a fix since over the last couple of months?

     

    What I find disappointing is that I asked the question about Office 2016 and was told it would not be a problem.  Now I can't send Thank you letters.  How are other organizations working around this issue?  do we really need to keep two verisons of Office on our server?

    Thanks,

    Peggy

     

  • Peggy Osborn:

    Nate Laning:

    Paul Mulligan:

    Hi,


    I was wondering if anyone has been successful in getting Outlook integration to work with RE (we're on v7.95) in Office 2016. We had a 64 bit version of Office 2016 installed and when we went to install the RE7Outlook.dll file we got a popup saying the file is not a valid Office Add-in. We were told through BB back channels that it *should* work with the 32 bit version so we installed that and now don't get the same error message, but the file is still not installing - nothing happens. Our IT person suspects it is more of a DLL permissions issue than a BB issue. Since BB doesn't support Office 2016 I was hoping some fellow users might be able to point us in the right, or any, direction.


    Thanks!



    Paul, we are experiencing the same issue at our organization. Similar to you, when I try to add the RE7Outlook.dll to my Outlook 2016 add-in screen, nothing happens. have you found a fix since over the last couple of months?

     

    What I find disappointing is that I asked the question about Office 2016 and was told it would not be a problem.  Now I can't send Thank you letters.  How are other organizations working around this issue?  do we really need to keep two verisons of Office on our server?

    Thanks,

    Peggy

     

     

    Ditto, We just upgraded to Office 365 and found out that we are now unable to generate letters as well.  I contacted support and they still towed the same line  that developement is looking into it.  Taking over a year to add support for one of the most widely used products in business is ridiculous.  I was told I could add it to the ideas page, but it's been on there since 2014 so good luck with that.


     


  • Our IT suggests that
    this might be a solution if you use Google; I've been so busy that
    I've not checked it out.




















    Joan (Jo)
    Bell

    GSA
    Foundation

    Database
    Coordinator

    Work:
    303.357.1067

















  • Ditto, We just upgraded to Office 365 and found out that we are now unable to generate letters as well.  I contacted support and they still towed the same line  that developement is looking into it.  Taking over a year to add support for one of the most widely used products in business is ridiculous.  I was told I could add it to the ideas page, but it's been on there since 2014 so good luck with that.

     
    We purchased a Hosted Raiser's Edge and deployed it in January of 2015 and before the purchase we were also told Raiser's Edge would integrate with our Office server. We're using Office 365 (with dynamic DNS) and nope, no integration available.

  •  

    What version of Outlook were you using before moving to 2016? We couldn't get Outlook 2013 integration working and after an hour on the phone with Support they finally pointed us to this article https://kb.blackbaud.com/articles/Article/91998 So it does not surprise me that 2016 integration is not available. I am still running Outlook 2010 so having integration but I often get Microsoft jet engine database errors so resort to the old copy and paste method. Or you could save the email and then attach it to the media tab. 

     

  • What we found from the BB engineers is that the MSADDNDR.DLL is missing from the 7.95 build. I was able to copy the missing DLL and copy it to C:\\Program Files (x86)\\Blackbaud\\The Raisers Edge 7\\DLL". Then registered it and the RE7Outlook.DLL with “regsvr32” and we are back in business. I hope this helps

    Rob


    __________________________________________________________________________________________________________________

    Peggy Osborn:

     

    Nate Laning:

    Paul Mulligan:

    Hi,


    I was wondering if anyone has been successful in getting Outlook integration to work with RE (we're on v7.95) in Office 2016. We had a 64 bit version of Office 2016 installed and when we went to install the RE7Outlook.dll file we got a popup saying the file is not a valid Office Add-in. We were told through BB back channels that it *should* work with the 32 bit version so we installed that and now don't get the same error message, but the file is still not installing - nothing happens. Our IT person suspects it is more of a DLL permissions issue than a BB issue. Since BB doesn't support Office 2016 I was hoping some fellow users might be able to point us in the right, or any, direction.


    Thanks!



    Paul, we are experiencing the same issue at our organization. Similar to you, when I try to add the RE7Outlook.dll to my Outlook 2016 add-in screen, nothing happens. have you found a fix since over the last couple of months?

     

    What I find disappointing is that I asked the question about Office 2016 and was told it would not be a problem.  Now I can't send Thank you letters.  How are other organizations working around this issue?  do we really need to keep two verisons of Office on our server?

    Thanks,

    Peggy

     

     

     

  • Robert Lambert:

    What we found from the BB engineers is that the MSADDNDR.DLL is missing from the 7.95 build. I was able to copy the missing DLL and copy it to C:\\Program Files (x86)\\Blackbaud\\The Raisers Edge 7\\DLL". Then registered it and the RE7Outlook.DLL with “regsvr32” and we are back in business. I hope this helps

    Rob


    Does anyone know if this has been fixed for 7.96 at all?

  • Posting on this thread because it’s the most recent I’ve found on the Office 2016 topic...


    I don’t see dates on KB articles, but https://kb.blackbaud.com/articles/Article/98871 says:
    Compatibility improvements are currently being developed, and are planned to be released in a future patch in early 2017.
    However when I asked Blackbaud support about that I received this today, bolding mine:
    While the 2016 version of Word is currently under evaluation for compatibility we do not have a time frame for if and when this will be released. If we release compatibility with Office 2016…
    This was in response to me pointing out that 2016 has been out for about a year and a half and Microsoft’s “support for the 2013 versions of Office 365 client applications will end” tomorrow:  https://support.microsoft.com/en-us/help/3199744/support-for-the-2013-versions-of-office-365-proplus-ends-february-28,-2017


    Earlier in my conversation with Blackbaud support I was told this, in reponse to pressing about what features users should expect to be problematic.  Again my bolding:
    Any portion of Raiser's Edge that interacts directly with Office can expect to see functionality decrease to cease altogether if you begin to use Office 2016.
    …and from today's message there are “no plans to update the article with compatibility limitations and issues”.  I'd think they'd have made a list, to know what they were working on back when the KB article was written.  It would be useful as some RE users with minimal needs might not be affected, though just opening RE loads DLLs from C:\\Program Files (x86)\\Microsoft Office\\.


    What version of Office are other 365 customer organizations expecting to install for new staff?
  • I just upgraded to RE 7.96 patch 8 and Office 365 (Office 2016 x32).  I have the connection working fine, but only if the workstation has the 2010 AccessDatabaseEngine installed on the workstation (a free download from MS).   You will notice after the install that your registry has a new folder and branch under Local Machine WOW6432Node under MS Office  called 14.o  Access Connecitivity Engine.


    Microsoft just issued some security updates which my WSUS applied this moring and that is when it started working.


Categories