RE: Event log error; publishing FP2000 on XP-Pro system



Sounds like you need to apply the Frontpage server extensions to the website.
Go to Internet Information Services snap-in and right-click on your website.
From there you should be able to add the extensions.

Also, just a note ... you can save yourself a lot of NTFS security
nightmares by working from inetpub\wwwroot\myweb2. Putting your website out
of the webroot results in your not inheriting some permissions that create
less configuration needs.

"Jim T" wrote:

I'm creating (newbiee; still under construction) a web site for my small home
town using my Dell Laptop 9300 w/XP-pro and Front Page 2000 (IIS ver 5.1 and
FP Server Extensions). I have the web stored in a directory "C:\stoneham\my
web2\ and accessing it using the "open web" option in FP. When I start the
publishing process, it runs for a couple of minutes and then comes back with
the following error:

03/19/2006 09:13:19
An error occurred accessing your FrontPage web files.
Authors - if authoring against a web server,
please contact the webmaster for this server's site.
WebMasters - please see the server's system log for more details.

Looking into the Event Log:
------------------------------------
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 3/19/2006
Time: 7:49:26 AM
User: N/A
Computer: JIMT
Description:
The ptssvc service failed to start due to the following error:
The system cannot find the file specified.
For more information,
see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Drilling down to the detail:
-------------------------------------
Category: None
Company Name: Microsoft Corporation
Date: 3/19/2006
Event ID: 7000
File Name: Netevent.dll
File Version: 5.1.2600.0
Product Name: Microsoft Windows Operating System
Source: Service Control Manager
Time: 07:49:26 AM
Type: Error

A search of my system finds the DLL file so it must be the DLL call to a
file that is not found.

I don't seem to find anything in the KB regarding this problem.

Any ideas the root of the problem? XP issue(s) vs. (and/or) FP issue(s)

Reseach/debugging I can do to resolve the problem(s)?

Is there any parameters required on the source web folder (e.g. shared, web
sharing, etc.)?

I have a user logon (admin rights); are there any restrictions on FP
publishing with system logon passwords?


--
Thanks...
Jim Tinder
.



Relevant Pages

  • RE: Form not working! Help
    ... If you are doing it on a website, having FrontPage server extensions. ... Do a recalculate Hyperlinks from the FrontPage ...
    (microsoft.public.frontpage.client)
  • FrontPage Server Extensions
    ... I created a website with FP2003 and published it to SBS2003 and ALLOWED all ... FrontPage Run-Time Component Page ... server and the FrontPage Server Extensions to function properly. ... this web to a web server that has the FrontPage Server Extensions installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot create ASP.Net project in Visual Studio .Net 2003
    ... server extensions did not solve the issue. ... There are two methods for remote file access from VS: File Share and FrontPage Server Extensions. ... Visual Studio creates a "working copy" of the remote master copy in the specified working folder. ... Developers perform all work against this working copy. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: VS 2008 New Website...create on server?
    ... When you create a website *on a non-standard port*, like 99 instead of 80, ... you need to first create the website manually using the IIS manager. ... at the root level where you are creating the new Web site. ... FrontPage Server Extensions must be enabled for the Web site. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Upload Large Files
    ... You might want to consider using a ASP File Upload Component where you then have more control over ... security update, then there is usually no charge for the call. ... > server and the FrontPage Server Extensions to function properly. ...
    (microsoft.public.frontpage.programming)

Loading