There are a bunch of *log files in the bin directory (some are .log and some are .errlog). They may have a clue in them. I just had a problem with my PE version at home not starting properly and found a clue in the smm.errlog file. Turns out one of the files in the bin directory was set to read only and UD wouldn't fully start. I think I had to set a flag to increase the tracing level though.
It may be tough if they've installed/upgraded UD a couple of times - who knows where they decided to put things. Could it be something as silly as updatevoc not being run in the accounts? What if you try to connect to the full path to the database (rather than what's in ud_database). hth Colin Alfke Calgary, Canada > From: precisonline> > Colin, I agree. In retrospect, creating the files from scratch seems to be> a bad idea.> > This being a client system I don't have the flexibility to create a new> account. I set up ud_database entries for all of the known accounts and VSG> blows up exactly the same way on each with that "helper program error", so> I'm thinking that udsrvd is not being started for whatever reason. The> train of thought at the moment is that the version of udsrvd does not match> unirpcd and that may be causing the issue, as we're already ruled out> permissions and just about everything else I can think of. I also compared> the size of udsrvd on a 6.1 system that works and the size is about 100K> smaller on this system that doesn't work.> > But that begs the question: If one of these programs doesn't start, is the> event logged anywhere?> > -Kevin _________________________________________________________________ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
