Ignition Error Report missing window

When our users get an error and click on the Report Details to send the error message to us, it’s not saying what window they were in when they got the error. It’s an incredibly verbose report other than that, so is it possible that the name of the window is buried in there somewhere? Here’s one that I manually triggered:

[quote]CD-Key
HKL55N
User
User Name
user.name@domain.com
User Message
dan, testing the error reporting from ignition designer
Error Message
Error executing script for event: actionPerformed
on component: btnSave.
Error Details
Traceback (most recent call last):
File “”, line 49, in
NameError: name ‘errinfo’ is not defined

at org.python.core.Py.NameError(Py.java:260)
at org.python.core.PyFrame.getname(PyFrame.java:257)
at org.python.pycode._pyx7987.f$0(:91)
at org.python.pycode._pyx7987.call_function()
at org.python.core.PyTableCode.call(PyTableCode.java:165)
at org.python.core.PyCode.call(PyCode.java:18)
at org.python.core.Py.runCode(Py.java:1275)
at com.inductiveautomation.ignition.common.script.ScriptManager.runCode(ScriptManager.java:568)
at com.inductiveautomation.ignition.common.script.ScriptManager.runCode(ScriptManager.java:561)
at com.inductiveautomation.factorypmi.application.binding.action.ActionAdapter.runActions(ActionAdapter.java:170)
at com.inductiveautomation.factorypmi.application.binding.action.ActionAdapter.invoke(ActionAdapter.java:265)
at com.inductiveautomation.factorypmi.application.binding.action.RelayInvocationHandler.invoke(RelayInvocationHandler.java:55)
at com.sun.proxy.$Proxy23.actionPerformed(Unknown Source)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$200(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue$4.run(Unknown Source)
at java.awt.EventQueue$4.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)

System Details
fpmi.client.memory.used=1020.50
fpmi.client.memory.max=1820.50
fpmi.client.type=Designer
fpmi.client.version=7.7.1 (b2014092209)
java.vm.version=24.71-b01
java.vm.vendor=Oracle Corporation
java.vm.name=Java HotSpot™ 64-Bit Server VM
user.country=US
os.name=Windows 7
os.arch=amd64
sun.os.patch.level=Service Pack 1
os.version=6.1
java.specification.version=1.7
user.language=en
ignition.gateway.version=7.7.1 (b2014092209)
ignition.gateway.memory.used=990.75
ignition.gateway.memory.max=990.75
ignition.gateway.uptime=2 days, 21 hours, 57 minutes, 6 seconds
ignition.module.com.inductiveautomation.alarm-notification=2.7.1 (b2014092209) - RUNNING
ignition.module.apachecommons=3.2.0 (b1) - LOADED
ignition.module.itext=5.1.3 (b0) - LOADED
ignition.module.math=3.3.0 (b0) - LOADED
ignition.module.mobile=2.7.1 (b2014092209) - RUNNING
ignition.module.xopc=2.7.1 (b2014092209) - RUNNING
ignition.module.poi=3.9.0 (b0) - LOADED
ignition.module.rept=2.7.1 (b2014092209) - LOADED
ignition.module.com.inductiveautomation.sfc=1.7.1-beta11 (b2014092209) - RUNNING
ignition.module.help=2.7.1 (b2014092209) - RUNNING
ignition.module.fpmi=7.7.1 (b2014092209) - RUNNING
ignition.module.com.inductiveautomation.webbrowser=1.7.0 (b2014071518) - LOADED
fpmi.client.memory.used=1020.50
fpmi.client.memory.max=1820.50
fpmi.client.type=Designer
fpmi.client.version=7.7.1 (b2014092209)
java.vm.version=24.71-b01
java.vm.vendor=Oracle Corporation
java.vm.name=Java HotSpot™ 64-Bit Server VM
user.country=US
os.name=Windows 7
os.arch=amd64
sun.os.patch.level=Service Pack 1
os.version=6.1
java.specification.version=1.7
user.language=en
[/quote]

Hey Dan,

There isn’t a window name listed in the stack trace, nor do I think it can be added to that. This is where it become beneficial to have unique component names with meaning. I can tell that this error was triggered by Line 49 in an action performed script on the component btnSave. Hopefully the btnSave component name has meaning and can be easily tracked down within the project.

Alas, we have been naming components for what they do within the window, and letting the name of the window distinguish them. Worse, we often have multiple layers of containers within a window, many of which have similar components with the same names. It’s easy enough to distinguish them on the browser, but obviously less so in this circumstance.

I guess we’ll either do a lot of renaming, or ask the users to type the name of the window in the error report.

[quote=“Greg.Simpson”]Hey Dan,

There isn’t a window name listed in the stack trace, nor do I think it can be added to that. This is where it become beneficial to have unique component names with meaning.[/quote]

Greg: thanks for the response. Is it ‘really’ true that the window name cannot be added to the stack trace? Our projects are large, but there have to be even larger ones out there… It just seems to me a bit overkill to somehow embed the window name in each component (those that perform actions, anyway). david