11-15-2013 07:18 AM
Ok, let me setup this up:
BSM 9.22, BPM 9.22, VuGenSA 11.51
Key (or changed) VuGen Runtime Settings:
Standard Log (Log errors/warnings only)
Replay Options - (Checked) Failed end event causes step failure
Snapshots generation - Replay snapshots generation - On error
Action on error - Abort script
Script runs as it should in Developer and Load modes as well as fails when textCheck is changed to an invalid value in VuGen. No problem with VuGen.
I first created a simple "login and text check" script but for some reason it would not initialize on the BPM. So then I scripted an more simple "browse to google", search, and verify search text with "verify" text check. I uploaded this to BSM and everything seemed to be fine (green) except that I was not receiving any performance metrics to the reports even though the script seemed to be running fine.
I then changed the textCheck parameter I had created for text check to a value that should fail "ASDFLKAJDS". Script still showed that it was running without error but then I did start receiving the performance metrics (including the times from when I was seeing nothing). A few minutes later I started seeing transaction errors produced for the script runs but BSM still showed the script as "OK"... solid green since it started showing up. The next issue was that the BPM Triage Raw Data Error log is showing that:
Error Name was "-1" with Error Message "N/A" and no snapshot.
Error Name was "0" with Error Message " - " and no snapshot.
I'm truly at a loss and could really use some help here.
11-18-2013 08:14 AM
I'd start with some enhanced logging, perhaps this will give you more information of what's going on.
To Increase log level to agent.txt log, shut down BPM.
Change <inst dir>\config\agent1.cfg: set in [agent] section LogLevel to be LogLevel=debug
Now restart BPM.
After BPM has started, please go to script folder (under SiteX/?) and update the script's default.cfg file [Log] section:
Wait till the issue happens again, and check the BPM logs if there is more details about the error.
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.