Mike,
This came back from the field, and wasn't in the trace log.
As it happened it has been resolved. The user did not have any bluetooth device (and likely no drivers or stack installed). After installing his dongle correctly the problem went away.
I imagine the fault is still due to not checking the API loaded OK and could be more gracefully handled though so I will look into it.
Thanks