Could we have something custom running that is causing this problem?