We're you part of the controlled release of 6.3? This problem can occur when you are running the final controlled release of KID 1.1.0.0, rather than the final release of KID 1.1.0.0, which confusingly has the same version number. If this is the cause, you can resolve the problem by re-running kinstall, and installing just the KID module again (even though it will say it doesn't need an update).
If you weren't part of the controlled release, just open a ticket, and we'll take a look at your server and sort out the problem.