This kind of thing usually occurs after a plugin has been moved, re-installed or in rare cases after it's been upgraded. It doesn't sound like any of those scenarios apply to you, but it's worth checking out.
You can get the full path to the plugin in the Plugin Manager and verify that it matches its physical location.
[EDIT] Just remembered another (rare) scenario that can cause this: two plugins with the same CLSID. It doesn't happen often, but I have seen it. This problem will show up after re-scanning plugins.