DVan Zummeren

I have an existing WSS 3.0 installation that was working great. Permissions/groups were all setup. Then last thursday all the permissions seemed to not work anymore. There was a list of tasks that someone had contribute rights too. When they click on 'New' they get a '403 Forbidden' error.

the only way we can get people to be able to add new tasks is if they are farm administrators.

Any suggestions


Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

Curtis Ruppe (MicroStaff IT)

Something larger is going on here. Farm Administrators typically don't have access to your site collections. Verify you are in the correct site collection (not Central Administration), and that you haven't set any special web policies within the Web Application to deny / allow unneccessary access.



Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

Craig Larmer

Sorry, can't help with a solution but we have the exact same problem. Towards the end of last week we suddenly started getting '403 Forbidden' errors on our WSS3.0 installation that had been working fine for months.

Not all objects are affected. e.g. users can create/edit tasks but can't create/edit events.

Is it possible the latest batch of windows updates has changed some security features in IIS


Anyone else having problems like this




Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

Curtis Ruppe (MicroStaff IT)

Even though this article refers to SPS 2003, it might be a solution to your problem. It has to do with Application Pool Identities not having enough access.

http://aspadvice.com/blogs/rjdudley/archive/2005/12/21/14422.aspx





Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

DVan Zummeren

I haven't looked into that yet. If we create a new top level site, everything works fine. The permissions seem to only be with a few lists, not the entire site.




Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

ISA IT Department

We have the same problem. We have a new WSS 3.0 site. Permission were fine and seem to work in most cases, but those with contribue level permissions can not create new calendar events. We've tried resetting permissions and even elevating them (just to test) with no luck.




Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

DVan Zummeren

We've narrowed it down to any list that contains a date field, permissions do not work properly.




Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

ISA IT Department

We found out that changing the impersonate identity property in the web config file from false to true. This completely solved the problem, it also breaks the share point search function. It still runs but the index contains no data.

Any word on a fix for this issue I've seen mention of this issue in a few other places. We are wondering if it's related to an issue with .net 2.0 that cropped up after the last update.






Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

dhunter

Changing the impersonate identity property in the web.config will run SharePoint in the context of the application pool account, this will bypass the security you have configured on your site.

This may not be connected, but we had an issue with MOSS that when you break the security inheritance for a list of a sub site, users got a 403 error when accessing the site. This seems to be a issue with the underlying security for WSS. After raising a support call with MS they gave us hotfix KB936867. It's not public yet but can be requested via https://support.microsoft.com/contactus2/emailcontact.aspx scid=sw;en;1410&WS=hotfix.

The hotfix comes with the following warning ....

WARNING: This fix is not publicly available through the Microsoft
website as it has not gone through full Microsoft regression testing. If
you would like confirmation that this fix is designed to address your
specific problem, or if you would like to confirm whether there are any
special compatibility or installation issues associated with this fix,
you are encouraged to speak to a Support Professional in Product Support
Services.

The hotfix I received addresses KB 934577, 935958, 936867, 937038.

Hope this helps

Dave





Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

ISA IT Department

Thank you very much. I have been very concerned about changing the identity impersonate property for the reason you mentioned. The site is internal and insulated from the outside world, and we view this as a short term solution, but your words of caution mirror my own concerns.

I have been reading up on each KB issue you mentioned. They sound like they could be related although none represent an exact match. We're going to grab a hot fix and give it a try.

thank you very much for your assitance.

ISA IT Dept.






Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

ISA IT Department

That did it! It's fixed.






Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

dhunter

I'm glad your issue is now fixed. I would like to point out to anyone thinking of installing the hotfix, please backup the SharePoint SQL Server databases and do a complete farm SharePoint backup before installing. The hotfix hasn't been fully regression tested yet.



Re: SharePoint - Setup, Upgrade, Administration and Operation Contributors can not contribute

KMSP

Hi,

As far as I can tell, this (and a lot of related type problems about not being able to upload single documents - although multiple file upload is fine, create alerts etc in WSS 3 and I assume also SharePoint 2007) is caused by the ASP.NET 2 hotfix released in July. Before we installed that, everything was fine. Then after we installed it in late July, we started experiencing all the symptoms reported in this discussion. After uninstalling the hotfix (after finding a reference to this issue elsewhere on the Internet), the problem went away.

Now I want to know if this problem is recognised and that the cause is definately the ASP.NET 2 hotfix, and if so, whether a new ASP.NET 2 hotfix will be released which does not cause the problem.

Keith