Question

Scenario: We have an authoring server that we do our content editing on for our SharePoint 2007 public website. We have a Content Deployment Path setup to deploy the content from the authoring server to the production server that external users access.

On the web application settings we have Anonymous Access enabled (for both environments) and on the site collection it is enabled as well. On the IIS web application for the production environment, anonymous access is enabled, but all other methods of authentication (Windows, etc.) are disabled. This works just fine on our other web applications.

Issue: On the authoring server, we can access the site anonymously just fine. However, after deploying the content to the production server, everything we try to access anonymously gives "Access Denied" or "401 Not Authorized".

What am I missing?

Update: I discovered the Alternate Access Map that I added for the public URL wasn't setup correctly and wasn't in the IIS bindings. Fixed both of those and now receive "You are not authorized to view this page", Error 401.1. Any ideas?

Was it helpful?

Solution

Verify that everything used to make up your typical page has a published version. It is common to forgot about some things in certain areas like CSS/JS/Images in the /Style Library or page layouts in the Master Page Gallery.

If you have /PublishingImages that are being included, ensure that they have a published version as well.

Licensed under: CC-BY-SA with attribution
Not affiliated with sharepoint.stackexchange
scroll top