Web Adapter Crashing on 2nd Use
Hi,
I have an automation that is crashing on the second use every time. I can debug once, perfectly fine. If I stop debug and press debug again, the build starts and succeeds, but the webpage never loads and Openspan Studio crashes and must be closed with task manager. Runtime also crashes and will not close, even via task manager. If I restart Openspan, the studio loads fine, but if I attempt to debug again, I get errors, likely due to Runtime still being stuck. The only remedy I have found so far is to restart my computer.
From my testing, it seems that the issue only occurs after the 'Start WebAdapter' automation, so I can only assume it's something to do with attempting to interact with the form. However, when the system crashes, it has not even loaded up the form yet, the whole adapter just fails to start and Runtime crashes.
Has anyone has come across this issue before? I would be very grateful for any help that can be provided.
The webpage I am automating is Microsoft Sharepoint 2007. I am running Windows XP, Visual Studio 2010 with Openspan Studio Plugin Proprietary information hidden, and Internet Explorer 8.
Below are my automations and the properties of my Web Adapter.
Automation1 (created for the purpose of testing):
Hi,
I have an automation that is crashing on the second use every time. I can debug once, perfectly fine. If I stop debug and press debug again, the build starts and succeeds, but the webpage never loads and Openspan Studio crashes and must be closed with task manager. Runtime also crashes and will not close, even via task manager. If I restart Openspan, the studio loads fine, but if I attempt to debug again, I get errors, likely due to Runtime still being stuck. The only remedy I have found so far is to restart my computer.
From my testing, it seems that the issue only occurs after the 'Start WebAdapter' automation, so I can only assume it's something to do with attempting to interact with the form. However, when the system crashes, it has not even loaded up the form yet, the whole adapter just fails to start and Runtime crashes.
Has anyone has come across this issue before? I would be very grateful for any help that can be provided.
The webpage I am automating is Microsoft Sharepoint 2007. I am running Windows XP, Visual Studio 2010 with Openspan Studio Plugin Proprietary information hidden, and Internet Explorer 8.
Below are my automations and the properties of my Web Adapter.
Automation1 (created for the purpose of testing):
Start WebAdapter automation:
Web Adapter properties:
Thanks,
Ryan
Accepted Solution
Endsleigh
GB
Hi Zach,
Yes, it does appear to be something to do with iexplore.exe, it is not closing down properly. I tried setting StopWhenMainWindowCloses to false but had the same issues.
I have decided to go with a Universal Web Adapter instead and use Google Chrome instead, this avoids the issues I've been having :)
Thankyou for your help.
Ryan
Pegasystems Inc.
US
Ryan,
- What causes automation1 to start?
- Is there any reason why you have the ExitSuccess execution link from the starttppshaepointadapter autx asycnhronous?
- What happens if ExitSuccess execution link is made synchronous?
- The txtPHName control, is that to a windows form or to a control on the web adapter?
--Zach
Endsleigh
GB
Hi Zach,
Thanks for your response.
Automation1 has its StartOnProjectStart property set to true, so that's how it starts. - I would not normally build like this (normally I'd start based on control events), but the application I have shown you, is an application I have built specifically to test this adapter error I've been having in my real project.
The asynchronous link is only there as part of my testing, it did not help or seem to change anything at all. If it is made synchronous, the same issues occur.
txtPHName is a control on a web adapter. It is matched based on Input Type and Element ID. Here is a list of my interrogated controls:
Thanks,
Ryan
Pegasystems Inc.
US
Ryan,
It sounds to me that the iexplore.exe is getting into a bad state when shutting down the debugging the first time around.
Can you check to see if the iexplore.exe is still running in task manager when you stop debugging the first time?
I would also check to see if setting the StopWhenMainWindowCloses to false reproduces the behavior as well.
--Zach
Accepted Solution
Endsleigh
GB
Hi Zach,
Yes, it does appear to be something to do with iexplore.exe, it is not closing down properly. I tried setting StopWhenMainWindowCloses to false but had the same issues.
I have decided to go with a Universal Web Adapter instead and use Google Chrome instead, this avoids the issues I've been having :)
Thankyou for your help.
Ryan