POL 3012 device write error on windows mobile 6 and lite 10.2.0.1

Question

Hi all,
This was an issue even some times ago and still appearing on and off for some clients and I did not find any recovery process which could be done remotely via the web to go admin.
1. When the device write error occurs we cannot initiate sync or any other from client or server and it just gives pol 3012.
2. If this happens to a client in far away area , how can we re configure the device from remotely (still device management is up and running).
3. If there is any mechanism to do a complete database refresh and re-create at client device from the admin functions in web to go device management.
4. Even the complete refresh sync has no use when this occurs and If we can delete and recreate the odb files only on the device it will be very convinient.
5. Currently only way i can see is just to uninstall the client and do a complete installation with deleting the odb files that arfe in the storage card.
Any help on this is highly appreciated.
Thanks
Paninie.

Answer 1

greetings:P
well in our client it doesnt work to "and then asked the user to ..." users usually dont know how to use the handheld , some times they are very old and we never ask the users to do something like deleting the files manually because that normally causes them to start complaining and say stuff like "your app sucks etc etc":(:(
my proposal is much simplier and will work i think for your purpose. you simply create a small c sharp application. you asked
"How to create it to stop DMAgent."
well thats very simple in c sharp and in most languages i think,
OpenNETCF.Diagnostics.Process is the namespace you need to work with, you simply kill the process with name dmagent.exe. this is the simplest way to close the dmagent in 5-6lines of code.(use the OpenNETCF.Diagnostics.Process class, from the OpenNETCF
library, which you can download from http://www.opennetcf.org)
then you use the normal file.delete to delete the files of the database, and then you want to do the sync, that can be easilly done through c sharp as you already do i guess.
the cab file i mentioned is simply the way to distribute the small c sharp app to all clients. it can be created with simply cab files generators which are freeware or through visual studio.
you can distribute the small app to all clients simply through the packaging wizard. so when a user has a problem you dont need to "ask the user to .." you just tell him ok, leave the the handheld alone for 15 minutes and it will get fixxed by itself, you send the command i described in my previous reply and the handheld's small app fixxes the problem. the user doesnt need to get involved. the cab file is sent to all clients (actually it is downloaded through oracle lite) . of course you dont wait for the problem to happen and then send the cab file. all users will have the cab file's small application preinstalled . it will be on the mobile device waiting for the command. so even if in some point this error occurs you can handle it. you dont wait for a user to call and say i have a problem and then send the cab file.
btw if you want to distribute your cab file you open the packaging wizard, edit your application..go in the file selection tab and select your cab file. the next time all users sync they will be asked to install the cab file. this is how we install our cab files, and this is how we install our application upgraded versions, we do not copy the cab files in a flash disk or send them with email or stuff like that. all application cab files are distributed through oracle lite remotely when ( i love olite for this, in other systems like mobilink you need to buy a second program to do that or else send your cab files through email.... ) .
code for stopping dmagent should look like about this
using OpenNETCF.ToolHelp;
ProcessEntry[] processes= ProcessEntry.GetProcesses();
foreach(ProcessEntry pe in processes){
if(pe.ExeFile.Equals("dmagent.exe")){
pe.Kill();
break;
stopping the dmagent is like stopping any other running process on the windows mobile.
so you have 5-6 lines of code for stopping the dmagent+1-2 lines for the file.delete (for the database files)+1 line for the c sharp olite synchronization . your app shouldnt be more than 10 lines of code i think.
we have used this cab file tactic which was proposed from an oracle lite representative actually after our request for creating a server side initiated synchronization which syncs a specific set ot tables with push only. we wanted the guy on the office to have a small java app which will have a button that sends a specific command on the handheld that forces it without the user concent to sync some specific tables with push only , the normal synchronize databases command can not do this job, so we created our own small c sharp app, which is distributed as a second cab file (the first is the main app) and the users now in the office have a small java util where they select the user and then send the command (using the java apis). so this second cab file+command tactic can help in solving a lot of problems. give it a try.