Our problem with WMIS was that UniData would start on a reboot of the server, but if you stopped UD it wouldn't restart unless you rebooted. Until I found the conflict with the WMIS service. Then I stopped the WMIS service, stopped and restarted UD - which worked fine, and then restarted the WMIS service.
I used the process explorer from <www.sysinternals.com> to find an smm handle being held by the WMIS service. If it's only udt on the console that is giving you the problem - are you sure you're in a valid account when you start udt, or maybe the pathing is messed up? Sorry, I'm not much more help here - I always use telnet (SBClient) to connect. Can you use telnet? Hth Colin Alfke Calgary Canada >-----Original Message----- >From: Christensen, Steve > >I've burned up any urge to become frantic years ago :^) > >Licensing is fine on the machine. I've verified it as I >accidentally invalidated it and had to obtain a new >authorization code the other day. > >The smm is running, just getting a failure on the udt command >line so I suspect some system issues that need to be addressed. > >The system has been running for several years with no >maintenance. I believe it has been accumulating maintenance >issues and data transfers via odbc have become rather slow and >cause some cross-department locking issues which is what I am >working on addressing. > >Did you shut down the instrumentation service and the driver >extension service that goes along with it? I suspect I will >need to review and shut down all unnecessary services to find >the culprit on this problem. > >Thanks >Steve ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
