Suddenly the proximity sender needs a password.

[jordi120]

A few customers noticed this, suddenly the proximity sender, or whatever, starts to ask for a password. Here you can see an image of what is happening:

http://img175.imageshack.us/img175/192/imagen7ru.png

I am doing something wrong?? Maybe the usb dongle gets mad?

[Mike Petrichenko]

wclAuthenticator helps you.

[jordi120]

but the wclAuthenticator is open. Maybe something happens that closes the authenticator?

each time I start the proximity sender I do this:

            if (!wclAuthenticator.Active)
            {
                wclAuthenticator.Radio = this.device;
                wclAuthenticator.Open();
            }

Maybe I should check each X seconds if the wclAuthenticator is'nt active...

[Mike Petrichenko]

Does demo app work? Also what BT driver are you using?

[jordi120]

I've been notified of this error with a Vivanco usb and a Emtec, they didn't send me the model  of the Vivanco so I couldn't find it...

The Emtec one uses the windows stack, and the generic windows drivers.

I have been thinking... maybe the OBEX service of the dongle stops running?

[Mike Petrichenko]

I think there is something wrong with Authenticator usage.

[jordi120]

:S:S ok but... it's so wierd, because the app works fine, but suddenly starts to do this things (and only in a few machines, 2 PC's from almost 40 have reported this error :S).

Furthermore, when this error begins, every sending try to every single device, throws this password windows. If I didn't use the authenticator, the proximity sender would work fine with some devices (the ones which don't need a password),

[Mike Petrichenko]

It is very strange. Could you please test our software on that PCs? Or may be just ProximitySender demo?

[jordi120]

This is how I use the authenticator and the proximitysender:

On main form Closing event (irrelevant):

                if (wclProximitySender.Active)
                    wclProximitySender.Stop();

                if (wclAuthenticator.Active)
                    wclAuthenticator.Close();
                wclAPI.Unload();
On custom functions 'proximitySenderStart()' and 'proximitySenderStop()':

        public void proximitySenderStart()
        {
            if (!wclAuthenticator.Active)
            {
                wclAuthenticator.Radio = this.device;
                wclAuthenticator.Open();
            }
            if (!wclProximitySender.Active)
            {
                if (wcl.wclErrors.wclShowError(wclProximitySender.Start()))
                    wclAuthenticator.Close();
                setStatus("Iniciando campanyas", 1);
            }
        }
        public void proximitySenderStop()
        {
            if (wclProximitySender.Active)
                wclProximitySender.Stop();

            if (wclAuthenticator.Active)
                wclAuthenticator.Close();
            setStatus("Campanyas detenidas", 9);
        }

And this code on the app init:
                wclProximitySender.SendRadio = this.device;
                wclProximitySender.DiscoveryRadio = this.device;
                wclAuthenticator.Radio = this.device;
                wclAuthenticator.Open();
                if (wcl.wclErrors.wclShowError(wclProximitySender.Start()))
                    wclAuthenticator.Close();
Sorry for bothering you so much.

[Mike Petrichenko]

It looks absolutly correct. But it would be relay great to check our TextBlue application on those PC. As there may be bug in WCL .NET which may not appear in WCL VCL so we can compare and fix.

Also please check what drivers are there (APIDemo shows it).

[jordi120]

I will try to check your software or the Demo, but don't know if I will be able since it's not my PC.



The thing is this don't happens every day, somedays it does, and somedays it does not, and this PC's are active the 24 hours of the day, so your software I guess will have some limitations of max number of files sended to a device when is in trial mode, didn't it? i will ask to put the proximitySender Demo one day...

Thanks you btw

Drivers on those pc's are the windows one's (windows stack and generic bluetooth radios drivers) I think...

Pd:Then you thing it's impossible that the OBEX service fail?

[Mike Petrichenko]

You can try demo. But the main information I need:

* OS
* BT driver

Also would be really great to know what devices (remote device) cause the issue.

[jordi120]

OS: Windows XP sp2

BT Driver: Microsoft Stack

The remote devices... are a lot, a really lot, i think i saw a Nokia x600 music? well I don't know, since my app only stores the MAC (I don't know if the model can be known from the MAC)

[Mike Petrichenko]

try to store names also, it should help to identify devices.

[jordi120]

Yap, I will (since my app is constantly exchanging data with a remote server, i tried to minimize as much as possible the size of the DB, so I did'nt thought of storing the devices name, furthermore, this data will be never used by te user, the app, just show plots and graphics), just for this couple of computers...

What do you think, is a problem of the wclauthenticator, or something else? do you think I should try to put a little 'watchdog' that checks if the authenticator is active, each X period of time? or this is useless...?