Win a copy of JDBC Workbook this week in the JDBC and Relational Databases forum
or A Day in Code in the A Day in Code 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 ...
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
  • Piet Souris
  • salvin francis
  • fred rosenberger

Websphere Portal Server:Problem in Administrative Console

Posts: 15
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hii everybody

i have installed WebSphere Application Server V6 and WebSphere Portal Server V6 on Linux operating system V5 red hat.

I am able to start both the application server and the portal server from the command prompt where it is successfully started. I am also able to access the administrative console of application server. But when i try to open the administrative console of the Portal server by the following :

<a href="http://hostname:10038/wps/portal</b rel="nofollow">" target="_blank">http://hostname:10038/wps/portal[/B]

i get the following error:

Error 404: Initialization of one or more services failed.

Can anybody guide me in this. I have configured openldap with the websphere application server.

Thanks for any help in advance.

author and cow tipper
Posts: 5000
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I had a similar, but not completely identical error. Maybe my solution will address your problem as well. I wrote about it on this post:

WebSphere Admin Port Issues When Connecting

Hmmm....Just got an update as I submitted that.

Apparently, the problem is documented in the readme for IRAD. After doing the update, you have to delete the WAS server that is created with the IRAD server installation, create a new WebSphere Portal Server in the server perspective, and then bounce IRAD, stopping and starting it again.

Then, you need to initialize the server status. Not sure why, but you do. And apparently, you have to do that little initialize server status step in the server perspective every subsequent time you start up IRAD.

Sounds reasonable and straight forward. Surprised I didn't just do that on my own.

-Cameron McKenzie
knowledge is the difference between drudgery and strategic action -- tiny ad
Devious Experiments for a Truly Passive Greenhouse!
    Bookmark Topic Watch Topic
  • New Topic