wclOPPClient OnConnect "Out of system resources"

[Nature]

Hi there I think I have a bug...

When trying to send to Nokia N96 or Nokia 6500 I cannot connect, I am getting a WCL Error "Out of system resources"
Using wcl.wclOPPClient, this is the value returned from the OnConnect event in the wcl.wclConnectEventArgs Error property.

Microsoft Windows XP Professional (Embedded) Service Pack 2
wcl2wbt2.dll = 6,6,3,0
wcl2wbt.dll = 6,7,1,0
wcl.dll = 6.7.1.0
Microsoft Bluetooth stack
ConnectTimeout = 45000

Does this ring a bell or do you want me to raise a ticket for this?

Thanks

[Mike Petrichenko]

Hi,

I do not think it is a bug. This error can appear only when there is not enought memory/resources. So check your system. In normal work this error can never happen.

However, if you think it is bug, prepare the demo app which will reproduce the error or tell me the steps to reproduce the error.

BTW, it can be issue of wrong wcl2wbt2.dll version.

[Nature]

In the past I noticed I could to send to devices without the wcl2wbt2.dll (when I forgot to include it in deployments) so I know it is not essential, perhaps I should try removing it?

[Mike Petrichenko]

wcl2wbt.dll is for widcomm only.

However, I will need steps sequence to reproduce the issue. Or demo code which will reproduce the issue.

[Nature]

Okay it looks like the problem must at our end. There is plenty of memory and disk space but it looking the in Device Manager it looks like the Windows Drivers might not be fully or correctly installed. Going to try installing SP2 again and see if this helps.

If we continue to have problems after sorting out the drivers I'll send you an application and source code for testing but I expect that it wont come to that.

Thanks for the help

[Mike Petrichenko]

Ok,

Better if you can send small demo app. It is very hard to understand someone's code and will take lot of time. So simple cut/patse problem code part into new simple project which reproduces the issue.

[Nature]

Sorry for the late reply I have been on holiday This problem was due to the Windows Drivers not being correctly installed on a Windows XP Embedded machine, the engineers had just copied in some of the driver files rather than doing a full install which meant that scanning worked but some other features had problems eg the sending code. All working now I'm glad to say.

[Mike Petrichenko]

Hi,

Thnaks for letting me know