Our users are getting a 403 Forbidden error when trying to upload
single documents to our Sharepoint Team Service server. The multiple
document upload feature seems to work ok.
I have checked the user permissions in the virtual directory, the
windows temp directory and they seem ok. The feature worked without
issue since we implemented Team Services 3.0 about 6 months ago. We
have not made any changes in the environment, other than windows
server patches.
We are running the latest version Windows Server 2003 R2 and
Sharepoint Team Services 3.0
Has anyone else run into the same issue?
thanks kindly,
Sasha
Tablus IT
403 FORBIDDEN
This behavior is strange and very annoying! We are running SharePoint 3.0
WSS on Windows 2003 x64 R2. The SharePoint install is the x64 version. We are
also using a forms authentication coupled with a customized version of the
HostingFeature. This enables site admins to manage the ASP.net users in the
SQL database. This behavior can be fixed temporarily by renaming the
web.config file, loading a page to produce an error, resetting the web.config
file to its correct name and continuing to use the site.
Any help would be welcome as this behavior makes SharePoint essentially
useless.
Has anyone found a fix for this???
This manefests itself as the Upload returning "403 Forbidden" (and only
that) after clicking Upload. If the user is deleted, and then re-added to
the Owners group for the site, it works fine. Then after a server reboot, or
some unknown period of time, the security is "lost" and the 403 Forbidden
returns. The user is still in the Owners group at that time. If I remove
the user and re-add the upload will work again until reboot or the lapse of
time.
Anyone have a thought based on that quirk?
As far as I can tell, this 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
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
I found the answer from another post where they claim to have notified
Microsoft more than a month ago and were still waiting for feedback/fix.
"Jim Nitterauer" wrote:
I have the exact same problem!!! Has anybody found a solid solution yet?