ogbutch
asked on
SharePoint 2007 403 Forbidden error when accessing a specific application window.
I have been on this site and on other web forums trying to find the answer to a strange problem I am having. I have two SharePoint 2007 sites that are producing very inconsistent results of this error.. When trying to edit a web part on a site and attempting to add a hyperlink to a document in a document library on SharePoint (selecting the browse button to open a Web Page Dialog page to choose the document to link), I simply get a blank web page dialog page that says 403 FORBIDDEN . On one site (production) I am able to access this links web page dialog page as either an administrator, an approver with full control, and a page editor with page editing control. On the other SharePoint site (development), I am able to access the same page with full control as an administrator in the owners group, but I am unable to see it (I get the 403 error) as either an approver with full control or a page editor with page editing rights. I have tried uninstalling the asp.net hot fix on the server (928365), I have looked as WSS 3.0 , IIS 6.0 and permissions in MOSS 2007 and in Windows Server 2003 but can not pin point the exact problem why I keep getting this error. I would appreciate any help or advice anyone may have.
ASKER
There are two different site. One site was used to develop the SharePoint portal and then when we felt it was ready for viewing, we built a new site for production. Each site is on its own server and has its own instance of MOSS 2007 and WSS.
It is not just the admin permission account that can access the page. Anyone in the Owners Group of the site, the groups created primarily when sites are created (visitors, member, owners) do not get the 403 error when trying to browse to create a hyperlink to the document libraries. I have tried different sub sites inside the development site and I get the error every time I am in any other group no matter what permissions I have assigned to them.
It is not just the admin permission account that can access the page. Anyone in the Owners Group of the site, the groups created primarily when sites are created (visitors, member, owners) do not get the 403 error when trying to browse to create a hyperlink to the document libraries. I have tried different sub sites inside the development site and I get the error every time I am in any other group no matter what permissions I have assigned to them.
did you use the site migration tool ... backing up the site and then restoring it on the new server? If not then you probably have an issue with the accounts.
The security configuration information for a site is stored in the web.config in the wwwroot directory (assuming you installed to the default site).
I don't know enough about the files to tell you off hand what the differences are between the installs but looking in this file might give you some ideas as to what the problem is.
The security configuration information for a site is stored in the web.config in the wwwroot directory (assuming you installed to the default site).
I don't know enough about the files to tell you off hand what the differences are between the installs but looking in this file might give you some ideas as to what the problem is.
ASKER
No, I did not use a site migration tool. The two different sites were created separately on two different servers. I did replace the web.config file from the site and server that works to the one that is getting the error, and I still get the same error. So, I do not think that is the problem.
ASKER
Does anyone else have any ideas that can help me solve this problem?
I'm having the same problem. I also tried uninstaling .Net 2.0 hotfix 928365 and it didn't help.
ogbutch, have you been able to resolve this issue since your last post?
ogbutch, have you been able to resolve this issue since your last post?
ASKER
No, I have been working on other problems like the spell check error and both have questions posted with no aswers yet.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi ,
i dont know if the question is revelant any more but,
i faced a similar sort of issue when one of the users said she was getting the 403 forbidden error in the summary web part . Strangely the user did get the 403 forbidden error on the browse button adjacent to the link and did not get the error on the browse button near the image link.
The most weird part is that when i added the user to owners of the site. it still did not work, but when i added another to the members group . the other user did not get the 403 forbidden error.
The issue turned out to be an issue with an conflict with the member groups that the user was part. When i checked the user was a member of the same admin group which was conflicting with the sharepoint groups. i just removed the group members in AD and it worked.
i dont know if the question is revelant any more but,
i faced a similar sort of issue when one of the users said she was getting the 403 forbidden error in the summary web part . Strangely the user did get the 403 forbidden error on the browse button adjacent to the link and did not get the error on the browse button near the image link.
The most weird part is that when i added the user to owners of the site. it still did not work, but when i added another to the members group . the other user did not get the 403 forbidden error.
The issue turned out to be an issue with an conflict with the member groups that the user was part. When i checked the user was a member of the same admin group which was conflicting with the sharepoint groups. i just removed the group members in AD and it worked.
Are you trying to do this in the same place in the same site, just one on prod and one in dev or is this 2 different sites? Just checking ot make see if we are dealing with the same directory structure or if this could be a broader site related problem.
Next, can you do this functionality from within another site on the same server? Is this a site specific or server centric problem?