Skip to Content
author's profile photo Former Member
Former Member

Temporary MI data lost


We want to know where the temporary data are saved before MI synchorization process. We have a problem because when the synchorinzation hung, we have ty reset the MI mobile client, so the data are lost.

There any way to save this data?? where the files are located in MI directory files before sync??

Thanks a lot


Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2008 at 05:50 AM

    Hello Gaby,

    By reset do you mean you reinstalled it again or you restarted the client?

    If you just restarted the client and did not perform a hard reset, all you have to do is sync again and the sync data will be sent to the server.

    Best Regards,


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jan 08, 2008 at 06:29 AM

    Hi Gaby!

    well, as the previous post already mentioned: why is not possible to simply sync again? Even if you need to restart the device, the information is not lost. Sync again and all data should go to the backend.

    If you have an error that halts you back from sync - what is the APP you are using? MI is usually stable from that point if the APP is corretly developed - and this is the case for SAP standard Apps.

    Well, anyway, if you really do not trust MI - I know it is tricky sometimes. The data is stored in the DATA folder inside MI installation folder. But I think this is not really the information you need, cause from there you can not read the data with a textbrowser or so. This is okay, because this gives us somes security as well.

    Okay, why not another route: either with every write process to MI persistence you write the information to a textfile as well. Or betteR: before you sync you run through the persistence layer, take all items in status L and safe them to your backup textfile.

    Then you have the backup solution for the case Sync fails again. It is easy to develop, it just can take a few seconds to run through the complete persistence layer.

    Well, but again: why do you need to reset the device and why is it not possible to sync again after restart of the device? AND: reset device? Is it a complete new installation or just the reset of the persistence? If it is a complete new installation - well, then we should talk! This is really not necessary in 99.9% of the cases MI users do that!

    Anyway, I hope this helps to solve the issue for you!



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Gaby,

      so it is just a Soft Reset of the device, not a reset of the MI persistence. Ok, that is something else.

      Well, what application are you using? This error usually shows up on certain devices, yes, but usually this is just the frame refresh that is missing. The sync itself run succesfully and the data was transfered already in the first try. How should I explain that ......

      Using MI with JSP, we have a browser and a server. The browser just displays the informations he gets and the server does the work. Even on a PDA this is the cae. All is running on that single machine. So a sync: if you press the browser button, the server is told to collect the data and send it to the middleware. So collection takes some time, then it send the data and then it send data from middleware to client. Client books in the data to persistence and this takes a while again and at the end the IE screen is told to end the sync loop screen.

      Well, unfortunately because of caching, this last stept is sometimes not successfull. On some machines this happens quiet often, on others it enver shows up with this problem. So what you say as Suync Loop is simply the caching problem of IE/JSP and not a problem of the sync in general.

      Because of that please check if the data is not there in the backend and on the client after such a mistake.

      It helps to add a timestamp to the URL. I am not sure if you have an own developed app or a standard APP like MAM. Even that makes no difference, because we talk about the usual MI sync here, it would be nice to know.

      Anyway I hope this helps to switch on some lights again.



Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.