This is not a known issue. We have used emScript on numerous devices under simialr use cases and have not seen this. If you can narrow down the script calls that you feel are suspect, it would help to progress the root cause of the issue. I suspect it is not neccessarialy emScript but more of a system type of interaction on call that the tool is making at the same time as some underlying condition. I would be very interesting to know what it is. Also keep in mind, emScript runs a script that is meant to be easily tailored so if the problem you have is easily reproduced, it should be pretty straight forward to triage. If you still feel there is an emScript issue, you can continue to use this forum or email ECSGTEAM@motorola.com to take this to the next step. The help desk does not support emscript issues but it is used in the support of existing cases. So if you need to engage them, it should be under a normal triage effort. In other words, if you can show the problem where emScript is not a factor, they will look into the issue. They will not look into emScript bugs. This is somthing we do as a best effort within ECSG/ECRT.

Matthew, eMscript is supported by ECSG/ECRT when used in connection with an SPR.  This is not known issue and we are very interested in insuring that it corrected.  Can you provide any additional information pertaining to this scenario. Does the device have AC power when problem occurs? Does the device have WAN data connection? Does the device have WLAN association? Does the device have ActiveSync Connection? Can you zip up the contents of the \Application\emscript directory of a device that does not recover and submit it to the forum for analysis. Thanks,