I've been getting this error since patch 5.2 was released and even went to live support whose suggestions didn't fix anything. I've pretty much googled this error every day to see if there was a solid fix but nothing seems to work and it's getting a little frustrating seeing this error not being accepted as a bug in the bug report forum. What is going on?
Continue reading...
Continue reading...