Web element is invalid

[omayer]

after upgrade to ranrox 3.3. now Kept getting error "Web element is invalid. " work around to hit ALT key from keyboard, now sure how key gets locked on each run...Here are mote details on the error-
NOTE: looks like if I add this line --" Keyboard.Press("{LMenu}");" on each function then it works otherwise failed each function-

Server stack trace: at Ranorex.Core.InvokerControl.CallMethod(CallMethodDelegate target, Object[] args) at Ranorex.Plugin.TridentIpc.TridentDom.GetElementValue(IntPtr elemRef, String name, Boolean isSpecialValue) at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs) at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Ranorex.Plugin.TridentIpc.ITridentDom.GetElementValue(IntPtr elemRef, String name, Boolean isSpecialValue) at Ranorex.Plugin.WebRemoteFlavorElement..ctor(IntPtr elementRef, IntPtr superBrowserRef, List`1 parentFrameElemRefs, IntPtr ieHandle, ITridentDom proxy, IDictionary`2 initialValues, Boolean doRemoteRefCnt) at Ranorex.Plugin.WebFlavor.GetChildLineageFromUId(LinkedList`1 lineage, List`1 parentFrameRefs, IntPtr browserRef, IntPtr ieHandle, ITridentDom proxy, UidFindResult& result) at Ranorex.Plugin.WebDocumentRemoteFlavorElement.GetChildLineageFromUid(String uidValue, UidFindResult& result) at Ranorex.Core.Element.FindFromUid(String uidValue, Element& result) at Ranorex.Core.RxPath.ApplyInternal(RxPath path, Element startElement, Duration timeout, Boolean findSingle) at Ranorex.Core.Element.TryFindInternal(RxPath path, Duration timeout, Boolean findSingle, IList`1& foundElements) at Ranorex.Core.Element.TryFindSingleInternal(RxPath path, Duration timeout, Element& foundElement) at Ranorex.Core.Element.TryFindSingle(RxPath path, Duration timeout, Element& foundElement) at Ranorex.Adapter.TryFindSingle[T](RxPath path, Duration timeout, T& foundAdapter) at ConsoleAppProject.TestRunAttempt.PeoplSoftPageLoad() in c:\SVNviews\Automation\MASTER\Projects\ConsoleAppProject\TestRunAttempt.cs:line 83 at ConsoleAppProject.TestRunAttempt.Ranorex.Core.Testing.ITestModule.Run() in c:\SVNviews\Automation\MASTER\Projects\ConsoleAppProject\TestRunAttempt.cs:line 193 at Ranorex.Core.Testing.TestSuiteModule.RunInternal(DataContext parentDataContext)


Thank you,

[omayer]

Ok looks like ATL key gets stuck when Ranroex executing the testcase.
Thank you,

[Support Team]

Hi,

Are you still having the problem with the ALT key or did you solve it?

Regards,
Markus
Ranorex Support Team

[omayer]

every 3rd test run having ALT key issue, i do have console prompt that prompt to enter url and userid and password, and scenarioid, then hit enter , when it start enterring user id on web then i get webelement not found error, after pressing down couple of time on ALT key then i can rerun the same test w/out any error.

[Support Team]

Hi,

every 3rd test run having ALT key issue, i do have console prompt that prompt to enter url and userid and password, and scenarioid, then hit enter , when it start enterring user id on web then i get webelement not found error, after pressing down couple of time on ALT key then i can rerun the same test w/out any error.

Can you please describe your "Alt key issue" in detail, as we do not have a clue what exact problem you are running into.

Regards,
Tobias
Ranorex Team

[omayer]

ok, finally narrowed down the issue, it was not the ALT key , it was object identification issue after ranorex upgrade to 3.3, after modification of object path , now working as expected. Thank you for looking into it.
Thanks,
Omayer