MDM server distribution path issue

Hi,
Has anyone faced below issue??
When we create repository in MDM Console, It should create a Folder under MDM server distribution path...right.
I have unarchived a standard repository but still i don't see this repository folder in 'Distribution" folder path...Also we tried creating a repository in u2018MDM console,u2019 but it doesnu2019t create a folder in mentioned path.
What can be the issue.??
Cheers,
Rc

Hi RC,
Just check with your basis team, how they hav maintained MDS server, If they had used shared environment. Distribution folder might have been got changed in your issue. you might be finding a distribution path in MDS.ini, however another distribution folder might have been created unknowingly where all the repositories are creating their folders.
Regards
MSR

Similar Messages

  • RMI Server Class path issue

    hi ,
    i am facing classpath issue when try to run rmi server. i have a jar file
    (RmiServer.jar) for rmi server , which contain some other jar file .
    when i run this jar file it throws ClassNotFoundException
    the java classloader are not able to load class from jar(RmiServer.jar)
    file. pls. tell me what i did wrong .
    Regards
    Brajesh K

    Actully you dont understand my problem.
    i have 2 jar file RmiClient.jar and RmiServer.jar
    when i run RMIserver.jar it throws following exception.
    Caused by: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
    java.lang.ClassNotFoundException: RmiServer_Stub
    the RmiServer.jar contain all the class file (stub/skelton,remote,etc) whichever needed.
    even i set class path to that folder where RMIserver.jar is placed
    inspite of that it throws ClassNotFoundException : RmiServer_Stub
    i dont undersatand why classloder , not able to load class file from Rmiserver.jar.
    any idea.
    thanks in advance
    Regards
    Brajesh K

  • When mount MDM server on MDM console...MDM Console hangs.

    Hi,
    when i try to mount MDM server on MDM console, MDM Console hangs and then i have to stop MDM console with task manager.
    For this i have tried with restarting  MDM server - then also issue was not resolved, then i have rebooted the server, then issue resolved.
    But rebooting the server is not permanent solution, this problem occurs everything next 3-4 days.
    Please let me know the cause and it's solution if anyone has faced the similar issue.
    ---------------Server details----------------
    SAP MDM 7.1SPS11
    OS - Suse Linux
    DB - MaxDB
    MDM Console is also SPS11
    Thanks and Regards,
    Murtaza Najmi

    Hi Murtaza,
    This may be due to the memory full issue. It is advisable to allocate appropriate memory in the RAM where server is running. Generally it will be done by the DB team or Linux/unix team. Raise this ticket to your concerned teams.
    Thanks,
    Vinoth

  • Renaming of files by MDM Server (MDM 5.5 SP4)

    Hi Experts,
    I am checking the MDM Server Logs and found that there is always renaming of files happening from ".tmp" to ".xml" as shown below:
    7560 2011/09/13 15:39:16.773 GMT SyndicateToPortImpl: rename files (0) "C:\PROGRA1\SAPMDM1.5\Server\Distributions\MR4_ORCL\BP US FUELS CUSTOMER MASTER_PRD\Outbound\SCDB_BP\Modify_BP_SCDB\Ready\Data_110913-153916_000.tmp"
    to
    "C:\PROGRA1\SAPMDM1.5\Server\Distributions\MR4_ORCL\BP US FUELS CUSTOMER MASTER_PRD\Outbound\SCDB_BP\Modify_BP_SCDB\Ready\Data_110913-153916_000.xml".
    Can someone tell me why this renaming of files is happening?
    Thanks!

    Hi,
    This should be happening to avoid incomplete files getting picked up by tools from the Ready folder.
    So until the file is completely transferred into Ready folder, it gets created as .tmp and then it gets converted to .xml once the file is completely copied.
    Same thing you can see when you archive a repository. The .a2a extension is different if the Archive operation aborts.
    As per SAP MDM 7.1 Console reference guide , this is recommended to avoid issues with incomplete files. But in your case of MDM 5.5, if you say that you have not implemented this logic manually and it is happening automatically then it is good for you.
    SAP MDM Console Reference Guide - Page 272.  http://help.sap.com/saphelp_mdm71/helpdata/en/4b/71608566ae3260e10000000a42189b/MDMConsole71.pdf
    Thanks,
    Shambhu.

  • 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

  • Flat file connection: The file name "\server\share\path\file.txt" specified in the connection was not valid

    I'm trying to execute a SSIS package via SQL agent with a flat file source - however it fails with Code: 0xC001401E The file name "\server\share\path\file.txt" specified in the connection was not valid.
    It appears that the problem is with the rights of the user that's running the package (it's a proxy account). If I use a higher-privelege account (domain admin) to run the package it completes successfully. But this is not a long-term solution, and I can't
    see a reason why the user doesn't have rights to the file. The effective permissions of the file and parent folder both give the user full control. The user has full control over the share as well. The user can access the file (copy, etc) outside the SSIS
    package.
    Running the package manually via DTExec gives me the same error - I've tried 32 and 64bit versions with the same result. But running as a domain admin works correctly every time.
    I feel like I've been beating my head against a brick wall on this one... Is there some sort of magic permissions, file or otherwise, that are required to use a flat file target in an SSIS package?

    Hi Rossco150,
    I have tried to reproduce the issue in my test environment (Windows Server 2012 R2 + SQL Server 2008 R2), however, everything goes well with the permission settings as you mentioned. In my test, the permissions of the folders are set as follows:
    \\ServerName\Temp  --- Read
    \\ServerName\Temp\Source  --- No access
    \\ServerName\Temp\Source\Flat Files --- Full control
    I suspect that your permission settings on the folders are not absolutely as you said above. Could you double check the permission settings on each level of the folder hierarchy? In addition, check the “Execute as user” information from job history to make
    sure the job was running in the proxy security context indeed. Which version of SSIS are you using? If possible, I suggest that you install the latest Service Pack for you SQL Server or even install the latest CU patch. 
    Regards,
    Mike Yin
    If you have any feedback on our support, please click
    here
    Mike Yin
    TechNet Community Support

  • Regarding Application server file path browsing

    Hi All,
    I have a issue regarding Application Server File Path browsing.
    Actually in my selection-screen i will declare a parameter as <b>Application Server File Path</b> now when i press F4 in that field it should be able to browse through <b>Application Server Path's</b>.
    Just like <b>F4_FILENAME</b> in the case of <b>Presentation Server File Path</b> Browsing.
    Can anybody solve my issue.
    Thanks in advance.
    Thanks & Regards,
    Rayeez.

    Hi Shaik,
    Just copy and paste:
    Here is the code for retrieving list of files contained within specific Application server directory(SAP).
    PARAMETER: p_fdir type pfeflnamel DEFAULT '/usr/sap/tmp'.
    data: begin of it_filedir occurs 10.
    include structure salfldir.
    data: end of it_filedir.
    START-OF-SELECTION.
    Get Current Directory Listing for OUT Dir
    call function 'RZL_READ_DIR_LOCAL'
    exporting
    name = p_fdir
    tables
    file_tbl = it_filedir.
    List of files are contained within table it_filedir
    loop at it_filedir.
    write: / it_filedir-NAME.
    endloop.
    Hope this will help you.
    Let me know incase of any concerns.
    EDIT:
    There are few FM for ur refernce :
    RZL_READ_DIR_LOCAL
    SUBST_GET_FILE_LIST Return table with file list for the given directory (pattern allowed)
    F4_DXFILENAME_TOPRECURSION Popup to select one file from the given application server directory
    TH_SERVER_LIST Returns list of application servers.
    EPS_GET_DIRECTORY_LISTING – Lists filenames from the application server .
    Cheers
    Sunny
    Rewrd points, if found helpful
    Message was edited by: Sunny

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

  • Unable to Start MDM Server through MDM Console

    Dear All,
    We have issue to start MDM through MDM Console , MDM instance is up and running SAP console.
    I have already mounted MDM Server but its show MDM is not started , we are try to start manualy while right clicking.
    It shows below error .
    error starting 'sap1024.sap.xxx.com (MDM Server)'
    Call to SAPWebServiceStartInstance failed with error .A connection attempt failed because the connected party did not properly respond after a period of time , or established connecton failed bacause connected host has failed to respond.
    Kindly suggest to resolve the above issue in MDM.
    thanks

    Closing the thread , same thread post in MDM .

  • 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 Web Service authentication issue. How to use ?

    Hi,
    I' am a Microsoft technology person I' am working on integrating SAP MDM 7.1 to SharePoint 2010 using MDM Web Services interface and consuming the same in .NET custom component.
    I tried the WS with "None" authentication and it worked great.
    I' am having issues understanding how HTTPAuthentication with SAP Logon ticket authentication works in MDM.
    Created the authentication enabled web service and while testing in NetWeaver WS Navigator, it throws me exception, not able to establish session with repository for user XYZ.
    Please help me with the following queries I have:
    1) How to test a authentication enabled web service in NetWeaver WS Navigator ? Do the user id/password needs to be set in the "Invocation Parameters" ? Link to any article etc will be appreciated.
    2) How to pass the MDM user credentials (or just the username) in the MDM web service in .NET code. I didn't see any parameter in the Client class constructor to pass the same, nothing related to that found in the code that gets generated on adding the service reference.
    As per the documentation on the MDM security, looks like a trust relationship also needs to be configured on MDM - allow.ip file entries.
    However first I want to understand how to pass this information in Web Services through code.
    SharePoint   -
    (1)--> SAP PI  -(2)--
    > SAP MDM                                             
    (integrated with Active Directory                        (Where Web services are deployed     (have its own user accounts)
    so logged in user is already authenticated)          and have its own user accounts)
    The trust relationship configuration could solve the problem of authentication marked in second hop (2) by registering the IP address of PI server.
    Please help me understand how would it work to solve the first hop (1) problem and what needs to be done.
    Thanks,
    Parvinder

    Thanks Gaurav.
    The link talks about setting up the Trust with MDM server.
    The code sample provided there has the following step where user name is being set and passed to MDM:
    Use  command to authenticate user session on trusted connection
           TrustedUserSessionCommand  tuscTrustedUser =
           new TrustedUserSessionCommand(mySimpleConnection);
           //  Set the user name to use
           tuscTrustedUser.setUserName(UsernameAsString);
           tuscTrustedUser.setSession(session);
           tuscTrustedUser.execute();
           session =  tuscTrustedUser.getSession();
    I want to understand how to do that for MDM Web Services.
    I didn't see any method accepting this user name while calling the web service method / creating client object.
    So that link is still missing.
    Appreciate if anyone can help me with that.
    This is for MDM 7.1
    Thanks,
    Parvinder

  • Unable to start MDM Server using CLIX

    I am able to Stop the MDM Server by issuing 'mdsStop' command from command line. But I'm unable to re-start the MDM Server by issuing the 'mdsStart' command from command line. Is anyone else using CLIX? If so, are you successful in starting the server from CLIX?
    My command:
    CLIX mdsStart SERVERNAME
    I get no error messages and the command line prompt comes back like normal but the MDM Server is still not running.

    Klaus, the point is that the MDSSTOP command will work and the result of this command is that the MDM Server service on the hostmachine gets killed.  I would assume that the MDSSTART command is supposed to startup the MDM Server service on the host machine, but it does not.
    The MDMSTATUS command will work if the MDM server service is running.

  • Windows 8.1 MDM not responding to first SyncML from MDM server per session

    Here is the behaviour which I face after enrolling 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 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>{DevID}</LocURI>
            </Target>
            <Source>
                <LocURI>https://#####</LocURI>
            </Source>
        </SyncHdr>
        <SyncBody>
            <Status>
                <CmdID>1</CmdID>
                <MsgRef>1</MsgRef>
                <CmdRef>0</CmdRef>
                <Cmd>SyncHdr</Cmd>
                <TargetRef>{DevID}</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. Thanks in advance.

    Thanks Obaid for the information but still my question is not answered. Here are more details about it:
    I completed enrollment for a win8.1 device successfully, and got first SyncML message from device, but in the SyncML message,
    the the url of mdm server was  http://localhost:8000/handler.ashx as you mentioned, while the uri of device was 0,
    actually it should be the device Id. I responded a SyncML message to the device, but got no response from device any more. I’ve checked all registries after enrollment, all registries were well applied. Can give me some hints for such issue.
    Looking forward to your reply. Thanks a lot.
    The first message got from win8.1 device after enrollment is:
    <SyncML xmlns="SYNCML:SYNCML1.2">
        <SyncHdr>
            <VerDTD>1.2</VerDTD>
            <VerProto>DM/1.2</VerProto>
            <SessionID>1</SessionID>
            <MsgID>1</MsgID>
            <Target>
                <LocURI>http://localhost:8000/handler.ashx</LocURI>
            </Target>
            <Source>
                <LocURI>0</LocURI>
            </Source>
        </SyncHdr>
        <SyncBody>
            <Alert>
                <CmdID>2</CmdID>
                <Data>0</Data>
            </Alert>
            <Replace>
                <CmdID>3</CmdID>
                <Item>
                    <Source>
                        <LocURI>./DevInfo/DevId</LocURI>
                    </Source>
                    <Data>16313492</Data>
                </Item>
                <Item>
                    <Source>
                        <LocURI>./DevInfo/Man</LocURI>
                    </Source>
                    <Data>Microsoft Corporation</Data>
                </Item>
                <Item>
                    <Source>
                        <LocURI>./DevInfo/Mod</LocURI>
                    </Source>
                    <Data>Microsoft Windows NT Workstation 6.3 (Tablet Edition)</Data>
                </Item>
                <Item>
                    <Source>
                        <LocURI>./DevInfo/DmV</LocURI>
                    </Source>
                    <Data>1.2</Data>
                </Item>
                <Item>
                    <Source>
                        <LocURI>./DevInfo/Lang</LocURI>
                    </Source>
                    <Data>en-IN</Data>
                </Item>
            </Replace>
            <Final />
        </SyncBody>
    </SyncML>
    This message sent to device for which no response was received:
    <SyncML 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>http://localhost:8000/handler.ashx</LocURI>
            </Source>
        </SyncHdr>
        <SyncBody>
            <Status>
                <CmdID>1</CmdID>
                <MsgRef>1</MsgRef>
                <CmdRef>0</CmdRef>
                <Cmd>SyncHdr</Cmd>
                <TargetRef>0</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>

  • %PATH% issue sending job

    11g grid control, 11g agent, 9i database
    installed agent, echo %PATH% and dont see the agent binaries there.
    created a job locally on machine for rman, runs ok from command line and scheduled tasks but fails from grid control when I created an OS task job. server has dbschedule as its preferred credentials
    Put some logging in, can see it logged on as dbschedule.
    however the %PATH% now has my 11g agent install path at the front of the path so is failing as the 11g binaries are incorrect for the 9i database.
    I can get round this by setting the paths and homes in the script. However.....
    If I send an RMAN specific job down from grid control it fails as well but this time it forces grid control to lose its configuration with the 9i database. Im pretty sure its related to the PATH issue above.
    anyone know why this is happening and how to fix? Im pretty sure its the logon interactive and logon as a batch job are the issues but dont know why the PATH would be different.

    answered this myself in case anyone else comes across it. If you call an OS job from grid control ,the agent on the server that your calling, prepends the path with the agent version binaries, so if your path on the agent server is d:\oracle\9i and youre using an 11g agent
    calling the OS job from GC means the PATH gets changed to d:\oracle\11gagent\bin;...more 11g paths;d:\oracle\9i so the wrong binary is used for sqlplus or RMAN or whatever tool you wanted to use
    Should always be putting paths in any OS script anyway but interesting to note the behaviour.

  • Database error - MDM server installation

    Hi,
    I installed SQL Server and then MDM server. Now SQL server is up, server sign on console is green,  when I try to unarchive repository archive, I got database error: error to initialize database. (I uses "sa" to connect )
    What is needed to configure MDM to talk with SQL Server?
    Thanks a lot in advance!
    David

    Hi Subbu,
    When i tried to set DBMS settings or unarchive repository, it prompt me <server name>[Sql Server] Initialization. Two entries are needed there:
    Data file path:
    Transactional log file path:
    I set them as following:
    C:\Program Files\Microsoft SQL Server\MSSQL\Data
    C:\Program Files\Microsoft SQL Server\MSSQL\Data
    then get error:
    "Unable to set current database with database server";
    "The MDM repository list schema has not been created"
    I also tried to input as "C:\Program Files\Microsoft SQL Server\MSSQL\Data\mdmsp3_Data.mdf" and C:\Program Files\Microsoft SQL Server\MSSQL\Data\mdmsp3_log.ldf"
    still get the same error.
    Please put some light on this!
    Thanks!
    David

Maybe you are looking for