shankar_r wrote:
This is error is not related to any code that you have. We have to look this object Name mapping.
Lets do following things,
1. Try to highlight the Object from the Name Mapping = ?
2. If 1 is fine, Then Add a script before your setSelectedDate
if(JCCalendarObject.Exists)
{
//put setSelectedDate line here
}
Let me know your results.
I'm with shankar_r on this. Something changed somewhere, but not in your script code necessarily. The problem has to do with the identification of the JCCalendarObject in your NameMapping. And, it MIGHT not be a problem with the mapping of the particular component itself but with something further up the hierarchaly tree.
From your screenshot, I see this is running as some sort of descendant child of javaw. Did the Java engine recently get an update? Have you moved the tests to a new machine that might not have the same Java environment installed? These are things to start investigating.
Also, could we get a shot of the actual error in the error log and perhaps any errors/warnings leading up to it? There could be things like ambiguous recognition errors, parent object not found errors, "took too long to find" warnings, etc., which could all contribute to not being able to find the JCCalendarComponent.