I am trying to enable the Server extensions for a folder in IIS, and I
receive the message above... Cannot create file 'services.lck'"

I have been following the instructions in the Developer Walkthrough: Using
Microsoft FrontPage Extensions for WSS Forms

I am performing these steps on my Exchange 2003 Server, running on a Windows
2000 Server.

I tried to publish from FrontPAge and I get a message that I cannot create a
subweb from a virtual directory from within FrontPage, and that I needed to
perform this step on the server itself.

However when I attempt to do that, I get the cannot create error...above.

My goal would be to create a FrontPage enabled folder on my Exchange Server
so that I can publish custom forms for users to access.

Currently users are connecting to Exchange using the OWA features and would
connect something like https://server/exchange (I am only using OWA
internally)

My thought process was to make use of other CDOHTML features and create some
custom forms that users could easily just have a link to, like
http://server/frontpage and be able to select certain forms and submit them,
so that it generates an email and sends it to someone.

Like I said the doc I am following is written by Jeff Wierer - MS Corp...and
I found it at

MSDN Home --> MSDN Library --> Servers and Enterprise Developement -->
Exchange Server --> MS Exchange 2000 --> Technical Articles

Any help woudl be appreciated.

J

WSS is only available on a Windows 2003 server. You must publish to IIS web server once the FP
extensions have been installed and configured for the default web, etc., not Exchange Server

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

"Smurfman" <(E-Mail Removed)> wrote in message
news:C262254A-00A6-4679-814A-(E-Mail Removed)...
>I am trying to enable the Server extensions for a folder in IIS, and I
> receive the message above... Cannot create file 'services.lck'"
>
> I have been following the instructions in the Developer Walkthrough: Using
> Microsoft FrontPage Extensions for WSS Forms
>
> I am performing these steps on my Exchange 2003 Server, running on a Windows
> 2000 Server.
>
> I tried to publish from FrontPAge and I get a message that I cannot create a
> subweb from a virtual directory from within FrontPage, and that I needed to
> perform this step on the server itself.
>
> However when I attempt to do that, I get the cannot create error...above.
>
> My goal would be to create a FrontPage enabled folder on my Exchange Server
> so that I can publish custom forms for users to access.
>
> Currently users are connecting to Exchange using the OWA features and would
> connect something like https://server/exchange (I am only using OWA
> internally)
>
> My thought process was to make use of other CDOHTML features and create some
> custom forms that users could easily just have a link to, like
> http://server/frontpage and be able to select certain forms and submit them,
> so that it generates an email and sends it to someone.
>
> Like I said the doc I am following is written by Jeff Wierer - MS Corp...and
> I found it at
>
> MSDN Home --> MSDN Library --> Servers and Enterprise Developement -->
> Exchange Server --> MS Exchange 2000 --> Technical Articles
>
> Any help woudl be appreciated.
>
> J

Hi,

It seems the folder you are trying to enable FPSE with is created from Exchange System Manager following the steps in the article
"Developer Walkthrough: Using Microsoft FrontPage Extensions for WSS Forms". Is that right?

In this article, it also lists the steps to convert the virtual directory to a subweb in IIS Manager. I assume you receive the "Cannot create file
'service.lck'" error when coverting the virtual directory to a FPSE subweb on the IIS Server.

I suggest you first check if the "_vti_pvt" folder exists under this virtual directory. If so, remove or rename it and then try converting again.
Also, if you are using FPSE 2000, you may consider upgrade it to FPSE 2002.

Furthermore, you may try directly creating new virtual directory under the default web site and extend it with FPSE to identify if this issue is
only with the specific virtual directory.

In case the same issue occurs with a new virtual directory, you may consider creating a new virtual server in IIS and then extending it with
FPSE to test if the same issue occurs with the new virtual server. This can identify if FPSE is working fine.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks for the info Jason.

So here is the update...
I removed FPSE 2000 from the Windows Components of IIS
I removed all the old settings I made, such as the Public Folder, Public
Store, and Virtual Directories that I had created before.

I downloaded the Web Install of the FPSE 2002 and the Hotfix, and installed
both.

Thus far I have followed the steps in the Document to the point of enabling
the FrontPage Extensions for 2002.

Then in FrontPage, things get crazy...the Doc talks about creating a blank
website at the http://server/frontpage location, when I attempt to do this, I
am unable.

Then on the exchange server, IIS I get repeated messages that the connection
to the Web server 'SERVER' was lost. Do you want to attempt to reconnect?

I hit YES, the Default Web Site starts, then a few seconds later it stops
again.

When I try to refresh the Default Web Site, I get the following:

"Unable to enumerate Web virtual directories because the following error
occurred:
The remote procedure call failed."

The event log starts filling up with these errors: (Note, that after a
reboot I get these errors 3 times, but then I do not see them again, until I
attempt something with FrontPage...)
I have looked at:

PSS ID Number: 827214 then since this was geared for Windows 2003 Server,
there is a W2K link
PSS ID Number: 885264 was related to Windows 2000 Server

It referenced a fix PSS ID Number: 885882 Which took me to here:

Microsoft Security Bulletin MS04-035
Vulnerability in SMTP Could Allow Remote Code Execution (885881)

I then downloaded this link
Security Update for Exchange 2003 (KB885882)

Tried to install it, and I was told that it was older than the Service Pack
on the machine...and something about RTM

This did not fix the issue.

I used the new Microsoft Update, there was one patch for Exchange something
like July 12, 2005, it installed, but nothing changed.

After some time, the server stops generating errors, I am then able to
reconnect the Default Web Site, and refresh the folders and Virtual
Directories.


Well, that is the update. Thanks Jason

J



APPLICATION LOG

Event Type: Error
Event Source: Microsoft Exchange Server
Event Category: None
Event ID: 1000
Date: 7/19/2005
Time: 11:57:46 AM
User: N/A
Computer: SERVER
Description:
Faulting application inetinfo.exe, version 5.0.2195.6620, stamp 3de2893b,
faulting module atl.dll, version 3.0.9435.0, stamp 3ef274de, debug? 0, fault
address 0x00001150.
Data:
0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 69 00 6e 00 65 00 .i.n.e.
0030: 74 00 69 00 6e 00 66 00 t.i.n.f.
0038: 6f 00 2e 00 65 00 78 00 o...e.x.
0040: 65 00 20 00 35 00 2e 00 e. .5...
0048: 30 00 2e 00 32 00 31 00 0...2.1.
0050: 39 00 35 00 2e 00 36 00 9.5...6.
0058: 36 00 32 00 30 00 20 00 6.2.0. .
0060: 33 00 64 00 65 00 32 00 3.d.e.2.
0068: 38 00 39 00 33 00 62 00 8.9.3.b.
0070: 20 00 69 00 6e 00 20 00 .i.n. .
0078: 61 00 74 00 6c 00 2e 00 a.t.l...
0080: 64 00 6c 00 6c 00 20 00 d.l.l. .
0088: 33 00 2e 00 30 00 2e 00 3...0...
0090: 39 00 34 00 33 00 35 00 9.4.3.5.
0098: 2e 00 30 00 20 00 33 00 ..0. .3.
00a0: 65 00 66 00 32 00 37 00 e.f.2.7.
00a8: 34 00 64 00 65 00 20 00 4.d.e. .
00b0: 66 00 44 00 65 00 62 00 f.D.e.b.
00b8: 75 00 67 00 20 00 30 00 u.g. .0.
00c0: 20 00 61 00 74 00 20 00 .a.t. .
00c8: 6f 00 66 00 66 00 73 00 o.f.f.s.
00d0: 65 00 74 00 20 00 30 00 e.t. .0.
00d8: 30 00 30 00 30 00 31 00 0.0.0.1.
00e0: 31 00 35 00 30 00 0d 00 1.5.0...
00e8: 0a 00 ..

SECURITY

Event Type: Failure Audit
Event Source: Security
Event Category: Object Access
Event ID: 565
Date: 7/19/2005
Time: 11:56:56 AM
User: NT AUTHORITY\SYSTEM
Computer: EXCHANGE_SERVER
Description:
Object Open:
Object Server: Microsoft Exchange
Object Type: Microsoft Exchange Logon
Object Name: /o=DOMAIN/ou=First Administrative
Group/cn=Configuration/cn=Connections/cn=SMTP
(SERVER)/cn={E1737C54-5B8D-47BD-BE3C-DAD766FB3DBD}
New Handle ID: -
Operation ID: {0,1939683}
Process ID: 2332
Primary User Name: SERVER$
Primary Domain: DOMAIN
Primary Logon ID: (0x0,0x3E7)
Client User Name: SERVER$
Client Domain: DOMAIN
Client Logon ID: (0x0,0x1C1EE)
Accesses Unknown specific access (bit 8)

Privileges -

Properties:
WRITE_DAC
WRITE_OWNER
Unknown specific access (bit 5)
%{ab721a54-1e2f-11d0-9819-00aa0040529b}



SYSTEM LOG

Event Type: Information
Event Source: IISCTLS
Event Category: None
Event ID: 2
Date: 7/19/2005
Time: 11:57:38 AM
User: N/A
Computer: SERVER
Description:
IIS stop command received from user NT AUTHORITY\SYSTEM. The logged data is
the status code.
For additional information specific to this message please visit the
Microsoft Online Support site located at:
http://www.microsoft.com/contentredirect.asp.
Data:
0000: 00 00 00 00 ....


Event Type: Information
Event Source: IISCTLS
Event Category: None
Event ID: 1
Date: 7/19/2005
Time: 11:57:45 AM
User: N/A
Computer: SERVER
Description:
IIS start command received from user NT AUTHORITY\SYSTEM. The logged data is
the status code.
For additional information specific to this message please visit the
Microsoft Online Support site located at:
http://www.microsoft.com/contentredirect.asp.
Data:
0000: 00 00 00 00 ....


Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7031
Date: 7/19/2005
Time: 11:57:55 AM
User: N/A
Computer: SERVER
Description:
The IIS Admin Service service terminated unexpectedly. It has done this 51
time(s). The following corrective action will be taken in 1 milliseconds:
Run the configured recovery program.


"Jason Lu [MSFT]" wrote:

> Hi,
>
> It seems the folder you are trying to enable FPSE with is created from Exchange System Manager following the steps in the article
> "Developer Walkthrough: Using Microsoft FrontPage Extensions for WSS Forms". Is that right?
>
> In this article, it also lists the steps to convert the virtual directory to a subweb in IIS Manager. I assume you receive the "Cannot create file
> 'service.lck'" error when coverting the virtual directory to a FPSE subweb on the IIS Server.
>
> I suggest you first check if the "_vti_pvt" folder exists under this virtual directory. If so, remove or rename it and then try converting again.
> Also, if you are using FPSE 2000, you may consider upgrade it to FPSE 2002.
>
> Furthermore, you may try directly creating new virtual directory under the default web site and extend it with FPSE to identify if this issue is
> only with the specific virtual directory.
>
> In case the same issue occurs with a new virtual directory, you may consider creating a new virtual server in IIS and then extending it with
> FPSE to test if the same issue occurs with the new virtual server. This can identify if FPSE is working fine.
>
> I hope the information helps.
>
> Regards,
> Jason Lu
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
>

One other update, after I let the server settle down again...lol, I tried to
create a new web, according to the doc referenced: And I received this
error...

"Server error: The server extenstions were unable to access the file
"frontpg.lck". Please check the file permissions. Contact your Internet
Service Provider or Web server administrator for more inofrmation"

So...I looked on the server, the only place I am seeing a frontpg.lck file
is in the _vti_pvt folder of the Default Web Site folder. Which happens to
be where the services.lck file is also located.

I was under the impression that when enabling FPSE 2002 on my desired
Virtual Directory, that the services.lck file would have been created in the
_vti_pvt folder for that Virtual Directory.

And should there even be an _vti_pvt folder in the Default Web Site folder,
or are server extentions just installed for the Default Web Site
automatically once installed. Which allows for Virtual Directories on that
site to be enabled? Or could something just be screwed up from attempting
some of these steps with FPSE 2000?

Finally, lol, I know I said a couple updates..., but I am thinking that the
event errors, were not related to FrontPage, but rather to me attempting to
go to the http://server/frontpage location. I noticed that doing so,
although there are no htm files present, an html page is generated with a
blue line down the left side of the page, and then a frontpage link, no
images, and then someother login button...not sure what this is?

Thanks again.
J

"Jason Lu [MSFT]" wrote:

> Hi,
>
> It seems the folder you are trying to enable FPSE with is created from Exchange System Manager following the steps in the article
> "Developer Walkthrough: Using Microsoft FrontPage Extensions for WSS Forms". Is that right?
>
> In this article, it also lists the steps to convert the virtual directory to a subweb in IIS Manager. I assume you receive the "Cannot create file
> 'service.lck'" error when coverting the virtual directory to a FPSE subweb on the IIS Server.
>
> I suggest you first check if the "_vti_pvt" folder exists under this virtual directory. If so, remove or rename it and then try converting again.
> Also, if you are using FPSE 2000, you may consider upgrade it to FPSE 2002.
>
> Furthermore, you may try directly creating new virtual directory under the default web site and extend it with FPSE to identify if this issue is
> only with the specific virtual directory.
>
> In case the same issue occurs with a new virtual directory, you may consider creating a new virtual server in IIS and then extending it with
> FPSE to test if the same issue occurs with the new virtual server. This can identify if FPSE is working fine.
>
> I hope the information helps.
>
> Regards,
> Jason Lu
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
>

Hi,

Based on your information, the server is now running fine with FPSE 2002. The current problem is still the original one that you cannot
create a subweb from a virtual directory under the default web site. The error now is:

"Server error: The server extenstions were unable to access the file "frontpg.lck". Please check the file permissions. Contact your Internet
Service Provider or Web server administrator for more inofrmation"

Your understanding are correct. The root virtual server needs to be extended by FPSE so that the virtual directories under it can be
converted to subwebs. The service.lck file needs to be created for the subweb.

Considering the previous error, it seems there are two possible causes for this issue:
1. The LCK files are damaged.
2. There are permissions issues over the subweb.

I suggest you try the steps below to see if they help:

1. Stop IIS
2. Search for all instances of frontpg.lck.
3. Delete all instances of frontpg.lck.
4. Restart IIS
5. Try creating the site now.
6. If the issue still persists, recalculate the web and then run the Check Server Extensions on the web.

In case the steps above do not help, please check the permissions over the virtual directory in IIS and ensure the account you used to
create the subweb has Full Control permission. Also, the following article may help on this issue.

840466 FrontPage 2002 ASP pages may not function correctly and you may receive
http://support.microsoft.com/?id=840466

Furthermore, the following information is helpful in case further troubleshooting is necessary:
1. Do all the errors occur when you create the subweb within IIS Manager on the web server?
2. Are you using Anonymous authentication or Integrated Windows authentication in IIS for the default web site and the virtual directory?

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.

Hey Jason,
Well, this is where I am at...

First recall that I had FPSE 2000 installed by using the Add Windows
Components wizard, it seems that during this time, IIS may have become
correupted as well...I will get to this in a minute.

But, when you suggested FPSE 2002, I figured I could install them, and if
200 was present it was okay, either there would be no conflict, or the old
would be uninstalled by default.

It was at that point that IIS for the Default Web Site, reported that I
could Configure Server Extensions or, I could Configure Server Extensions
2002.

But I also had the option on the Virtual Directory located under the
Default Web Site, lets call it FrontPage. That was the folder I Configured
Server Extensions 2002 on, and not the default web site...(unless it
automatically put them on the root when I specified a subweb)

In any case, by configuring the subweb for the virtual directory
FrontPage, I was able to connect in FrontPage, but there was no Default.Htm
file, and this is when I was unable to publish back to the server.

Well, I thought perhaps the FPSE 2000 was the issue, so I removed them
with the windows component wizard and left the FPSE 2002 in tact. Yet, I
still have the option to configure the old server extensions...I can't figure
out why this would be.

But during all of this configuring of FPSE 2000 in the IIS portion of
windows, IIS was damaged, or at least SMTP. Exchange no longer worked, I
figured the config changes in the IIS Windows Component Wizard, even though I
made no change to IIS, must have loaded old DLLs of some sort, and it broke
exchange, IISAdmin was up and down like every 20 seconds, and exchange no
longer wanted to talk to my Relay server.

In any case to make a long story longer, I was forced to remove IIS
completely (well I followed the steps in KB304166) since the event log errors
were exact...and the previous solutions had not worked.

SO - as of right this minute, I have everything back to normal, no FPSE
2000 or FPSE 2002 installed, yet the configure server extentions is still
present.

My question today is this:

1) How do I manually remove FPSE 2000 so that IIS does not think it is an
option to install, or does it no longer matter?

2a) If I install FPSE 2002, can I only configure Server Extentions for the
SubWeb since this is an option, or do I need to configure the Default Web
Site first and then the subweb?

2b) If in fact the Default Web Site needs server extentions installed, and
I only configure the FrontPage Virtual Directory for SE, will this effect the
other exchange web components such as OWA? Meaning will users accessing OWA
and the OWAAdmin of the IIS Virtual Directories under that Default Web Site
--> Break the server extentions for the who web site including the subweb?

3) Could I create another Website, and still accomplish the tasks in the
article mentioned at the outset?

Phew...sorry for the long story, just trying to give you the most info I
can... Thanks

J

"Jason Lu [MSFT]" wrote:

> Hi,
>
> Based on your information, the server is now running fine with FPSE 2002. The current problem is still the original one that you cannot
> create a subweb from a virtual directory under the default web site. The error now is:
>
> "Server error: The server extenstions were unable to access the file "frontpg.lck". Please check the file permissions. Contact your Internet
> Service Provider or Web server administrator for more inofrmation"
>
> Your understanding are correct. The root virtual server needs to be extended by FPSE so that the virtual directories under it can be
> converted to subwebs. The service.lck file needs to be created for the subweb.
>
> Considering the previous error, it seems there are two possible causes for this issue:
> 1. The LCK files are damaged.
> 2. There are permissions issues over the subweb.
>
> I suggest you try the steps below to see if they help:
>
> 1. Stop IIS
> 2. Search for all instances of frontpg.lck.
> 3. Delete all instances of frontpg.lck.
> 4. Restart IIS
> 5. Try creating the site now.
> 6. If the issue still persists, recalculate the web and then run the Check Server Extensions on the web.
>
> In case the steps above do not help, please check the permissions over the virtual directory in IIS and ensure the account you used to
> create the subweb has Full Control permission. Also, the following article may help on this issue.
>
> 840466 FrontPage 2002 ASP pages may not function correctly and you may receive
> http://support.microsoft.com/?id=840466
>
> Furthermore, the following information is helpful in case further troubleshooting is necessary:
> 1. Do all the errors occur when you create the subweb within IIS Manager on the web server?
> 2. Are you using Anonymous authentication or Integrated Windows authentication in IIS for the default web site and the virtual directory?
>
> Regards,
> Jason Lu
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
>

Hi,

Regarding the left "configure server extensions" option, it is most likely due to a un-complete removal of FPSE 2000. You may take the
following steps to completely remove FPSE2000. Please perform the steps besides removing in "Add/Remove Programs" in the
following article to remove FPSE2000 completely.

265063 HOW TO: Completely Remove the Server Extensions in FrontPage 2000
http://support.microsoft.com/?id=265063

To covert a virtual directory (vd) to a subweb, the parent web of the vd needs to be extended by FPSE first. As I know, OWA should work
fine on a FPSE 2002 extended web site.

However, I think I found the cause of the original issue in your post. It seems Exchange creates the virtual directory in a different way like
IIS does. Due to the "davex.dll" Exchange uses to manage this site, FrontPage publishing may encounter issues. You may check the
following article for the details.

282419 FP2000: Error Messages When You Try to Use Exchange 2000 Virtual
http://support.microsoft.com/?id=282419

Also as I know, it is not available to manually create a virtual directory in IIS and point it to an Exchange public folder.

Since this issue involves an Exchange solution, you may also consider post your questions in public Exchange newsgroup for
suggestions.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.

Thanks Jason,
Tried the steps in the kb265063 to remove FPSE 2000, I was able to
unregister teh dll, which appears to have removed the link in the All Tasks
piece of the Default Web Site.

However, I was unable to delete the ...Microsoft Frontpage\version3.0
folder, and also unable to delete the web server extensions folder, as I was
told that they were in use. I tried deleting them when IIS was stopped.

The good news is that the All Tasks no longer shows the option for the old
server extensions.

Now....I looked at the other KB that you referenced about the DAVEX.DLL and
although this sounds logical in one sense, the Artical that I am following
that is published by Microsoft does not indicate that the server extensions
will not work. The second point in this regard is that the KB also only
applied to FP2000, I am using FP2003 to attempt to publish. The Davex.dll
does sound familiar though, I seem to recall reading another KB that talked
about removing the davex.dll that exchange links to the virtual directory.

I think that the reason perhaps it was not working before, was that IIS and
SMTP was damaged by installing the older FPSE2000, this caused a chain
reaction in terms of Exchange breaking. Today, everything seems to be
running smooth once again. My plan is to try this with only the FPSE2002 and
see if things go smoother...

J



"Jason Lu [MSFT]" wrote:

> Hi,
>
> Regarding the left "configure server extensions" option, it is most likely due to a un-complete removal of FPSE 2000. You may take the
> following steps to completely remove FPSE2000. Please perform the steps besides removing in "Add/Remove Programs" in the
> following article to remove FPSE2000 completely.
>
> 265063 HOW TO: Completely Remove the Server Extensions in FrontPage 2000
> http://support.microsoft.com/?id=265063
>
> To covert a virtual directory (vd) to a subweb, the parent web of the vd needs to be extended by FPSE first. As I know, OWA should work
> fine on a FPSE 2002 extended web site.
>
> However, I think I found the cause of the original issue in your post. It seems Exchange creates the virtual directory in a different way like
> IIS does. Due to the "davex.dll" Exchange uses to manage this site, FrontPage publishing may encounter issues. You may check the
> following article for the details.
>
> 282419 FP2000: Error Messages When You Try to Use Exchange 2000 Virtual
> http://support.microsoft.com/?id=282419
>
> Also as I know, it is not available to manually create a virtual directory in IIS and point it to an Exchange public folder.
>
> Since this issue involves an Exchange solution, you may also consider post your questions in public Exchange newsgroup for
> suggestions.
>
> I hope the information helps.
>
> Regards,
> Jason Lu
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
>
>
>

FYI: You can not delete the Microsoft FrontPage\version3.0 folder as it is part of Windows, not the
FP extensions or the FP application.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

"Smurfman" <(E-Mail Removed)> wrote in message
news:766DE8F2-024B-4BBA-AFC6-(E-Mail Removed)...
> Thanks Jason,
> Tried the steps in the kb265063 to remove FPSE 2000, I was able to
> unregister teh dll, which appears to have removed the link in the All Tasks
> piece of the Default Web Site.
>
> However, I was unable to delete the ...Microsoft Frontpage\version3.0
> folder, and also unable to delete the web server extensions folder, as I was
> told that they were in use. I tried deleting them when IIS was stopped.
>
> The good news is that the All Tasks no longer shows the option for the old
> server extensions.
>
> Now....I looked at the other KB that you referenced about the DAVEX.DLL and
> although this sounds logical in one sense, the Artical that I am following
> that is published by Microsoft does not indicate that the server extensions
> will not work. The second point in this regard is that the KB also only
> applied to FP2000, I am using FP2003 to attempt to publish. The Davex.dll
> does sound familiar though, I seem to recall reading another KB that talked
> about removing the davex.dll that exchange links to the virtual directory.
>
> I think that the reason perhaps it was not working before, was that IIS and
> SMTP was damaged by installing the older FPSE2000, this caused a chain
> reaction in terms of Exchange breaking. Today, everything seems to be
> running smooth once again. My plan is to try this with only the FPSE2002 and
> see if things go smoother...
>
> J
>
>
>
> "Jason Lu [MSFT]" wrote:
>
>> Hi,
>>
>> Regarding the left "configure server extensions" option, it is most likely due to a un-complete
>> removal of FPSE 2000. You may take the
>> following steps to completely remove FPSE2000. Please perform the steps besides removing in
>> "Add/Remove Programs" in the
>> following article to remove FPSE2000 completely.
>>
>> 265063 HOW TO: Completely Remove the Server Extensions in FrontPage 2000
>> http://support.microsoft.com/?id=265063
>>
>> To covert a virtual directory (vd) to a subweb, the parent web of the vd needs to be extended by
>> FPSE first. As I know, OWA should work
>> fine on a FPSE 2002 extended web site.
>>
>> However, I think I found the cause of the original issue in your post. It seems Exchange creates
>> the virtual directory in a different way like
>> IIS does. Due to the "davex.dll" Exchange uses to manage this site, FrontPage publishing may
>> encounter issues. You may check the
>> following article for the details.
>>
>> 282419 FP2000: Error Messages When You Try to Use Exchange 2000 Virtual
>> http://support.microsoft.com/?id=282419
>>
>> Also as I know, it is not available to manually create a virtual directory in IIS and point it to
>> an Exchange public folder.
>>
>> Since this issue involves an Exchange solution, you may also consider post your questions in
>> public Exchange newsgroup for
>> suggestions.
>>
>> I hope the information helps.
>>
>> Regards,
>> Jason Lu
>> Microsoft Online Partner Support
>>
>> When responding to posts, please "Reply to Group" via your newsreader so that others may learn
>> and benefit from your issue.
>> This posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>
>>
>>
>>