PDS Error - Urgent!

[kdawg]

Hi,

I am currently using the PDS to develop an application. However, I am no
longer able to connect to it. When I use the Test Utility in the SDK to try
to connect, I get the following error:

WSDLReader:XML Parser failed at linenumber 0, lineposition 0, reason is: The
system cannot locate the object specified.
HRESULT=0x1: Incorrect function.
- WSDLReader:Loading of the WSDL file failed HRESULT=0x80070057: The
parameter is incorrect.
- Client:One of the parameters supplied is invalid. HRESULT=0x80070057: The
parameter is incorrect.

Can someone please help?

Thank you in advance.

 

[Ed Morrison]

What has changed recently on your installation? IIS settings, service
packs, hot-fixes, etc?

Do the pds.wsdl and pds.wsml files exist in your servers \Program
Files\Microsoft Office Project Server 2003\IIS Virtual Root directory?

Did you validate the url and user/password?

 

[kdawg]

We installed a hot fix (KB898463) that we received from Microsoft which is
supposed to fix certain errors in the stored SQL procedures. However, we did
the same thing in our test environment, and we did not have this error.

Both the pds.wsdl ad pds.wsml files exist in the directories you asked. The
URL is valid. And user/password are valid as well.

The error occurs when SOAP attemps to initialize and load the WSDL file. The
specific line of code where the error is generated is:

SClient.MSSoapInit WSDL

where WSDL is the URL of the pds.wsdl file.

 

[Ed Morrison]

Its tough, if not impossible to help debug an issue like this via the
newsgroup, but we can try.

Since you are not having problems in test, you can compare the two
instances.

If you type in the url of the wsdl file into IE,
(http://myserver/projectserver/pds.wsdl) does the file open? Does it look
exactly the same as the file on the test server?

Are any IIS settings, particularly security, different between the test
server and production?

Can you verify that the patch was completely installed? For example, do the
dates of the procedures in production match the dates on your test server?
Do the dll's and exe's versions/dates match those in the knowledge base
article? A frequent problem after a hot fix is that only the dll's were
installed and not the sql scripts or vice versa.



--
Ed Morrison
msProjectExperts
"We wrote the books on Project Server"
http://www.msprojectexperts.com
FAQ - http://www.projectserverexperts.com

 

[kdawg]

Actually when I try viewing the file through IE, it does not load. Although
it does load in our test environment. I guess that might be the issue.

Do you know how I can resolve this?

As for you other questions, the files look identical, minus the NET BIOS
name of the machines. The IIS settings are the same. And the update did go
through as all the stored procs have different dates.

 

[Ed Morrison]

In IIS, verify the pds.wsdl file's settings. It is in the root project
server folder. It should have read rights and integrated window
authentication. Do the same for the pds.wsml file.
--
Ed Morrison
msProjectExperts
"We wrote the books on Project Server"
http://www.msprojectexperts.com
FAQ - http://www.projectserverexperts.com

 

[kdawg]

Thank for your help Ed

Our IT guys were able to fix the problem. The hot fix changed the
permissions on the default site. So once they restored it to both built-in
and windows authentication everything worked smoothly.

Thanks.