Skip to Content
avatar image
Former Member

MaxDB hanging up "Starting"

Good day,

I am running MaxDB with Netweaver CE on a VM. It was running fine for months when connected through cable at an SAP office. This week I went to support a conference where I also had a cable connection (though obvious not an SAP network connection) I couldn't get my CE instance to run. At that point MaxDb was running as I was able to start and stop. I had to change the Virtual Network Connections to get the VM settings to work. Then I could not get MaxDB started.

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, and though I have been given some suggestions by other colleagues, none of them really know MaxDb.

Any suggestions?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Oct 23, 2009 at 07:29 AM

    Hey Bob,

    lucky you that there in fact are some SAP colleagues that know a bit about MaxDB 😉

    Usually there will be entries in the KNLDIAG/KNLMSG file if there are problems during the startup phase.

    Have you checked this file?



    (SAP primary support - message solving, NEXUS for MaxDB)

    Add comment
    10|10000 characters needed characters exceeded

    • > Here is my log from KNLMSG Error

      Step to the directory where you have the knlmsg file immediately after your rebooted the machine. Then execute

      protconf > knldiag.txt

      Check the resulting textfile.