So.I was doing a install verification on WAS 6.0 by using this command from
QSH:
/QIBM/ProdData/WebSphere/AppServer/V6/edition/bin/ivt server1 default
And it was taking forever to start.so I went into the HTTP Admin panel and
tried to start the WAS server there. Then that one hung up too.
I waited about 45 minutes for either one to finish and when they didn't, I
finally said screw it and I did a controlled IPL and restart. Now when my
system came back up, I get an error when clicking on the IBM Web
Administration for iSeries link from the HTTP Admin web page of my system.
So I cannot get into any the admin configuration pages.
When I look at the job log for the ADMIN server instance, I see this error:
QSYS/CALL PGM(QSYS/QLWISVR) PARM('Admin')
Object copied.
Product information not found.
Product information not found.
Product information not found.
Product information not found.
Product information not found.
Product information not found.
Product information not found.
Product information not found.
Product information not found.
Product information not found.
And the extended help on those errors are:
Recovery . . . : The product ID 5722IWE, release *ONLY, product option
0002,load ID *CODE and format PRDR0100, requested is not valid. Specif
valid product and format information then try the request again.
Recovery . . . : The product ID 5733WS5, release *ONLY, product option
0002,load ID *CODE and format PRDR0100, requested is not valid. Specify
valid product and format information then try the request again.
Etc..
It appears to me that it is looking for WAS 5.1 which had been on this
system earlier but I removed it. Now I'm thinking that just doing a
RMVLICPGM on that old version of WAS was not enough and that there were
other steps I should have followed to get rid of it. This is the first IPL
I've done since I removed that older version of WAS.
Anyone experienced this problem before?
I wonder if I could just reinstall WAS 5.1 and then it would see that
product and I could get back into my iSeries Web Admin panel again?
Or maybe I could just change the httpd.conf file for the ADMIN server?
I'm hesitant to do too much at the moment as I don't want to compound the
problem.
Ideas?
Shannon O'Donnell
As an Amazon Associate we earn from qualifying purchases.