Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, January 20, 2016 7:42 PM | 1 vote
Hello, I noticed a rather critical error in testing of Windows 10 Enterprise today. I am not able to open any PDF files that are stored on a network share, using Edge as the default PDF application.
If I copy that same PDF locally, it opens without issue.
I tested it again with having Reader XI installed and the PDF opened without issue. Same goes for previous versions of Windows with Reader installed, so the issue is isolated to Windows 10 + Edge as default handling for PDF.
We were hoping to avoid using a 3rd party PDF application for viewing. Has anyone experienced this and if so is there a fix?
The error is a generic, "Hmm, we can't reach this page."
Thank you in advance.
All replies (44)
Wednesday, January 20, 2016 11:51 PM | 1 vote
Have not got this on a basic test to one mapped drive I have on this system. The pdf was created with Windows 10 Print to PDF and opens fine. So does this affect every pdf or is there a setting or option that maybe caused this Edge?
Not saying this will resolve it for you but not perhaps as straight forward as Edge does not open pdf on any networked drive.
Thursday, January 21, 2016 7:44 AM | 1 vote
Hi Onatam,
I just tested at my side and Microsoft Edge could open PDF on the network share without issues.
Please fist verify there is no network issues, then try to map the drive to the local computer, then open it with Microsoft Edge to check out.
Regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Thursday, January 21, 2016 12:20 PM | 1 vote
Hi Onatam,
I just tested at my side and Microsoft Edge could open PDF on the network share without issues.
Please fist verify there is no network issues, then try to map the drive to the local computer, then open it with Microsoft Edge to check out.
Regards
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Michael, I attempted to map a couple of the network shares as local drive mappings and the PDF's still failed to open. If I copy them local they open without issue.
Here is something interesting, I tried a different share and it appears to open directly from the network. So for right now there are 3 failures and 1 server that I can open successfully. My access is limited from a share administration perspective but I will try to compare the 3 servers that provide errors to the 1 share that I can open successfully. All 4 servers I have access to R/W/M in the shares I am trying to pull from. Others are also unable to pull from the same server that I am unable to as well.
If Acrobat Reader is installed, it opens without issue but we were really hoping to use Edge as the default. Instead of installing and managing Acrobat on all machines, we wanted to keep it limited to an on request basis with 10 moving forward.
Friday, January 22, 2016 12:57 PM | 3 votes
I fell into same problem.
Edge does not understand network shares.
Neither mounted nor un-mounted.
Other browsers work with doubleklick (if assigned to pdf), with entereing file://///server/path/file.pdf or file:///Z:/path/file.pdf or even drag&drop.
Edge as default viewer for PDF does not work. You have to copy file locally and open it there.
Funniest of all is that you can open IE, drag&drop pdf from share into IE, select "open" and it will open in Edge without problems. Once the PDF was successfully opened you can reopen it normally within File Explorer(double click) and it opens also in Edge without errors.
Friday, January 22, 2016 12:59 PM | 1 vote
Works also if Edge is closed & and reopened.
Tuesday, January 26, 2016 3:07 PM | 1 vote
Works also if Edge is closed & and reopened.
I cannot replicate PDF opening by closing and reopening Edge. I have the same experience that you posted about on your first post, except dragging to IE and selecting open does not work.
Version 1511 - TH2. 10586.36
Friday, January 29, 2016 6:23 PM | 2 votes
Can you provide me more information regarding your scenario? I was tracking an issue regarding Edge not able to open pdf files on network share, however our product group fixed it for 10586 according to the one I was tracking.
- What device/operating system is hosting the network share? Windows Server, another client machine or NAS device?
- Can you capture a trace when reproducing the issue?
a) unmap all network drives
b) reboot client machine
c) open elevated command prompt and run ipconfig /flushdns and netsh trace start capture=yes scenario=FileSharing d) open file explorer and navigate to fileshare location and attempt to open the .pdf file using edge
e) stop the trace using netsh trace stop
Please send me an email directly to arudell at Microsoft dot com with subject name of this TechNet forum thread that includes the .etl and .cab file generated from the trace.
Regards,
Adam Rudell | Windows Networking Beta | Microsoft Corporation
Friday, January 29, 2016 7:09 PM | 1 vote
@ARUDELL
Thank you for the reply. I have emailed you the requested files. To briefly answer your two questions here:
1) The Network Share in this example is a Windows Share, running Server 2008.
2) Trace captured with your requested command line from "c)" and emailed to you.
Monday, February 22, 2016 10:24 PM | 1 vote
To Adam and others, I had not found this January 2016 post when I created my February 19, 2016 post on
the same problem. If and when the problem is solved, please add a link in the 2/19/2016 thread to here so readers of that thread can see the solution here.
My 2/19/2016 post on the same problem:
On 1/29/2016 Microsoft's Adam Rudell (Arudel) asked Onatam to provide some information to Adam and to generate some trace files and provide those. I completed those actions, too, and have emailed the information and trace files to Adam as well. In case it helps some elses, I provide below the text of my email to Adam Rudell.
Dear Adam Rudell
On January 20, 2016 Onatam made a Microsoft TechNet forum post titled "Unable to open a PDF with Edge over a network share". In your January 29, 2016 reply post in that thread
you replied:
"Can you provide me more information regarding your scenario? I was tracking an issue regarding Edge not able to open pdf files on network share, however our product group fixed it for 10586 according to the one I was tracking.
1.What device/operating system is hosting the network share? Windows Server, another client machine or NAS device?
2.Can you capture a trace when reproducing the issue?
a) unmap all network drives
b) reboot client machine
c) open elevated command prompt and run ipconfig /flushdns and netsh trace start capture=yes scenario=FileSharing
d) open file explorer and navigate to fileshare location and attempt to open the .pdf file using edge
e) stop the trace using netsh trace stop
Please send me an email directly to arudell at Microsoft dot com with subject name of this TechNet forum thread that includes the .etl and .cab file generated from the trace."
Here is the information you requested in items (1) and (2).
I am running a QNAP NAS device (model TS-439-II pro) that contains the network share folder that I mapped as drive Q. The QNAP NAS runs a Linux operating system, as I understand it. The device firmware has been updated to the latest January 19, 2016 firmware. My computer is new (October 2015) with OEM Windows 10 Home, updated through version 1511, OS Build 105.86.105. The version of Microsoft Edge on my computer is version 25.10586.00, the second public release that occurred on, I understand, November 5, 2015. As far as I can determine, there is no subsequent release of Microsoft Edge as of February 19, 2016. The QNAP NAS is connected directly to my computer through an Ethernet cable (not Wi-Fi).
Today I completed the above actions you described in (a) – (e), however, to be able to navigate to the PDF file on the network drive, as you requested in step (d), I had to first remap the network drive, which I did between step (c) and (d). I assume/hope this is what you anticipated/meant since, as far as I know, one cannot navigate to the PDF file on the network drive in File Explorer without remapping the network drive first.
As has been the problem for me since October 2015, Microsoft Edge presented the following error message:
"Hmm, we can't reach this page.
Try this
•Make sure you’ve got the right web address:
ms-appx-web://microsoft.microsoftedge/assets/errorpages/dnserror.html#file:///Q:/SH%20Shrd%20Fls/TestPDFfile.pdf"
I had not found Onatum's January 20, 2016 post in which you made your above excerpted January 29 reply when I created my February 19, 2016 post titled "Microsoft Edge (Windows 10 Home version 1511) still cannot open PDF file on a mapped network drive" at
https://social.technet.microsoft.com/Forums/en-US/384172dc-ea64-420e-95f0-e9c8e4979fb5/microsoft-edge-windows-10-home-version-1511-still-cannot-open-pdf-file-on-a-mapped-network-drive?forum=win10itprogeneral
Please see my February 19, 2016 post for more information about my experience.
After completing your step (e), the trace files were generated. I have attached them to this email, as you had asked of Onatam in your January 29, 2016 reply to Onatam in his post.
I hope the information in the attached files, that I describe above, and that I describe in my February 19, 2016 post can help you or others in Microsoft to establish the root cause of the problem and devise a fix. When this is resolved, please make sure the resolution information is added to Onatam's 1/29/2016 post and to my 2/19/2016 post. I will continue to monitor these posts for a resolution.
My file TestPDFfile.pdf that prompted Microsoft Edge to present the above error message is located on the mapped network drive Q:\SH Shrd Fls
This error message result applies for every PDF file hat I have on the mapped network drive, at least the dozens in several different locations that I have tried. I have not found one PDF file on the mapped network drive that will open in Microsoft Edge. All of my PDF files will open properly in Microsoft Edge if I first copy them from the mapped network drive, paste them onto the hard drive in the computer that is running Windows and Edge, and open them from this location. All other file types successfully open directly from the mapped network drive in their respective applications, it is only PDF files with Microsoft Edge that have a problem.
I hope someone at Microsoft can determine the problem and provide a resolution.
Thank you.
Steven
Tuesday, February 23, 2016 8:16 PM | 2 votes
I wanted to let you know that I have filed a ticket with our product group to get their feedback as I am unable to reproduce in any of my environments running build 10586 + and multiple different storage devices hosting the network share. Hoping they can provide me some more context on why Edge would fail to be opening the file as the network trace looks fine and nothing standing out at me from a network perspective. I will update you as soon as I have some more information.
Adam Rudell | Windows Networking Beta | Microsoft Corporation
Wednesday, February 24, 2016 7:55 PM | 1 vote
Thank you, Adam. I will continue to monitor this post and mine of February 19, 2016 and eagerly await any update or, even better, a solution. Steven
Thursday, February 25, 2016 4:56 AM | 1 vote
eagerly await any update or, even better, a solution. Steven
Meanwhile have you tried putting Fiddler in between?
Robert Aldwinckle
Thursday, February 25, 2016 8:56 PM | 1 vote
Dear Robert, thank you for providing your post. [I don't know why, but this post editor won't keep line/paragraph breaks I insert. It makes distinguishing the paragraphs/comments a little more difficult. I've inserted paragraph numbers to help, but blank lines keep getting removed when I submit the post].
You asked "Meanwhile have you tried putting Fiddler in between?"
1. I am not an IT or network professional. I am a Windows 10 Home and Microsoft Edge user at home. That being said, I am not afraid to try somewhat more technical actions in an effort to diagnos and solve a problem ... within reason. Until you mentioned Fiddler, I had never hear of it or knew what it was. I provide most of the next three paragraphs of information for other post readers who might also not know about Fiddler.
2A. Fiddler Summay - As of today, Wikipedia says "Fiddler (software)" "captures HTTP and HTTPS traffic and logs it for the user to review (the latter by implementing man-in-the-middle interception using self-signed certificates)." and "Fiddler can also be used to modify ("fiddle with") HTTP traffic for troubleshooting purposes as it is being sent or received. By default, traffic from Microsoft's WinINET HTTP(S) stack is automatically directed to the proxy at runtime, but any browser or web application (and most mobile devices) can be configured to route its traffic through Fiddler."
2B. Free Fiddler-Like Programs Exist - A Google search indicated that multiple companies distribute programs called Fiddler or an otherwise very similarly named program. One than I found is Telerik (telerik_com) that appeared to have well written information and documentation about their program "Fiddler". My guess as to which company's "Fiddler" software to use over another is little more than a guess. Telerik says their Fiddler is "The free web debugging proxy for any browser, system or platform".
2C. Fiddler Uses Proxy Setting - Among many things, Telerik's documentation on their Fiddler program says one must "set the browser to connect to a proxy server" and it presented the steps for how to do this for several browsers (not including Microsoft Edge by name) and, for non-named browsers, what browser settings to look for to change to accomplish this. I got to the proxy server settings in Microsoft Edge at [...]>Settings>View Advanced Settings>Open Proxy Settings where, upon clicking the "Open Proxy Settings" button, a Windows Settings screen then opens up. The Windows settings screen is at Settings>Network & Internet>Proxy and this screen presents a number of settings and value entries for "Automatic proxy setup" and "Manual proxy setup".
3. I know essentially nothing about how network interfaces/communication works or about Network and Internet settings, including nothing about "Automatic proxy setup" and "Manual proxy setup" settings and value entries. I recognize that I could complete a significant amount of time online trying to learn what these settings and value entries are and, hopefully, what I am doing when I change the values and what to change them too. I am very worried, however, that my limited understanding and no experience with changing these values might cause me more problems that I do not understand and that I would have a very difficult time recognizing or reversing. That being said ...
4. Assuming
a) I downloaded/installed a Fiddler program and learned the program well enough to cause it to do what it is designed to do or what you want,
b) I succesfully learned about and properly changed the Windows proxy server settings and value entries to allow Fiddler to work and to not cause other problems, and
c) I successfully got Fiddler and Microsoft Edge working together with the changed Windows proxy server settings, then
I'd have to be able to understand the (I'm guessing) significant amount of Fiddler-generated/captured technical information. I do not presently have any knowledge or experience that I believe would allow me to understand the Fiddler-generated/captured technical information or, if I understood it, what I should do next to try to understand and resolve the problem of Microsoft Edge not opening PDF files directly from a mapped network drive. I get the impression you believe I have that understanding. I'm sorry, I do not.
5. Can you offer anything more about what present/existing settings and information I can check or capture and provide to you that might help you recognzie the problem?
6. As I mentioned in my previous posts on this problem, for any file type other than a PDF file, Windows successfully opens the associated program and the file directly from its location on the mapped network drive (a shared drive on an Ethernet connected NAS). My impression is that if there is a network problem of a type that requires its detection with a program like Fiddler (and requires the knowledge and experience to interpret that Fiddler-generated technical information), such a network problem would be present for programs/files other than Microsoft Edge and PDF files.
7. If you know of no other present/existing settings and information I can check or capture and provide to you that might help you recognize the problem, please let me know. If, however, you do know of such potentially helpful settings or other information that I can record or capture and provide to you, please let me know what those are and what are any special steps, settings information, CMD prompt instructions, Event Viewer information, that I need to complete to obtain/generate the information to provide to you.
8. Thank you. I await your response. Steven
Friday, February 26, 2016 4:03 AM | 1 vote
ms-appx-web://microsoft.microsoftedge/assets/errorpages/dnserror.html#file:///Q:/SH%20Shrd%20Fls/TestPDFfile.pdf
resolve the problem of Microsoft Edge not opening PDF files directly from a mapped network drive.
Oops. I just realized that the protocol involved is probably not HTTP so Fiddler won't see it. Otherwise the idea was just to buffer IE from whatever network problems might be causing this scenario. Fiddler tends to be more robust especially in timeout situations.
In fact, I may be being too hasty in dismissing the idea because Fiddler can also do tracing involving the loopback address. I would wonder if the ms-appx-web:// URL might be using that.
In any case, it could not hurt to try. You might see something interesting then. However, in this case you would need to be using Fiddler4 because it has support for that scenario (or at least has it for it in W8.1).
Telerik now owns Fiddler so that is where you would get it.
Alternatively you can use NetMon to get a look at the trace Adam had you do. In fact, you could use NetMon to supplement the trace with the real traffic.
Robert Aldwinckle
Friday, February 26, 2016 9:18 PM | 2 votes
Dear Robert, thank you for your reply.
1. My Uncertainty of Fiddler Benefit and My Challenge - I am confused by your comments. First you say "I just realized that the protocol involved is probably not HTTP so Fiddler won't see it." Then you say "I may be being too hasty in dismissing the idea because Fiddler can also do tracing involving the loopback address." and "In any case, it could not hurt to try. You might see something interesting then." Your second comments leave me believing that you think running Fiddler might help, regardless of your first comment that Fiddler probably "won't see" the problem. As I mentioned in my last post, it is a very big challenge with my limited knowledge and experience for me to learn what I need to learn to change applicable proxy settings and variable values to enable Fiddler to perform as desired, let alone the additional very big challenge for me of understanding the Fiddler-generated/captured technical information and to recognize the problem and its fix.
2. Your Other Fiddler-Related Comments, Other Options? - You say "Fiddler can also do tracing involving the loopback address." and "I would wonder if the ms-appx-web:// URL might be using that." I do not know what a loopback address is or how to determine if one is involved. Nor do I know what to look for to determine if a "ms-appx-web:// URL" is being used other than that we already know that this term appears in the error message presented by Microsoft Edge. I regret your comments are not really helping me or helping me to help you. Is there a way without using Fiddler to determine if a loopback address is involved or if the problem is related to the ms-appx-web:// term in the error message? You also comment "In any case, it could not hurt to try. You might see something interesting then. However, in this case you would need to be using Fiddler4 because it has support for that scenario (or at least has it for it in W8.1)." Me"try"ing Fiddler is a very big challenge, one I have very limited time to try to learn and pursue, particularly if you only think we "might see something interesting then". Is there any other approach to detecting the problem? I can run CMD commands and capture and provide the desired information if you or someone tells me what CMD commands to run and how to capture the desired information. Are there entries that would show up in Windows Event Viewer that I can look for and add to this post? If so, what entries?
3. Which Version of Fiddler? - You comment that I would need to use "Fiddler4 because it has support for that scenario (or at least has it for it in W8.1)" and "Telerik now owns Fiddler so that is where you would get it." So far I am not ready to devote the time/learning needed for me to use Fiddler without knowing that "it has support for that scenario", the (unclear to me) scenario to which you refer. Telerik has a program that they identify as "Fiddler for .NET4, Version 4.6.2.1, Signed EXE" Released on February 22, 2016. For my benefit and the benefit of other post readers, do you mean that program?
4. Network Monitor (NetMon) and Network Analyzer - You comment "Alternatively you can use NetMon to get a look at the trace Adam had you do. In fact, you could use NetMon to supplement the trace with the real traffic." Until you brought my attention to it, I did not know about Microsoft's Network Monitor (NetMon) utility. For other post readers, it is described at
https://support.microsoft.com/en-us/kb/294818
I do not believe this utility is included with Windows 10 Home, probably because it has been superceded as I describe below. NetMon v 3.4 can be downloaded from Microsoft's web site, however, from what I could find online, such as at
some of its features do not function as intended running in Windows 10. I did find a related post that refers to Microsoft's Message Analyzer utility that is described, and can be downloaded at,
https://www.microsoft.com/en-us/download/details.aspx?id=44226
On that utility's webpage, Microsoft says "Microsoft Message Analyzer (v1.3.1) is the current versioned tool for capturing, displaying, and analyzing protocol messaging traffic and other system messages. Message Analyzer also enables you to import, aggregate, and analyze data from log and trace files. It is the successor to Microsoft Network Monitor 3.4 and Message Analyzer v1.3." and that it works with Windows 10. Unfortunately, I find that using Message Analyzer and understanding the information that it captures and presents and then recognizing the cause for why Microsoft Edge won't open a PDF file on a mapped network drive is (like for Fiddler) beyond my existing knowledge and experience.
5. Thank You and What I Can Do - I appreciate the time you spent reviewing my posts and providing your comments. I do not have the prior experience/knowledge needed to use Fiddler or Message Analyzer and, at present, I cannot devote the time (days/weeks?) needed for me to learn how to do so and to understand the captured/presented information. I need to wait to see if a Microsoft representative, you, or another can help in some way besides me learning to properly use Fiddler or Message Analyzer and understanding the information they capture/present. If someone can give me steps to properly use Message Analyzer and provide them with the captured information, I suspect that I can learn to do that. As I mentioned in paragraph 2 above, I can also execute commands in the Windows CMD interface and I can view entries in Event Viewer logs and I can complete actions that require similar knowledge and effort.
Thank you. Steven
Saturday, February 27, 2016 5:40 AM | 1 vote
challenge with my limited knowledge and experience for me to learn what I need to learn to change applicable proxy settings and variable values to enable Fiddler to perform as desired
Actually Fiddler does that for us automatically now. If you need to do any diagnosis of browsing sessions it is well worth your while getting familiar with it.
Is there a way without using Fiddler to determine if a loopback address is involved or if the problem is related to the ms-appx-web:// term in the error message?
I don't know. I first saw it with W8. Fiddler provides a much simpler method than the provided utility. I don't even know if that thing still exists... CheckNetIsolation.exe it's still there.
Telerik has a program that they identify as "Fiddler for .NET4, Version 4.6.2.1, Signed EXE" Released on February 22, 2016. For my benefit and the benefit of other post readers, do you mean that program?
Apparently. It is easy to get behind though. It gets updated frequently but is usually very easy to update once installed.
need to wait to see if a Microsoft representative, you, or another can help in some way besides me learning to properly use Fiddler or Message Analyzer and understanding the information they capture/present.
If I can figure out how to simulate your symptom I can try doing the tests which will answer these questions. No promises.
Robert Aldwinckle
Monday, February 29, 2016 10:10 PM | 1 vote
Today I completed the above actions you described in (a) – (e), however, to be able to navigate to the PDF file on the network drive, as you requested in step (d), I had to first remap the network drive
Why? I don't think that is what was being asked. Can you open the file without mapping it to a drive letter?
Also, I found out that the symptom description is too vague to know what to do even then to open the .pdf. E.g. opening it from File Explorer would be one thing but opening it from Edge would be significantly different. For one thing it appears that BING may get into the act and possibly have difficulty parsing the requested file:// URL.
So, if you can open the .pdf by remotely addressing it from the File Explorer Address bar instead of using a drive letter that might act as a workaround for whatever it is that you are trying to do but having difficulty with. A surprise for me is that Fiddler then detects nothing happening on Edge but otherwise it does get involved at least with traffic to BING .
Robert Aldwinckle
Monday, February 29, 2016 10:28 PM | 1 vote
Fiddler is when troubleshooting HTTP/HTTPS protocol. Since the symptom comes when attempting to access the .pdf using explorer (either mapped drive or browsing directly to \share\folder) and attempt to open with using edge as the default application, it still is using SMB over TCP 445 which is why Fiddler does not pick up anything.
Adam Rudell | Windows Networking Beta | Microsoft Corporation
Tuesday, March 1, 2016 12:36 AM | 1 vote
ms-appx-web://microsoft.microsoftedge/assets/errorpages/dnserror.html#file:///Q:/SH%20Shrd%20Fls/TestPDFfile.pdf
why Fiddler does not pick up anything.
What about the symptom message? If it flows over the local loopback and you are using Fiddler's Loopback exemption for Edge what protocol is involved then?
Also there is at least one mention in this thread about using the browser to make the request and as I indicated when I tried doing that BING got involved.
Robert Aldwinckle
Wednesday, March 2, 2016 7:49 PM | 1 vote
Robert,
I really appreciate the time you have taken to help me with this problem. I am hoping you (or another) can help me learn how to try some actions you suggested in your February 29 comment to me.
1. Open File Without Remapping Network Drive - You suggested:
Why? I don't think that [my mapping the shared network folder as a drive while I completed Adam's requested steps] **is what was being asked. Can you open the file without mapping it to a drive letter? **
and you suggested
So, if you can open the .pdf by remotely addressing it from the File Explorer Address bar instead of using a drive letter that might act as a workaround for whatever it is that you are trying to do but having difficulty with.
I do not know how to use Windows File Explorer to get to the file to select it to open it without first mapping the network shared folder as a drive. If there is a way, please let me know how to do it.
2. Opening File From Edge - You suggested:
Also, I found out that the symptom description is too vague to know what to do even then to open the .pdf. E.g. opening it from File Explorer would be one thing but opening it from Edge would be significantly different. For one thing it appears that BING may get into the act and possibly have difficulty parsing the requested file:// URL.
I do not know how to directly instruct Microsoft Edge to open the file, either while the shared network folder is mapped as a drive or while the shared network folder is not mapped as a drive. I tried entering the value \169.254.100.100\SH Shrd Fls\TestPDFfile.pdf" in the search box in Microsoft Edge, however, Microsoft Edge presents the error message that I provide below. Can you (or anyone) tell me how to get Microsoft Edge to directly open a pdf file from a shared network folder that is or is not mapped as a drive?
Hmm, we can't reach this page.
Try this
- <id id="dnserror_unavailable_righturl">Make sure you’ve got the right web address:</id> ms-appx-web://microsoft.microsoftedge/assets/errorpages/dnserror.html#file://169.254.100.100/SH%20Shrd%20Fls/TestPDFfile.pdf
Any further comments that you provide on how to complete the actions you suggested to me would be greatly appreciated. Thank you. Steven
Wednesday, March 2, 2016 8:09 PM | 1 vote
Adam, thank you for continuing to monitor this problem. After reviewing your February 29 comments, I get the impression that you believe using Fiddler will not likely help me/us to diagnose the problem that I am experiencing. If my impression is incorrect, please clarify for me.
You comment "Since the symptom comes when attempting to access the .pdf using explorer (either mapped drive or browsing directly to \share\folder) and attempt to open with using edge as the default application, it still is using SMB over TCP 445 which is why Fiddler does not pick up anything."
I do not know what SMB or TCP 445 is (I am not an IT or network professional). If there is something I can check about my computer or Ethernet-connected NAS to determine or confirm if SMB or TCP 445 is involved and working or not working properly, please let me know and I would be happy (and eager) to do so.
You mention the possibility of me "browsing directly to \share\folder". I tried entering the value "\169.254.100.100\SH Shrd Fls\TestPDFfile.pdf" in the search box in Microsoft Edge but Microsoft Edge presents the same error message:
Hmm, we can't reach this page.
Try this
- <id id="dnserror_unavailable_righturl">Make sure you’ve got the right web address:</id> ms-appx-web://microsoft.microsoftedge/assets/errorpages/dnserror.html#file://169.254.100.100/SH%20Shrd%20Fls/TestPDFfile.pdf
How do I browse to a file from within Microsoft Edge?
For some reason, when I copy the error message from the Edge window and paste it into my forum posts, the pasted text (like above) includes the entries <id id="dnserror_unavailable_righturl"> and </id> that do not appear in the text that is shown to me by Microsoft Edge. I don't know if these <> terms are helpful or important but if they are, I hope you can recognize how they are and can tell me what they indicate and what I should do next to pursue resolving this problem. Thank you. Steven
Wednesday, March 2, 2016 11:42 PM | 1 vote
I do not know how to use Windows File Explorer to get to the file to select it to open it without first mapping the network shared folder as a drive. If there is a way, please let me know how to do it.
Just by adding the user account in the front after adding two backslashes. Can your NAS do that or does it have to use a drive letter identification?
I tried entering the value \169.254.100.100\SH Shrd Fls\TestPDFfile.pdf" in the search box in Microsoft Edge, however, Microsoft Edge presents the error message that I provide below.
Yes. Me too. The same syntax works from a File Explorer Address bar (Win-E, Alt-d) and opens the document in Edge. That's why I'm thinking it could be a symptom of incorrectly parsing a strange "URL" which would then get passed to BING but if BING had a better parser it might think that it was fine. Etc. Who knows? That's why I am suggesting tracing but not having much luck figuring out where to do it.
The only other idea I have is to use the Developer Tools to make it do the parsing and bypass the Edge Address bar/Search box parser that way but I would have to figure out the right syntax for doing that in there first.
Robert Aldwinckle
Thursday, March 3, 2016 5:44 AM
The only other idea I have is to use the Developer Tools to make it do the parsing and bypass the Edge Address bar/Search box parser that way but I would have to figure out the right syntax for doing that in there first.
In fact, I have found the "right syntax". Now the problem is security/obscurity. I keep getting "Permission denied" when I try to use window.location(file://169.254.100.100/SH Shrd Fls/TestPDFfile.pdf); (to use your example in my template) in Edge's Console tab. Same symptom in IE except there the message is "Access is denied". I am trying to use About:Blank to switch from and I have added it to Local Intranet Sites list. Maybe it would help to have a real Intranet page to switch from. Who knows? I may try tracing this with ProcMon to see if I can get any insight on the security/obscurity issue that is blocking this tack.
Robert Aldwinckle
Thursday, March 3, 2016 4:56 PM | 1 vote
I have been looking into this more, and inside the Edge Dev Tools console I get the following 2 errors each time I refresh the page with the file:// url loaded:
DOM7011: The code on this page disabled back and forward caching. For more information, see: http://go.microsoft.com/fwlink/?LinkID=291337
SEC7117: Network request to (changed to generic naming) did not succeed.
This Internet Explorer instance does not have the following capabilities: privateNetworkClientServer
Thursday, March 3, 2016 8:26 PM | 1 vote
Hi,
<quote>
SEC7117: Network request to (changed to generic naming) did not succeed.
This Internet Explorer instance does not have the following capabilities: privateNetworkClientServer
</quote>
The last time I've seen this message, it was due to IE11 Enhanced Protected Mode and it seems that AppContainer technology is activated by default on Edge.
Link: https://blogs.windows.com/msedgedev/2015/05/11/microsoft-edge-building-a-safer-browser/
App Container Sandbox by Default
IE7 on Windows Vista was the first web browser to provide a browsing sandbox, called protected mode, where the part of the browser that renders the web content runs with less privilege than the browser controls (e.g. the back button) and the user do. This provides the user with a level of protection should a malicious web site exploit a bug in the browser or one of its plugins, in that the attacker is now stuck inside the sandbox and does not have full access to all of the user’s resources.
IE7’s protected mode was built on Vista’s mandatory integrity control, which provides a degree of protection, but is limited. IE10 introduced EPM (Enhanced Protected Mode) based on Windows 8’s app container sandbox. EPM provided a much stronger sandbox than protected mode, including for example deny-by-default and no-read-up semantics. EPM was on by default in the immersive browser, but was only an option on the desktop in IE10 and IE11 because some browser extensions are not compatible with EPM.
Microsoft Edge is rebooting our browser extension model, allowing it to run its content processes in app containers, not just as a default, but all the time. Thus every Internet page that Microsoft Edge visits will be rendered inside an app container, the latest and most secure client-side app sandbox in Windows.
Your problem may be caused by the IP address you are using with your NAS.
169.x.x.x is not a Private Internet Address defined in RFC 1918.
Can you try to change the IP address or add a second that respect the RFC?
Should be something defined in these ranges: 10.0.0.0/8, 172.16.0.0/16 or 192.168.0.0/24
Gerald
Edit: Just tested... Not an IP problem... Doesn't work with LAN IP too :-(
Thursday, March 3, 2016 10:53 PM | 1 vote
Edit: Just tested... Not an IP problem... Doesn't work with LAN IP too :-(
Do you have a real Intranet page which you could test my window.location() override on? ; )
I know. Let's try two different .pdf files from the same location. Open the first one using File Explorer. Then use Developer Tools to try to open the second one. What can go wrong? <eg>
Robert Aldwinckle
Friday, March 4, 2016 10:50 AM | 3 votes
Hi,
Just fixed the problem in my quick lab by adding the location in Internet Explorer's Local Intranet sites.
Without this, I get an error in Edge. After adding this then restarted Edge, I can open the PDF on my network share.
Have you tried that?
Friday, March 4, 2016 3:06 PM | 1 vote
adding the location in Internet Explorer's Local Intranet sites.
[file://192.168...]
The address is supposed to be implicitly Intranet. So this must be saying it is necessary to specify that the file:// protocol is OK in that zone?
But I still get Permission denied when trying to use my DT override. ; ]
Robert Aldwinckle
Friday, March 4, 2016 3:16 PM | 1 vote
Hi,
Just fixed the problem in my quick lab by adding the location in Internet Explorer's Local Intranet sites.
Without this, I get an error in Edge. After adding this then restarted Edge, I can open the PDF on my network share.Have you tried that?
Even if this in theory did work, we have thousands of servers in our environment around the world. Adding allowances to file servers inside the LAN should not have to have specific permission to open within Edge.
To another reply, if I open in File Explorer, Edge opens and the error comes up. If I open with Dev Tools up with Edge, same result occurs.
If I load Adobe Reader or Acrobat, the file loads perfectly fine.
Friday, March 4, 2016 3:33 PM | 1 vote
Probably because Adobe reader is not a browser. That's why you never add this problem before.
Edge is a new Microsoft Browser that relies on these kind of settings.
Also, having the AppContainer technology activated by default requires some configuration.
Anyway, I just gives some results I've made in a lab, this needs to be confirmed.
Just test it to see if it works, see I you can tune my idea for your infra and if needed, report the problem to Microsoft.
Actually, I don't have this problem with my client and nothing was changed to the Internet Explorer settings but they rely on EPM since Windows 7, even if this OS doesn't have the AppContainer Technology. It is when I implemented the first Windows 10 clients that we found the side effects of EPM with AppContainers.
Gerald
Friday, March 4, 2016 3:59 PM | 1 vote
if I open in File Explorer, Edge opens and the error comes up.
That seems to be different from everyone else who is responding to you in this thread. So, again, I would try tracing with ProcMon (since it is what I know best). It would be best to have two traces to compare for their significant differences, one working and your failure case. I'll try to remember to trace my two cases too to try to help you have useful filters. Note that with ProcMon the more other tracing you are doing at the same time the better because then the write event of each other trace record would be captured in the ProcMon trace, including the series of events which would have caused it. For example, you could be running the trace that Adam requested and see how its write events correlate with the rest. I could try doing that too. No promises.
Robert Aldwinckle
Monday, March 7, 2016 3:07 AM | 1 vote
Dear Gerald, and all other contributors,
1. Gerald's Solution (workaround) Worked for me - I really appreciate everyone's help with this. I regret I do not understand a lot of the technical stuff discussed in this forum post. However, Gerald's March 4, 2016 suggestion solved the problem for me. Specifically, both PDF files and XML files successfully opened in Microsoft Edge by selecting the PDF or XML file (in Windows File Explorer) at its location on the shared network folder that I had mapped as a drive after I changed the security settings in Internet Explorer as Gerald summarized. On my system, Microsoft Edge is set as the default application to open PDF and XML file types. For readers that might benefit, I describe in paragraphs 3 and 4 below in more detail the changes in Internet Explorer's settings that Gerald describes. I have no idea why changing these settings in Internet Explorer solves the present problem for Microsoft Edge or why there are (as far as I could find) no similar security settings change options in Microsoft Edge. I do not know of any location in Windows Settings where these same changes can be made. If someone knows, please identify where they are.
2. Setup & Software Versions - For the record, my network accessible server (NAS) is connected directly to my notebook computer via an Ethernet cable (not WiFi). My computer is running Windows 10 Home version 1511, OS Build 105.86.122. Microsoft Edge is version 25.10586.00 and Internet Explorer 11 is version 11.103.10586.0. I have mapped the shared network folder on my NAS as drive Q.
3. Settings Changes In Internet Explorer - I added this location as a "website" to be included in the "Local Intranet" "Zone" in Internet Explorer by following the IE menu/options path identified below.
Tools>Internet Options>Security>Local Intranet>Sites>Advanced
4. Changes In (final) Local Intranet Dialog Box - Upon clicking on the "Advanced" button, another (final) "Local Intranet" dialog box opens up that contains a text entry box for the user to enter the "website" to be included in the Local Intranet "zone". Gerald's post shows this dialog box. The text entry box is prefilled with the address for the current page being displayed by Internet Explorer. Delete this prefilled address and type in the three characters [drive letter]:\ for the drive to which the shared network folder is mapped. In my case, the three characters I entered were Q:\ After entering the drive information, click on the [Add] button and the associated location is added to the list of "websites" in the so-labeled box that also appears in this same "Local Intranet" dialog box. For my setup and shared network folder mapped as a drive, the associated location appeared as file://169.254.100.100 in this "websites" box. I would expect a similar location description format for another person's shared network folders mapped as a drive on their Local Intranet.
5. Changed Settings Immediately Solved Problem - Until I added my mapped drive as a "website" in Internet Explorer settings as I describe above, attempting to open in Microsoft Edge a PDF file (or XML file) located on my shared network folder always prompted Microsoft Edge to present the error message below.
Hmm, we can't reach this page.
Try this
•<id id="dnserror_unavailable_righturl">Make sure you’ve got the right web address:</id> ms-appx-web://microsoft.microsoftedge/assets/errorpages/dnserror.html#file://169.254.100.100/SH%20Shrd%20Fls/TestPDFfile.pdf
Immediately after adding my mapped drive as describe above, and after restarting Microsoft Edge, all PDF (and XML) files located on my shared network folder opened successfully in Microsoft Edge with no error. No restarting of Internet Explorer or Microsoft Edge was required.
6. Solution Is A Workaround And Not Always Viable - As Onatum stated in his March 4, 2016 comments on this solution that Gerald found/described, "Even if this in theory did work, we have thousands of servers in our environment around the world. Adding allowances to file servers inside the LAN should not have to have specific permission to open within Edge." I agree with Onatum. One should not have to add each file server on a Local Intranet (LAN) to this list of included "websites" in Internet Explorer to get the files to open successfully in Microsoft Edge. I hope Microsoft continues to sort out this problem and devise a fix that does not require users to complete these steps. Since I have only one file server, this workaround works okay for me for now and might be a similar useful workaround for others.
7. Thank you - Again, thank you to all who worked on this problem, reviewed my comments and others and made suggestions. Steven
Tuesday, June 14, 2016 1:36 PM | 1 vote
The PG has made several adjustments in this code path area as of late and they believe they may have fixed this issue.
Is anyone able to encounter this scenario when running the latest windows insider preview builds? If so, please reach out to me directly at arudell at Microsoft dot com.
Adam Rudell | Windows Networking Beta | Microsoft Corporation
Tuesday, June 14, 2016 8:07 PM
Is anyone able to encounter this scenario when running the latest windows insider preview builds?
It may be sufficiently better--once you have negotiated all the necessary security/obscurity hoops and obstacles. The window.location() workaround is still getting Permission denied.
Robert Aldwinckle
Saturday, November 5, 2016 7:47 AM
I found a workable solution for the main problem of not able to open PDF files from a network location on Microsoft Edge.
It worked for me...
Here's the link...
https://scriptimus.wordpress.com/2016/08/22/unable-to-open-pdf-in-edge/
Friday, April 21, 2017 7:57 AM
Did the trick for me!
Thank you for sharing
Saturday, May 11, 2019 3:50 PM
You need to turn on network sharing in order for edge to open pdf on a network.
Wednesday, June 19, 2019 10:54 PM
Deosn't it drive you crazy that edge keeps on hijacking pdf's and htm/html files, but still can't open them from a share!!
Ron Kirschner
Thursday, June 20, 2019 10:04 AM
Dear Ron, it does work when configured and is normal behaviour (from a security point of view) that is doesn't out of the box. All you have to do is add your network location to your trusted intranet sites as Jonas74 mentioned , see following picture:
Thursday, June 20, 2019 12:22 PM
I will try that but what I would really like is for Edge to stop changing my file access defaults without approval!
Ron Kirschner
Tuesday, July 2, 2019 2:52 PM
I wanted to alert others that my solution to the problem was solved by accessing the network share or mapped drive by server name. If I access the share by IP address I get the IE Pdf error.
Friday, July 19, 2019 6:03 PM
Hi, The workaround I figured is to reduce the size of a PDF.
I simply use Adobe Acrobat Pro, to open a PDF, from File menu,
select Save As Other..., from drop-down list,
select Reduced Size PDF...
Give a new file a name and press OK.
in few minutes, you can open PDFs on Microsoft Edge.
spa909
Monday, November 25, 2019 1:30 PM
Thank you so much!! :) working 100%
Monday, November 25, 2019 2:38 PM
**pleasure **
spa909