If the 9.0 subkey does not exist, you will need to create it and the subsequent Common, Internet, and ForceShellExecute subkeys. To test if this is the root cause, find/change the value or create the registry key using these steps (which are from Error message when selecting hyperlink in Office: "Cannot locate the Internet server or proxy server":Īll versions of Office require that the ForceShellExecute key be located under the 9.0 registry subkey. If the ForceShellExecute registry key is set to 0 or not present, it is likely the reason Word does not wish to process the API-rendered PDF. When set to 1, Office will use the Windows process (basically the same as if the user opened the link via Start | Run | paste link | Enter). When the key is set to 0 (or is not present) Office applications use an internal Office process to launch hyperlinks.
#POWERPOINT FOR MAC CANNOT LOCATE THE INTERNET SERVER OR PROXY SERVER HYPERLINK ERROR PDF#
You may be able to change the rendering of the PDF in some way to work better with Word, but I believe the issue may stem from the ForceShellExecute registry key that controls how Office processes hyperlinks. Windows: Windows 10 Enterprise 64 bit Version 1903 (OS build 18362.476).Office: Microsoft Word for Office 365 MSO (0.20232) 32-bit.Word version does not seem to be an issue - tried 2010 through Office 365 ProPlus.ĮDIT: The reason I think it's related to the above code is because an actual PDF file from the same website can be linked from Word and Word will simply display an "unsafe content" warning but still allow you to open it, unlike the PDF from API. The PDF opens with no issue in browsers (IE/Edge/FF/Chrome - mobile or desktop).
= new MediaTypeHeaderValue("application/pdf") Result.Content = new StreamContent(stream) If a user copies a PDF link from the website into Word, Word does not open the file and displays "Cannot open the specified file" error HttpResponseMessage result = new HttpResponseMessage()
The action renders the PDF correctly in browsers.Įverything is working fine, except for an issue that we came across today. We have the following snippet in a Web API action than handles PDF requests.
0 kommentar(er)
