PWA - SharePoint - Access Denied

[Fabrice]

When I try to view the details of an issue or edit the
metadata of a document linked to a task recorded in PWA, I
get an "Access Denied" scripting error.

The URL is something
like http://SharePoint/subweb/_vti_bin/Owssvr.dll

I am also unable to link existing documents to a task...

When I view the issues or the document directly from
SharePoint site I don't get any error...

Here is my setup:

PWA is on machine PWAserv with IIS set to use NT
authentication. I am an administrator of PWA web site. In
addition the PWAserv machine has IIS Default website
allowing anonymous access turned on. The PAW subweb has
allow anonymous access turned off.

SharePoint Team Services is on Machine SharePointServ
using NT authentication. I am also an administrator of
SharePoint web site.

Both machine are on the same domaine and are Win2k servers
and I am member of the domain's administrator group.

I have tried to open security on both WWWROOT directory
structure without any success.

I have sychronized permissions between PWA and the
SharePoint subweb.

The SubWeb are set to inherit permission from the master
SharePoint web.

I have setup PAW to transfer all accounts to SharePoint.

Does anybody has some suggestion?

Thank you,

Fabrice

 

[Jim Snider]

There are several settings in permissions and categories
which control access to Documents and Issues.
The first thing to do is determine what role PWA assigned
you in the subweb. From SharePoint, go to Site Settings
and then Manage Users to see what role you are currently
assigned. Anonymous users are only assigned the Browser
role by default, which is not adequate for what you are
trying to do.
If you only have the Browser role, then your PWA
Permissions in conjunction with your Category are not set
properly. If you have the Project Manager role, then I am
not sure what it might be.
Hope this helps, Jim

 

[Fabrice]

I have identifyed the problem.

The computer that experienced the problem had the servers
listed in the IE trusted zone and it was generating the
errors eventhough the security level for that zone was set
to low...

To remove the computer from the list, and thus puting the
site in the intranet zone resolved the problem.

Fabrice