TonyJuurlink

I am encountering "Access denied" errors while enumerating services on our Panasonic CF-19 MK5 toughbooks (and some other models) with the Microsoft stack. The devices ship with the Toshiba stack. We uninstall the Toshiba drivers, and the Microsoft stack/drivers install automatically.

Initially, all works properly. When we run the BluetoothDiscoveryDemo application, devices show after Discovery and we can Enumerate Services without issue. Eventually, we end up getting an Access Denied message while attempting to Enumerate Services. Once we get the Access Denied message, we are no longer able to enumerate services, even if we reboot the machines. If we re-install and uninstall the Toshiba stack things work properly for awhile, then we start getting Access Denied again.

We have no issues with enumerating services using the Toshiba stack, but other applications we need to hook into require the Microsoft stack.

TonyJuurlink

Thanks. I don't understand why they would initially work without pairing, then subsequently require pairing. I would think that if the devices required pairing before allowing to enumerate its services, they would consistently require pairing.

Not alway but I agree, it looks strange. Would be great if you can provide me more information: which driver runs on client side, which on server? Is there any software on server side? OS on both sides? As more infor as possible so we can try to reproduce the problem here and may be find workaround.

In this case, we are testing between two same model/version devices (client/server). We restore the devices to factory os, and after uninstalling the Toshiba Bluetooth software, there does not seem to be any other software present that would affect bluetooth.

Are there any other specific version details that you would find helpful?

Not to overload, but:We have also tested with various Panasonic CF-19s. The MK2 and MK3 models are not experiencing this issue. The MK4 and MK5 models are experiencing this issue.MK2 and MK2 are running HCI version 3.3164, LMP version 3.3164.MK4 and MK5 are running HCI version 4.5276 and LMP version 4.5276.Testing indicates the issue manifests when running Windows 7, and the devices were not having the issue with Windows XP.

Thank you a lot for the detailed information. I will try to reproduce the problem (from your information I guess it is something with BT 4 BLE mode support on Win 7/8) and keep you updated with my experience. I think I'll have something useful in a couple of days.

I have checked the problem you reported and found that it looks like WCL returns wrong error code for this situation. Actualy WCL shoudl return WCL_E_SERVICE_NOT_FOUND instead of WCL_E_ACCESS_DENIED when call wclBluetoothDevice.EnumServices fals with no one service found on device. So temporary just keep in mind that this is wrong error code. We will fix it in WCL in next release.