Last error [50000] Failed to compile a moniker from given string. Not found.

Same issue here.  So far, two computers with 10.00.03.140 get the error with links from two different machines running 10.00.02.265 and 10.00.03.49.  COME ON Bentley!  We're CONSTANTLY troubleshooting issues related to MS Office integration.  

Hello

This is a known issue and will be fixed in the next update release.  Please log a service request so that we can track this issue.

Sorry.  This just came to my attention.  Had two users just yesterday complaining about this.  Will be fixed in a future release, but here's a temporary work-around: https://pwstorageazure.blob.core.windows.net/public/copylinkstoclipboardsetup20180919.zip

The issue is that PW URN document links now need to include a trailing forward slash.  I ran into this last week when adding the cmdlet Add-PWPDFLink to PowerShell.

This installer adds a Copy Document Links to Clipboard and a Copy Document Links to Clipboard (Bare) command to the Document menu in ProjectWise Explorer as well as a Copy Folder Link and Copy Folder Link (Bare) command to the Folder menu. These commands return properly formatted PW URN links with my http launcher address (http://pwazurecloudservice.cloudapp.net/Web/PWURLLauncher.html?) prepended to it. The advantage of this approach is that Outlook and Gmail don't bark at you when you try to follow the link because they appear to be regular web links. Nonetheless, you also end up with a PW Document URN with a trailing slash. I'm not sure how this will be fixed in upcoming releases, so this may stop working when PW Explorer is updated.

Great and easy enough solution going forward. But it doesn't resolve existing links.  Any ideas to get those links to work?

Hi all, I've also logged a ticket and that has led me here.
Apologies if this is already known. I found that document URNs aren't working in MS Outlook, Word, Excel
They are working if you create a desktop shortcut or if you paste the URN directly into windows explorer. Does this indicate an issue with Office and the way it's handling the document URNs? or is windows explorer adding a "/" 
Folder URNs and both document and folder URLs seem to work fine. 

I can see your comment about the trailing forward slash, although when I create the URN as a desktop shortcut it doesn't seem to need this? (adding it does still work though) 

Also taking an old URN link in an email, copying, adding the / seems to resolve. 

Eager to hear the solution for old links as mentioned by Amber.