View Single Post
Old 08-24-2009, 01:35 PM   #1 (permalink)
BES admin
Talking BlackBerry Encyclopedia
 
BES admin's Avatar
 
Join Date: Dec 2005
Location: NY
Model: Droid
Carrier: Android -> AT&T
Posts: 491
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default BBConvert.exe Unable to locate. WMVCore.DLL was not found

Please Login to Remove!

I have a BES 5 server with a handful of test users up and running. It seems that when folks open certain attachment types (.doc, .docx, .wav seem most common) I receive a popup window at the BES with the following message:

"BBConvert.exe - Unable To Locate Component : This application has failed to start because WMVCore.DLL was not found. Re-installing the application may fix this problem."

The System log has the following entry:

Log Name: System
Source: Application Popup
Date: 8/24/2009 1:02:58 PM
Event ID: 26
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: <BES>
Description:
Application popup: BBConvert.exe - Unable To Locate Component : This application has failed to start because WMVCore.DLL was not found. Re-installing the application may fix this problem.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Popup" />
<EventID Qualifiers="16384">26</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2009-08-24T17:02:58.000Z" />
<EventRecordID>19526</EventRecordID>
<Channel>System</Channel>
<Computer>troy-bb2.win.rpi.edu</Computer>
<Security />
</System>
<EventData>
<Data>BBConvert.exe - Unable To Locate Component</Data>
<Data>This application has failed to start because WMVCore.DLL was not found. Re-installing the application may fix this problem. </Data>
</EventData>
</Event>


RIM support blames Miscrosoft, as the WMVCore.DLL is a Windows Media Player component, but their application is calling it, and thus, they won't provide any help.

I've tried registering WMVCore.DLL in both "System32" and "SysWOW64" directories. It was working for a few days and then out of the blue, it began again.

BES Server info:
BES Version: 5 w/SR1 (SR2 is not installed yet)
Messaging Environment: MS Exchange 2003 SP2
Windows Version: 2008 Ent. x64
BES Server running as VMWare Client on ESXi server
IBM x64 Server hardware
__________________
You had me at EHLO!
Offline   Reply With Quote