J2EE Server doesn't start

[#1]

I was doing a deployment from a WebDynpro application which stopped responding and stayed there forever.

To get around this I shut down dev studio and then stopped the J2EE server using the MMC.

Now when I try to restart, the server doesn't start again.

Any pointers appreciated,

[former_member5350]

We had the same issue with root cause full data log, and we solved it the following ( extract from a document created after we found the solution):

<b>Applies to</b>

SAP WAS 6.40 SP 13 including

J2EE Engine 6.40 PatchLevel 95420. 313 on

Microsoft Windows 2003 Server with SP 2 using / connected to

SAP DB.

<b>Issue</b>

The J2E engine doesn't complete the startup process successfully.

In SAP MMC status is "Some processes running..."

<b>Indication</b>

The instance is marked yellow. The application server therefore can't be accessed, deploying of applications via SAP Netweaver Developer Studio is not possible.

<b>Possible problem</b>

It seems that the underlying databases' full log-table/-file is causing the problem,

while the options are set as below:

auto-log : on

log overwrite : on

<b>Solution</b>

Possible solution to this is to clear log table by backup the existing data and log data. It was found out that the system obviously clears the log automatically afterwards.

<b>How-To</b>

To get this to work, do the following:

On server-side start the Database Manager and

log on to you database by

selecting the instance and the connect to button

and providing username and password for logon.

Select Backup Wizard from the left pane and choose the Backup-Wizard. on the Welcome screen click "next".

Now select "Log Backup" and select a backup medium on the following screen (you have to create one if no exists).

Click "next" and "Start". The backup will be started.

If you get an error message such as “error 24998 “, you have to switch off

the “log overwrite” mode via Configuration -Configuration Wizard.

The Log Backup will be performed and then the log-table will be cleared.

Now you can restart the server - instance as usual via SAP MMC.

<b>Conclusion</b>

It worked for us with the limitation that we switched off log afterwards.