on 07-20-2009 12:46 PM
Dear All,
While trying to install a DI I am getting the following error:
#############
An error occurred while processing service SAP CRM 5.0 Support Release 3 > Software Life-Cycle Options > Application Server > MS SQL Server > Dialog Instance( Last error reported by the step :Caught ESAPinstException in Modulecall: in getMsPort() rdisp/msserv_no not possible. You need a newer message server..). You may now
choose Retry to repeat the current step.
choose View Log to get more information about the error.
stop the task and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/CRM05/LM/AS/MSS/DI.
#############
The log says the following:
INFO 2009-07-20 05:21:54.298
Disconnect from message server (UT1VC7P01/3901) succeeded.
ERROR 2009-07-20 05:21:54.298
CJS-00030 Assertion failed: in getMsPort() rdisp/msserv_no not possible. You need a newer message server.
ERROR 2009-07-20 05:21:54.376
MUT-03025 Caught ESAPinstException in Modulecall: in getMsPort() rdisp/msserv_no not possible. You need a newer message server..
ERROR 2009-07-20 05:21:54.470
FCO-00011 The step getMsPort with step key |NW_DI|ind|ind|ind|ind|0|0|NW_GetSidFromProfiles|ind|ind|ind|ind|1|0|NW_checkMsgServer|ind|ind|ind|ind|2|0|getMsPort was executed with status ERROR ( Last error reported by the step :Caught ESAPinstException in Modulecall: in getMsPort() rdisp/msserv_no not possible. You need a newer message server..).
##############
Please share your views on what could be missing here.
Thanks a lot for your help and time,
Shival
Hi Shival,
If its a production system, its recommended not to change the control.xml without SAP's permission. (if its a sandbox and not that important to you, then you can definitely play around)
Can you please check if rdisp/msserv_no parameter is set in the SAP system or not. if set whats the value?
Regards
Debasis.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Interestingly enough the installation went through by restoring the original kernel files, i.e. kernel fils as soon as the CI installation was completed.
I have upgraded kernel on CI now and am facing another issue of "Dialong Queue info Unavailable".
Not sure if I should open up a new thread for it.
Please let me know your views/ideas on the above.
Thanks a lot for your help and time,
Shival
Refer this,
If this dosent resolve Ur issues,
provide us Ur system details like(SAP version/DB/OS/patch level of both Kernel and SP)
Regards,
Ravi
Hi Shival,
Refer SAP note for this problem. This looks like a kernel mismatch / parameter value problem.
https://service.sap.com/sap/support/notes/396309
You may also refer the existing thread which says about the similar problem.
Regards,
Debasis.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.