Mike
There is a related KB entry: The plugin server connects back to AR Server using what it thinks is the Fully Qualified Domain Name (FQDN). This is designed behavior. The FQDN must be resolvable on the network. In this case, it is not, hence the connection error is issued. The FQDN in this case is "arprod.domain.com". The short name of AR Server is "arprod". AR Server determines the FQDN by taking "adprod", which is the server name (in ar.cfg file, its the Server-Name parameter) and then AR Server does a Windows function call to determine the domain. It concatenates the two together and believes this to be the FQDN. Usually this is a problem when the Server-Name is not the same as the machine host name (a server name alias). There are a couple of ways to work around the problem, but the real solution is to make the FQDN resolvable on the network. Optionally you could add the FQDN to the host file so it resolves locally. Another option is to add the following parameter to the ar.cfg file: Server-Plugin-Alias: REMEDY.ARDBC.SERVER.ADMINISTRATION REMEDY.ARDBC.SERVER.ADMINISTRATION adprod.domain.com After adding this parameter, Remedy services would need to be restarted. There is more information on this parameter on page 337 of the 7.0 Configuring AR System manual available online at Supportweb. _____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Mike Tuck Sent: 17 July 2008 13:52 To: [email protected] Subject: Licensing Problem I am trying to install a new Remedy Server 7.0.3 on MS Windows 2003 64 bit and I am having a licensing problem, I cannot get the HOSTID. When I select the Licensing link to open the form I get the following errors : ARERR 8762 GETSERVERINFO Failed initialization values. ARERR 623 Authentication failed I noticed a problem with starting the service, it will not run when I select "Run as a local system account" but it will run when I have it run as a Domain User Account that belongs to the Domain Admin group. I added the UserID to the local Administrator Group and gave it "Act as part of the Operating System" and "Log on as a service" in the Local Security Policy. I also changed the default installation directory to d:\AR System, otherwise the initial install is plain vanilla to this point. Mike Tuck mailto: [EMAIL PROTECTED] __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
