ChatterBank1 min ago
Cookies
6 Answers
Ok I'm tearing my hair out here so hope someone has a suggestion.
My woman needs to open a .mht file in order to log into her work account. It used to work fine, defaulting to opening in IE. Then for reasons unknown this suddenly started to fail with the obviously ludicrous message that cookies needed to be turned on for it to work. Since no one had changed anything and cookies are not a problem when surfing, this was, and still is, a mystery.
We managed to work round the erroneous error by opening the file in Chrome. That worked for a while. However now, again inexplicably, it too has started to pretend cookies are disabled and need to be enabled.
As I write I realise I've not scanned for virus or malware at the moment. I'll kick off a scan or two once I've posted, but I have little confidence that will find anything significant.
Does anyone know how to fix this browser error that is so insistent that cookies are disabled, when they work fine for the website visited ?
Thanks.
My woman needs to open a .mht file in order to log into her work account. It used to work fine, defaulting to opening in IE. Then for reasons unknown this suddenly started to fail with the obviously ludicrous message that cookies needed to be turned on for it to work. Since no one had changed anything and cookies are not a problem when surfing, this was, and still is, a mystery.
We managed to work round the erroneous error by opening the file in Chrome. That worked for a while. However now, again inexplicably, it too has started to pretend cookies are disabled and need to be enabled.
As I write I realise I've not scanned for virus or malware at the moment. I'll kick off a scan or two once I've posted, but I have little confidence that will find anything significant.
Does anyone know how to fix this browser error that is so insistent that cookies are disabled, when they work fine for the website visited ?
Thanks.
Answers
The error message is coming from the remote Outlook Web App service. Possibly try positively allowing cookies for the target website. The address will probably be an address of the format http:// mail. company. com or https:// mail. company. com . http:// windows. microsoft. com/ en- gb/ windows7/ block- enable- or- allow- cookies Though I don't recall...
00:11 Sun 01st Sep 2013
Standard refusal to work in either IE or now Chrome is :
Please enable cookies for this Web site.
Cookies are currently disabled by your browser. Outlook Web App requires that cookies be enabled.
For information about how to enable cookies, see the Help for your Web browser.
I have used earlier advice from TTG re Firefox, for use on my PC, to create a work-around here for now. But I really need to solve the root cause if I can.
Thanks.
Please enable cookies for this Web site.
Cookies are currently disabled by your browser. Outlook Web App requires that cookies be enabled.
For information about how to enable cookies, see the Help for your Web browser.
I have used earlier advice from TTG re Firefox, for use on my PC, to create a work-around here for now. But I really need to solve the root cause if I can.
Thanks.
-- answer removed --
Thanks for that methyl. Bit of a surprise it wasn't a local warning. One lives and learns.
Biggest problem I had is whilst I feel reasonably confident of solving common PC issues, OWA is a complete mystery to me. I think I'll advise her to tell her IT department that she has had issues. See if they have suggestions. Meanwhile I'll bear the V9 suggestion in mind but see what transpires when she tells IT first.
Cheers again.
Biggest problem I had is whilst I feel reasonably confident of solving common PC issues, OWA is a complete mystery to me. I think I'll advise her to tell her IT department that she has had issues. See if they have suggestions. Meanwhile I'll bear the V9 suggestion in mind but see what transpires when she tells IT first.
Cheers again.
BTW the site address was not easy to spot (the one shown in the address bar for the error message was weird and not in the format you suggested (did not even start http)) but the one displayed when we actually get in, looked plausible. But allowing it didn't work unfortunately.