Error in starting MDM Server from MDM Console

[Former Member]

Hi,

I have installed SAP MDM 5.5 SP05 on Windows 2003 Server.

When i try to start the MDM Server (i.e. MDM Service) from the MDM console it gives me the following error:

<i>Error Starting apmdmd(MDM Server): The machine 'apmdmd' is not Windows-based. The MDM server cannot be started from this application; please use CLIX on the machine instead. </i>

But if i start the MDM Service manually and then mount the server, it works fine.

Kindly help.

Regards,

Chintan Sheth

[Former Member]

Hi ,

Can any one please tell me how to start the MDM from the console ? I have installed MDM5.5 SP04 on UNIX box. After the install, in the MDM_HOME/bin, I have CLIX. But, I have no idea how we get the MDM console. Please let me know.

From CLIX, I am using the command " clix mdsStart hostname" to start the MDM, but then I get an error in the nohup.out as follows "Loading '/usr/sap/MD5/MDM/LangStrings/Networking.lang' (English)...

bind() failed in ServerListeningSocket::Create() with errno 000000E2 : Address already in use\"Initialization failed, error code = 0x83000000"

So, I am not sure what is wrong. Please help me start the MDM server.

Your quick reply is highly appreciated. Thank you

[Former Member]

Hi Chaitan,

<b>I faced the same problem Initailly.</b>

I installed the MDM Server for windows and got the same error.

I changed the logon credentails in services.msc and started the server once from services.msc

Get Back for help

Vijay

[former_member278106]

Hi,

In the MDM Console you may only use hostname, fqdn or ip number; not any type of aliases.

Regards, Lev

[Former Member]

Hi ,

I also installed SAP MDM SP05 . I got the same error as the one u got . I even tried to use CLIX to start the MDM server. But the MDM server never responded. The best way is as follows ( it worked for me )

Remove all the MDM components from the System and also oracle . Re-install all the MDM components and oracle. While installing Check on the MDM server ( 32 or 64 bit ). Choose the correct one . Check the mds.ini and mdis.ini files. Now try mounting the MDM server on the MDM Console. It will mount and u can aslo start the MDM server from the Console itself .You need not use the Clix to start the MDM Server. This should solve the issue .

[Former Member]

Hi Ramakanth,

I am able to use CLIX to start MDM Server but not using console.

I had also tried removing all MDM components and reinstalling it, but didnt work.

[Former Member]

Someone plz help me on this..

[Former Member]

Hi Chintan

I encounter the same message on VMWare Virtual Machines. I simply use the same workaround you mentioned - starting mds from the Windows Services. Is it absolutely required that the mds be started from the Console?

CLIX may work - I haven't tried it. You could also use "net start".

Mark

[Former Member]

Hi Mark,

Thanks for the reply.

Yes. It is important for starting the mds service from the Console. This is because the functional users do not have access to the server and they can only start the service from the console.

Is there any solution for this?

I have no idea on using CLIX. Will also check that.

Regards,

Chintan Sheth

[Former Member]

Can someone plz help me in resolving this problem.

[Former Member]

Hi

May be this note would help you out: (Check the pre-requisite section)

Note 967088 - SRM-MDM Catalog 1.0 Installation & Configuration

Thanks

[Former Member]

Hi,

The CLIX command to start MDM server is :

<b>CLIX mdsStart MDMHostSpec [-D]</b> but am not sure whether it will work on UNIX/LINUX.

Also use <b>mdsHelp</b>, to get more Server related command help with description...

Hope you issue might get resolved using the above informations...

thanks

Alexander

[Former Member]

Hi,

Thank u all for the reply.

Is it necessary to use CLIX only to start the MDM Server ?

Can't i start the MDM Server from the Console itself ?

Regards,

Chintan Sheth

[Former Member]

Basically its an method to Start the MDM server, depends on the platform you can use either of those...

thanks

Alexander

[Former Member]

Yes it will start the MDM Server in both the cases, but when i start MDM Serevr from the console i get the error:

"<i>Error Starting apmdmd(MDM Server): The machine 'apmdmd' is not Windows-based. The MDM server cannot be started from this application; please use CLIX on the machine instead</i>"

I can also start the MDM Server by manually starting the MDM service.

But if i want to start the server using console then how do i overcome this error?

Regards,

Chintan Sheth

[Former Member]

Hi Chintan,

I am not sure even the message says that " The MDM server cannot be started from this application; " ....

let me explore more about this and revert back wt some solution...

thanks

Alexander

[Former Member]

It sounds to me like a problem potentially with either the permissions of the Windows user or perhaps a software firewall. The Console uses a low-level Windows API function to determine if the target machine on which MDS is installed is Windows-based. This function may be blocked by some OS or firewall-level setting. This may be the case even if you are able to use the same client machine to connect to the target machine via the Service Control Manager and start MDS from there.

I would like to help with this problem, but I need to know a few more things:

When the problem occurs, is the Console running on the same Windows machine as MDS?

You mentioned Windows 2003 Server... when you run the Console on this machine, are you logged in as an Administrator of the machine? And do you still get the error when you attempt to start MDS from within the Console?

Once MDS is started, and you mount it within the Console, are you having any other problems, such as logging in to a repository, or viewing logs?

Is there a firewall installed on the machine or machines that the software is installed on? We may have to review the settings of the firewall, or try temporarily disabling it (on both ends, or at least on the machine running MDS), to see if the problem goes away -- then we'll know the problem is with the firewall settings.

CLIX is a fine workaround if you can use it, but clearly this problem needs to be rectified.

-cleo

[Former Member]

Hi,

I cannot start MDM Server form any machines using the console, not even from the machine where the MDM Server is installed with user having administrator rights. So i think there is no issue of firewall also.

The error is

<i>Error Starting apmdmd(MDM Server): The machine 'apmdmd' is not Windows-based. The MDM server cannot be started from this application; please use CLIX on the machine instead. </i>

And once i start the mds service manually, i can work well with repository without facing any problem.

Regards,

Chintan Sheth

[Former Member]

Hi Chintan,

A software firewall could still interfere, even when running the Console on the same machine as MDS. Could you please see if a software firewall is running on this machine, and temporarily disable it, to see if that makes the problem go away? (Typically if no third-party firewall has been installed, the Windows firewall will be enabled.)

Since we are not experiencing this problem in the development environment it's a bit difficult for me to diagnose it other than to just guess... and the API function that is being used has no documentation about what could cause it to fail in this way.

Thanks for the help!

-Cleopatra

[Former Member]

Hi Von,

I have already disabled the firewall.

The problem is still there.

Regards,

Chintan Sheth

[Former Member]

Hi Chintan,

You're running Windows 2003 Server, right? What is the service pack level? Have all security patches been applied (meaning if you go to Windows update, does it recommend any critical updates)? Service pack 2 for 2003 Server was just released, and has potentially closed some access to machines that would affect the API function we're using. I haven't tried this myself yet, but it would be good to know if your environment is different from ours. If it is, I will update my machine to see if I can break it with the latest patches.

Is NetBIOS disabled for your network? This would prevent the API function from working.

Try this:

On the server, open a command prompt window and run the command: net use
<servername> "" /user:""

(replace only the servername in this command; do not provide a user)

Does the command complete successfully? If it does not, that means the NULL user has been disabled on this server, and a variety of Windows API functions will no longer work.

Have WINS client or NetBIOS bindings been diasabled for the server's NIC? Maybe the system administrator would be able to answer this question.

When you mount the server in the Console, are you providing the name of the machine? Without
in front of it, right? Could you see what happens when you put in localhost instead? Also please try the IP address.

Thanks,

Cleopatra

[Former Member]

Chintan,

Did you try the suggestions I made in my post from May 24th (re. checking to see if NetBIOS or the Null user have been disabled)? Did you discover anything?

Thanks,

Cleopatra

[Former Member]

Hi Cleopatra,

Well sorry for my delay.

I checked out all things that you mentioned but didn't help me.

I have raised an OSS for the same.

Regards,

Chintan Sheth

[Former Member]

Chintan,

I hope you will provide answers in the OSS message to the questions I had posted above, because all of that information will be needed in order to solve the problem (or at least determine what the problem is). If the problem is what I think it is, related to the function NetServerGetInfo, that function is no longer being used in SP5 Patch 2 Console.

Regards,

Cleopatra