Last post Mar 25, 2008 05:13 PM by iconan
Aug 09, 2002 02:17 AM|JariR|LINK
Aug 12, 2002 03:41 PM|omar_k|LINK
Aug 13, 2002 02:44 AM|JariR|LINK
Nov 29, 2002 06:45 AM|snorrk|LINK
Sep 24, 2003 12:19 PM|scev|LINK
Apr 28, 2006 11:56 AM|Muffin|LINK
I had the same problem recently and I fixed it by destroying my local profile and then rebuilding it. To see if this would work for you, logon as another user and see if 'they' get the same problem. For me the problem went away if I pretended to be someone
else. If the same applies, I recommend something like this...
Take a copy of the files in your local profile. Logon as another user. Launch Control Panel / System, select the "Advanced" tab and select [Settings...] under the "User Profiles" heading. Select and [Delete] the offending profile. Log off. Logon as yourself
again to create a new profile. Copy back only the files that you need from the backup you took earlier.
It's can be a pain to go through all that but it worked for me.
Apr 28, 2006 08:19 PM|Mikhail Arkhipov (MSFT)|LINK
May 06, 2006 06:48 AM|hnisp|LINK
IIS ==>>FrontPage2000 Server Extensions
Aug 16, 2006 10:32 AM|Vittorio5|LINK
Has anyone figured out the the solution to this problem.
I am getting the same error after having instsalled Atlas over the weekend.
Aug 16, 2006 10:39 AM|Vittorio5|LINK
I have tried reinstalling the FrontPage server extensions
I have tried reinstalling VS.
I have Visual Studio 2003 and Visual Web Developer on the same laptop.
All worked well untill yesterday. The only thing different is that I installed the Atlas tool kit over the weekend. When I tried to open a Visual Studio 2003 project for the first time after installing Atlas I get the following error:
"Cannot find the components for communicating with FrontPage Server extensions"
I need help really fast!
Sep 11, 2006 11:05 AM|rjcobain|LINK
Sep 13, 2006 12:42 PM|Vittorio5|LINK
Thanks for you help Robert!
I have non of those applications installed on my computer.
Still trying to figure this one out.
Mar 26, 2007 06:57 AM|shabana|LINK
ur advise hepld me lot
Mar 25, 2008 05:13 PM|iconan|LINK
Same problem occured when switched to Vista
read thread, read Muffin's suggestion, signed in as Administrator (the superuser account that is normally disabled by default) the problem went away.
went pack to my user account, right clicked on visual studio 2008 icon, selected run as adinistrator, problem went away
omg what a potential wild goose chase.