GrahamS 5/11/2009 12:42 AM PST
Question
Hi,
NB Also posted to Application Development
--------------------------------------------
I have a CE application which runs pretty well on a number of embedded PC's
(eBox 2300sx).
I am experiencing seemingly random failures however - some appearing days
after the application is started. These put up a dialog with the above
message (xxx is my app name).
Similar messages have also reported this as being in 'udevice.exe'.
My app is a Managed C# CF3.5 app and makes extensive use of a TCP Socket and
a serial port (Com2).
My app has a full set of exception handlers - with some wrapping threads,
and one wrapping the whole app - but none of these are triggered when this
dialog pops up.
1. How do I identify what is causing this dialog ??.
2. How do I prevent it from occurring. There is no user - its a remotely
located device with no screen, keyboard or mouse and MUST run 24x7 completely
unattended. There is a UI but for 'diagnostic' purposes only - plug in a
screen and see what the device is doing.
I would make it a full 'windows service' if this were a PC - but its CE :-O.
My app is run from within a command file so that IF it were to crash out -
it just gets restarted - this all works until the OS puts up this dialog box
:-O - then one of my threads stops (serial port) until the OK button is
pressed.
This is making me wonder if I really should be using CE for this project at
all :-((.
I cannot really 'instrument' this any further as adding KITL prevents me
from using the serial and ethernet ports - on which my app is based. It also
completely changes the footprint of the device and thus may even mask the
issue anyway ??.
It 'looks' to me like an exception outside of my own code - maybe in the
'managed wrappers' ??.
This one has been driving me nuts for many weeks now as I cannot get to the
bottom of it - especially as the error message is SO unhelpful!.
NB I replaced the MS SerialPort with OpenNetCF Serial and this seems to have
made the occurrence rarer - I thought it had gone away - but yesterday it
came back again after running perfectly for a few days :-O.
Finally - it does not appear to happen on ALL boxes - although this may well
be a 'red herring' - ie there could be other code changes introduced whilst
trying to instrument the problem to locate it ;-O.
I am even now getting to the stage of questioning whether CE is the right
choice here - if it can put up a show-stopper like this. My eBox has 128M RAM
so maybe I should be thinking about Embedded XP or some other OS ?? - ie one
which has better support for 'services'.
Thanks hopefully.
Regards
Graham
|
Similar Threads
