MDM Server problem

Hi All,
I am new to MDM. If I load some repositories with the server.
it stops sometimes.why it happens.Even Log don't gives any information.
Please tell me some suitable suggestions.
Thanks
New User

Hi,
In this case
It seems that MDM server discovered some tables having duplicate data, voilating the Unique constraint. In such cases it appends a field to the repository and sets it as Unique. This resolves the problem and enables you to load the repository. You then have to clean the table and then delete the field added by MDM server.
Try to repair the repository and load it again.you will get the solution.
and Uninstall your Console and Reinstall it again.
Stop MDM Server, Go to mds.ini file remove all enteries for Repositories and then start server again.Check your server version and console version compatibility.check the memory of machine on which server is installed. It may cause problem while loading or unarchiving repositories.
I guess it might help.
Please reward.
Rgds
Deepak

Similar Messages

Problem while creating JCA connection to MDM server

Hi All,
I have restarted my mdm connector(com.sap.mdm.tech.connector) along with the applications related to Enrichment Controller. All applications restarted successfully. After that I tried accessing the URL
http://MDMSERVER:50000/MDM_EnrichmentController/WorkflowPolling?process=Monitor
but I am getting following exception in this page
Polling Repository
    name=Vijaybabu_Repo_on_MDMSERVER, status=No repository connection, error description=com.sap.mdm.net.ConnectionException: Problem while creating JCA connection to MDM server MDMSERVER
        Enrichment Request Threads
Could somebody help me pointing if something I have missed..
Thanks and Regards,
Manoj

hi Swarna,
I have verified the repository and found 0 fatal errors, 0 non-fatal erros and 0 warnings. I also checked the MDM Factory and Connector service is running fine.
The detailed exception is
Sep 2, 2008 12:49:40 PM com.sap.mdm.logging.MdmLogger error
SEVERE: Problem while creating JCA connection to MDM server 'KOLAPON'
com.sap.mdm.net.ConnectionException: Can not resolve JCA connection
     at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:119)
     at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnectionAccessor(JcaConnectionUtil.java:62)
     at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:70)
     at com.sap.mdm.internal.session.JcaConnectionAccessor.reserveConnection(JcaConnectionAccessor.java:59)
     at com.sap.mdm.repository.commands.GetRepositoryStatusCommand.execute(GetRepositoryStatusCommand.java:67)
     at com.sap.mdm.enrichment.common.ECAdminUtils.getRepositoryStatus(ECAdminUtils.java:125)
     at com.sap.mdm.enrichment.common.EnrichmentUtils.validateRepostiryConfiguration(EnrichmentUtils.java:889)
     at com.sap.mdm.enrichment.common.EnrichmentUtils.getCatalogManager(EnrichmentUtils.java:144)
     at com.sap.mdm.enrichment.workflowpolling.PollingThread.getCatalogManager(PollingThread.java:166)
     at com.sap.mdm.enrichment.workflowpolling.PollingThread.run(PollingThread.java:102)
Caused by: com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: "ConnectionManager" is closed. Possible reasons: 1) connector "MDM Factory" is stopped or not started, 2) Connector service is stopped or has not been started.
     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:223)
     at com.sap.mdm.internal.session.JcaConnectionUtil.getJcaConnection(JcaConnectionUtil.java:108)
     ... 9 more
Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: "ConnectionManager" is closed. Possible reasons: 1) connector "MDM Factory" is stopped or not started, 2) Connector service is stopped or has not been started.
     at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:122)
     at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:213)
     ... 10 more
Regards,
Manoj
Edited by: Manoj Kumar Nanda on Sep 2, 2008 9:21 AM

Error in starting MDM Server from MDM Console

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

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

Error Message in MDM Server Log

Hi Experts,
Can anybody tell me what could be the problems if we have the following scenario ?
For an example: Our MDM Server is based on 5.5 SP06, MDM Server name is DFM and our repository name is MDMQ110.
1) Checking the Reports from this Repository MDMQ110 from MDM Console, no errors and no warning. This repository can be loaded successfully and completed.
2) Server Log has an error in message:
Error: Service 'DFM', Schema 'MDMQ110_m000', ERROR CODE = 0,
SELECT LENGTH(Data) FROM A2i_Misc_Blobs WHERE Id=1000
Thanks very much for your help in advance
Regards,
WD

Hi Kanstantsin,
Thanks for your reply. I have done the stop and repair but It did not help any. By repair, there are no errors and warnings that have been fixed which I can see in the repository reports.
The Assertion Log has come up first with the messages like:
6426            2010/01/12 09:07:08.500               Error: Data_2 accelerator does not exist in A2i_CM_Accelerator_Status
6426            2010/01/12 09:07:08.683               Error: Data_53 accelerator does not exist in A2i_CM_Accelerator_Status
4884 2010/01/12 09:43:30.335   Error: KeyWord_2_F4_Leng_USA accelerator does not exist in A2i_CM_Accelerator_Status
As soon as I run into MDM, the Server Log has come up the same messages:
It looks like not only happened to this repository. As I can see if I load any other repository, there are the same messages in Server Log but only the repository name in the message is different.

Error while connecting to MDM server from Webdynpro

Hi ,
   I am trying to connect to MDM server (5.5 SP04 no patches) through a webdynpro application . The following is the piece of code that I am using as a test .
CatalogData CatalogData = new CatalogData();
    int resultLogin = 0;
    try {
          resultLogin = CatalogData.Login("USNOC01AQ05",2005,"Admin","Erico1234","English [US]");
    }catch(Exception e){
          wdContext.currentContextElement().setValueattr("Not Connected");
         //System.out.println("Error while establishing connection");
    if (resultLogin != RC.RC_OK){
          wdContext.currentContextElement().setValueattr("Not Connected");
         //System.out.println("Error logging to the SDM server");
         //System.exit(-1);
     wdContext.currentContextElement().setValueattr("Connected");
    //System.out.println("MDM server connected");
The import statements are as follows
import a2i.common.CatalogData;
import a2i.generated.RC;
I have put the following jar files in the java build path
MDM4J
mdm-admin
mdm-common
mdm-core
mdm-data
mdm-protocol
When I deploy my application I get the following error
java.lang.NoClassDefFoundError: a2i/common/CatalogData
It can't be determined from the exception chain, which class loader failed to load the above class. But at least the class loader of the current application does not contain a resource with name 'a2i/common/CatalogData'.
What do you guys think is the problem ?
Regards
DeepaK Singh

Hi ,
   I found a document which says that MDM4J is the legacy API and is considered deprecated .The MDM Java API is the new one .I have both of them in the java build path . I am not sure if this is that cause of the problem .
Now I had a look at the javadoc for the new API but I am not able to locate the class to obtain a connection to the MDM server from a custom application being built in Netweaver Developer Studio . Can someone help me out with the same ?What would be the code to obtain the connection to the MDM server with the new JAVA API ?
Regards
DeepaK Singh

Windows 8.1 MDM not responding to more than one SyncML from MDM server per session

Here is the behaviour i see, which was not expected by Windows 8.1.
1) Device is enrolled
2) Client initiates the connection with the MDM server defined in provisioning XML during enrollment.
3) MDM Server sends some commands as a SyncML response.
4) Client accepts the commands and sends Status and results.
5) Again MDM Server sends some commands as a SyncML response.
6) Client doesn't respond to these commands or not sending any SyncML. Here is the problem that i am referring to.
We are capturing the traffic in fiddler and found that device is not sending the next request where we are expecting the status for these commands.
The same is being repeated in all the requests client initiates. DM Client responds back only for one syncML sent by the MDM server per session.
Is this the expected behaviour with Windows 8.1? Or are we doing something wrong to see this behaviour?
Below is the SyncML for which I am expecting the response from the DM client. (Note: I got the response for the same SyncML in the first connection, but not in the second.)
<SyncML xml:lang="en" xmlns="syncml:SYNCML1.2">
<SyncHdr>
<VerDTD>1.2</VerDTD>
<VerProto>DM/1.2</VerProto>
<SessionID>1</SessionID>
<MsgID>1</MsgID>
<Target>
<LocURI>0</LocURI>
</Target>
<Source>
<LocURI>https://####</LocURI>
<LocName>AfariaWinPhoneProvider</LocName>
</Source>
<RespURI>https://####</RespURI>
</SyncHdr>
<SyncBody>
<Status>
<CmdID>1</CmdID>
<MsgRef>2</MsgRef>
<CmdRef>0</CmdRef>
<Cmd>SyncHdr</Cmd>
<TargetRef>https://####</TargetRef>
<SourceRef>0</SourceRef>
<Data>200</Data>
</Status>
<Get>
<CmdID>2</CmdID>
<Item>
<Target>
<LocURI>./cimv2/Win32_ComputerSystemProduct</LocURI>
</Target>
</Item>
</Get>
<Final />
</SyncBody>
</SyncML>

Hello Sreekanth,
I am facing similar issue, here is the behaviour description:
1) Device is enrolled
2) Client initiates the connection with the MDM server defined in provisioning XML during enrollment.
3) MDM Server sends some commands as a SyncML response.
4) Client doesn't respond to these commands or not sending any SyncML.
The same is being repeated in all client request.
Below is the SyncML
for which I am expecting the response from the DM client:
<SyncML xmlns="SYNCML:SYNCML1.2">
<SyncHdr>
<VerDTD>1.2</VerDTD>
<VerProto>DM/1.2</VerProto>
<SessionID>1</SessionID>
<MsgID>1</MsgID>
<Target>
<LocURI>9302116</LocURI>
</Target>
<Source>
<LocURI>https://#####</LocURI>
</Source>
</SyncHdr>
<SyncBody>
<Status>
<CmdID>1</CmdID>
<MsgRef>1</MsgRef>
<CmdRef>0</CmdRef>
<Cmd>SyncHdr</Cmd>
<TargetRef>9302116</TargetRef>
<Data>212</Data>
</Status>
<Status>
<CmdID>2</CmdID>
<MsgRef>1</MsgRef>
<CmdRef>2</CmdRef>
<Cmd>Alert</Cmd>
<Data>200</Data>
</Status>
<Status>
<CmdID>3</CmdID>
<MsgRef>1</MsgRef>
<CmdRef>3</CmdRef>
<Cmd>Replace</Cmd>
<TargetRef>./devinf12</TargetRef>
<Data>200</Data>
</Status>
<Get>
<CmdID>75</CmdID>
<Item>
<Target>
<LocURI>./DevDetail/SwV</LocURI>
</Target>
</Item>
</Get>
</SyncBody>
</SyncML>
Here
we had tried sending
<Target>
<LocURI>0</LocURI>
</Target>
But it didn't worked.

PI to MDM Connection Problem.

Hi Experts;
I have a connection Problem. I Sent data from r3 to PI System.PI System Convert Idoc to xml and sent to mdm server but PI cannot connect to mdm server. I Controled my connection information ip and mdm repository name is true . but I dont see ServerUser Id .
How I see and change this server user ?
Can you help me !
"MDM Adapter listener could not start due to: Can not create repository session '<server=192.168.10.35 serverUser=Admin repository=p0349 user=Admin>' caused by: Connection Failed: Cannot create connection to MDM Server '192.168.10.35' for one of the following reasons: (1) server does not exist, (2) server is not started, or (3) input/output problem while creating connection, error code: UnknownServer"

Hi Turgut,
How I see and change this server user ? As scenario is R/3>PI>MDM.
You need to look into your receiver Communication channel in Integration Directory (Integration Builder) where you have settings for defining MDM Server, Repository , Repository User and Password , Port Code of the Outbound MDM port etc.
Please find the below link to check settings for Setting Up Inbound Messaging into MDM.
http://help.sap.com/saphelp_nwmdm71/helpdata/en/48/9854884d3217cee10000000a421937/content.htm
There is no Server User ID but it is Repository User and Password along with other parameters in Communication channel.
Note: Make Sure that your MDM Import Server is also running.
Regards,
Mandeep Saini

MDM 5.5 SP03 - Error while connecting EP to MDM server

Hello colleagues,
I've deployed the following content of MDM 55 SP03 delivery to portal:
a. com.sap.mdm.tech.mdm4j.sda
b. com.sap.mdm.tech.connector.sda
c. BPMDMTECHN00_0.sca
d. BPMDMAPPLI00_0.sca
Then I created MDM system in Portal, arranged mapping but I couldn't
connect to MDM server using Connection test.
The MDM server is ip and running, port number in Portal is correct,
versions of deployed JAVA API and MDM connector fit to MDM server, user
mapping is correct too.
I actually have no idea what is the problem.
Are there any authorization requirements while connecting from EP to MDM Server?
Thanks and regards,
Konstantin.

Hi Nir,
Sorry for replying so late. I am following the steps given in the Business Package document.
1.I have created a system with system alias SAP_MDM_Repository_Customer(I want to connect to only customer repository) in a folder "Customer Repository".
2. I have created three groups MDM 5.5 SP3 Business Expert, MDM 5.5 SP3 MDM Admin, MDM 5.5 SP3 MD Expert
3. Then from the "Content provided by SAP" -> Specialist i am copying all the roles viz. Business Expert, Master Data Administrator, Master Data Expert. And then in the folder "Customer Repository" paste them as delta links.
4. Then in the user administration tab in the roles tab I am searching by group and adding the roles to these groups as below:
       Group                               Role
MDM 5.5 SP3 Business Expert      Business Expert
MDM 5.5 SP3 MDM Admin            Master Data Administrator
MDM 5.5 SP3 MD Expert            Master Data Expert
(Initially i have not adde eu_role but later i have added that also)
5. Then in the user mapping tab. I do the user mapping for the groups with the mdm repository users as below:
PortalUser           Group                 Repository
user
mdmuser    MDM 5.5 SP3 Business Expert     User/pwd
mdmadmin    MDM 5.5 SP3 MDM Admin           Admin/pwd
mdmexpert MDM 5.5 SP3 MD Expert           Expert/pwd
6. Then when i test the connection i get connection failed error.
7. When i add each roles in the "Everyone" group the connection test is successful but no data is displayed when i login with the portal user mdmuser no data is displayed.
Thats all. AFAIK i have covered every detail. Waiting for your reply.
Regards,
Jaydeep
Message was edited by: Jaydeep Kalmankar

MDM Server Enrollment Fails with Nginx Proxy

Hello everyone, I'm at my wits end trying to configure nginx as a transparent proxy to my OS X Server (in virtualbox) running our mdm service. Without nginx in the mix the mdm server works properly, and I can performce remote device enrollment and management, but I host multiple servers on the same network, and need to be able to proxy to multiple ips and ports using nginx.
The setup without nginx:
I'm using external DNS for my fqdn, mdm.servername.com, which is correctly resolving to my public ip address. I have my firewall successfully forwarding ports 443, and 1640 to my mdm server at private ip, 10.0.1.60. I have the OS X server DNS disabled, and I'm also using mdm.servername.com as my OS Server's hostname. I set mdm.servername.com to resolve to 127.0.0.1 in /etc/hosts in order to build the open directory, and then I removed this entry from /etc/hosts. Don't know if this is one of the issues. I can access http://mdm.servername.com/mydevices from outside of the network, and enroll my ipad without problems. Everything is working properly until I introduce nginx.
The setup with nginx:
Again using external DNS for my fqdn, mdm.servername.com. I have nginx running on private ip 10.0.1.50, and I'm forwarding ports 443 and 1640 to 10.0.1.50. I have the OS X mdm server running on ip 10.0.1.50. The mdm server has DNS disabled, and the mdm server is also using mdm.servername.com as the OS hostname. I can still access the website portion of mdm (https://mdm.servername.com/mydevices), I can install the Trust Profile without any issues, but when I try to enroll my iPad from outside the network, it successfully "enrolls the certificate", but when it's "Installing Profile" it evenutally times out. I see the progression of api calls in the nginx access logs:
Nginx access.log
173.171.23.81 - - [16/Nov/2013:19:56:47 -0500] "GET /scep/?operation=GetCACert&message=Device%20Management%20Identity%20Certificate HTTP/1.1" 200 1126 "-" "profiled/1.0 CFNetwork/672.0.8 Darwin/14.0.0"
173.171.23.81 - - [16/Nov/2013:19:56:48 -0500] "GET /scep/?operation=GetCACaps&message=Device%20Management%20Identity%20Certificate HTTP/1.1" 200 52 "-" "profiled/1.0 CFNetwork/672.0.8 Darwin/14.0.0"
173.171.23.81 - - [16/Nov/2013:19:56:49 -0500] "POST /scep/?operation=PKIOperation HTTP/1.1" 200 3046 "-" "profiled/1.0 CFNetwork/672.0.8 Darwin/14.0.0"
173.171.23.81 - - [16/Nov/2013:19:58:20 -0500] "PUT /devicemanagement/api/device/mdm_checkin HTTP/1.1" 504 191 "-" "MDM/1.0"
The 504 error on the PUT happens about 30 seconds after the iPad already reports the profile installation failed.
Nginx error.log
2013/11/16 19:58:20 [error] 7983#0: *10 upstream timed out (110: Connection timed out) while reading response header from upstream, client: xxx.xxx.xx.xx, server: mdm.servername.com, request: "PUT /devicemanagement/api/device/mdm_checkin HTTP/1.1", upstream: "https://10.0.1.60:443/devicemanagement/api/device/mdm_checkin", host: "mdm.servername.com"
So nginx is reporting a timeout talking to the mdm server for the PUT checkin action...
On the MDM Server the Apache Logs indicate connection errors also
Apache access_log
mdm.servername.com 10.0.1.50 - - [16/Nov/2013:19:56:47 -0500] "PUT /devicemanagement/api/device/mdm_checkin HTTP/1.0" 403 - "-" "MDM/1.0"
Apache error_log
[Sat Nov 16 19:56:22 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3328 (127.0.0.1) failed
[Sat Nov 16 19:56:22 2013] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Sat Nov 16 19:56:22 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3329 (127.0.0.1) failed
[Sat Nov 16 19:56:22 2013] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Sat Nov 16 19:56:22 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3327 (127.0.0.1) failed
[Sat Nov 16 19:56:22 2013] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Sat Nov 16 19:56:22 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3325 (127.0.0.1) failed
[Sat Nov 16 19:56:22 2013] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Sat Nov 16 19:56:22 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3326 (127.0.0.1) failed
[Sat Nov 16 19:56:22 2013] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Sat Nov 16 19:56:22 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3324 (127.0.0.1) failed
[Sat Nov 16 19:56:22 2013] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Sat Nov 16 19:56:22 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3322 (127.0.0.1) failed
[Sat Nov 16 19:56:22 2013] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Sat Nov 16 19:56:22 2013] [error] (61)Connection refused: proxy: HTTP: attempt to connect to 127.0.0.1:3323 (127.0.0.1) failed
[Sat Nov 16 19:56:22 2013] [error] ap_proxy_connect_backend disabling worker for (127.0.0.1)
[Sat Nov 16 19:58:17 2013] [error] [client 10.0.1.50] Re-negotiation handshake failed: Not accepted by client!?
I'm assuming I have something misconfigured with nginx, but I'm not smart enough to put all these pieces together for a solution...Hopefully one you more capaple guys or gals can help me out...
Nginx Config
user www-data;
worker_processes 4;
pid /run/nginx.pid;
events {
        worker_connections 768;
http {
tcp_nopush on;
tcp_nodelay on;
keepalive_timeout 65;
types_hash_max_size 4096;
default_type application/octet-stream;
ssl_certificate     /etc/nginx/ssl/servername.com/_.servername.com.combined.crt;
ssl_certificate_key /etc/nginx/ssl/servername.com/_.servername.com.key;
access_log /var/log/nginx/access.log;
error_log /var/log/nginx/error.log;
gzip on;
gzip_disable "msie6";
server {
    listen        443 ssl;
    listen        1640;
    server_name   mdm.servername.com;
    location / {
      proxy_pass      $scheme://10.0.1.60:$server_port$request_uri;
      sendfile off;
      proxy_set_header   Host                   $host;
      proxy_set_header   X-Real-IP            $remote_addr;
      proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_max_temp_file_size 0;
      #this is the maximum upload size
      client_max_body_size       10m;
      client_body_buffer_size    128k;
      proxy_connect_timeout      90;
      proxy_send_timeout         90;
      proxy_read_timeout         90;
      proxy_buffer_size          4k;
      proxy_buffers              4 32k;
      proxy_busy_buffers_size    64k;
      proxy_temp_file_write_size 64k;
Additional info:
I have a wildcard ssl cert from go daddy that nginx is using for ssl, and I'm also using this for the websites server on OS X Server. I'm using the intermediate cert that Server generates for signing the configuration profile.
Thanks in advance for any help you can provide.

Thanks for the input Stephen! I am having trouble recieving application pushes on my guest network, I'm going to try and open the ports like you suggested.
Opening ports 443, and 1640 are definitely a must on the MDM server, or enrollment from the guest network will not succeed.
I noticed a lot of action in the /Library/Logs/ProfileManager/php.log on my MDM server, whenever I bypass nginx, and successfully enroll, so I'm guessing there needs to by some fastcgi proxying in the nginx config block:
1::Nov 18 10:52:55.329 [30721] {require_once (mdm_enroll.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - POST mdm_enroll
1::Nov 18 10:53:00.499 [30721] {GetMDMACLFromUserAgentHeader (mdm_enroll.php:40)} iOS version 7.0
1::Nov 18 10:53:06.400 [30721] {SendFinalOutput (mdm_enroll.php:69)} Sent Final Output (10933 bytes)
1::Nov 18 10:53:06.400 [30721] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/mdm/mdm_enroll
0::Nov 18 10:53:06.419 [30721] {SendFinalOutput (mdm_enroll.php:69)} Completed in 11303ms | 200 OK [https://mdm.servername.com/devicemanagement/mdm/mdm_enroll]
1::Nov 18 10:53:22.673 [30722] {LogElapsedTime (common.php:74)} Time since script start: 441us [https://mdm.servername.com/devicemanagement/api/device/mdm_checkin]
1::Nov 18 10:53:22.720 [30722] {require_once (mdm_checkin.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_checkin
0::Nov 18 10:53:22.751 [30722] checkin: 'Authenticate'
1::Nov 18 10:53:23.046 [30722] {SendFinalOutput (mdm_checkin.php:145)} Sent Final Output (0 bytes)
1::Nov 18 10:53:23.046 [30722] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/mdm/mdm_checkin
0::Nov 18 10:53:23.046 [30722] {SendFinalOutput (mdm_checkin.php:145)} Completed in 373ms | 200 OK [https://mdm.servername.com/devicemanagement/api/device/mdm_checkin]
1::Nov 18 10:53:28.220 [32005] {LogElapsedTime (common.php:74)} Time since script start: 476us [https://mdm.servername.com/devicemanagement/api/device/mdm_checkin]
1::Nov 18 10:53:28.220 [32005] {require_once (mdm_checkin.php:11)} vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv - PUT mdm_checkin
0::Nov 18 10:53:28.220 [32005] checkin: 'TokenUpdate'
1::Nov 18 10:53:28.225 [32005] {Target_for_incoming_request (target.php:210)} Found target iOS: <''[10](OWNER:User[9])>1::Nov 18 10:53:28.501 [32005] {SendFinalOutput (mdm_checkin.php:145)} Sent Final Output (0 bytes)
1::Nov 18 10:53:28.501 [32005] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ - /devicemanagement/mdm/mdm_checkin
0::Nov 18 10:53:28.501 [32005] {SendFinalOutput (mdm_checkin.php:145)} Completed in 281ms | 200 OK [https://mdm.servername.com/devicemanagement/api/device/mdm_checkin]
I tried adding the following location section into the config, but still no luck:
location /devicemanagement/api/device/mdm_checkin {
    fastcgi_pass 10.0.1.49:$server_port;
    fastcgi_index index.php;
    include fastcgi_params;

MDM 7.1 Portal Connectivity to MDM server

Hi all
I was running the MDM 7.1 ramp up version so far with full connectivity from the portal to MDM. I had configured both the standard business partner and a custom repository using the Portal Business Content . Now that I have migrated to the just released MDM 7.1 (GA ) , I am encountering the following error at the portal level . I am using the standard "Using Mapping" to connect to the MDM server from the portal and not the newly introduced "Trusted Connection" . Any body has any clue as to whats going wrong ..
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)... [see details]
DETAILED MESSAGE
com.sap.mdm.commands.CommandException: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:61)
at com.sap.mdm.blobs.ObjectCache.initialize(ObjectCache.java:521)
at com.sap.mdm.admin.utils.MdmConnectionProvider.createBlobObjectCache(MdmConnectionProvider.java:308)
at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.initContexts(MdmeBaseDynPage.java:364)
at com.sap.pct.mdm.appl.masteriviews.MdmeBaseDynPage.doProcessBeforeOutput(MdmeBaseDynPage.java:154)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:127)
at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:134)
at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)
at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:645)
at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)
at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)
at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)
at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)
at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:524)
at java.security.AccessController.doPrivileged(Native Method)
at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:407)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
Caused by: com.sap.mdm.internal.protocol.manual.ServerException: The connection is not trusted
at com.sap.mdm.internal.protocol.manual.AbstractProtocolCommand.execute(AbstractProtocolCommand.java:126)
at com.sap.mdm.commands.TrustedUserSessionCommand.execute(TrustedUserSessionCommand.java:56)
... 38 more
Thanks
Ray

Hi Ray,
This is a trusted connection problem. For this you need to create allow.ip and deny.ip files in your server. In allow.ip you need to give those ip address through which you would be connecting to MDM server executable file(mds.exe) like in your case your portals ip address. And in deny.ip you need to specify those ip which you feel shouldnt connect to MDM server. After assigning this ip remember to restart your mds.
Also the users through which you are trying to connect to an MDM repository, their usernames must exist on the MDM repositoryu2019s Users table.
For more details please see page 299 from MDM 7.1 Console refernece guide
I hope I am able to solve your problem
Thans & Regards
Dilmit Chadha

MDM server error

Hello MDM Experts,
When trying to install mdm server i am getting the following error....
"This application has failed to start because xerces-c_2_6.dll was not found. Re-installing the application may fix this problem."
Regards, Jatin

Thanks Jitesh,
Now i get the following error while installing MDM
ERROR      2010-12-02 17:27:22.51 [sixxcstepexecute.cpp:984]
FCO-00011 The step createInitialIniFile with step key |MDM_SRM_Install|ind|ind|ind|ind|0|0|MDS_Instance|ind|ind|ind|ind|6|0|createInitialIniFile was executed with status ERROR ( Last error reported by the step :Sed.run(): source is undefined.).
TRACE      2010-12-02 17:27:22.080
Call block:CallBackInCaseOfAnErrorDuringStepExecution
    function:CallTheLogInquirer
is validator: true
WARNING    2010-12-02 17:27:22.80 [iaxxejshlp.cpp:150]
Could not get property IDs of the JavaScript object.
ERROR      2010-12-02 17:27:22.80 [iaxxejsctl.cpp:492]
FJS-00010 Could not get value for property .
TRACE      2010-12-02 17:27:22.104
A problem occurs during execution the inquirer callback. SAPinst will switch back to the standard behaiviour.
TRACE      2010-12-02 17:27:22.104 [iaxxgenimp.cpp:707]
            CGuiEngineImp::showMessageBox
Regards, Jatin

MDM console GUI on Windows is not mounting the MDM server on Solaris

Hello MDM experts,
This is kind of administrative problem. I am basis person, installing SAP MDM 5.5 SP04 for the first time.
I have configured the MDM server (mds) on solaris 10 system. I have also configured MDM import server(mdis) and Syndication serever (mdss) on the same machine. I have installed the database software and configured the empty repository on the same host machine.
So, Database and all the 3 MDM services (mds,mdis,mdss) are running on Solaris machine.
After that, I installed "MDM console fat client GUI" component on my desktop and trying to "mount the server" by specifying the "hostname" of the solaris machine where MDM services are running.
But I am not able to mount it...it says invalid server and does not mount.
Any idea what might be the problem ????
I referred following link :
http://help.sap.com/saphelp_mdmgds55/helpdata/EN/8e/9f9c427055c66ae10000000a155106/frameset.htm
which says, you should have administrative right on Solaris machine where MDM server is running....but how do I have that being a Windows user ???
Please advise.

Hello Mark,
1. When I right click on the "SAP MDM servers" node in "Console Hierarchy" pane on the left hand side of the Console GUI, and select "Mount MDM Server..." option in context menu, I get a dialog box for entering my MDM server name.
I typed in the fully qualified host name of my solaris server where "mds-r" is running.
When I click "OK" button, it adds an entry in "Console Hierarchy" on left hand side, but the entry comes with "Yellow exclamation Mark" sign. Also it says Status "Invalid" when I see the "MDM servers" section on right hand side top.
When I right click on my newly created entry of MDM server, all the options on context menu like "Mount Repository, Create Repository, Connect to MDM server" look greyed out. Only the option of "Unmount MDM server" seems to be enabled
2. I tried to do the same thing on 2 different Windows machines and got the same output.
Regards,
Bharat

Import Server problem

Hello,
in the last days we experience some strange phenomena with the Import Server. For example, I created an XML import mapping for the standard repository "Material", created a port in the console and used the mapping there. Manual execution of the mapping worked fine. I dumped the file in the correspondent Ready-folder and the Import Server swallowed the file and progressed it.
So far so good.
I did this again, no problem. I tried a different file and got error messages, because the file format didn't match. But the Import Server still swallowed the file. Then I tried a larger file like the first one (the first one was just a 10-records-test), but no reaction. The Import Server did not swallow the file.
I read this thread: , stopped and started the MDM Server and the Import Server several times and then dumped files again - same result, even with the file with which it worked before.
I created a new mapping on Repository "Vendor" like the one on "Material", for the same file, no reaction. The Import Server seems to be sleeping.
Anyone faced a similar situation before? Any suggestions what I could do to resolve the problem?
Best regards,
Jörg
Message was edited by: Jörg Thiesmann

Some additional information on my problem:
The second file read the following error once for each record I wanted to read:
So there IS only one root element. The test file with which it worked before has exactly the same start/end.
This was the last logfile.
Message was edited by: Jörg Thiesmann

Open Hub Destination and MDM server

Dear colleagues,
Does anybody have the experience of creating OHD with MDM Tech (for pushing data into MDM server)?
I've got the problem of activation my created OHD.
I have tried to connect to MS SQL Server and Oracle server
I think that i don't understand the prerequisites.
Could please advise me my mistakes? What are the configurations of BW and MDM server?
I would be pleased if you write me to my addres

HI
May be this doc helps you
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/media/uuid/368ed888-0701-0010-aa94-b21cfebe4eee
https://websmp210.sap-ag.de/~sapidp/011000358700001612132004E.pdf
https://www.sdn.sap.com/irj/scn/articles-mdm-all?prtmode=print&startindex=241
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3065806b-dce5-2a10-1493-c933ac8daca5

Unable to MERGE-Err Msg "MDM Server Failed to Merge the Selected Records"

Hi Friends,
I am using a Match Strategy in the Workflow. In the START Process of the workflow I CHECK OUT the records. In the step MATCH / MERGE when I try to MERGE similar records I get the Error Message "MDM Server Failed to Merge the Selected Records".
But the same step works fine when I dont CHECK OUT (CHECK OUT = NO) the records in the START STEP. But this would not be the right way to do it, as the incoming duplicate records would be visible in the Data Manager by other users even before it is merged.
Your inputs would be greatly appreciated to tackle this problem.
Thanks.

Hi Ravi,
The workflow steps are as follows: (I am on MDM 5.5 and SP 6)
Start (Check Out)   -
> Process -
> Validate -
> Match    (Manual Merge)   -
> Approve----
> Stop    (Check In)
                                                                                The Match and Merge step is a Manual step in the Workflow.
I Check out the records when i start the Workflow and Once the entire process is complete I check in the record. What is happening is that it does not allow me to Merge the records and I get the Error message.
If i dont Check out the Incoming records and run the workflow it Merges fine. But this would not be correct as the Incoming records(whihc could be duplicates) would be visible in the system until they are merged.
Your Input woould be greatly appreciated.
Thanks in Advance.

MDM Server problem

Similar Messages

Maybe you are looking for