I am installing Lawson on a development server. (Windows and SQL db) I have completed all prereq installs, LID, Portal, LDAP/ADAM, LSF9 v9.004, IIS, websphere application server ND v6.1 fixpak 17, Lawson Security, RM, etc. Everything is lovely and operational. EXCEPT - I cannot start websphere application server as a windows service. The WAS will start from command line using start_win_was.bat. The WAS will start from start>>all programs>>IBM Websphere>>Application Server ND v6.1>> Profiles>> blah blah blah.
Here is the command I used to create the windows service for the dmgr: WASService -add JKDCVX19CellManager01 -servername dmgr -profilePath e:\Websphere\AppServer\profiles\Dmgr01 -wasHome e:\Websphere\AppServer\ -configRoot e:\Websphere\AppServer\profiles\dmgr\config -logFile "e:\WebSphere\AppServer\profiles\Dmgr01\logs\JKDCVX19CellManager01 Service.log" -logRoot E:\WebSphere\AppServer\profiles\Dmgr01\logs\dmgr -restart true
When I attempt to start websphere as a windows service I recieve this error: Event Type: Error Event Source: IBMWAS61Service - JKDCVX19CellManager01 Event Category: None Event ID: 109 Date: 2/9/2009 Time: 10:53:33 AM User: N/A Computer: JKDCVX19 Description: Could not determine the process id of the java process. Changing the IBMWAS61Service - JKDCVX19CellManager01 service status to the "stopped" state. To prevent this error, try recreating this service with the -logRoot parameter. The value of the logRoot parameter should be the directory in which the server's .pid file is created. I call myself having completed dev install just like my prod install... but....