Accessing Risks and Issues in a workspace if you're not a Project Server user

D

David Brebner

I think this should work, but any ideas appreciated:

I have a Project Server 2007 installation using WSS 3.0 that is working just
fine. I give Contribute permissions to a project workspace to a user who is
not a Project Server user. That user can access the site, can see all the
lists and can see all items in all lists, except Risks and Issues. Even
though the user can see the Risks and Issues lists, and see all the items in
these lists, if the user tries to open a Risk or an Issue they get an error
(see below). It doesn't matter if I change the user's rights to Read Only,
to Contribute or to Full Access, the same thing occurs. This is probably
because of the magic glue that binds Risks and Issues in workspaces to
Project Server. Interestingly, the user can add/edit/delete Deliverables,
which I thought shared the magic glue.

I think a user who is not a Project Server user should be able to access all
aspects of the workspace without a Project Server licence - am I correct in
this assumption?

Thanks,
David Brebner


The detailed error message from WSS is as follows:

Server Error in '/' Application.
--------------------------------------------------------------------------------

The request failed with HTTP status 401: Unauthorized.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Net.WebException: The request failed with HTTP
status 401: Unauthorized.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:


[WebException: The request failed with HTTP status 401: Unauthorized.]
Microsoft.Office.Project.Server.WebServiceProxy.PSIProxyBase.InvokePSI(String
serviceName, String methodName, Object[] parameters) +167
Microsoft.Office.Project.Server.WebServiceProxy.Security.CheckUserProjectPermission(Guid
projectUid, Guid categoryPermissionUid) +244
Microsoft.Office.Project.PWA.CustomFieldWebControls.CustomPWALinkField.OnLoad(EventArgs
e) +1993
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436

--------------------------------------------------------------------------------Version Information: Microsoft .NET Framework Version:2.0.50727.1434;ASP.NET Version:2.0.50727.1434
 
S

Sander

Hi david,

I have not tested this, but I think the 'magic glue' you are talking about,
is the possibiliy to link issues to tasks. For this link, sharepoint accesses
the projectserver webservices and if you are not authorized in ProjectServer,
you will get a 401 on the webservices.
So my guess is that all the issues that give a 401 for these users are
linked to tasks in the project. (and the deliverables are not linked
probably).

can you verify this?

Sander

David Brebner said:
I think this should work, but any ideas appreciated:

I have a Project Server 2007 installation using WSS 3.0 that is working just
fine. I give Contribute permissions to a project workspace to a user who is
not a Project Server user. That user can access the site, can see all the
lists and can see all items in all lists, except Risks and Issues. Even
though the user can see the Risks and Issues lists, and see all the items in
these lists, if the user tries to open a Risk or an Issue they get an error
(see below). It doesn't matter if I change the user's rights to Read Only,
to Contribute or to Full Access, the same thing occurs. This is probably
because of the magic glue that binds Risks and Issues in workspaces to
Project Server. Interestingly, the user can add/edit/delete Deliverables,
which I thought shared the magic glue.

I think a user who is not a Project Server user should be able to access all
aspects of the workspace without a Project Server licence - am I correct in
this assumption?

Thanks,
David Brebner


The detailed error message from WSS is as follows:

Server Error in '/' Application.
--------------------------------------------------------------------------------

The request failed with HTTP status 401: Unauthorized.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Net.WebException: The request failed with HTTP
status 401: Unauthorized.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:


[WebException: The request failed with HTTP status 401: Unauthorized.]
Microsoft.Office.Project.Server.WebServiceProxy.PSIProxyBase.InvokePSI(String
serviceName, String methodName, Object[] parameters) +167
Microsoft.Office.Project.Server.WebServiceProxy.Security.CheckUserProjectPermission(Guid
projectUid, Guid categoryPermissionUid) +244
Microsoft.Office.Project.PWA.CustomFieldWebControls.CustomPWALinkField.OnLoad(EventArgs
e) +1993
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1436

--------------------------------------------------------------------------------Version Information: Microsoft .NET Framework Version:2.0.50727.1434;ASP.NET Version:2.0.50727.1434
Click to expand...
 
D

David Brebner

I like your thinking Sander, but unfortunately it's not the case. There are
no Risks or Issues linked to any tasks, they are just entries in the list in
the workspace.

Sander said:
Hi david,

I have not tested this, but I think the 'magic glue' you are talking
about,
is the possibiliy to link issues to tasks. For this link, sharepoint
accesses
the projectserver webservices and if you are not authorized in
ProjectServer,
you will get a 401 on the webservices.
So my guess is that all the issues that give a 401 for these users are
linked to tasks in the project. (and the deliverables are not linked
probably).

can you verify this?

Sander

David Brebner said:
I think this should work, but any ideas appreciated:

I have a Project Server 2007 installation using WSS 3.0 that is working
just
fine. I give Contribute permissions to a project workspace to a user who
is
not a Project Server user. That user can access the site, can see all the
lists and can see all items in all lists, except Risks and Issues. Even
though the user can see the Risks and Issues lists, and see all the items
in
these lists, if the user tries to open a Risk or an Issue they get an
error
(see below). It doesn't matter if I change the user's rights to Read
Only,
to Contribute or to Full Access, the same thing occurs. This is probably
because of the magic glue that binds Risks and Issues in workspaces to
Project Server. Interestingly, the user can add/edit/delete Deliverables,
which I thought shared the magic glue.

I think a user who is not a Project Server user should be able to access
all
aspects of the workspace without a Project Server licence - am I correct
in
this assumption?

Thanks,
David Brebner


The detailed error message from WSS is as follows:

Server Error in '/' Application.
--------------------------------------------------------------------------------

The request failed with HTTP status 401: Unauthorized.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Net.WebException: The request failed with HTTP
status 401: Unauthorized.

Source Error:

An unhandled exception was generated during the execution of the current
web
request. Information regarding the origin and location of the exception
can
be identified using the exception stack trace below.

Stack Trace:


[WebException: The request failed with HTTP status 401: Unauthorized.]

Microsoft.Office.Project.Server.WebServiceProxy.PSIProxyBase.InvokePSI(String
serviceName, String methodName, Object[] parameters) +167

Microsoft.Office.Project.Server.WebServiceProxy.Security.CheckUserProjectPermission(Guid
projectUid, Guid categoryPermissionUid) +244

Microsoft.Office.Project.PWA.CustomFieldWebControls.CustomPWALinkField.OnLoad(EventArgs
e) +1993
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+1436

--------------------------------------------------------------------------------Version
Information: Microsoft .NET Framework Version:2.0.50727.1434;ASP.NET
Version:2.0.50727.1434
Click to expand...
Click to expand...
 
G

Gary L. Chefetz

David:

I think Sander is correct nonetheless. The difference between Risks and
Issues versus Deliverables, is that the links to the Project Sechedule for
Risks and Issues are managed from the SharePoint workspace whereas the links
to deliverables are managed through the Project Client. So, it seems logical
that the issues and risks code would be checking for access rights on
initiation while the deliverables would not. Using these does require you to
have a web CAL for the user.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com


David Brebner said:
I like your thinking Sander, but unfortunately it's not the case. There are
no Risks or Issues linked to any tasks, they are just entries in the list
in the workspace.

Sander said:
Hi david,

I have not tested this, but I think the 'magic glue' you are talking
about,
is the possibiliy to link issues to tasks. For this link, sharepoint
accesses
the projectserver webservices and if you are not authorized in
ProjectServer,
you will get a 401 on the webservices.
So my guess is that all the issues that give a 401 for these users are
linked to tasks in the project. (and the deliverables are not linked
probably).

can you verify this?

Sander

David Brebner said:
I think this should work, but any ideas appreciated:

I have a Project Server 2007 installation using WSS 3.0 that is working
just
fine. I give Contribute permissions to a project workspace to a user who
is
not a Project Server user. That user can access the site, can see all
the
lists and can see all items in all lists, except Risks and Issues. Even
though the user can see the Risks and Issues lists, and see all the
items in
these lists, if the user tries to open a Risk or an Issue they get an
error
(see below). It doesn't matter if I change the user's rights to Read
Only,
to Contribute or to Full Access, the same thing occurs. This is probably
because of the magic glue that binds Risks and Issues in workspaces to
Project Server. Interestingly, the user can add/edit/delete
Deliverables,
which I thought shared the magic glue.

I think a user who is not a Project Server user should be able to access
all
aspects of the workspace without a Project Server licence - am I correct
in
this assumption?

Thanks,
David Brebner


The detailed error message from WSS is as follows:

Server Error in '/' Application.
--------------------------------------------------------------------------------

The request failed with HTTP status 401: Unauthorized.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Net.WebException: The request failed with HTTP
status 401: Unauthorized.

Source Error:

An unhandled exception was generated during the execution of the current
web
request. Information regarding the origin and location of the exception
can
be identified using the exception stack trace below.

Stack Trace:


[WebException: The request failed with HTTP status 401: Unauthorized.]

Microsoft.Office.Project.Server.WebServiceProxy.PSIProxyBase.InvokePSI(String
serviceName, String methodName, Object[] parameters) +167

Microsoft.Office.Project.Server.WebServiceProxy.Security.CheckUserProjectPermission(Guid
projectUid, Guid categoryPermissionUid) +244

Microsoft.Office.Project.PWA.CustomFieldWebControls.CustomPWALinkField.OnLoad(EventArgs
e) +1993
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+1436

--------------------------------------------------------------------------------Version
Information: Microsoft .NET Framework Version:2.0.50727.1434;ASP.NET
Version:2.0.50727.1434
Click to expand...
Click to expand...
Click to expand...
 
D

David Brebner

It's a pity, but I think this analysis is right. It's functionality from
PS2003 that has been removed and I can't find any statement that it won't or
shouldn't work any more in PS2007, so I think it may be accidental (or
accidentally there in PS2003, depending on your outlook, of course ;-) ).

Gary L. Chefetz said:
David:

I think Sander is correct nonetheless. The difference between Risks and
Issues versus Deliverables, is that the links to the Project Sechedule for
Risks and Issues are managed from the SharePoint workspace whereas the
links to deliverables are managed through the Project Client. So, it seems
logical that the issues and risks code would be checking for access rights
on initiation while the deliverables would not. Using these does require
you to have a web CAL for the user.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com


David Brebner said:
I like your thinking Sander, but unfortunately it's not the case. There
are no Risks or Issues linked to any tasks, they are just entries in the
list in the workspace.

Sander said:
Hi david,

I have not tested this, but I think the 'magic glue' you are talking
about,
is the possibiliy to link issues to tasks. For this link, sharepoint
accesses
the projectserver webservices and if you are not authorized in
ProjectServer,
you will get a 401 on the webservices.
So my guess is that all the issues that give a 401 for these users are
linked to tasks in the project. (and the deliverables are not linked
probably).

can you verify this?

Sander

:

I think this should work, but any ideas appreciated:

I have a Project Server 2007 installation using WSS 3.0 that is working
just
fine. I give Contribute permissions to a project workspace to a user
who is
not a Project Server user. That user can access the site, can see all
the
lists and can see all items in all lists, except Risks and Issues. Even
though the user can see the Risks and Issues lists, and see all the
items in
these lists, if the user tries to open a Risk or an Issue they get an
error
(see below). It doesn't matter if I change the user's rights to Read
Only,
to Contribute or to Full Access, the same thing occurs. This is
probably
because of the magic glue that binds Risks and Issues in workspaces to
Project Server. Interestingly, the user can add/edit/delete
Deliverables,
which I thought shared the magic glue.

I think a user who is not a Project Server user should be able to
access all
aspects of the workspace without a Project Server licence - am I
correct in
this assumption?

Thanks,
David Brebner


The detailed error message from WSS is as follows:

Server Error in '/' Application.
--------------------------------------------------------------------------------

The request failed with HTTP status 401: Unauthorized.
Description: An unhandled exception occurred during the execution of
the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.Net.WebException: The request failed with
HTTP
status 401: Unauthorized.

Source Error:

An unhandled exception was generated during the execution of the
current web
request. Information regarding the origin and location of the exception
can
be identified using the exception stack trace below.

Stack Trace:


[WebException: The request failed with HTTP status 401: Unauthorized.]

Microsoft.Office.Project.Server.WebServiceProxy.PSIProxyBase.InvokePSI(String
serviceName, String methodName, Object[] parameters) +167

Microsoft.Office.Project.Server.WebServiceProxy.Security.CheckUserProjectPermission(Guid
projectUid, Guid categoryPermissionUid) +244

Microsoft.Office.Project.PWA.CustomFieldWebControls.CustomPWALinkField.OnLoad(EventArgs
e) +1993
System.Web.UI.Control.LoadRecursive() +47
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Control.LoadRecursive() +131
System.Web.UI.Page.ProcessRequestMain(Boolean
includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
+1436

--------------------------------------------------------------------------------Version
Information: Microsoft .NET Framework Version:2.0.50727.1434;ASP.NET
Version:2.0.50727.1434
Click to expand...
Click to expand...
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Issues/risks pointing to old server after migration 1
Error on PWA Issues and Risks 7
Error on Risk and Issues link in Project Web Access 1
Server Error in '/' Application 3
Workspace enumeration causing duplicate fields in Issues and Risks 0
Project Pro Project Guide not Displaying 2
Problem in Adding the Project Server Webparts in Workspace 5
No Issues and risks in PWA 5

Top