| || |
Has anyone pinned down the sequence that causes this when running scripts and maintaining them on another PC at the same time? (yeah, I know, I know - just avoid editing/opening a script when it might be running on another machine...)
I have just searched this forum and also Mercury knowledge base, and whilst there is quite a bit on unhandled exception, very little of it mentioned the multiple instance secenario.
At one place I work we have been running multiple instances of scripts on WR 7.01 and Windows 2000 LAN environment for a couple of years. We know from plenty of experience that WR is very sensitive to opening a script and modifying it on one machine when it might be running (or previously run)(even though not actually "open") on another instance. It seems that in many cases the other machine(s) will crash with the unhandled exception even if no changes are saved on the "edit" instance - so this suggests that it must be just the opening of the script on another machine which may be running (or may get run later) on the first machine... but if I had pinned it down exactly I wouldn't be writing this...
Another interesting/surprising aspect of it is that the unhandled exception on the running machine(s) very often doesn't happen immediately - it seems to wait until it returns control back up to the top level script before happening...
Now I am working in a second scenario with WR 7.6 on Windows XP, and here although we are still using multiple run instances, we have had the exception only once (although it did still seem to be related to editing a sub-script on one machine that was running on another)
My feeling is that there is a bug in Winrunner which could be improved so that it handles this a lot better. It should be possible to open a script on one machine, even if it is running (or has run, or will be run) on another. Alternatively, if this sequence is going to commonly cause the unhandled exception, then WR should be improved by "locking" every script that it is running / has run, until such time as that process is STOPPED, so that those scripts cannot be opened on another PC giving rise to the liklihood of the dreaded exception...
Any thoughts welcomed...
Re: Unhandled Exception
mmmmmm not sure the same thing but........I have had a problem with locking on 7.01 which I raised and was fixed with a patch on 7.5 WR75p71. The problem being that if a compiled module was opened an another PC the user was not informed that the script was in use by another machine. So then I could update it and override some other users script. If this happened when the script was running we got an unhandled exception.
This might be the same as you having the child script open and editing(I think the fact it is being edited is the key) and when WinRunner comes to save it in then notices it is locked and crashes.....maybe anyway