Strange bug in "Smart Device Authentication Utility"

  • Thread starter Thread starter superfluent
  • Start date Start date
S

superfluent

I'm trying to connect to my device using Smart Device Authentication
Utility. I launch the sdauthutildevice.exe on the device, select the
correct network device and start.
On the PC i launch Smart Device Authentication Utility and enters the
device ip address.

I click on "Set up device" and Smart Device Authentication Utility
displays a fairly large, completely blank message-box. Not even the
"OK" button has a caption! Anyway, after klicking the blank button on
the messagebox the Smart Device Authentication Utility status says
"connected". However, I cannot connect to the device, and checking the
processes running on the device i do not see ConnmanClient.exe process.

I'm running Windows XP Pro SP2 (Swedish), VS2003, Windows CE .NET
Utilities v1.1 for Visual Studio .NET 2003, Xscale/pxa270, Windows CE
5.0 with all QFE:s up and until Q3 2005.

Any ideas?
 
I don't see that sort of thing, but the first thing that occurs to me is the
use of the non-US OS. Do you have the capability to try a Windows XP US
version for comparison?

Paul T.
 
Yes, I also figured it might have something to do with the locale so I
tried it on a US XP version and the device connects flawlessly. I've
done some more testing and I notice that when I run it on the "bad"
system, the keys are not created/stored properly on the device. The
only key file created is "bubkey.blb" and it is 0 bytes long.

I guess the message box tries to tell me something useful, but since it
dosn't display properly it's hard to make anything out of it.

Any ideas about why the keys are not created properly?
 
I'm afraid that the connection process is all pretty much under wraps. I
don't know of any publicly-available information on what it does. Some of
the team members that work on it were here for a while answering questions,
but that's kind of died down lately. You've checked the archives for
"sdauthutildevice" to see if any of the previously-reported
problems/solutions apply to you?

Paul T.
 
I've checked the archives and searched the net for a solution or
explanation but i've drawn blanks so far. We're pretty much out of
ideas here, so we filed a problem report to ms premier support. We'll
se what comes out of that.
 
Back
Top