cancel
Showing results for 
Search instead for 
Did you mean: 

MDS is shown as an invalid status even though it is Running

Former Member
0 Kudos

Hello guys,

MDM server connected on the MDM Console getting disconnected very frequently and giving message as "Connection to the Server lost" And even after remounting the MDM Server via the MDM Console, the server status icon showing status is stopped. When i try to start the MDM server with the MDM console fails with the error message "Instance already started".

However, SAPMMC shows that the mds instance icon is green meaning that the Server is running. This is happening very frequently.

Additional Information:

MDM Server is on MDM 7.1

Memory size is 16.00GB

Total Repositoris mounted on this Server: 6

Another MDM Server installed with same version is working fine

Could any body suggest

Thanks & Best Regards

Vema

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Vema,

Please refer to SAP notes 1355666.

Regards,

Silpa

Former Member
0 Kudos

Hello Shilpa,

In Note 1355666 it has been mentioned that, to restart the instance on SAPMMC console. and true. if i restart the instance in SAPMMC, i could able to remount again on Console. But this is happening very frequently say twice in a week (but not at perticular time) every time i have restart the instamce which is a show stopper. So is there any permenent solution or do i need to check any configurations which is making this effect?

Best Regards

Vema

Former Member
0 Kudos

Hello Vema

My point of view, you have bad connection(or periodically network connection broke) to MDM Sever in your local network

Regards

Kanstantsin

Former Member
0 Kudos

Hello Guys,

This may not be the reason. as i do not have this problem with other MDM server. and also Network configuration as same as another one

Best Regards

Vema

Former Member
0 Kudos

Hello guys,

When problem existed there were 321 opened connections from which 119 were in the CLOSE_WAIT state. But how do i check that the clients with status CLOSE_WAIT are terminating a connection on the MDM port.?

Best Regards

Vema

former_member189669
Active Participant
0 Kudos

Hi Vema,

Please perform the below checks. One of them might be the possible reasons.

1) Set appropriate connection parameters to oracleDBMS (SAP Note 1325833)

2) Core dump file - Gets created when server crashes.Check for existence of core dump and delete if existing.

3) Might happen due to port lock.

Netstat |grep <portnum > check if port is locked. Release port if locked.

4) Ensure network bandwidth parameters are properly maintained .Refer SAP note 1278497

Please let us know if you are able to crack this issue.

Regards,

Vinay M.S

Former Member
0 Kudos

Hello Vinay,

Thanks. I was able to find the reason. i.e the point 3 what you have mentioned here.

But my MDM servers and DB are on Windows and MSSQL respectivly. Here how can i release the Port which is showing as CLOSE_WAIT ? Can you please suggest for Windows?

Best Regards

Vema

former_member189669
Active Participant
0 Kudos

Hi Vema,

Try unmounting the repository and mounting it back on a different port. Ensure you provide a diff port number between 2000 and 9999.

Regards,

Vinay M.S

Former Member
0 Kudos

HI Vinay,

Sorry i have a problem with MDM server connection. not the Repository. and more over all the repositories are with diff. port.

Please check my issue and request in above note. and help me in this

Best Regards

Vema

former_member189669
Active Participant
0 Kudos

Hi Vema,

Sorry. Pl ignore my previous reply.

Please refer to SAP note 1391296 which closely matches to your scenario .Only difference - this is applicable to Solaris OS.

As we see in the note, control for TCP/IP is stored in tcp_time_wait_interval parameter.

As equivalent to this, in Windows OS it is maintained in Win Registry settings -TcpTimedWaitDelay .

Please execute this -

1.Start >Run > Regedit > Windows registry settings window opens.

2.Navigate to - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
TcpTimedWaitDelay

It can range from 30-300 seconds. The default is 240. You can set this to 60seconds.

Can you please try and update us if this resolved ?

Alternately, suggest you to raise an OSS note for this as SAP note doesnt for Windows OS.

Regards,

Vinay M.S

Edited by: Vinay Simha on Oct 27, 2009 10:07 PM

Former Member
0 Kudos

Hi Vinay,

I could able to Navigate up to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.

But could not find "TcpTimedWaitDelay" parameter there. do you mean we have cteate this parameter there?

Best Regards

Vema

former_member189669
Active Participant
0 Kudos

Hi Vema,

For any server runing on Windows , TCP/IP parameters are maintained in this path. Not sure why this is absent and need for creating it.

Can you please raise an OSS for this ? Lets see what SAP suggests for this.

Regards,

Vinay M.S

former_member189669
Active Participant
0 Kudos

Hi Vema,

Please clarify - 'Another MDM Server installed with same version is working fine' - Are you running another MDM server on same machine ?

Regards,

Vinay M.S

Former Member
0 Kudos

Hello,

I mean, Another MDM Server of same version is installed on different host with similar environment.

But now we could ablte find the root cause. here... when no of connections thro' TCP from client side exceeds or when some of the connections goes to CLOSE_WAIT state., this problem occurs.

Now the issue is how to overcome this?

As mentioned by Vinay above, I am trying to edit registry setting for HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters.

But here "TcpTimedWaitDelay" parameter is not found iam little bit confused here. whether i need to create a new paramete here if so in which form?

Best Regards

Vema

former_member189669
Active Participant
0 Kudos

Hi Vema,

Please check if you are using MDM Version 7.1.03 . Starting this version MDM will be using diff TCP ports for its operations.Please refer to SAP Note 1359600 - MDM stopped communicating after upgrading to 7.1.03 elaborating on this.

New ports are :

Application Old Port # New Port #

MDS 20005 59950

MDLS 20008 59650

MDIS 20009 59750

MDSS 20010 59850

Also,please compare the port settings in another server running normally.

Regards,

Vinay M.S

former_member189669
Active Participant
0 Kudos

Hi Vema,

Please update if you could crack this issue?

Regards,

Vinay M.S

Former Member
0 Kudos

Hi Vinay,

Problem still persists. but i have not edited the Registry as you mentioned. iam not sure about how to add this parameter "TcpTimedWaitDelay " in parameters folder.

We are using 7.1.04.36 version. And as you mentioned, ports used for MDM server are 59950.

Can you help me entering this parameter in Registry? like in which form i have to select like word? or someother form?

Best Regards

Vema

former_member189669
Active Participant
0 Kudos

Hi Vema,

I think this gets created in Registry during server installation. Not sure why this is missing. And, I too dont know how to add an entry into Windows registry manually.

Alternately, you can take help from System adminstrators or raise an OSS note.

Regards,

Vinay M.S