Does anyone know of a solution to this? We are having the same problem.
Thanks,
Paul
Quote:
Originally Posted by thomas.fischer
Hi,
we try to poll the DST Patcher to our devices wireless but got a problem.
We´ve configured the software configuration as described from RIM and the Config File is also fine and assignable to users.
We´re using BES 4.1.1 SP2 and get the following error messeage in the POLC Log:
[40000] (02/19 10:24:08.034):{0x1E40} RequestHandler::PollForMissingApps: Starting Poll For Missing Apps.
[20000] (02/19 10:24:08.143):{0x1E40} Syntax error in vendorxml line 0, column 0. Reason: XML document must have a top level element.
[20000] (02/19 10:24:08.143):{0x1E40} Syntax error in devicexml line 0, column 0. Reason: XML document must have a top level element.
[40000] (02/19 10:24:08.143):{0x1E40} RequestHandler::PollForMissingApps: Completed Poll For Missing Apps, elapsed time 0 seconds.
Does anybody got a solution or a tip what the problem is ?
We have found that if we apply the Exchange update to the BES server, the time is out by 1 hour. We have patched the BES with the Windows 2003 DST patch, the SQL update and updated only those handhelds that are 4.1.x that can receive the DST patch. We have been told by our telco's that handhelds with 4.2.x do not need the DST patch if the server has the SQL patch. We have done testing on our test BES server and so far all seems to work fine.
Yesterday I applied all the patches required to our BES server and used the Handheld Configuration to apply the patch to our BB's. However, none of the BB's have had the patch applied. The Handheld Configuration app is showing the Configuration Status for all the BBS as Handheld State Unavailable.
Does anyone have any ideas?
I have wiped a BB and deleted the user form the BB Manager and added and activated the BB again but the problem is still there.
I run a domino environment and I used the techical knowledge centre KB15122. Reading the note we applied the patch via the sql because most of our devices were 4.2.xx and above. Speaking with other admins the devices 4.1.0.344 and above would also pick up the SQL patch.
Now we are getting the following:
8800/8100/8310/8700's showing incorrect time on the front screen, yet when you go into Date/Time its correct. Now this is not uniform across the fleet, other show incorrect times in both places. All time is set to "BlackBery" and we do not have any option to switch over to network.
By pulling the battery this resolves most of the issues. If users manually change the time it screws up the calander so we are sending then the manual patch and once the patch is applied to the device and rebooted all is OK.
We have a call opened with RIM but I'm not holding my breath. I don't know if the device is not playing the game or not.
Could anyone tell me when looking in the logs, is there anything I should see that could point me in the right direction of what could be causing the devices to switch or what is actually the problem. The BEs's are all OK