I have same problem and have been trying everything to get this fixed. Dell support in Sweden basically said to reinstall Windows so not much help there. The problem seems to be the Dell Mobile Broadband Card Utility software.
Have reinstalled the Dell Mobile Broadband Card Utility several times and have upgraded the modem firmware but nothing really fixes the problem. Keep getting the “Unknown application error:9999” as soon as I start the Dell Mobile Broadband Card Utility software. This happens in both win XP and Vista.
Have found a temporary solution to get it working in XP:
If I don’t disable the Bluetooth radio it will work but only for about 20-30 min then it crashes. Probably some port conflict between Bluetooth card and the Dell 5520 card.
Another solution I have found under XP is to only install the drivers for Dell 5520 card and then set up a normal modem dial up connection through Windows. Problem is that I cannot change then modem configuration (e g use 3G or GSM) using this setup. Also it requires you to disable any PIN code on the sim card (so not good for security).
Cannot get it to work at all under Vista. If anyone finds a proper solution please post…
- - -
Dell Latitude D8302GBDell Wireless 5520 Generic L Mobile Broadband Card (3G HSDPA) MinicardIntel 3945ABGDell Wireless 350 Bluetooth Internal CardXP Pro and Vista Ultimate 32-bit
Since sending it yesterday I have heard from the devs with this note:
" Error 9999 is generated by Novatel's code when it looks like an object is not available (specifically license manager or the zeepe window object).
They have dealt with this issue before, having asked our help before - and from their responses it looks like the customer was somehow blocking objects."
There follows a whole bunch of detail, including the observation that:
>> When the customer adds a Latitude D830/D820 (Dell factory image) to
>> their domain (Admin Group) and runs the DMBCU application, they get
>> the error message "Unknown application error: 9999".
The application only generates this error message after putting a system onto the customer's domain. Getting the system back out of the domain, the application runs fine again.
Customer claims that it has to do something with his Active Directory, but due to about 2000 possible rules he needs to know which privileges the tool exactly needs to be run. <<
I see that we provided a whole bunch of CLSIDs to check through, following which things went quiet (which we always have to assume means 'resolved').
I don't know if any of this rings any bells in your situation, but I include it as being possibly relevant.