Application server in WebSphere 6.1 ND not starting

We have WebSphere 6.1 ND installed on Windows 2003 server. I have just one Application server instance running in WebSphere. We take daily offline backups in the morning , prior to starting backup which is all automated we stop WebSphere app server using a stop script that is scheduled to run daily at 4:56AM. The script runs just fine.

However after the backup is run automatically the TWS (tivoli workload scheduler) is configured automatically to execute another batch script on the windows server to start websphere app server. This script has been failing to start app server since last Saturday morning for no reason. No patches were applied on the server nor to websphere it just stopped working. Only work around is I get paged and I login remotly onto the server and kick start the same script and IT RUNS JUST FINE. I have no clue whats going on since the same script starts app server when I run it manually and it is not when auto run by TWS. Can anyone throw some light on this issue. I am attaching the start script and the output of the script generated when TWS runs it for your reference. ANY HELP IS APPRECIATED.
Restart-LBI.bat.txt
startlbi.log
vemi007Asked:
Who is Participating?
 
AdminRAMCommented:
unable to start the server using scripts could be number of reason on v6.1

1) certificate is renewed and not propagated to trust.p12 of etc

2) having problem with javashared resources..
0
 
wasadmin11Commented:
can u paste the SystemOut.log
SystemOut.log(or job log in zOS) and other log files under
           D:\sys_apps_01\WebSphere61\AppServer\profiles\BaseLawsonWAS61_profile\logs\LawsonLBI_server
0
 
vemi007Author Commented:
Hello,

Sorry I missed sending the information. The log activity that I have that shows that websphere app server was not coming up is the script output. There is no activity in the StartServer.log nor in the SysltemOut.log that shows any signs of this issue.
0
KuppingerCole Reviews AlgoSec in Executive Report

Leading analyst firm, KuppingerCole reviews AlgoSec's Security Policy Management Solution, and the security challenges faced by companies today in their Executive View report.

 
ponrajk22Commented:
Check the file system space and let us know..........
0
 
wasadmin11Commented:
is there a SystemOut.log when u start manually ?
0
 
vemi007Author Commented:
No output in Sysltemout when the issue occurs, if the windows server is rebooted based oin your opinion could this be causing the anamoly ?
0
 
vemi007Author Commented:
No space issues on the server as well.
0
 
vemi007Author Commented:
The above options provided guided me in to the root cause of the issue. It was related file permissions being changed.
0
 
AdminRAMCommented:
Thank you for your point. I appreciate it..

Have a good day
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.