I recently resolved a UniAdmin issue, and having found no information in searching the web and archives I figured I'd post the issue and resolution here in case someone else experiences the same. Here's the setup: A customer had an older AIX system that they wanted to replace. So they bought a newer, bigger, faster, ... well, you get the idea... and reclassed the old production machine as their dev/test box. Unidata 5.2 was running on the old box, 6.1 on the new box. After the conversion, UniAdmin worked fine on the old box. No problems whatsoever. UniAdmin would not work on the new box, however. The unirpcd service was running exactly as on the old box, but every time UniAdmin would try to connect to the new box the message "No RPC Connection Active" would be displayed. We tried various versions of UniAdmin with no success. Every time the result was the same. The Solution: I noticed on another system where UniAdmin was connected that the service name was uniadmin60, not uniadmin. Looking at the unirpcservices file in /ud/uv/unishared/unirpc I noticed that there was no uniadmin61, but there was a uniadmin entry. So looking at the other machine that was working - to verify I wasn't crazy - I copied the uniadmin entry in unirpcservices into a new uniadmin61 entry and restarted unirpcd and UniAdmin works fine. It appears that 5.2 uses the "uniadmin" service name, but 6.0 and 6.1 use the "uniadmin60" and "uniadmin61" entries. Not sure if that's wholly true, but that's what it seems like. Wally, can you confirm? Anyway, hope this helps, and if anyone sees anything I've done horribly wrong, please speak now. -Kevin [EMAIL PROTECTED] http://www.PrecisOnline.com <http://www.precisonline.com/> ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
