0 Replies Latest reply on Oct 25, 2007 2:46 PM by John van Ommen

    When app server unames the file server, what's it expecting?

      My client moved his app server to a different Active Directory domain, and now we're getting a "can't uname fileserver" error when we start up the app server.


      Does anyone with knowledge of the app server understand what it's doing with this "uname" call?


      I've already run through all the obvious stuff (ACLs, licensing, DNS.)


      When I went digging in the database I found that the fileserver is named "somesqlserver01", but agentinfo replies with "somesqlserver01c". Each address is on the same hardware, but they're different IPs on different interfaces. (The file server lives on a clustered database server.)


      Perhaps I need a way to get the agent to listen on all interfaces (or does it do that by default??)