Search results matching tag 'FPSE'

FrontPage Extensions HTTP Error 401.1

bubbaaintfly — Thu, 08 Oct 2009 22:18:05 GMT

I'm having the exact same problem, but it seems to be limited to virtual sites that are using host headers as opposed to listening on a unique IP address. Such as...

1. In IIS Manager, right-click Web Sites -> New -> Web Site
2. Fill out info & listen on unique IP address (already configured in TCP/IP network properties). Point to a new root web directory..
3. All Programs -> Administrative Tools -> Microsoft SharePoint Administrator (http://localhost:6109/fpadmdll.dll)
4. Click Extend to create FrontPage Server Extensions 2002 on the new virtual server.
5. Set an admin user (HOSTNAME\Administrator).
6. Click the new virtual server via SharePoint admin page.. links to:
http://<website-url>/_vti_bin/_vti_adm/fpadmdll.dll?page=webadmin.htm
This page prompts for UserName/Password. Enter HOSTNAME\Administrator & password. Displays website administration page (Works fine).

When I repeat the same steps using host header instead of a unique IP at Step 2, instead of properly displaying the admin config page at step 6, I keep getting the prompt to enter Username/Password 3 times until it finally results in:
HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials.
----------

NOTE: This only happens if I attempt to run the SharePoint Administration from the the host the web sites are installed on. Accessing the virtual web site administration from a remote host works fine:
http://<website-url>/_vti_bin/_vti_adm/fpadmdll.dll?page=webadmin.htm

I can only guess the SharePoint is having trouble resolving the use of the host headers.

Can't publish newly created files from local IIS6/FPSE site to remote IIS7/WebDAV site

dpellenwood — Tue, 15 Sep 2009 17:49:17 GMT

We have a development server setup with IIS6 and FrontPage Server Extensions. We also have a brand new production server running IIS7 and would like to avoid using FPSE on the new server. Instead, I have setup WebDAV and for the most part things are working. However, there is one issue I can't seem to resolve.

When I try to publish a file that I create on the development server (IIS6 & FPSE) to the production server (IIS7 & WebDAV), the publish appears to work correctly, but immediately the published file disappears from the remote file list. In fact, it never gets created on/copied to the production server. A check of the HTTP logs on the production server shows the PUT command returns a 201 response as if the file is created just fine even though the file is most certainly not there. Publish logs from our editor state the command completed successfully with no warnings or errors.

Additional notes:

File type doesn't appear to matter. Regardless of if it is a htm, css, asp, php or txt file it won't publish.
I can publish changes to files that already exist in both directions.
I can delete files in both directions
I can create a new file on the production server and publish it down to the dev server.
I'm using MS SharePoint Designer 2007 (Expression Web) as the editor and publishing tool.

Anyone run into a similar issue? Is there a setting I'm missing in a configuration file somewhere? Any things I can try to diagnose this further?

Thanks for the help!

DaveE

Server Error: The folder "/" is marked executable. You are not allowed to put files into an executable folder on this server.

rumblepup — Mon, 07 Sep 2009 10:14:30 GMT

I'm sorry if I'm not very technical here, so please bare with me. Firstly I'm running,

Vista Ultimate

IIS 7

FPSE 2002 for IIS7

Expression Web

Everything was working fine until I started trying out some PHP programming. I installed Zend Server CE so I could work with Magento Ecommerce, but I decided to uninstall since I'm going to be deploying to a Linux server, and felt I didn't need it. Started using WAMP server on port 8080 and everything worked fine.

But when I fired up Expression Web to work on an asp.net app, I was able to open the localhost dev installation just fine, but when I tried to add a simple html doc, I got this error.

Server Error: The folder "/" is marked executable. You are not allowed to put files into an executable folder on this server.

Which was strange because I didn't get this error before I installed Zend. I have been trying to trouble shoot the problem but I haven't been able to come up with any answers. As far as I can tell, none of my local webs have been set as an executable, I checked the Default Website Permissions and all seemed in order. I reinstalled FPSE just in case, and all seems fine on that front. I even went as far as to grant "Everyone" admin privileges on the default www folder. Still got the problem.

What should be my next step?

Disappearing FrontPage permissions

Melinda D — Wed, 26 Aug 2009 19:33:56 GMT

I am having trouble with permissions disappearing from web pages. I am running Server 2008, IIS7 and the latest FronPage extensions. Users call me and tell me they can no longer access their site through FrontPage, so I jump in and their ID is completely removed from the site. I am able to add them again fairly easily, but this is becoming a big problem. Occasionally I will see a user with permissions on a site that is not even theirs! Any help would be appreciated.

FPSE on Server08 gives HTTP Error 500.19

daniel.ceola — Tue, 21 Jul 2009 20:25:04 GMT

I followed the below page to install FPSE on my 08 server, and when i follow the instructions on how to add the extensions to a site, i receive an HTTP 500.19 error

http://learn.iis.net/page.aspx/134/install-frontpage-server-extensions

Error message received in browser when trying to add extensions via the web interface:

Internet Information Services 7.0

Error Summary

HTTP Error 500.19 - Internal Server Error

The requested page cannot be accessed because the related configuration data for the page is invalid.

Detailed Error Information

Module	DynamicCompressionModule
Notification	SendResponse
Handler	StaticFile
Error Code	0x8007007e

Requested URL	http://localhost:5826/
Physical Path	C:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\50\isapi\_vti_adm
Logon Method	Not yet determined
Logon User	Not yet determined

Most likely causes:

The worker process is unable to read the applicationhost.config or web.config file.
There is malformed XML in the applicationhost.config or web.config file.
The server cannot access the applicationhost.config or web.config file because of incorrect NTFS permissions.

Things you can try:

Look in the event logs for information about why the configuration files are not readable.
Make sure the user identity specified for the application pool, or the authenticated user, has the required permissions to access the web.config file.

Links and More InformationThis error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.

View more information »

The instructions also include a command line method to extend a site, however the path to the commands did not exist on my machine, and i couldn't find it after an initial scan.

Any assistance is greatly appreciated

Re: 'Data at the root level is invalid. Line 1. Position 1'

robmcm — Fri, 05 Jun 2009 17:51:22 GMT

I would suggest removing any web.config files that are located in any _vti_cnf folders. Here’s why – in each folder of your web site FPSE keeps metadata about the files in your web site in _vti_cnf subfolders, and names the metadata files after the source files. Unfortunately, in the case of web.config files this means that IIS or ASP.NET may try to parse those files for valid web.config content and that will ultimately fail.

Re: Downloaded FrontPage Extensions for Server 2008

robmcm — Mon, 18 May 2009 07:10:44 GMT

The times that I have seen this error in the past had to do with mismatched versions of FPSE, which should not be the case since there is only one version of FPSE for Windows Server 2008. Did you copy your content from another server, or was it used with a different version of FPSE?

Anonymous users can edit frontpage sites

PhilDev — Mon, 30 Mar 2009 18:11:28 GMT

Hi All.

I've installed front page server extensions on a windows 2008 web edition IIS7 server. Everything is working fine - I can extend/uninstall sites, create fp users and put them in roles etc. I can use the web GUI for this or the command line - both work ok and report no errors.

I am using basic authentication for the extended sites. If I browse to the site's front-page administration page then I am prompted for the credentials of the frontpage admin user for the site and when I enter them I can administer the site correctly. I can also browse to the site without entering credentials - all fine.

However, when I use the front-page client to open the site I am not prompted to enter any credentials and I can edit the site's content without ever being authenticated!

If I use the site's admin page to disable anonymous access then I DO have to supply credentials to edit it using the front-page client (however I also have to enter credentials to browse the site - which is not what I want). That's not the solution so I have switched anonymous access back on.

Using the log files I am guessing that the front-page client is doing its authoring by calling into _vti_bin/_vti_aut. If I disable anonymous authentication (in the IIS7 GUI) for that folder then I seem to get the expected behaviour and I am prompted for credentials when using the front-page client but not for browsing. However I'm not confident that this is the correct solution - for example a parallel folder _vti_bin/_vti_adm is being called to do site administration and for that I am being prompted for credentials - but that folder has anonymous authentication enabled.

Does anyone have any ideas what is going on here or where I should look next?

FYI I am running my sites on a 64-bit server with dedicated application pools using 32-bit. I have a domain user for each site which is configured as the app pool owner and the anonymous user.

FPSE 2002 and Windows 2008 std. x64

metcalfc — Wed, 25 Mar 2009 01:49:25 GMT

I have sucessfully installed FPSE on a Windows Server 2008 std. edition (SP1). However, the FP administration web site reports a 503 error when started. MSSharePointAppPoll will show started and then stopped after the error. Apparently the fault is in rpcproxy.dll as that module failed to load. I would like to run IIS 7.0 using FPSE as I have two web sites on this server that are FP sites.

The Event log shows a 2280 error with the following information:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Channel>Application</Channel>

<Computer>WVFDFS1.local.walkertownfire.com</Computer>

</System>

- <EventData>

<Data Name="ModuleDll">C:\Windows\system32\RpcProxy\RpcProxy.dll</Data>

</EventData>

</Event>

This server is an Exchange 2007 server, a domain controller.

Any thoughts would be appreciated.

Mickey Metcalf

Re: Can't install FrontPage 2002 Server Extensions for IIS 7.0 - RC0 - x86 - internal error

salibhai — Wed, 28 Jan 2009 19:01:19 GMT

Have you tried this?

If you are using Vista 64bit, you need to run

go to c:\windows\SysWOW64
regsvr32 vbscript.dll

The key is that the folder is different for 64bit Vista, otherwise you will get that internal error message.

Search results matching tag 'FPSE'

FrontPage Extensions HTTP Error 401.1

Can't publish newly created files from local IIS6/FPSE site to remote IIS7/WebDAV site

Server Error: The folder "/" is marked executable. You are not allowed to put files into an executable folder on this server.

Disappearing FrontPage permissions

FPSE on Server08 gives HTTP Error 500.19

Server Error in Application "MICROSOFT SHAREPOINT ADMINISTRATION"

HTTP Error 500.19 - Internal Server Error

The requested page cannot be accessed because the related configuration data for the page is invalid.

Re: 'Data at the root level is invalid. Line 1. Position 1'

Re: Downloaded FrontPage Extensions for Server 2008

Anonymous users can edit frontpage sites

FPSE 2002 and Windows 2008 std. x64

Re: Can't install FrontPage 2002 Server Extensions for IIS 7.0 - RC0 - x86 - internal error