I am running MS Exchange 2003 with SP2, and have two devices with WM5.0 / AKU2.0 on them (Imate Kjam and Imate Jasjar) The push email funtion works perfectly if I turn on the device and click Send/Recieve in pocket outlook once. It will bind and then keep pushing untill I go into an area without coverage. The problem is that it is not automaticaly binding to the data bearer (GPRS) when I turn on the device, or after I enter a bad coverage area and return to good coverage. So what I have is very intermitent Push Email service for an hour or two and then must reset and manualy start a sync to connect again (IT Does stay connected or keep the heartbeat going untill loosing coverage again) So in essence it is all functioning togetehr propperly, but the service is up for a few hours and then with a reset up for a few hours again. I am assuming that the intent of the Push Email service is to provide a blackberry like email environment. What I have currently is more of just a novelty in that when bound I get my email within 2 seconds, but it requires constant personal maintenence to make sure I am connected and the heartbeat is going propperly. Does anyone have any ideas as to a solution?? I am correct in assuming this should be rocksolid like a blackberry when everything is functioning as it is suposed to, correct?? Your help is greatly appreciated. BR Seth
Hi, I had the same problem with Imate JasJar. The problem seems to be when there is pocket outlook in memory. You can try to close pocket outlook with task manager and you will see that the gprs connection will work right with activesync and directpush. The problem, it's a my opinion, is on the addin for MMS. I have tried to rename a registry key that governs the MMS configuration and now i can leave pocket outlook opened. "seth" wrote: > I am running MS Exchange 2003 with SP2, and have two devices with WM5.0 / > AKU2.0 on them (Imate Kjam and Imate Jasjar) > > The push email funtion works perfectly if I turn on the device and click > Send/Recieve in pocket outlook once. It will bind and then keep pushing > untill I go into an area without coverage. > > The problem is that it is not automaticaly binding to the data bearer (GPRS) > when I turn on the device, or after I enter a bad coverage area and return to > good coverage. So what I have is very intermitent Push Email service for an > hour or two and then must reset and manualy start a sync to connect again (IT > Does stay connected or keep the heartbeat going untill loosing coverage again) > > So in essence it is all functioning togetehr propperly, but the service is > up for a few hours and then with a reset up for a few hours again. > > I am assuming that the intent of the Push Email service is to provide a > blackberry like email environment. What I have currently is more of just a > novelty in that when bound I get my email within 2 seconds, but it requires > constant personal maintenence to make sure I am connected and the heartbeat > is going propperly. > > Does anyone have any ideas as to a solution?? I am correct in assuming this > should be rocksolid like a blackberry when everything is functioning as it is > suposed to, correct?? > > Your help is greatly appreciated. > > BR > Seth >
