PDSNet sample app does not connect

[Guest]

Problem Statement:
We have two independent instances of Project Server installed on two
different servers. Our developer is attempting to retreive a list of tasks
assigned to a particular resource. On both instances, he is using a domain
level account which has been added to each PWA instance and granted
permissions based on the Administrator template. If he attempts to connect
to the PDS on serverA, the connection is denied with a <STATUS>50</STATUS>
indicating access denied. If he attempts to connect to the PDS on serverB,
all of the relevant information is returned.

I installed each of these instances, and so I believe they are similar, if
not identical. The one difference I can find is that on serverA, where
connection is denied, a consultant configured the application, and the
Administrators group has been removed. However, I have given the account all
administrator rights from the PWA admin interface.

Can anyone point me in a direction to look?

Thanks

John Willard
Enterprise Architect
VA Dept of Transportation

 

[Ray McCoppin]

Depended in the PDS method that is trying to be accessed, access can be
denied to some of the PDS methods. I would say that the consultant must
have modifed the adminstators security template. Try adding all secuirty
rights to this user and see if it works.

 

[William Raymond]

Hi John,

EditSite does not work 'out of the box' with PDS. Here is what you need to
do:

1) Update IIS so your new Project Serer site knows how to work with
SOAP/WSDL files.
a) Right click on the new virtual directory created using EditSite
b) Click on Properties for the new virtual directory
c) Click on the Configuration.. button
d) Click Add..
e) Enter the following executable path (quotes REQUIRED):
"c:\Program Files\Common Files\MSSOAP\BINARIES\SOAPIS30.dll"
f) Type an extension of (do not use quotes) "WSDL"
g) Choose "ALL VERBS" (Enter GET, POST in the Limit To box if you are
experiencing problems).
h) Click OK Twice.

2) Go to the Project Server IIS Virtual Root Folder and copy/paste the
PDS.WSDL, PDS.WSML, PDSBIZ.WSDL and PDSBIZ.WSML and follow these steps:
a) Rename the copied files to reflect your new Project Server instance
(i.e. pdsmynewinstance.wsdl, pdsmynewinstance.wsml,
pdsbizmynewinstance.wsdl, pdsbizmynewinstance.wsml).
b) Edit both WSDL files and modify the Location of each site (found at
the end of the WSDL files). There is no need to edit the WSML files.

3) Perform an IISRESET for good measure.

Now give it a go and your PDS calls should work as planned!

-Bill

 

[William Raymond [MVP]]

FYI... PDSTest.net only uses the PDS.WSDL file, so you will need to edit the
code using Visual Studio and re-compile with the new WSDL file. I actually
modified the code to include a textbox on the front-end that allows you to
type in the appropriate WSDL file to use.

-Bill

--
William Raymond
BLOG: http://www.mympa.org/blog.aspx

Hi John,

EditSite does not work 'out of the box' with PDS. Here is what you need
to do:

1) Update IIS so your new Project Serer site knows how to work with
SOAP/WSDL files.
a) Right click on the new virtual directory created using EditSite
b) Click on Properties for the new virtual directory
c) Click on the Configuration.. button
d) Click Add..
e) Enter the following executable path (quotes REQUIRED):
"c:\Program Files\Common Files\MSSOAP\BINARIES\SOAPIS30.dll"
f) Type an extension of (do not use quotes) "WSDL"
g) Choose "ALL VERBS" (Enter GET, POST in the Limit To box if you are
experiencing problems).
h) Click OK Twice.

2) Go to the Project Server IIS Virtual Root Folder and copy/paste the
PDS.WSDL, PDS.WSML, PDSBIZ.WSDL and PDSBIZ.WSML and follow these steps:
a) Rename the copied files to reflect your new Project Server instance
(i.e. pdsmynewinstance.wsdl, pdsmynewinstance.wsml,
pdsbizmynewinstance.wsdl, pdsbizmynewinstance.wsml).
b) Edit both WSDL files and modify the Location of each site (found at
the end of the WSDL files). There is no need to edit the WSML files.

3) Perform an IISRESET for good measure.

Now give it a go and your PDS calls should work as planned!

-Bill

--
William Raymond [MS Project MVP]
(e-mail address removed)
BLOG: http://www.mympa.org/blog.aspx

Problem Statement:
We have two independent instances of Project Server installed on two
different servers. Our developer is attempting to retreive a list of
tasks assigned to a particular resource. On both instances, he is using a
domain level account which has been added to each PWA instance and
granted permissions based on the Administrator template. If he attempts
to connect to the PDS on serverA, the connection is denied with a
<STATUS>50</STATUS> indicating access denied. If he attempts to connect
to the PDS on serverB, all of the relevant information is returned.

I installed each of these instances, and so I believe they are similar,
if not identical. The one difference I can find is that on serverA, where
connection is denied, a consultant configured the application, and the
Administrators group has been removed. However, I have given the account
all administrator rights from the PWA admin interface.

Can anyone point me in a direction to look?

Thanks

John Willard
Enterprise Architect
VA Dept of Transportation