X
Tap here to go to the mobile version of the site.

Support Forum

"The address wasn't understood"

Posted

Sharepoint offers links of the form ms-word:ofe|u|https://somebusinessname.sharepoint.com/sites/somesitename/somefilename.docx and firefox responds with the subject error message and cannot open the file in MS Word. IE, Edge and Chrome all behave correctly for this same sharepoint link on the same machine.

Sharepoint offers links of the form ms-word:ofe|u|https://somebusinessname.sharepoint.com/sites/somesitename/somefilename.docx and firefox responds with the subject error message and cannot open the file in MS Word. IE, Edge and Chrome all behave correctly for this same sharepoint link on the same machine.
Attached screenshots
Quote

Additional System Details

Installed Plug-ins

noscript

Application

  • User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

More Information

FredMcD
  • Top 10 Contributor
4269 solutions 59846 answers

https://somebusinessname.sharepoint.com/sites/somesitename/somefilename.docx

I get: Server not found

Note: Everything before ' https ' is not understood as part of a weblink.

https://somebusinessname.sharepoint.com/sites/somesitename/somefilename.docx I get: Server not found Note: Everything before ' https ' is not understood as part of a weblink.
Was this helpful to you? 0
Quote
FredMcD
  • Top 10 Contributor
4269 solutions 59846 answers
sharepoint.com takes me to https://products.office.com/en-us/sharepoint/collaboration?ms.officeurl=sharepoint&rtc=1 http://somebusinessname.sharepoint.com/ gives me Server not found
Was this helpful to you?
Quote

Question owner

Respectfully, of course the server is not found! I removed the stuff that identifies our sharepoint site, ie I generalized the link. The exact same link (with the actual server name and filename) works fine on IE, Edge and Chrome, but not on FF.

Respectfully, '''of course''' the server is not found! I removed the stuff that identifies our sharepoint site, ie I generalized the link. The exact same link (with the actual server name and filename) works fine on IE, Edge and Chrome, but not on FF.
Was this helpful to you?
Quote
jscher2000
  • Top 10 Contributor
8789 solutions 71880 answers

Hi alabamatoy, I don't know if I have any links like that to test on.

Firefox comes with certain preference for novel protocols (the part to the left of the :// in a URL). For example:

network.protocol-handler.external.ms-windows-store

You could try creating a new preference for ms-word and see whether that helps. Here's how:

(0) Select (triple-click is fastest) and copy this new preference name

network.protocol-handler.external.ms-word

(1) In a new tab, type about:config in the address bar and press Enter/Return. Click the button accepting the risk.

(2) In the search box above the list, type or paste ms- and pause while the list is filtered

(3) Right-click a blank area of the page, click New, then click Boolean

(4) In the dialog that pops up, paste the new preference name, then click OK, then select true, then click OK

network.protocol-handler.external.ms-word should now appear in the list bolded with a value of true.

Does Firefox handle the links any better now?

Hi alabamatoy, I don't know if I have any links like that to test on. Firefox comes with certain preference for novel protocols (the part to the left of the :// in a URL). For example: network.protocol-handler.external.'''ms-windows-store''' You could try creating a new preference for '''ms-word''' and see whether that helps. Here's how: (0) Select (triple-click is fastest) and copy this new preference name network.protocol-handler.external.'''ms-word''' (1) In a new tab, type '''about:config''' in the address bar and press Enter/Return. Click the button accepting the risk. (2) In the search box above the list, type or paste '''ms-''' and pause while the list is filtered (3) Right-click a blank area of the page, click New, then click Boolean (4) In the dialog that pops up, paste the new preference name, then click OK, then select true, then click OK network.protocol-handler.external.ms-word should now appear in the list bolded with a value of true. Does Firefox handle the links any better now?
Was this helpful to you? 1
Quote

Question owner

This fixed the problem. I expect to have to replicate this for the other Micro$oft products since they work same way. Thanks!

This fixed the problem. I expect to have to replicate this for the other Micro$oft products since they work same way. Thanks!
Was this helpful to you?
Quote
Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.