INS support forum
|Welcome to the Integrated Notification System
Before entering a query/request
please search the forum to see if someone else has asked the question before.
Please feel also free to
respond to queries from other users if you have experienced the same type
of problem and found a solution to it.
Our support team will monitor
this forum and endeavour to provide answers to the queries posted.
Please make sure to post
your query to the right forum as there is a separate forum for each application
provided by MAW Software.
Back to the forum
, the 10.10.2011, Richard Knouse wrote at 21:06:38 :
>>>>>>Need to autoboot
All problems now solved. First we have Msg Server running as a service rather than as a dll dependent of Message Service. This eliminated the reset instability. It also allows for automatic load at reboot. Msg Server is configured to load automatically after Dialogic Service. This required some registry fiddling.
Msg Server needs to log in to the domain account that is open on the machine to access its text files and launch executables. Because the script calls a .Net exe that loads FileMaker as an ActiveX, FileMaker DCOM also needs to use the same domain user.
Finally, I set up a backdoor in the script that can force a reboot if necessary.
CGIForum (C) Markus Triska