topic It is very likely that you in Product Forum

Toggling to AA spy mode crashes Blue Prism

blue_meanie — Tue, 21 Nov 2017 15:07:00 GMT

We have one user here who's machine will crash literally every single time he tries to spy in AA mode. It happens the moment he presses Alt when it goes to cycle through to the AA mode. We had seen it previously with one other user, who ended up getting a new machine to fix the issue! His colleagues with (supposedly) identical system build have no issues. This happens regardless of the application type trying to be spied. Has anyone else come across this very odd behaviour before, and if so, what is the solution? (other than replacing their machine 🙂 ) I captured the following from the windows error log: 6.1 7601 Service Pack 1 (0x4): Windows 7 Enterprise Enterprise 7601.23915.amd64fre.win7sp1_ldr.170913-0600 1130 Multiprocessor Free X64 1033 CLR20r3 automate.exe 4.2.37.0 5494580a WindowSpy 4.2.37.0 549457a6 4f 0 System.InvalidCastException 6.1.7601.2.1.0.256.4 2057 ****** Dell Inc. Latitude E6430 A16

It is very likely that you

Denis__Dennehy — Tue, 28 Nov 2017 18:29:00 GMT

It is very likely that you are using the incorrect Application Modeller mode for your application, have you experimented with the 32bit/64bit external/internal settings?

Hi Denis, thanks for your

blue_meanie — Wed, 06 Dec 2017 21:02:00 GMT

Hi Denis, thanks for your reply. The application in question was actually SAP! We were able to spy all of the elements we wanted in SAP (which the SAP spy mode could not capture) on his colleagues machine. In fact, we tried it on a couple of his colleagues machines, no issue. It must have been something to do with the setup of his particular machine, not the end application, etc. As mentioned, we had seen this a few months earlier with another couple of his colleagues machines, where literally just toggling into AA mode (without getting a chance to try spying anything) would cause Blue Prism to crash immediately. I have not seen this with any other clients (there have been quite a few over the years!), and obviously it only seems to affect a very small number of developers' machines. I no longer have access to their machine, so can't do any further analysis for you i'm afraid. Guess this one has to be filed in the ""Mystery"" box.