Hello All, I have managed to install the trial version of WAS[AE]. Sometimes the console is up in 3-4 minutes but sometimes it takes more than 15-20 mins and it is still saying :Establishing Connection ,Please wait.... Can anyone please explain why this would be happening...? All the services are running okay and the log file does not give any info on this. [Configuration: NT,384MB ram,P2 HP machine] regards, Suchitra [This message has been edited by Suchitra VB (edited May 28, 2001).]
Suchitra VB
Greenhorn
Joined: May 25, 2001
Posts: 12
posted
0
Hi All, Please could someone help me out... I have to install WAS every alternate day... The console does not come up. i know i am playing with some configuration properties but don't know how to track them.The logs do not give why this fails...it says things like: Tue May 29 16:50:47 2001 - Error - ws_open_domain_client_socket - WaitNamedPipe Tue May 29 16:50:47 2001 - Error - ws_open_domain_client_socket - WaitNamedPipe Tue May 29 16:50:47 2001 - Error - ws_open_domain_client_socket return error Tue May 29 16:50:47 2001 - Error - ERROR: In do_service_time_request, connect_to_queue failed Tue May 29 16:50:47 2001 - Error - Error passing service/run request ... error 8 on clone 0 Tue May 29 16:50:47 2001 - Error - router_service : Failed 8 regards, Suchitra
John Dale
Ranch Hand
Joined: Feb 22, 2001
Posts: 399
posted
0
I just started with WAS(AE) on NT and was fighting something like this myself. It seemed I was able to start the Admin Console once or twice, but then never again. I think I could start it until I rebooted. I saw this with the full install (DB2) and, I think, with the Quick install (InstantDB). I think the problem started after I installed the full InfoCenter, or after I installed FP4 on top of 3.5. To avoid the problem and tind out what leads to it, I started over with just a 3.5 Full install, without the InfoCenter update and any fix packs. To do this, I carefully removed everything (uninstall FP4, then all components, then reboot and remove all directories, including the directory for the uninstalled DB2, if used), and reinstalled 3.5 AE Full install. In my initial operations this way, I've not seen the problem again. I think I found a post that might give a clue about this, but I don't have it with me. I'll pass it along tonight. Another problem I had, which I don't think is related, is that I first tried to install this using the NT "Administrator" account. This appears to have caused problems (error 10, as I recall), perhaps because some components truncate the NT account name to 8 characters. I'm currently using another NT account - a new account in my case. I use that account for everything associated with WebSphere: the DB2 account, and also, when I get around to it, the HTTP server account. As usual, any change leads to another problem if there is other software around. I happen to have Notes and Domino 5.0.x on the machine on which I'm learning Websphere, although I haven't run them at the same time. When I put Websphere under a different NT userid than used for Notes/Domino, I saw dialog boxes about missing DLLs from db2nq.exe: js32.dll and then ccstr.dll, I think. I've worked around these by ensuring that the Domino (or Notes) directory that contains js32.dll is in the NT path for that userid - actually, I now put it in the system path. I've found reports suggesting that once the release of Notes and Domino I use are installed, you need the Domino directory in the path for some "net query" commands to work. I'll follow up with the pointer to the note about InfoCenter and the admin console tonight. After I get a few evenings of experience with WAS, I'll try to install InfoCenter and FP4.
John Dale
Ranch Hand
Joined: Feb 22, 2001
Posts: 399
posted
0
Does this post from ibm.software.websphere.application-server look like it refers to the problem you are having? Like I said before, I'll try the fixpack and InfoCenter update after I have a bit more experience. <pre> From: "Mike Spradbery" <msprad@uk.ibm.com> Subject: Re: Infocenter.jar Date: Friday, May 25, 2001 9:50 AM Hi, I had this problem. Go to x:\websphere\appserver\web\infocenter\was (where x: is the drive you installed was on) and edit the file helpfile.txt using wordpad. You will find that you have two blank lines at the end - delete one of them so there's only one blank line. Save it and try to start the admin service again. The error you were getting trying to start the console is because the WS admin service hasn't started correctly (even though it looks OK on the services panel). So once you've re-started the admin service, you should be able to successfully restart the console. Hope this makes sense - if not, email me. Cheers, Mike. msprad@uk.ibm.com
Ellis wrote: > I was having problems with an upgrade to WAS AE 3.5.3 and decided to > delete and start fresh. Everything works well now, however when I try > to apply the latest Infocenter.jar file (24.3Mb) from the web site WAS > Console just hangs when I try to start. I install my old infocenter > file and everything works fine. Anyone else having similar problems? > > Ellis </pre>
Richard Bassemir
Greenhorn
Joined: Dec 09, 2001
Posts: 2
posted
0
Thank you, thank you, thank you Deleting the extra blank line in the helpfile.txt fixed my problem and I was able to start the admin client. Never in a million years would I have found that error. I could find nothing in the logs to indicate what the problem was. Thanks for taking the time to post those instructions
0
