MAXDB service (Windows XP) remains 'Starting'

[Former Member]

Dear experts,

I'm running MaxDB with minisap trial version (Netweaver 7.01). It was running fine for months. This week I couldn't get my instance to run. The computer was locked on starting sometimes. I could see the cause on Windows Services: MaxDB was showing STARTING and didn't have any options for Stop or Restart. The only way to stop it was to restart or shut down Windows.

In Windows Services, I had to change the setting back to Manual (from Automatic). By restarting Windows I get it to shut down, but when I start the Service again, it opens very slowly and then right before completing the operation it throws up an Error Message 1053: service couldn't start in timely manner. It doesn't stop the service, it keeps running and shows STARTING.

I tried killing kernel.exe in Task Manager, but it just restarts again. It seems like there is something else going on, I don't know how to solve the problem.

Any suggestions?

Thank you very much,

Sergio

[markus_doehr2 · Accepted solution]

Did you do a full backup since you installed the system? And/or a log backup?

Execute

x_cons <SID> sh ac 1

after your restarted the service.

What do you see?

Markus

[Former Member · Accepted solution]

Hello Markus,

I never made any backup of DB.

After restart Windows, I tried to start NSP Service and remains STARTING like always. The command I had execute is this:

x_ cons NSP sh ac 1

and the anwser is a bucle like this

SERVERDB: NSP

ID   UKT  Win   TASK       APPL Current         Timeout Region     Wait
          tid   type        pid state          priority cnt try    item

ID   UKT  Win   TASK       APPL Current         Timeout Region     Wait
          tid   type        pid state          priority cnt try    item

ID   UKT  Win   TASK       APPL Current         Timeout Region     Wait
          tid   type        pid state          priority cnt try    item

ID   UKT  Win   TASK       APPL Current         Timeout Region     Wait
          tid   type        pid state          priority cnt try    item
...

I had to stop it using CTRL + C.

In Windows Services I can´t stop or restart NSP service, it remains STARTING until I restart Windows.

It's seems like NSP service is locked. Any idea?

Thank you very much.

Regards.

[Former Member]

I could fix it renaming two files as it been explained here:

Thank you very much to all anwsers.

Regards.

[valeriocicchiel]

Hello Sergio,

you can try to see in the log files of MaxDB where the service stops

Another question: did you install something recently that could interfere with MaxDB? Probably MaxDB is not able to open network ports it needs are remains stuck

Valerio

[Former Member]

Hello Valerio,

Where are these logs and what are their names?

I don't remember If I installed somehing recently. I think I didn't.

Thank you very much for your help.

Sergio