D
db
Just posting something we learned today as a result of our effort to custmize
notifications from our PWA instance.
We were successfull in following the instructions provided by Microsoft here
up to a point:
http://msdn2.microsoft.com/en-us/library/bb968451.aspx
##BUT##
There is an 'overlooked' portion of the instruction that resulted in a 401
error until we called MSFT to get help. Here is the support response that
got us past the error:
For MOST purposes the SSP admin (the account set as the administrator of the
shared services provider i.e.: Domain\SPSharedServicesAcct) does not need to
be a PWA user. However this account runs the event and queue service - and
it is the event service that has the context of the SSP admin when running
event code. So if the event needs to access project data through the PSI
(which most events do) then it also needs to be a user in PWA with
permissions to get the data. I will be posting a comment onto the MSDN page
mentioning this and hopefully we can get this updated.
It is possible to do this another way - and use impersonation - but if you
can live with that account in PWA as a user then this is the most
straightforward workaround.
Hope this helps anyone working on this customization.
notifications from our PWA instance.
We were successfull in following the instructions provided by Microsoft here
up to a point:
http://msdn2.microsoft.com/en-us/library/bb968451.aspx
##BUT##
There is an 'overlooked' portion of the instruction that resulted in a 401
error until we called MSFT to get help. Here is the support response that
got us past the error:
For MOST purposes the SSP admin (the account set as the administrator of the
shared services provider i.e.: Domain\SPSharedServicesAcct) does not need to
be a PWA user. However this account runs the event and queue service - and
it is the event service that has the context of the SSP admin when running
event code. So if the event needs to access project data through the PSI
(which most events do) then it also needs to be a user in PWA with
permissions to get the data. I will be posting a comment onto the MSDN page
mentioning this and hopefully we can get this updated.
It is possible to do this another way - and use impersonation - but if you
can live with that account in PWA as a user then this is the most
straightforward workaround.
Hope this helps anyone working on this customization.