@thumper1, I never experienced this. Does the issue still persists? Is anyone else getting this error?