This week's book giveaway is in the Programmer Certification forum.
We're giving away four copies of OCP Oracle Certified Professional Java SE 11 Programmer I Study Guide: Exam 1Z0-815 and have Jeanne Boyarsky & Scott Selikoff on-line!
See this thread for details.
Win a copy of OCP Oracle Certified Professional Java SE 11 Programmer I Study Guide: Exam 1Z0-815 this week in the Programmer Certification forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Junilu Lacar
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Ron McLeod
  • Carey Brown
Bartenders:
  • Paweł Baczyński
  • Piet Souris
  • Vijitha Kumara

problem with starting websphere 4.0

 
Greenhorn
Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
ADGU2008E: The Administration Client failed to connect to the Administration Server. Start the local or remote Administration Server service before launching the Administration Client.
can anyone help me in solving this problem, i m facing this as soon as i start my server
deep
 
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This could be caused by a number of problems such as (1) IIOP (used by the console to connect to the server) can't go through NAT firewalls/switches without some configuration changes, or (2) your server is multi-homed (more than one IP address).
Try a couple things:
1. On the server, in <WAS_HOME>\properties\sas.server.properties add this line com.ibm.CORBRA.LocalHost=<short_name_of_machine>
note: provide the server's short name, not its
fully qualified name.
2. When you install the console on your remote machine, there is a step in the setup wizard which asks what node you wish to manage. At this stage, provide the short name of the server (not the long name). The wizard provides the long name as the default value.
3. Ensure that the remote node can ping the server using its short name. Update your host file if necessary.
 
Michael Bamford
Greenhorn
Posts: 3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
My last post above didn't make too much sense. I used angled brackets in my response which were stripped out by this discussion board's server and made my response unintelligable. Here is how it should have read:
1. On the server, in WAS_HOME\properties\sas.server.props, add this line:
com.ibm.CORBA.LocalHost=servershortname
 
To do a great right, do a little wrong - shakepeare. twisted little ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!