Terminal Services Configuration doesnt work

We have a problem with two out of four Terminal Services 2008 Servers.
They run Windows Server 2008 Standard x64 SP1 with two Intel Xeon E5420 processors and 16GB ram.

When we either local or remotely try to open the Terminal Services Configuration tool it pops up with an error. Its about 90 days since we installed them and could configure them without problems.

One of them says: The settings for this terminal server cannot be retrieved. The remote server does not support running Terminal Services Configuration tool remotely.
The other says: Unable to complete operation:Not found
I've tried rebooting, tried looking in the event viewer, tried googling, but can't find a clue to anything.

Users can connect without problems.
But on the server which says "unable to complete operation:not found" there isn't many users connected.

Take a look at the list here:
 Server:     Active   Inactive   Total   FreeMem MB
 ts1            90          3           94       4554
 ts2           104         2           107     6781  <--- The settings for this terminal server cannot be retrieved
 ts3            24          2           26       13089 <-- Unable to complete operation:Not found
 ts4           107         3             110      4164       

I could reinstall Windows, but it takes a lot of hours installing all those special applications and such, so if I could fix it without reinstalling, it would be the best solution.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

fzDKAuthor Commented:
The solution to the problem was to run winmgmt /salvagerepository and reboot afterwards on one of the servers the other i had to run winmgmt /resetrepository and a reboot afterwards.

Everything runs smoothly now.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
I am having these same errors on two different servers just like you did.

You told us what you ran but which command did you run on which error message??
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.