This error seems to be related to the 2.3 update. Also can't figure out how to fix it. Did you fix it?
