Note: This problem is local to one computer on the Sesame Server network. I've even upgraded it from Windows 7 to Windows 10 and the problem still exists.

Everytime I click the "WordMerge" button for a record, it allows me to choose the document, then I select "This Record Only" then I get this message:

FILE CANNOT BE OPENED.
THIS IS PROBABLY BECAUSE A MERGE DOCUMENT ATTACHED TO IT IS ALREADY OPENED.
CLOSE THE MERGE DOCUMENT(S) AND TRY AGAIN.

Usually when I get this message it's because a merge document is already open in Microsoft Word, and I simply have to close it. But in this case no word document is open.

Is this like an SQL cache or Microsoft Word cache issue? Is there a way to flush the cache?

Any tips or advice is greatly appreciated.

Not sure how to give Sesame write permission to the directory. But I did give the User account full control to the entire C:\Sesame2\ directory.

I also tried a few other things, disabling protected view, disabling file blocking in trust center, etc. At first it had said one of the files was locked but now it's not and read-only, but both documents are now fully editable. These are macro documents and this is running on Windows 10 Ultimate with Word 2016 (64 bit), I used the same setup on another computer and didn't have a problem.

This problem actually was occurring back when this was Windows 7 so I'm not sure the operating system has anything to do with it. But it did have the same version of Word 2016 (64 bit).

Tried clearing the document cache too, and there are no owner files opened. ($, etc.) Kind of stumped me, I know it's not the code, it's local to this computer.

I kind of think of permissions like read/write, but I gave full permissions. But there is a separate administrator account.

Anyways, hope I figure it out.

Check the Start In of the Sesame client icon. You will find it's different on the system that wasn't working, probably set to "C:\Sesame2\Program". Which means the relative path would end up in a different location("C:\Sesame2\Program\Docs" instead of "C:\Sesame2\Docs"). That's why I mentioned it in my first post.

-Ray