Hi , I'm trying to install WAS 3.5 on NT and am getting the foll error when i try to start WS ADmin service. I'm using oracle as the database. The IBM WS AdminServer service returned service specific error 10 I consulted ibm site and it was suggested that if ... and you encounter this error (in the Services panel on Windows NT): The IBM WebSphere AdminServer service returned service specific error 10 Add a newline character at the end of the administrative server configuration file. I did this too and still get the same error help me, thx in advance, Guna
"email@example.com" The Java Ranch has thousands of visitors every week, many with surprisingly similar names. To avoid confusion we have a naming convention, described at http://www.javaranch.com/name.jsp . We require names to have at least two words, separated by a space, and strongly recommend that you use your full real name. Please log in with a new name which meets the requirements. Thanks. ------------------ Mahindrakar IBM Application Server & Developer Forum Moderator Consultant - Zensar Technologies ,Pune India. SCJP2, SCJD2 & SCJEA (Part I)
Joined: Jul 28, 2000
Is this the first time that you are installing the WAS Server. If so then go in for the the default installation. You can practice working on the 3.5 default implementation and then move to oracle based backend. To undertake oracle installation you have to have some experience with installations. It is difficult. If you still want to install oracle then I can help you out. Write it here and I will tell you how. If you are learning WAS then I suggest you start working on the WAS 4.0 rather than 3.5.
First thing I do after an install: What user id are you trying to Start the Services under? I usually change, via the control panel, the services startup id to an generic WasServer id I have created. This id has the correct privilages level for running IBM WAS, HTTP and DB2. Peace Steve
Go step by step... check whether your WAS database is created.. if not created then create the table by executing the scripts provided in the bin directory .. check the logs folder for the error. When i encounter the problem its because of the java.exe's running in the background .. i kill them and then start again .. but since yours is not getting started in the first place .. maybe some other problem that the username and password of the database might not be entered correctly ? or the actual machine where the database is has not entered properly in the WAS installation Steps ------------------ IBM Certified WebSphere Application Server V3.5 Specialist
I was having the same problem installing WAS 4 fixpack 3 or higher, it was resolved by adding c:\winnt\system32 to the "path" environment variable and reinstalling the fixpack... something to do with the xcopy command failing.