D
dbeavon
Guest
All I did was move some of the classes to another directory (moved both the cls files and related r-code files). The only other thing that might make this unusual is that this portion of the PROPATH lives on a UNC (a NetApp share). The testing was performed from a Windows version of PASOE - OE v. 11.7.4. At the time I was actually trying to find various scenarios where -errorstack and -debugalert would provide some helpful messaging to the PASOE agent log file. I have seen situations where those two parameters will provide a lot of helpful information when the AVM runs into trouble. But, I've also seen situations where PASOE can encounter AVM errors at runtime, and the two parameters don't provide any additional information. I believe that those parameters are only helpful for the types of errors that would otherwise show an "error alert box", (or whatever its equivalent is in the context of PASOE). Unfortunately - while I was testing -errorstack and -debugalert - I found this other type of error that makes the AVM extremely unhappy, and it stops showing any meaningful messages since the entire process encounters an ACCESS_VIOLATION (precluding the ability to write any more to the agent log).
Continue reading...
Continue reading...