![]() ![]() Would the solution perhaps be to move to a single user deployment rather than a machine level deployment.Īny help with this issue would be greatly appreciated as it is reeking havoc with our user base which is over 20,000 users. I have it deployed for all users as some of my users are on a Terminal Server so I want to install once on the server and have all users pick up the add-in. ![]() Perhaps this is the problem and it might not happen if I deployed for single users only. My add-in is deployed via a setup.exe (click twice) and is deployed for all users. Is this true? I can't get it to have an effect so my tests seem to confirm it does not work for Word. This requires the users making a note of the path to adxloader.dll and it isn't a simple operation for many of them.Īlso I've read for Office 16.0 versions or later there is a DoNotDisableAddinList registry hive to make sure add-ins are not disabled but this only applies for Outlook and not Word. The only way in the case of C2R to get the add-in back is to remove it and re-add it from the File->options->add-ins Select "COM Add-ins". ![]() There seems to be no way to access this registry entry from within the add-in so the work around described above is not possible. This is the virtualization registry entry for C2R. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY\MACHINE\Software\Wow6432Node\Microsoft\Office\Word\AddIns\ In this case when the add-in is re-enabled the registry entry in This all works fine but there is yet another problem when the install of the host application is Click to Run e.g. In this way if the user does manage to get the add-in back, using the steps above, it will set itself to load on start up. HKCU\Software\Microsoft\Office\Word\Addins\ DWORD=3 When the host application is restarted it is gone again.Ī work around is to update the load behaviour to 3 using code in our add-in each time it loads by setting it in the key However in some situations although the add-in is enabled again it does not set the load behaviour in the registry to 3 but instead just loads it in that session only. The user can re-enable the add-in using File->options->add-ins Select "Disabled Items" from the drop down and find the add-in and enable it followed by selecting "COM Add-Ins" from the dropdown and checking the add-in if not checked. If the user clicks Yes (as many do) the add-in is disabled. If this keeps happening, disable the add-in and check for available updates. "Word is running into problems with the 'ADD-IN NAME' add-in. It seems that when it happens a user is prompted next time they run Word with a dialog box saying This is a common problem with COM add-ins in Word and other office applications it seems. It's also possible if the add-in is slow loading. This can happen if the add-in does not respond quickly when used or if there is a host application crash while the add-in is on the stack. We have a Word Add-in that is suffering from being periodically disabled by Word. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |