1

We have a Microsoft word add-in that is working fine on the majority of pc's.

On a particular windows 7 pc, it has the visual studio 2010 tools for office installed correctly.

But when a user creates a new template word document, they get teh following error:

The customization assembly could not be found or could not be loaded. You can still edit and save the document. Contact your administrator or the author of this document for further assistance.

We have tried unloading all dependencies but still does not make any difference.

This is an issue effecting a small amount of windows 7 pc's with office 2016 installed. It seems to be pc related rather than the application.

the_tr00per
  • 439
  • 7
  • 23
  • One of these may help: [Troubleshooting Office Solution Deployment](https://msdn.microsoft.com/en-us/library/bb608594.aspx?f=255&MSPPError=-2147217396) https://stackoverflow.com/questions/4668777/how-to-troubleshoot-a-vsto-addin-that-does-not-load – Chris May 23 '18 at 13:08
  • Thanks for your help – the_tr00per May 28 '18 at 16:31

1 Answers1

2

Usually, the reason behind such an error is that the permissions for loading the VSTO solution are missing. One thing that often gets "missed" when deploying VSTO solutions is that the document must be in a "trusted location". You might want to check that this is the case by looking in the Word "Trust Center" (in the Options). You also need to be sure you've installed the correct version of the VSTO run-time for the version of Windows and Office. Read more about that in the Troubleshooting Run Time Errors in Office Solutions article.

Also it may indicate that you didn't include all required dependencies to your add-in's installer (any platform-specific assemblies). Something is missing on the target machines, so I'd suggest looking for any difference between machines. You can add the .NET Framework, the Visual Studio Tools for Office runtime, and the Office primary interop assemblies to your Setup package as prerequisites that are deployed with your Office solution. For information about how to install the primary interop assemblies, see Configuring a Computer to Develop Office Solutions and How to: Install Office Primary Interop Assemblies.

The required steps for deploying Office solutions are described in the following articles:

You can use the event viewer in Windows to see error messages that are captured by the Visual Studio Tools for Office runtime when you install or uninstall Office solutions. You can use these messages from the event logger to resolve installation and deployment problems. For more information, see Event Logging for Office Solutions.

See Troubleshooting Office Solution Deployment for more information.

Eugene Astafiev
  • 47,483
  • 3
  • 24
  • 45