SOAP Errors encountered

[Johnnie Rotten]

I've installed 2003 Project Server with SP1 and started to receive SOAP
errors in the application event log. The errors are....

Event Type: Error
Event Source: MSSOAP
Event Category: Generic
Event ID: 16
Date: 6/14/2005
Time: 8:54:55 PM
User: N/A
Description:
Soap error: XML Parser failed at linenumber 0, lineposition 0, reason is:
The system cannot locate the object specified.

Event Type: Error
Event Source: MSSOAP
Event Category: Client
Event ID: 16
Date: 6/14/2005
Time: 8:54:45 PM
User: N/A
Computer: BABAGHANOUSH
Description:
Soap error: One of the parameters supplied is invalid..

Event Type: Error
Event Source: MSSOAP
Event Category: Generic
Event ID: 16
Date: 6/14/2005
Time: 8:54:45 PM
User: N/A
Description:
Soap error: Loading of the WSDL file failed.

I've edited the WSDL files to reflect the correct Project Server URL, given
the various Project Server Services sufficient privileges to read/interact
with AD, mapped the SOAPIS.DLL file to the WSDL extension for the website,
and applied all the critical updates I could find without success. Is this
event log message(s) a nuisance or a problem?

-johnnie rotten

 

[Johnnie Rotten]

My SOAP errors have been resolved.....

The errors were being recording into the event log every ten seconds and I
narrowed the problem to the connector service by stopping each project
server service and noting the lack of activity recorded within the
Application Event Log.

I had to modify the connector service registry key to reflect the correct
URL for the project server web front end.

An explanation of the registry keys can be found in the Project Server
Administrator Guide, appendix F, page 285.

A previous response to this news forum from Mr. Chefetz mentioned
installation errors and I don't see how the installation script would fail
to write the correct registry key. I also reviewed the WSDL files and
corrected the Project Server URL(s) recorded there.

So, to sum it up......RTFM!!!!

Thanks!!!

 

[Gary L. Chefetz [MVP]]

Security policies can prevent registry keys from being written.

--


Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project