Hi all,

I had installed TAMeb 6 in a windows server 2003 environment. I had ITDS, Po
licy and WebSEAL servers on separate physical servers. All components are ve
rsion 6, i.e. WAS 6, HTTP server 6.0 and ITDS 6.0.

I am trying to configure Websphere and ITDS services to start automatically 
on the ITDS server to minimise user intervention after server reboot.

Both HTTP Administration and Server services were set to automatic and start
ed without any problems. I set the startup type of WAS service to Automatic.
 However, the service is not started after reboot.

I found the following in the System event log with Error event id 7024.

?The IBM WebSphere Application Server V6 - Node01 service terminated with se
rvice-specific error 1 (0x1).?

I also see the following in the Application event log with Error event id 10
9.

===================================

Event Type:	Error
Event Source:	IBMWAS6Service - Node01
Event Category:	None
Event ID:	109
Date:		1/03/2006
Time:		5:02:44 PM
User:		N/A
Computer:	xxx
Description:
Could not determine the process id of the Java process. Changing the IBMWAS6
Service - Node01 service status to the "stopped" state.  To prevent this err
or, try recreating this service with the -logRoot parameter.  The value of t
he logRoot parameter should
be the directory in which the server's .pid file is created.

===============================


What is the correct way/order to start Websphere and ITDS service on the ITD
S server?

Thanks!

[ Post a follow-up to this message ]

Sean,

As the message suggests, recreate/update the WebSphere Windows service.

This can be done using the wasservice.exe utility under <WAS_HOME>\bin

Search the WebSphere 6 InfoCenter
(http://publib.boulder.ibm.com/infoc.../v6r0/index.jsp) for
wasservice for some more options.

Hope this helps.

Charly Oz.

<seanng@microhelp.com> wrote in message
news:1131628793.1141714659011.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> Hi all,
>
> I had installed TAMeb 6 in a windows server 2003 environment. I had ITDS,
> Policy and WebSEAL servers on separate physical servers. All components
> are version 6, i.e. WAS 6, HTTP server 6.0 and ITDS 6.0.
>
> I am trying to configure Websphere and ITDS services to start
> automatically on the ITDS server to minimise user intervention after
> server reboot.
>
> Both HTTP Administration and Server services were set to automatic and
> started without any problems. I set the startup type of WAS service to
> Automatic. However, the service is not started after reboot.
>
> I found the following in the System event log with Error event id 7024.
>
> ?The IBM WebSphere Application Server V6 - Node01 service terminated with
> service-specific error 1 (0x1).?
>
> I also see the following in the Application event log with Error event id
> 109.
>
> ===================================
>
> Event Type: Error
> Event Source: IBMWAS6Service - Node01
> Event Category: None
> Event ID: 109
> Date: 1/03/2006
> Time: 5:02:44 PM
> User: N/A
> Computer: xxx
> Description:
> Could not determine the process id of the Java process. Changing the
> IBMWAS6Service - Node01 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.
>
> ===============================
>
>
> What is the correct way/order to start Websphere and ITDS service on the
> ITDS server?
>
> Thanks!

[ Post a follow-up to this message ]