BlackBerry® Enterprise Service 10

[dday0002]

As stated in the subject the environment that I am working on is BES 5.0 installed on Windows Server 2008 in a VMWare esx 4 virtual machine and connects to our exchange 2007 server. Since this is a virtual machine, to install a sound card I had to get a usb sound card and hook it up via a ip enabled usb hub. The sound card has been installed on there server just fine, along with windows media player 11 and all the right codecs. The problem is when I try to play a wav attachment from my email, I get the error "An unknown error was encountered" (the wav file is encoded with g711). I can play the wav files directly on the server, or if I load the wav file onto my blackberry with a microSD card I can play it there in the included media player, but not if I try to open it from the email attachment. Please let me know if there is anymore information that is needed I am pretty much out of ideas at this point. I will also note that I have tried opening .doc files and they seem to open fine.

Thanks

Derek

[knottyrope]

not sure if this is relevent but take a look anyways

Unable to view or open attachments on the BlackBerry smartphone

http://www.blackberry.com/btsc/KB11304

[dday0002]

Thank you for the reply, unfortunatley this does not apply in my case.

[dhowell]

I'm experiencing the same issue.  BES 5 running virtualized in ESX pointing at Exchange 2007 and .wav files are simply not recognized by the handhelds.

[tng403]

I have the same issue with only these 2 devices, 7290 OS 4.1 and 8703e OS 4.2.1.  Other users that were unable to play wav attachments were resolved by upgrading there OS to 4.5 and higher.   

[ameadows]

Did you ever find a suitable resolution to this issue?

[ictexploitaitie]

Hello, just a little remark, did you get info from RIM regarding compatibility of your ESX environment?

ESX4.0 is not supported as stated in the documentation (not mentioned in documentation)

it only says : 

The BlackBerry Enterprise Server and its components support the following virtual environments:

            -VMware® ESX Server version 2.5.2 or later

            -VMware ESX Server version 3.0.1

            -VMware ESX Server version 3.5

Thanks for the info