X
Tryk her for at gå til webstedets mobilversion.

Supportforum

since upgrade to v. 13 Yahoo mail keeps getting "your session has expired"

Skrevet

Firefox automatic upgrade to ver. 13 today. now every 15 - 20 minutes my yahoo mail keeps popping up the message "Sorry, your session has expired. To protect your account, you need to confirm you account periodically. This only happens in FF ver. 13, IE & Chrome are fine

Firefox automatic upgrade to ver. 13 today. now every 15 - 20 minutes my yahoo mail keeps popping up the message "Sorry, your session has expired. To protect your account, you need to confirm you account periodically. This only happens in FF ver. 13, IE & Chrome are fine

Valgt løsning

Create a new profile as a test to check if your current profile is causing the problems.

See "Basic Troubleshooting: Make a new profile":

There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins" in case there are still problems.

If the new profile works then you can transfer some files from the old profile to that new profile, but be careful not to copy corrupted files.

See:


EDIT: See also this post on page two of this thread:

Læs dette svar i sammenhæng 4

Yderligere systemdetaljer

Det begyndte da...

FF was upgraded to Ver 13

Program

  • User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Win64; x64; Trident/5.0; .NET CLR 2.0.50727; SLCC2; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; InfoPath.3; .NET4.0C; .NET4.0E; Tablet PC 2.0)

Yderligere information

Luk
ideato 893 løsninger 6250 svar
See if this is helpful : http://help.yahoo.com/l/us/yahoo/mail/yahoomail/technical/settings-19.html thank you

Spørgsmålsstiller

Thanks for you help. Unfortunately that link does not apply to my situation. Up until FireFox upgraded me to Version 13, Yahoo Mail worked fine. None of my settings were changed during the upgrade to Ver. 13 and Yahoo mail works fine in IE 9 & chrome. Something in FF is making Yahoo Mail think that I have been logged in for more that 2 weeks every 15-20 minutes.

Thanks for you help. Unfortunately that link does not apply to my situation. Up until FireFox upgraded me to Version 13, Yahoo Mail worked fine. None of my settings were changed during the upgrade to Ver. 13 and Yahoo mail works fine in IE 9 & chrome. Something in FF is making Yahoo Mail think that I have been logged in for more that 2 weeks every 15-20 minutes.
cor-el
  • Top 10 Contributor
  • Moderator
17578 løsninger 158993 svar

Try to clear the (Yahoo!) cookies.

Clear the cache and the cookies from sites that cause problems.

"Clear the Cache":

  • Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now"

"Remove Cookies" from sites causing problems:

  • Tools > Options > Privacy > Cookies: "Show Cookies"

Start Firefox in Troubleshoot Firefox issues using Safe Mode to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance/Themes).


Also make sure that you do not have security software that is modifying cookies.

Try to clear the (Yahoo!) cookies. Clear the cache and the cookies from sites that cause problems. "Clear the Cache": *Tools > Options > Advanced > Network > Offline Storage (Cache): "Clear Now" "Remove Cookies" from sites causing problems: *Tools > Options > Privacy > Cookies: "Show Cookies" Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance/Themes). *Don't make any changes on the Safe mode start window. *https://support.mozilla.org/kb/Safe+Mode *https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes ---- Also make sure that you do not have security software that is modifying cookies.

Spørgsmålsstiller

Thank you cor-el for your assistance. I had already gone through these steps on my own, then with yahoo and then I tried again with your steps as they were a little different. Unfurtunately nothing has worked. I have gone back to Ver. 12 and the probelm has gone away, so it is definetly something with ver. 13 and as I stated, Yahoo mail (classic) works fine in IE 9 and chrome. Thanks Again

Thank you cor-el for your assistance. I had already gone through these steps on my own, then with yahoo and then I tried again with your steps as they were a little different. Unfurtunately nothing has worked. I have gone back to Ver. 12 and the probelm has gone away, so it is definetly something with ver. 13 and as I stated, Yahoo mail (classic) works fine in IE 9 and chrome. Thanks Again
cor-el
  • Top 10 Contributor
  • Moderator
17578 løsninger 158993 svar

Valgt løsning

Create a new profile as a test to check if your current profile is causing the problems.

See "Basic Troubleshooting: Make a new profile":

There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins" in case there are still problems.

If the new profile works then you can transfer some files from the old profile to that new profile, but be careful not to copy corrupted files.

See:


EDIT: See also this post on page two of this thread:

Create a new profile as a test to check if your current profile is causing the problems. See "Basic Troubleshooting: Make a new profile": *https://support.mozilla.org/kb/Basic+Troubleshooting#w_8-make-a-new-profile There may be extensions and plugins installed by default in a new profile, so check that in "Tools > Add-ons > Extensions & Plugins" in case there are still problems. If the new profile works then you can transfer some files from the old profile to that new profile, but be careful not to copy corrupted files. See: *http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox ---- EDIT: See also this post on page two of this thread: * [[/questions/928922?page=2#answer-344319]]

Ændret af cor-el den

Spørgsmålsstiller

Cor-el - That hit the proverbial nail on the Head. Thanks sooooo much.

I wanted to wait to make sure the problem was resolved before getting back to you. Yahoo mail has been active now for 12 hours and no messages!!! Yeah!!!!

Thanks again :)

Cor-el - That hit the proverbial nail on the Head. Thanks sooooo much. I wanted to wait to make sure the problem was resolved before getting back to you. Yahoo mail has been active now for 12 hours and no messages!!! Yeah!!!! Thanks again :)
aabill 0 løsninger 1 svar

I had exactly the same problem, and can confirm that the above fix does work, but I kept a copy of the corrupt installation to try to find the minimum action needed to fix the problem. I found that simply deleting sessionstore.js was enough, and of course avoids losing stored passwords, preferences, etc. Hopefully might work for others.

I had exactly the same problem, and can confirm that the above fix does work, but I kept a copy of the corrupt installation to try to find the minimum action needed to fix the problem. I found that simply deleting sessionstore.js was enough, and of course avoids losing stored passwords, preferences, etc. Hopefully might work for others.
cor-el
  • Top 10 Contributor
  • Moderator
17578 løsninger 158993 svar

If you restore windows from the previous session then it may have been caused by cookies that Firefox stores as part of the session data.

If you see this error often then you can try to disable storing cookies as session data.

Set the browser.sessionstore.privacy_level pref to 2 (never) or 1 (non-HTTPS, default in Firefox 3 versions) on the about:config page to disable saving cookies via session restore.
You can change the browser.sessionstore.privacy_level_deferred pref that is used when you do not reopen the previous session automatically via "Show my windows and tabs from last time".

If you restore windows from the previous session then it may have been caused by cookies that Firefox stores as part of the session data. If you see this error often then you can try to disable storing cookies as session data. Set the <b>browser.sessionstore.privacy_level</b> pref to 2 (never) or 1 (non-HTTPS, default in Firefox 3 versions) on the <b>about:config</b> page to disable saving cookies via session restore.<br /> You can change the browser.sessionstore.privacy_level_deferred pref that is used when you do not reopen the previous session automatically via "Show my windows and tabs from last time". * http://kb.mozillazine.org/browser.sessionstore.privacy_level *http://kb.mozillazine.org/about:config
lanefree 0 løsninger 9 svar

Nyttigt svar

Posted as solved but I do not think so. More than 28 people have this issue but this forum is hard to find and I contacted yahoo and they do not seem interested. Mozilla your upgrade needs a fix.

Posted as solved but I do not think so. More than 28 people have this issue but this forum is hard to find and I contacted yahoo and they do not seem interested. Mozilla your upgrade needs a fix.

Ændret af lanefree den

cor-el
  • Top 10 Contributor
  • Moderator
17578 løsninger 158993 svar

As a first step you can try to reset Firefox.

As a first step you can try to reset Firefox. *https://support.mozilla.org/kb/reset-firefox-easily-fix-most-problems
tsiegman 0 løsninger 2 svar

Asbill, I deleted sessionstore.js but no love. Any other suggestions before I do the whole profile dance?

Asbill, I deleted sessionstore.js but no love. Any other suggestions before I do the whole profile dance?

Ændret af tsiegman den

robijf 0 løsninger 1 svar

Hi everyone!

I had pretty much the same problem up until I disabled ALL Microsoft plugins, and the problem stopped.

It's worth trying (I disabled them all at once, then enabled those that I need most).

Hi everyone! I had pretty much the same problem up until I disabled ALL Microsoft plugins, and the problem stopped. It's worth trying (I disabled them all at once, then enabled those that I need most).
lanefree 0 løsninger 9 svar

Thank You Cor-el I see you have been very active and I appreciate your efforts. I wish mozilla would exert a fraction of your effort and send a patch to the more than fifty people with this issue. I have had to create a new profile in the past, and it was a mess. I lost a great deal of data and I want mozilla developers to do the work and create a patch or a working update.

Thank You Cor-el I see you have been very active and I appreciate your efforts. I wish mozilla would exert a fraction of your effort and send a patch to the more than fifty people with this issue. I have had to create a new profile in the past, and it was a mess. I lost a great deal of data and I want mozilla developers to do the work and create a patch or a working update.
jazzwineman 0 løsninger 23 svar

Please stop wasting time with creating new profiles and deleting this and that and so forth. I am an MCSE and spent a few minutes with it and said- why waste the time. Nothing is wrong on your side, there is no corruption of plug-ins or extension. It is a problem that Mozilla needs to figure out and just go back to 12 and wait until they fix. You do not need to be their tester in the field and this is like Microsoft junk that they put out to get fixed in the field instead f testing properly. Given time, they will figure it out. I probably know the answer, but am not a programmer for Mozilla and they can take care of their business, but for your own users sake- go back to 12 and stop wasting unnecessary time.

Please stop wasting time with creating new profiles and deleting this and that and so forth. I am an MCSE and spent a few minutes with it and said- why waste the time. Nothing is wrong on your side, there is no corruption of plug-ins or extension. It is a problem that Mozilla needs to figure out and just go back to 12 and wait until they fix. You do not need to be their tester in the field and this is like Microsoft junk that they put out to get fixed in the field instead f testing properly. Given time, they will figure it out. I probably know the answer, but am not a programmer for Mozilla and they can take care of their business, but for your own users sake- go back to 12 and stop wasting unnecessary time.
tsiegman 0 løsninger 2 svar

I finally resolved this problem. (YAY!) by going into my profile and replacing the file prefs.js

Ok. Here's what I really did 1. Created a new profile and verified that this solved the problem. (It did.) 2. Created a copy of the new profile for "rollback" 3. Copied half the files from my old profile into the new one.

   a. If no problem occurs, repeat.
   b. If problem occurs, rollback. 

And so forth until I'd found the one file that was causing the problems. For me it was prefs.js. For others it may be something else.

My Yahoo mail is now working just fine. Thank you Cor-el and Abhill for pointing me in the right direction.

I finally resolved this problem. (YAY!) by going into my profile and replacing the file '''prefs.js''' Ok. Here's what I really did 1. Created a new profile and verified that this solved the problem. (It did.) 2. Created a copy of the new profile for "rollback" 3. Copied half the files from my old profile into the new one. a. If no problem occurs, repeat. b. If problem occurs, rollback. And so forth until I'd found the one file that was causing the problems. For me it was prefs.js. For others it may be something else. My Yahoo mail is now working just fine. Thank you Cor-el and Abhill for pointing me in the right direction.
jazzwineman 0 løsninger 23 svar

I am curious why you would go through all of that to put in place a new browser that none of the new features you are using currently anyway. Are you actually making use of any new features or merely feeling that since it is newer that you "have" to have it??

I am curious why you would go through all of that to put in place a new browser that none of the new features you are using currently anyway. Are you actually making use of any new features or merely feeling that since it is newer that you "have" to have it??
cor-el
  • Top 10 Contributor
  • Moderator
17578 løsninger 158993 svar

jazzwineman

Are there any settings in the prefs.js file that refer to cookies or sessionstore that could have caused the problem?

jazzwineman Are there any settings in the prefs.js file that refer to cookies or sessionstore that could have caused the problem?

Ændret af cor-el den

ljrack 0 løsninger 1 svar

Took a few profile iterations, but I think I've got it stable now. I believe it is/was the pref.js file. But in my new profile the only thing I brought over were my bookmarks, places.sqlite.

jazzman.... we're not all programmers and certified whatevers.... I considered downgrading and frankly wasted time trying to figure out how to do it. Mozilla certainly encourages staying in the latest release and it's not readily apparent by getting pointed to an ftp directory on how to downgrade.

Anyway, no doubt Mozilla will eventually fix this particular issue, in mean time it's nice to have a work around. Glad I found this post.

Took a few profile iterations, but I think I've got it stable now. I believe it is/was the pref.js file. But in my new profile the only thing I brought over were my bookmarks, places.sqlite. jazzman.... we're not all programmers and certified whatevers.... I considered downgrading and frankly wasted time trying to figure out how to do it. Mozilla certainly encourages staying in the latest release and it's not readily apparent by getting pointed to an ftp directory on how to downgrade. Anyway, no doubt Mozilla will eventually fix this particular issue, in mean time it's nice to have a work around. Glad I found this post.
jazzwineman 0 løsninger 23 svar

That is why you have problems on a computer. We are talking about something on a level 1 of just general computer knowledge just barely above copy/paste. You uninstall and can leave your settings and then download 12 and install and whether recreate your profile or not and go on with your business.

I could care less what Mozilla or Microsoft or anyone else has said. having worked on more than 20,000 computers and currently managing about 8500- it is not up to us in the field to be beta testers for software companies.

You are taking more time- doing something you don't understand and just following steps- so if any judgements/decisions have to be made when doing this, you will not understand what to do. You consider it a downgrade. I am curious as to your browsing purposes what you see as a huge enough advantage to 13 that you consider 12 a downgrade? Once they get it straight then use, but until then why go through something you did not even know how to do in the first place??

That is why you have problems on a computer. We are talking about something on a level 1 of just general computer knowledge just barely above copy/paste. You uninstall and can leave your settings and then download 12 and install and whether recreate your profile or not and go on with your business. I could care less what Mozilla or Microsoft or anyone else has said. having worked on more than 20,000 computers and currently managing about 8500- it is not up to us in the field to be beta testers for software companies. You are taking more time- doing something you don't understand and just following steps- so if any judgements/decisions have to be made when doing this, you will not understand what to do. You consider it a downgrade. I am curious as to your browsing purposes what you see as a huge enough advantage to 13 that you consider 12 a downgrade? Once they get it straight then use, but until then why go through something you did not even know how to do in the first place??

Ændret af jazzwineman den

jazzwineman 0 løsninger 23 svar

no- it has to do with security certificates. I tried on a separate computer to uninstall everything on the computer with Firefox and do a complete clean install with 13 and found the same problem with Yahoo. They should be posting 13.1 or something and solve this problem.

They should also make sure that the Symantec IPS works with their new versions as well. This is not good programming for open source guys.

no- it has to do with security certificates. I tried on a separate computer to uninstall everything on the computer with Firefox and do a complete clean install with 13 and found the same problem with Yahoo. They should be posting 13.1 or something and solve this problem. They should also make sure that the Symantec IPS works with their new versions as well. This is not good programming for open source guys.