After that step fails in Chrome, use the Export Result to File feature in Step Failure Details and attach the file to your next post. If the site you're testing is publicly accessible, we'd like to see the issue first-hand. Please place a copy of the test files into a .zip file and attach it. You can attach that file to a support ticket, which unlike this forum is confidential.
The Unable to locate element failure is a common automation challenge. See here for suggestions on how to resolve it. It sounds like Chrome is rendering the page DOM slightly differently, invalidating a specific element's Find Settings. You'll probably need to edit the find logic so it works in all browsers. See here for more information on browser inconsistencies.
All the best,
the Telerik team
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?
Telerik Public Issue Tracking
system and vote to affect the priority of the items