re: the KB article - Call me crazy- but if you have other 8830s with like software, wouldn't those throw errors too? I am not sure if updating the device.xml file would help.
I'm seeing the same thing. One user of mine has an 8310 that's identical to mine, yet the error pops up for him: (email and PIN changed for posting)
[40000] (06/16 07:27:11.659):{0x12E4} {user@domain.com, PIN=12345678, UserId=107}SCS::CheckForFailedAppDeliveryRequests - Command SEND_APC_APP, Status 6, StatusMessage "GetHHCodePackages reported: HHCM_DEVICE_NOT_SUPPORTED. Upgrade your copy of device.xml".
His "Blackberry Device Model", "Hardware ID", "Platform Version", and "Blackberry Version" are identical to mine in the BES Manager console.
*I did notice that I have an old software config on the BES with a path that points to the \\UNC of an old server, but it's not assigned to anyone. I'm mentioning this because these errors show up in the "Software Config Status" tab.
Last edited by rafael_gonzalez; 06-17-2008 at 11:38 AM..
I have the same issue with an 8300 w/ AT&T. I have went through the knowledge base article and still get device not supported. We are on BES 4.1.5 for Exchange and Exchange 2k.
Does the server store one copy of Device.xml and when you follow the above instructions it just overwrites the file or does each new device.xml just update the db?
I am getting the same warnings on my BES. We run BES 4.1.5.26.
This is happening for a few different models and different carriers. It seems to have started when we upgraded a peice of software to get pushed out to the Blackberry.
We updated the device.xml file with a few different versions and re indexed, all to no avail.
Though it doesn't seem to be messing anythiing up, still trying to find an answer.
I have seen this on our Verizon 8330's using 4.2 OS. Upgrading to 4.5 made the hardware information available to BES & therefore resolved the software push issue. (it is not a device.xml issue it is the fact that the 4.2OS is not reporting the hardware information to the BES. You can verify by hooking up the device to the BES Manager and trying to view the hardware details there, even via USB they are missing)
__________________
BESX 4.1.7 on Exchange 2003: 65 Devices
BESX 5.0.3 on Exchange 2003: 2007 Devices
Same issue here - running latest version of BES for Exchange and get dozens of these errors in the event logs of the BES. We are running mostly 8330s and 8130s but still have a few 7130s.