I've seen this issue a couple times with sharepoint and the only resolution ultimately was to reinstall (sharepoint and the kit). We were unable to discover the root cause of the behavior in either case. When we tested in house everything always worked fine...
Regards,
Tim