Outside of a corrupt install, it's most likely caused by the SP running with the old 2.0 configuration schema for compatibility rather than being current. -- Scott