The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Kevin van Haaren — Tue, 30 Jun 2020 15:45:53 GMT

This doesn't work for exporting files from projectwise.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Juan Miller — Tue, 30 Jun 2020 14:25:31 GMT

Long Path Tool will let you easily delete, copy or rename long path files.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Rene Lloyd — Wed, 16 Jan 2019 11:50:25 GMT

When clicking on the links in Excel 2016 MSO or Word 2016 (16.0.6925.1041) 64-bit, Windows 7, the link calls PW Explorer (pwc) and works.

but in Excel Office 365 MSO(16.0.10730. 20264) 64-bit, Windows 10, the link calls PW Explorer (pwc) and is not understood, giving the Failed to compile a moniker from give n string error.

The behaviour in Office seems to be the same - the brackets are percent encoded automatically both in Office 2016 and in Office 365. And the PW Explorer is the same, so the difference would seem to be between Windows 7 and Windows 10.

But the connection defined in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\pw is the same.

There is a parameter "UseOriginal UrlEncoding"=dword:00000001 that is supposed to disable URL percent decoding. It doesn't seem to have any effect changing this to 0. And in any event if both Office and Explorer call the same pw\shell\open\command why do they behave differently ?

The PWC log does not show what the string was before raising Error 50000 "Failed to compile a moniker from given string” even with all logs at Debug. And there is no sign of the error in the server log.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Rene Lloyd — Tue, 15 Jan 2019 11:19:38 GMT

Hi Kevin - Have you tried links from Word and Excel in Office 365 / Office 2016? As far as I can see, these still fail with Failed to compile a moniker from given string.because they send the % codes directly to the client, whereas if you paste the links into any kind of HTML they work correctly.

René

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Rene Lloyd — Tue, 15 Jan 2019 10:09:30 GMT

I have installed 03.167, and I still get Failed to compile a moniker from given string when cicking on links from Excel Office 365 MSO(16.0.10730.20264) 64-bit. This is because Excel changes the brackets to percent codes.

Was this error supposed to fixed ?

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Nathan Banks — Tue, 15 Jan 2019 01:28:04 GMT

Strange - Works for me on Win10.

A longer way is to create a hyperlink in a blank new email and shift-click on that.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Phil Conard — Mon, 14 Jan 2019 20:38:04 GMT

Yes, it included Civil 3D 2019 as well. The autocad and civil 3d modules are delivered as one add-in module.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Kevin van Haaren — Mon, 14 Jan 2019 15:08:37 GMT

Phil - The new readme file doesn't explicitly list Civil 3D as included in the integrations but AutoCAD 2019 is. In the past those went together, does the new version have the Civil 3D integrations built-in?

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Kevin van Haaren — Mon, 14 Jan 2019 14:56:49 GMT

This client is working for me running through all the tests in my first note (tested with Outlook and OneNote). Only edge case I found that doesn't work is if you copy the actual link that has been URL encoded and paste it into the address bar of projectwise directly it doesn't work. That's a pretty obscure workflow for users (I use it a lot because i want to see the actual link)

These links DO work now if you paste them into the Windows Run box instead (tested Windows 10, Windows 7 already worked in the past, I assume it still does.)

Kevin

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Phil Conard — Mon, 14 Jan 2019 14:17:18 GMT

The new client that has this fix is available from the software download center.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Phil Conard — Fri, 04 Jan 2019 17:24:19 GMT

Hi Kirk, not yet but it will be soon. Look for it early next week.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Kirk Peterson — Fri, 04 Jan 2019 15:56:25 GMT

Phil Conard - Has that fixed client been released yet?

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Phil Conard — Mon, 03 Dec 2018 21:58:40 GMT

There will be a release of PW Explorer in the next few weeks that will have a fix for this issue. It will be a new version of the update 3.1 client.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Kevin van Haaren — Mon, 03 Dec 2018 19:40:33 GMT

I think this was in a recent update of Office 2016. We're running 32-bit 16.0.11001.20064

i'm hoping for a PW Explorer update that decodes the URL. Or for somebody to identify a way to turn this off in Office. I dug through autocorrect options and nothing in there seemed to affect it.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Patrick Tran — Mon, 03 Dec 2018 19:17:05 GMT

We've had a couple of unfortunate events early this year where the file path got too long for Windows clipboard to handle to full URL. Simply would not copy. URN was the answer there, but we've been on Office 2016/365 for over the last year so this is a recent change?

Wonder what we can do with those paths now that they're too long for URL and no way to copy URN.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Kevin van Haaren — Mon, 03 Dec 2018 17:08:02 GMT

it does, however work in Windows 7. UGH.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Kevin van Haaren — Mon, 03 Dec 2018 17:07:14 GMT

whoops, i tested this on Windows 10 and it doesn't work for me. And neither does my thought of pasting into IE address bar

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Kevin van Haaren — Mon, 03 Dec 2018 15:08:57 GMT

Oh, good call. I was going to mention I think it works if you paste into IE or Edge, but this is even better.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Nathan Banks — Mon, 03 Dec 2018 11:57:41 GMT

Win+R handles percent encoded pw links too.

RE: The definitive guide to why pasted URLs/URNs frequently don't work, but sometimes do

Kevin van Haaren — Sat, 01 Dec 2018 19:01:15 GMT

I had to edit this message as I misidentified this as a projectwise explorer bug when it's actually an Office 2016 bug. Ugh, sorry if you read the first version.

Also, not a real fix for users but if you have powershell 5.1 on your machine you can copy a broken URL and then do:

[System.Net.WebUtility]::URLDecode((get-clipboard)) | set-clipboard

that will take whatever is on the clipboard, decode the percent encoding, then put the result back on the clipboard.