-----Original Message-----
Yes.
1. Start regedit.exe.
2. Navigate to HKEY_LOCAL_MACHINE\
SOFTWARE\Microsoft\Shared Tools\
Web Server Extensions\Web Extender Client
3. Look for a value named wecctlflags.
4. Either delete this value or set it to zero.
In case you're curious, here's the explanation I received
from Microsoft:
The "wecctlflags" is a testing value left over from
previous versions of FrontPage. Setting the value to 2
forces FrontPage to attempt to bypass WinInet for Internet
functionality, so earlier versions of FrontPage would fall
back on their built-in Internet libraries that were
named "xxxxNWI.DLL", where the "xxxx" portion of the file
name represented the naming convention for the version of
FrontPage. So for FrontPage 2000 and FrontPage 2002 the
files were "FP4ANWI.DLL" and "FP5ANWI.DLL" respectively.
In the case of FrontPage 2003, the naming convention would
be "STSxxxx.DLL", hence the error message displaying the
filename that you were seeing. Since we don't support
that fall-back functionality any more, we don't ship the
DLL that FrontPage was trying to find, but the code is
still in the product to look for it when "wecctlflags" is
set.
Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------
.
