Hi All,
the problem was, that after doing client copy, the MaxDB LOG was full and then I will not react anymore if you dont backup the LOG.
I used one good programm Database Studio to free the LOG file and then the DB started working again. Its quite useful to activate automatic LOG Backup - if the log will full, it will be backup automatically and you will not experience the problem again.
According to SAP, my kernel is the newest one (701 Patch 69).
Thank you for your interest!
Mike
---------------Original Message---------------
From: Mike1981
Sent: Wednesday, May 05, 2010 9:17 AM
Subject: Dispatcher Running but not connected to Message Server
> Hello,
>
> Since yesterday I try to solve a problem with the Message Server and I didnt move forward. I looked already through other posts that are related to this problem. However as somebody said, the Solution depends on the System Version etc.
>
> How it happened? After started one of the transactions the System processed the request for more than 20 Minutes. So I was forced to kill the GUI with Windows Task Manager. After that I started the GUI again and wanted to log on to the System. Then I couldnt connect any more. After stop/start SAP and restart of the Windows System, after starting SAP, the System in the console was yellow and I got the message: "Dispatcher Running but not connected to Message Server"
> All the processes are working, only the Message Server not. If I log to the system now, I can do it only with SAP*, if I try another User, I get the message: “Licence expires”. For me, it means, that because Message Server doest work, the Licence Key cannot be checked.
> I didn’t change any parameter in the System.
>
> Here the trace file: dev_disp and dev_w0. Thank you in advance!!
> Michael
| __.____._ Copyright © 2010 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
| | Related Content White Papers
In the Spotlight  _.____.__ |
Mark as helpful
