An internal error has occurred and the module cannot be displayed.

[ShockerFever]

I get this message pretty frequently. Every so often I'll click on a thread and one of the pages has this message and I can't see the entire page's contents. But I click on another page of the same thread, it's fine. After some time, I'll check back in and everything will be back up.

It's been happening the last couple of months or so.

[Kung Wu]

Okay I will search vbulletin site and see whats up.

[Kung Wu]

I am running a process to fix this "for awhile". Let me know if/when you start seeing this again, because it will help me to know how frequently the "fix" needs to be run, then I can automate it so we don't have the issue anymore.

Note to myself: This link is just a reminder for myself on what to automate once we know the frequency of the problem -- you can ignore it.

[ShockerFever]

Will do. Thanks Kung Wu !

[ShockerFever]

Doing it again right now.

Dont know if it matters or not that I was logged out when viewing the threads.

[Kung Wu]

Okay, I will take a look.

[ShockerExpress]

Getting it now as well.

[Kung Wu]

I just ran a bunch of cleanup stuff, let's see if the problem goes away for a couple days.

[1979Shocker]

I did a refresh of the Wichita State at Tulane Game Thread and got the error.

[Kung Wu]

Bah! I'll clear the cache.

[FadedCrown]

Yeah just got the error as well. Just refreshed and it occured.

Edit: Seems to be repetitive for a couple of minutes then goes away.

[1979Shocker]

Just got it too.

[FadedCrown]

Seems to be sitewide and not a cookie issue or something related to that.

[ShockerFever]

Ditto. During the game too.

[Kung Wu]

Yeah, I reset the cache before the game trying to get out ahead of it, but it appears to be related to when the site is heavily trafficked. I can't really get to the bottom of it without putting it in debug mode, and I am not doing that during a tournament (creates a lot of garbage). Just have to limp along until we lose.

[Kung Wu]

I am rebuilding the indexes and clearing the cache ... hopefully it holds up past our game.