Hi sfeger, Potentially what could be occurring is that your application is using named windows whilst using the window.open() JavaScript method to launch the windows, resulting in known behaviour in Silk Performer in which virtual users share Windows rather than opening separate ones. Can you confirm whether a new window is opened after logging into the application? If so, confirm with your application developers whether the window that is opened is done so using the javascript method window.open() Can you confirm with your application developers whether the window that is opened is launched using the window.open() JavaScript method, and if so, is the window named? The following kb article provides further detail on the problem: community.microfocus.com/.../silk_performer_-_application_perfor mance_testing/w/knowledge_base/19645.browserengine-29-invalid-locator-or-dom-element-handle-when-running-multiple-users.aspx There are various workarounds to the problem: - Edit the internal JavaScript logic of the application, so that a named window is not used www.w3schools.com/.../met_win_open.asp - If the actual JavaScript within the application cannot be edited, and the window has a URL, use the BrowserExecuteJavaScript() function to call the window - As opposed to testing the application via the Browser Driven loadtesting approach, use the Web Business Transaction (HTML/HTTP) to test the application at the protocol level. Regards Paul
↧