I am getting this error message when I an tryin to open a URN link to a file mailed by my colleague.
I am using ProjewctWise Explorer Version 10.00.03.140
The Link to teh file is created is from Projectwise version 08.11.11.590.
Pleas ehelp to resolve.
Thanks.
Ranadeep Basu.
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, ExcelThey 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.
See if this helps: https://pwstorageazure.blob.core.windows.net/public/pwlinkprocessorforupdate3setup20181001.zip
The good thing about this approach is that the Update 4 installer (or whatever they end up calling it) should naturally overwrite it.
If you are going to post new links could you delete or disable the old ones.
This is excellent info to tell me that the installer will apparently not help us because we can't use additional commands. We already have nearly an identical config & commands that copy links for use in Gmail (as a target; it ignores the pw: handler unless wrapped in an https one as shown above). I fixed that part at our web site to postpend the / but with our other effort, hooking into Adobe Sign, will not work and will require the update.
However, a HUGE warning to all. This current service is not as secure as it needs to be. I fixed it for our site but this remains a large hole. Here's some examples. Someone sends your users an email saying
Please review this design in ProjectWise for correctness
http://pwazurecloudservice.cloudapp.net/Web/PWURLLauncher.html?https://zeltser.com/malware-sample-sources/
Or maybe you want your users to send feedback to Microsoft en masse:
http://pwazurecloudservice.cloudapp.net/Web/PWURLLauncher.html?windows-feedback:
These links are safe to click and the second one is a bit amusing though the downloads at the first are not safe. Of course, someone with evil intent would send you to a phishing site, not snarky feedback or a site that has samples of malware (yeah, don't download anything from that security researcher's site).
My modification requires the pw handler, datasource delimiter, and our domain name.
Bill