I'm getting 'A server error occurred. Please try again later.' message when I try to enter some threads. It occurs in both Firefox and Chrome and the only particular pattern I can see is that it seems to happen more often when I try to access threads where I have already posted. Very frustrating.
I can't enter over half the threads either, receiving same message as above. I hurts me to think of all these threads not being privy to my off-topic, immature comments.
There are two ways to get around this. 1. Mark all forums read by going to Quick Links -> Mark Forums Read. Apparently this doesn't work for everyone, but it did for me. 2. Instead of clicking on the thread title, click on the date below the name of the member who posted last, which will take you to the last post. Or if there's more than one page, you can click on the individual page number.
Another way to fix the issue is check whether your URL gets the at the end '/unread' remove that and the thread loads normally but I think thirdwinds method works best if you don't mind having everything flagged as read.
This is happening to me too. I can't read anything in Chrome. I had to open this page with IE just to read it. Clicking on the date of the last post does work, but is there a more permanent solution? I suppose I'll check out marking all forums as read once I read them. Thanks for the suggestions!
Thanks @Wreybies Is that error in you screenshot the same error everyone else is seeing? Roughly how often is this occuring? Can you copy a link that gives you this error message (being sure to copy it before it redirects, if it does)?
I can no longer reproduce the error. That error I posted happened when I attempted to enter into a thread via the Recent Post sidebar. I could enter the thread if I went to the subforum itself, but some subforums were being equally affected. None of them seem to be giving me the error now.
Same here. I'm fine now. But mine basically just said "Error. There was an error attempting to view this page. Please try again later" or something along those lines. But I haven't seen the error since I posted earlier on IE.
