It sounds like you are running 2.0 beta 3. This is a known bug in 2.0 beta 3. Upgrade to 2.0 beta 11 and all should be well.
_________________________
Tony Fabris