Removing the x:Name
attribute from the control can fix the issue if in the same scope there is another control defined with the same x:Name.
However, I cannot conclude what cause the issue only by the provided error.
If you can isolate the problem in a sample project where it can be reproduced, please send it to us. In this way, it will be much easier to find what might cause the issue and solve it.
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal
and vote to affect the priority of the items