So some troubleshooting was needed. This is what I did:
- Checked the availability of SDK service: Yes it was up & running
- Checked whether SDK could be connected over the LAN: Yes, no issues there
- Dumped the local cache of the Console (using /ClearCache switch)
- Cleared DNS cache on the client
- Started the Console on the RMS: no problems what so ever.
But still on the client the Console didn’t want to start. Same error, same screen.
Hmm. Wait! What about the time skew of Kerberos (> 5 minutes and it is over)? So I checked the time on the client and the server. Yes. They were out of sync and more than 5 minutes. After having adjusted that, all was well again and I could connect to the RMS again.
So whenever you experience the same issue follow the above mentioned steps and last, but not least check to see whether a time skew is the culprit.
6 comments:
This was a valuable post. I've gotten this same message trying to figure it out and you nailed it first time. As soon as I changed the time on the client it fired right up. Thanks for your post!
I ran into the same issue a while ago and although I ran through these steps, it turned out that I was in fault. I removed some Management packs, and it turned out that one or more was part of the default management pack. Once I re-imported the default MP, my error was gone.
This works! Thank you!!~
I installed the console at workgroup server but it prompt this long error message, was thought it doesn't work for workgroup server.
Thanks for your post. It works after i sync the time for the workgroup server :)
This works! Thank you!!~
I installed the console at workgroup server but it prompt this long error message, was thought it doesn't work for workgroup server.
Thanks for your post. It works after i sync the time for the workgroup server :)
Time skew - man o man, how this is a problem in long running lab environments that aren't managed well, like mine. Keep this post up! Thanks!
Great post, thanks for sharing, it fixed my issue as well.
Post a Comment