Current Issues For Tech Review

Issue from ALYS1:User Profile pages receives an error message and cannot be viewed.Warning: Memcache::connect() [function.Memcache-connect]: Can't connect to 172.16.1.35:11211, Connection timed out (110) in /includes/class_datastore.php on line 245

Unable to pull up all of a user's posts in order to delete. Only the first 25 posts show up.

Still receiving below error message when trying to access profile or mypage.Warning: Memcache::connect() [function.Memcache-connect]: Can't connect to 172.16.1.35:11211, Connection timed out (110) in /includes/class_datastore.php on line 245

I think mine is getting worse.....any hope of getting this fixed? Hope so!!!

Yep, getting worse.:( I've got a message out, but please be aware we are dealing with a new tech team so I have no idea when we'll see the fixes. I apologize!

Thanks.....I know it is beyond your control.....boy, if that was not so....it would be working great.

You know it clrklttn! I'd have my whip out!;)

Also am getting the Warning: Memcache::connect() [function.Memcache-connect]: Can't connect to 172.16.1.35:11211, Connection timed out (110) in /includes/class_datastore.php on line 245message when I attempt to access the View My Page link.Also, when I pull up the front page and attempt to use the View All of Today's Posts link, 95% of the time, I get a message that says:vBulletin MessageSorry no new matches - please try some different terms.

Still not receiving the notifications of updates to threads.

Warning: Memcache::connect() [function.Memcache-connect]: Can't connect to 172.16.1.35:11211, Connection timed out (110) in /includes/class_datastore.php on line 245

Is access to the forums gone forever???

You had access or you wouldn't have been able to post, so I'm unclear what exactly your issue is?

Sorry.....didn't mean access to the site, I meant getting the error messages when clicking on profiles etc.

Great that all seems to be back to normal this morning. Cudos to techies and Crick for carrying the load.:woohoo:

Unfortunately, I am still getting this error: