$ 0 0 Thanks wysocki, its in the database but it still can not find it. same error. This was not an issue with version 3.2... it only appeared when upgraded to 4.1