Strange. We've had one client use it nightly for years. It's worked fine - until their last UniData upgrade. Since then we've had to stop the Windows Management Instrumentation Service as well as it keeps a shared memory segment open that prevents UniData from starting. Once we started Stopping WMIS starting Unidata and then starting WMIS we haven't had a problem. This doesn't sound like your problem because it was consistent and not sporadic.
Colin Alfke Soggy, Calgary, AB >-----Original Message----- >From: Robert Paterson > >Only thing with the net stop and net start is that we have >seen this eventually fail on some systems. > >Usually the fix is that every three or four instances to >reboot to ensure memory is flushed. > >Neither we nor the customers investigated this as the reboot >was relatively straightforward to achieve. > >Robert Paterson > >-----Original Message----- > > >3. Use "net stop" to stop the UniData database and telnet >services. This is very similar to the stopud -f - but doesn't >ask for confirmation. Use "net start" to restart the services. ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
