Question Locked

SharePoint Central Administration HTTP 403

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm usign widows Sharepoint services 3.0. I have recently experienced a problem with not only logging into the SharePoint Central Administration but also with uploading files from the SharePoint portal. I continue to receive the message "The website declined to show this webpage" HTTP 403. It sounds like permissions right? This is more complicated than that. I have tried everything and still I am getting the HTTP 403 when I try to access the SPCA and when uploading files from the actual sharepoint site.
Furthermore, I am unable to sign into the sharepoint portal from the server computer. Everytime I log in it's like I'm using the wrong password. Then when I go to any other computer I can log in fine.

Please let me know if you have any suggestions. This is driving me nuts.

thanks

5 replies

by csheppard

If you're accessing SharePoint via HTTP, without adding the port number http://yourdomain:portnumber, then you're doing it wrong.

in IIS Manager, right click on Sharepoint and find out what port it's using. When you get that number make sure you add it into your web browser.

by jmercado

yes, I am using the right port. Sharepoint Central Administration = http://localhost:port_number and sharepoint portal is the actual sharepoint website, which is http://sharepoint.company_name.com. This site works, I'm just unable to upload any files and view certain parts of the website, like "people and groups". As soon as I click on one of those links it gives me the HTTP 403 Forbidden error. "Most likely cause, this website requires you to log in" There in that lies the problem.

by dougs

I know this is the equivalent of a band-aid on a bullet wound, but we've just run into this problem as well, and until it's fixed, while you get the HTTP 403 error when you click Upload Document, you can instead click Upload Multiple Documents and just upload one document. It seems to work for now.

by jmercado

With this particular problem I simply changed the application identity setting to "local system" instead of "network service". Not sure if this is a justifiable answer or not, but it works.

This discussion is closed to new replies.