on 03-03-2015 8:39 AM
Hi Experts,
I have added work orders from device and performed sync from the device.But encountering an :Internal Storage" error and sync has been stopped.
I have encountered this error many times and have performed reset of the Application.Kindly suggest the reason why this error will be encountered.
Thanks in advance.
Thanks & Regards,
Sravanthi Polu
Sravanthi,
When I saw this error before, it was caused by a corruption on the actual database stored on the device. This was caused by an initial sync gone bad. During the initial sync when you download all the application and data, something went wrong on the communication (Wifi interrupt) or something else.
Try using your clear client option and re-download the application again. Make sure that the initial sync is solid. This is the golden rule of thumb. The first sync has to be a clean sync. (Like you didn't make your computer go to sleep while you are still waiting for your iPAD to finish synching on your initial sync or you start doing some other things in the background while your iPAD is synching or your iPAD went to sleep).
Make sure your Agentry IPAD client 7.0.6.2.4 is compatible with your Agentry Server or SMP 3.0 server. I am assuming you are using the same version that was released.
Hope this helps.
Regards,
Mark Pe
SAP Senior Support Engineer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Many thanks for the reply.I have encountered the error while adding data from the device.If i perform Clear User Data and re-sync the application, the locally added data would be removed from the device.
Please suggest how to resolve the error in this scenario.
Thanks in advance.
Thanks & Regards,
Sravanthi polu
Sravanthi,
Another area we saw this occur are as follows (Agentry 7.0.2.X or 7.0.3.X):
A good Agentry.db with the same data is 40% the size of the bad Agentry.db.
We tried suggesting to see if there is something wrong with the commissioning and try a re-install of the Agentry client software instead. There must be an incompatible Agentry.db between the server and the client.
Do you have a clear reproduction step on how to really get it? This is the only way it can get fix.
Was there any lead from the logs on the type of transaction you are doing? Was it an attach document or something else?
Regards,
Mark Pe
SAP Senior Support Engineer
Sravanthi,
Can you duplicate this on the fly all the time? If you can give me a direct reproduction step that is reproducible from scratch then we can help you out (right away).
Let me know if you can share the exact replication step from the beginning. If you cannot reproduce on the fly (all the time) and do not have an exact reproduction step in your environment then it will not be easy to resolve. But if you do we are in business.
A corrupted agentry.db is in a state that is too late in the process to resolve. We need the steps to get in this state. This is also true with Daniel's comment. If you know the repro steps let me know.
Regards,
Mark Pe
SAP Senior Support Engineer
Sravanthi,
Thanks. If you do update this thread - I will personally get an email that the thread was updated. All other customers who have seen the same issue should try to help to get the repro steps so we in the SAP Labs for Agentry (and the support team) can assist immediately.
Please also specify your Agentry or SMP 3.0 version as the releases to SMP 3.0 is strictly controlled (with time) and if the fix needs to go in we need to get it in before the code is frozen for release. If you are using Agentry 6.0.X and earlier, it is suggested you do the upgrade to SMP 3.0 (Agentry 7.X) soon.
Regards,
Mark Pe
SAP Senior Support Engineer
Mark,
I saw this error once last week.
SMP 3.0 SP07
iOS client using SMP SDK SP06 PL02(Agentry version 70.6.0.2)
The end user claimed to perform a delta sync that morning in the yard and did not do anything with the device. He reports seeing the "Inactive timeout" error that is configured in the Agentry Editor.
He did not touch his device the whole day, came back to the yard to finish his work for the day and then saw this error. I had to reset his client to get this to work. I tried to reproduce this on my device but was not able to do so.
Just wanted to update this thread with our results. Have any other customers reported the same issue?
Regards,
Abhinav
Hi Sravanthi -
What iOS version are you running? Can you reproduce the issue on demand? If so, what are the steps? Additionally, have you tried testing on the latest version of WM to verify whether the issue persists based on your scenario/s?
Thanks,
Ray
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.