Others

Fix Dynamics GP Crashes After Deploying a Word Interop Add-in

Algirdas JasaitisAlgirdas Jasaitis Nov 18, 2026 869 views

Question details

Investigate why a deployed .NET add-in referencing Word interop crashes Dynamics GP after a Windows restart.

Fix Dynamics GP Crashes After Deploying a Word Interop Add-in
Product
Microsoft Dynamics GP 2016 R2, Microsoft 365, and Microsoft Office Word interop
Device & OS
Windows 10 Pro version 1909
Scenario
A custom .NET add-in is deployed to a Dynamics GP client computer that has Microsoft 365 installed.
Observed behavior
Dynamics GP crashes before initialization. Repairing Microsoft 365 temporarily resolves the crash, but it returns after Windows restarts.
Before you start

Record when the crash occurs and whether it returns immediately after a restart. Have the add-in deployment details and Microsoft 365 version available before collecting error information.

Solution 1Recommended

Collect crash details and seek Microsoft specialist support

Use this approach to investigate the recurring crash and give a developer or Office specialist the information needed to identify its cause.

The available information does not establish why the crash returns after a restart. A custom .NET add-in, Word interop, Dynamics GP, and the Office installation may all need investigation.

1
Record the Office configuration

Open Word and select File > Account > About Word. Record the Microsoft 365 version, build, and 32-bit or 64-bit architecture.

2
Collect crash events

After reproducing the crash, open Event Viewer and go to Windows Logs > Application. Look for relevant Application Error or .NET Runtime events at the crash time, and copy their error details.

3
Document the deployment

Record the Dynamics GP version, add-in version, .NET target framework, Word interop reference, deployment method, and whether the crash occurs before or after a Microsoft 365 repair and restart.

4
Ask a specialist

Post the collected details in a Microsoft developer or Office IT Pro community, or provide them to the add-in developer or administrator. Include the error messages and troubleshooting results, but remove sensitive information from logs before sharing.

Collect crash details and seek Microsoft specialist support
Repair is only a temporary workaround: A Microsoft 365 repair temporarily restores operation in this case, but the recurring crash requires further investigation.
Free Microsoft Office alternative

Work with Word documents in WPS Office

WPS Office is a free, lightweight Office alternative with a familiar interface and support for common Microsoft Office formats, making it easy to move everyday document work. It does not fix Microsoft Word interop or Dynamics GP add-in crashes.

Open and edit Microsoft Word DOC and DOCX filesUse a familiar interface for everyday document workMove compatible Office documents to a lightweight applicationWork on Word documents while the interop issue is investigated
microsoft office alternative - wps office

Frequently Asked Questions

Why does the crash return after restarting Windows?

The cause is not established from the reported symptoms. Collect Application Error and .NET Runtime events from Event Viewer > Windows Logs > Application after the crash and share them with a specialist.

Where can I find the installed Microsoft 365 version and architecture?

In Word, select File > Account > About Word. Record the version, build, and whether Office is 32-bit or 64-bit.

What should I include in a support request?

Include the Dynamics GP and Microsoft 365 versions, Office architecture, add-in deployment details, Word interop reference, crash messages, relevant event logs, and the results of the repair and restart.

Can WPS Office fix the Dynamics GP Word interop crash?

No. WPS Office can be used for compatible Word documents, but it does not repair Microsoft Word interop or the custom Dynamics GP add-in.