Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Error saving edited document after successful Word Merge



Application uses out-of-the-box (OOTB) Silverlight-based (SL) Word Merge implementation.

Some users sporadically experience error while trying to save Word document edited after successful Word Merge.
In cases when save failed, the SL control raises error and the document is not saved in the work object.

Error Messages

SilverLight Control ERROR in 'ReturnMergeResultToJS': [IO.IO_SharingViolation_File]Arguments: C:\Users\B17142\AppData\Local\Temp\1\SLWord_42556\WordMergeTemplate.docDebugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See

Steps to Reproduce

1. Advance application to the Word Merge flow action and clicks ‘Create Merge Document’ button.
2. After the merge process successfully completes, make a few changes.
3. Click "Close" x button to start closing Word document.
4. Select the "Save" option from the dialog to exit session with save.

Root Cause

On slower workstations, Word can be slow to completely release the lock on the edited document.

This may conflict with the SL control trying to establish the exclusive lock on the same file, causing "file sharing violation" error.


If the user saves the edited document prior to exiting Word session, takes a second long pause, and then closes the Word session, the "file sharing violation" error is not observed.

Published March 1, 2016 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us