Passport exceptions in wkssync and wksalone

(Just posted to the news sections in these Workspaces)

If you're running wkssync or wksalone on
a machine that's not previously been used with the VS.NET provider for Workspaces,
you need to do one of the following

-
Run the VS.NET provider installation package

or

-
Create the registry key 'SOFTWARE\Microsoft\Windows\CurrentVersion\\Internet Settings\Passport'
and add a string value titled 'LoginServerURL' that points to 'https://login.passport.com/login2.srf?lc=1033'

That should resolve any exceptions being thrown during the passport authentication
stages.

Thanks Ethan!

Comments

• Anonymous
  November 14, 2003
  That LoginServerURL only works for the English United States locale, right? I'm almost positive that wkssync and wksalone are not localized, but Passport is. I don't have a system where I can try this out, so my warning may be irrelevant.
• Anonymous
  November 14, 2003
  Yes, although Passports are usable worldwide and, while they contain a locale, do not require that the login be performed on the site of the same language. We're only after the cookies in this case.That detail aside, 'https://login.passport.com/login2.srf' actually works just as well :)
• Anonymous
  November 19, 2003
  No problem...Figured I'd drop my URL so you can link directly to me next time... ;)