Question:
In the system log there is an error stating that the client PRDAPP1_PRD-00 is not known to the MS. The documentation for the error says that the message sent to the client which has not logged on to the MS. The possible reason may be that the client is not started or the parameterization in wrong. But during the error time there was no significant effect on the system. Later on autmatically it stopped.
Please advice what may be the problem and if it happens in future what to do ?
Thanx
Answer:
I had that errors a few months ago, and asked OSS for advice with no results (all their answers were too vague). I think that this may happen due to network, CPU or memory overload. I have experienced that, in high workload in the application server box, the MS cannot receive a response to a requirement in a certain time. So, system raises the error, as a connection to the app server, or from app server to ms server had been not possible. Have a look at the workload history so you can check whether there is a relation between the error and system overload, or not.
Answer:
Is this a CI or an AI(DI)?
If its an AI it might have to do with profile parameters
Answer:
check profiles as ileola says especially abap/buffersize. I hit the same wall a month back with all the apps and for some weird reason one of the apps worked when i reduced that parameter to 150000.
Answer:
This indicates that you have an environment with a CI/DB instance and one or more application instances on different hosts. And one or more of these instances is down and not reachable. I am guessing PRDAPP1_PRD-00.
Answer:
yeah... could be one of the instances was down... but learnt something from the below
check profiles as ileola says especially abap/buffersize. I hit the same wall a month back with all the apps and for some weird reason one of the apps worked when i reduced that parameter to 150000.
didnt knew that profile parameters could cause this as well
_________________
The heart has its reasons which reason knows not of
PASCAL
Answer:
I must say, this error occurs even when all the instances are up and running. There was no reason for this error to happen, and however it happened!
Answer:
They may all be up and running, but are they all talking to one another?
Answer:
check profiles as ileola says especially abap/buffersize. I hit the same wall a month back with all the apps and for some weird reason one of the apps worked when i reduced that parameter to 150000.
But doesn't that mean that the instance wasn't all the way up to begin with? A abap/buffersize parameter value that is too high may keep an instance from getting the last "SAP initialization complete" message in the log.