MDM server user

Hello experts.
The developer requested me to take a look at the error.
MDM Adapter listener could not start due to: Can not create repository session '<server=turin serverUser=Admin repository=My_Catalog_Master user=pleaseMaintain>' caused by: The specified MDM repository was not found on the server
While i was investigating, i haven't found where the guy have specified that the serverUser was Admin. 'Cause, in fact, the server user had a passowrd that should be set somewhere (we removed the password, but devs want a password).
The error itself is not important, i just got curious about the server user.
anyone got a clue? the Communication channel have the user (the mdm repository user) but this Admin user
thanks
Thiago Delou

Hi,
By default, MDM Server takes System account i.e. windows user currently logged in. You can check this in Windows Services, while in Unix it asks for username at the time of server installation and by default it creates user=mdm. First try omitting serveruser parameter else try passing the login credentials of windows user. If you are at Unix then user=mdm should work for you.
Regards,
Jitesh Talreja

Similar Messages

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

User not found error when connecting to MDM server using NWDS

Hi,
I am getting the error as " User not found " when i am connecting to MDM server from the code written in NWDS.
If i make that user as admin in usermapping in MDM den it works fine bt if that user is not admin den get the error as user not found.
Please help.

Hi,
Thanks for the reply.
I have added the user in user mapping in MDM server. but i have to give the authority as admin.
other users who are added in usermapping bt not assigned as admin are getting the error.

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:
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. 
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

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

Error connecting to MDM server

Hi all,
I am getting the check user mapping error while connecting to MDM server. The MDM Server and EP Server are on different systems. And when i try using the group "Everyone". The connection test was successfull but when i login with that user id/pwd no data is displayed.
I am using MDM 5.5 SP03 and EP SP14.
Regards,
Jaydeep

Hi Simona,
I tired to import schema, but its not over written(user names & roles) by the merging it with the other Repsoitory schema.
I tried creating duplicate, but could not see the duplicate repository in the Console - server - repository, but could see the repository at the database level(Oracle DBMS).
Anyways SAP has adviced to Connect to Oracle DBMS directly and remove the trailing space in
USERNAME column of A2I_CM_USERS table for the user mentioned.
But, its not possible to reduce the length of the username field.
Could you please guide me, if u have any idea??
Cheers
Srihari Reddy

Mdm:iOS terminal does not communicate to a MDM server

How do you do?
It is Matsuzaki SHinji.
I want you to teach about Apple MDM.
I am MDM Vendor.
The MDM server is using Apache 2.2.3.
WavDAV is used.
The PUT method is supported.
The contract of an enterprise is completed.
The application of MDM is also completed.
I am using the following URL by webdav.
It has also checked that it was in the state which can be used.
https://www.anetm.com/dav/
It is a thing of APNs.
nj_dev_apns-dev.pem
The "user ID" of subject contained in a nj_dev_apns-dev-key-noenc.pem certificate is "jp.co.nishitele."
APNs is used using the following ruby script.
In the following codes, a device token is ending exchangeably.
"[ -device torkn string 32 length set- ]"
Start Script
#!/usr/bin/ruby -Ku
require 'openssl'
require 'socket'
 (msg = []) << "[ -device torkn string 32 length set- ]"
 device = msg.pack("H*")
 socket = TCPSocket.new('gateway.sandbox.push.apple.com',2195)
 context = OpenSSL::SSL::SSLContext.new('SSLv3')
 context.cert = OpenSSL::X509::Certificate.new(File.read('nj_dev_apns-dev.pem'))
 context.key = OpenSSL::PKey::RSA.new(File.read('nj_dev_apns-dev-key-noenc.pem'))
 ssl = OpenSSL::SSL::SSLSocket.new(socket, context)
 ssl.connect
 payload = <<-EOS
"mdm":{"<PushMagic>"
EOS
 (message = []) << ['0'].pack('H') << [32].pack('n') << device << [payload.size].pack('n') << payload
 ssl.write(message.join(''))
 ssl.close
 socket.close
End Script
It performs.
The next warning has occurred at the iPhone terminal.
Apr 30 11:04:35 Evangerion-iPhone4S apsd[60] <Warning>: <APSCourier: 0x131e80>: Failed to parse JSON message payload for topic 'jp.co.nishitele': The operation couldn’t be completed. (Cocoa error 3840.)
An iOS terminal does not communicate to a MDM server.
I would like to solve this.
And thank you.
Thank you for your consideration.
He is waiting for the reply.

Is this iPad used?
iTunes should be version 11
It should be reset to wipe all content from the device and set up as a new device with iTunes. It should update to IOS 7.0.4

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

MDM Server Password Reset

Hi,
In our MDM, someone has accidently change the password for the Server. As an Admin, how can I reset the MDM Server level Password without knowing the old password.
Regards,
Tanveer

Tanveer,
Only way to do it is go to underlying database, if you have access or a DBO can do that (with all permisions). In database every repository is saved under database tab, there Under tables--> you have mdm user table enteries and the password can be reset.
Otherwise you can not login to repository means no other way to do this.
I hope it will help. Please rewards if found helpful.
BR,
Alok

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.

Error with SAP MDM Server

Hi All,
We are working on discovery server version 3.
After I mount the server and when i start the repository i cannot start it and get the following error
u201CError Starting hp-discovery server (MDM Server) :
Could not open the service control manager on serveru2019 server nameu2019 / Verify that the current windows user has the correct permissions, and that the target system is a windows based operating system u201D
The problem sis resolved when i start the discovery server. and again occurs after few minutes.
Its a tedious job to start server everytime and i would like to know what could be the possible reasons for getting this error so that i can avaoid this problem
Thanks,
MS.

Hi,
i have some problem too,
the server was installed with option in MDS sap existing option.
the config for MDS Listening port as below:
MDS_LISTENING_PORT = 52250
But when i mount the server in MDM console the value in column port is 59950.
i have shared sapmnt folder with the other MDM server which is using port 59950 for MDS listening port.
is there anyone know how to resolve this
Regards,
Husin

MDM Server is responding very slow

Hi,
I am working with only 21,695 records and MDM Server is responding very slow.
MDM Server is running on Intel(R)Xeon(TM) 2.40Ghz 2.39Ghz, 3.89 GB of RAM.
System: Microsoft Windows Server 2003 Standard Edition Service Pack 2.
The hard disk partition F: has 43.7 GB Freespace.
It is impossible to do MDM Workflow matching and Merging with this slow speed.
Regards
Kaushik Banerjee

Hi Kaushik,
Please try to stop and restart the database server.
You can check the below:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_mdm/~form/handler7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d31303132373435%7d
Re: MDM Server is very slow and locks users out
Hope it helps.
Thank you,
Priti

Error in MDM - EP integration : "Failed to connect to MDM server. ....."

Dear SDN,
I m in middle of configuring the MDM and EP integration.
EP Version Info :
J2EE Engine 6.40 PatchLevel 108290.313
Portal 6.0.20.0.0
BP has been installed.
We are able to view MDM system and MDM search IViews in the Wizards in the portal.
MDM Version Info : MDM 5.5 SP 04
I come across the following error :
Step 4: An error has occurred
Failed to connect to MDM server. Check your system. The server may be down or there may be an error in one or more of your system parameters.
System parameters are Server name and pwd .
This parameters are used to start the server and pwd for accessing the server while mounting the server.
Also at the same time, my MDM server is running and repository is shown loaded and running.
Kindly suggest what should have been missed out from our side or some way we can make sure that error does not occur.
Please help.
Regards,
Chandani Shah.

Hi Chandani,
in Portal clik on Personalization, and in User Mapping you need to map the MDM repository user (may be Admin)..... then try another time.
Please, check the BP version in order to unserstand if it is the rigjt version for your MDM.
Hoper this help you.
Regards,
Vito

Why my MDM Server can only communicate with ipads and iphones with logging Junos sslvpn.

Why my MDM Server can only communicate with ipads and iphones when either of the iPhone or iPad Junos sslvpn? Any ideas
Our iPad and iPhones users have to log in to Junos SSLVPN to be able to communicate with our MDM Server (via wi-fi). Any ideas where users don't have to log in to Junos SSLVPN?

This bothers me so much. It is absolutely ridiculous. I use my Apple ID as well as a family member's Apple ID to download music.
Every once in a while I will purchase a song and it won't download correctly or will give me an error that my computer is not authorized, a solution I usually fix by deleting and redownloading the song from the cloud. This doesn't work, however, when it happens to both accounts within 90 days.
It is incredibly frustrating to me that I have paid for a song, it downloaded incorrectly, and I must wait 90 days to try downloading it again because of these assinine policies.

MDM server user

Similar Messages

Maybe you are looking for