locked
Our AddIn won't load, after opening a specific Word document RRS feed

  • Question

  • Hi all;

    We've had this happen on 2 systems. After opening a specific Word document, with our AddIn running, Word will no longer run our AddIn. All the registry settings are correct.

    And in Word we can bring up COM AddIns and check our AddIn. It then starts it in the instance of Word. But if we exit and restart, it is not running.

    How do we figure out why it no longer likes our AddIn? We are not in the disabled AddIn list.

    ??? - thanks - dave


    Who will win The Windward International Collegiate Programming Championships?

    Wednesday, June 5, 2013 4:48 PM

Answers

  • After running ProcMon I almost instantly found the issue. Our addins, when installed are supposed to be installed to the local machine in registry. For some odd reason, our addin was also located in current user. Now when the addin was disabled, it was disabled in current user and no local machine.

    Now the following might be an issue with word itself. When our addin was re-enabled it was enabled in the local machine part of the registry, and not current user. When word is booted, if first looks in HKLM (Local Machine) and enabled our addin. Than almost immediately, it looked in HKCU (current user) for addins as well, and because the addin was set as inactive in HKCU, it was than set as in active. 

    So, Word was enabling our addin, than almost right after setting it to inactive. Once the load behavior was set to be the same in both places, the issue went away.

     
    • Proposed as answer by SeanCallahan Friday, June 7, 2013 4:47 PM
    • Marked as answer by DavidThielen Friday, June 7, 2013 5:43 PM
    Friday, June 7, 2013 4:47 PM

All replies

  • Is this problem related to the other problem you also reported?

    What is the version of Word that is running on these 2 machines?


    Kind Regards, Rich ... http://greatcirclelearning.com

    Wednesday, June 5, 2013 10:10 PM
  • Nope, different systems. All are running Office 2013 64-bit.

    thanks - dave


    Who will win The Windward International Collegiate Programming Championships?

    Wednesday, June 5, 2013 10:24 PM
  • I had found ProcMon utility (process monitor) very useful in troubleshooting load issues for our company addins.

    Success rate for my cases is probably around 60%

    Regards,

    Michael

    Wednesday, June 5, 2013 11:42 PM
  • After running ProcMon I almost instantly found the issue. Our addins, when installed are supposed to be installed to the local machine in registry. For some odd reason, our addin was also located in current user. Now when the addin was disabled, it was disabled in current user and no local machine.

    Now the following might be an issue with word itself. When our addin was re-enabled it was enabled in the local machine part of the registry, and not current user. When word is booted, if first looks in HKLM (Local Machine) and enabled our addin. Than almost immediately, it looked in HKCU (current user) for addins as well, and because the addin was set as inactive in HKCU, it was than set as in active. 

    So, Word was enabling our addin, than almost right after setting it to inactive. Once the load behavior was set to be the same in both places, the issue went away.

     
    • Proposed as answer by SeanCallahan Friday, June 7, 2013 4:47 PM
    • Marked as answer by DavidThielen Friday, June 7, 2013 5:43 PM
    Friday, June 7, 2013 4:47 PM