Ms Project 2003 - Risks and Issues Problem connecting to WSS

[Gigi]

After logging in to the Microsoft ProjectServer web Access on the first page
I receive the following error when the server is gathering information abut
Risks and Issues :

"There is a problem establishing a connection with the Web server running
Windows SharePoint Services. Contact your system administrator."

If I click Issues for example and select a project the following information
will come again :

"The documents, risks and issues features in Project Web Access use Windows
SharePoint Services.
There is a problem establishing a connection with the Web server running
Windows SharePoint Services. Contact your system administrator."

What can be the problem ?

The server is running Windows 2003 SP1.
Sharepoint Services is running on the same server as Project.

Any ideeas ?

 

[Reid McTaggart]

Did this problem just start happening? That is, did everything work
correctly in the recent past?

 

[Gigi]

Think this started to happen after we installed Windows 2003 SP1 and the
following patches.
And yes , project managers confirmed that this feature worked before.

 

[Thorsten Chlupp]

I have the same issue after installing Win Server 2003 SP1 and very much
appriciate feedback on a solution. Everything worked fine before the patch
was applied.

Thanks - TC

 

[Vadim Glik]

we're experiencing same thing. Project Server worked for around a year but a
few weeks we've noticed a problem. I'm not sure if it was SharePoint SP1 or
Windows Server 2k03 SP1, or some other update, but something changed and now
we get that same error in risks & issues:

"There is a problem establishing a connection with the Web server running
Windows SharePoint Services"

also in the even viewer there are 3 MSSOAP errors as follows:

Source: MSSOAP
Category: (4)
Event ID: 16

The description for Event ID ( 16 ) in Source ( MSSOAP ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: XML Parser failed at
linenumber 0, lineposition 0, reason is: The system cannot locate the
resource specified.
____

Source: MSSOAP
Category: (4)
Event ID: 16

The description for Event ID ( 16 ) in Source ( MSSOAP ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: Loading of the WSDL
file failed.
_____
and

Source: MSSOAP
Category: (3)
Event ID: 16
The description for Event ID ( 16 ) in Source ( MSSOAP ) cannot be found.
The local computer may not have the necessary registry information or message
DLL files to display messages from a remote computer. You may be able to use
the /AUXSOURCE= flag to retrieve this description; see Help and Support for
details. The following information is part of the event: One of the
parameters supplied is invalid..

 

[bnh1310]

Seems to be consistant. Windows 2003 sp1 and post sp1 critical patches.
I've been looking for a solution too. Users do not see Issues an Risks
associatied with projects.

Just might be a call to Microsoft!

 

[bnh1310]

Seems to be consistant. Windows 2003 sp1 and post sp1 critical patches
I've been looking for a solution too. Users do not see Issues an Risk
associatied with projects.

Just might be a call to Microsoft!

*Did this problem just start happening? That is, did everythin
work
correctly in the recent past?

--
Reid McTaggart
Alegient, Inc., Houston
Project Server Experts
Microsoft Certified Partner

-
bnh131

 

[Stephen Hutchinson]

I was having a similar issue. I have a single server running WSS and Project
Server. I have been able to correct and re-create the problem with the
following configuration changes. When other users have reported correcting
the problem with a re-install... I imagine the installer sets the
configuration file correctly. The steps are listed below:

If your Project server is linked correctly to WSS you should not be able to
access Microsoft Update Services. To get Windows Update Service Working:
proxcfg -d

To get ProjectServer linked back to WSS enter the following (Since my WSS
server and ProjectServer are on the same host I am using that host name as
the proxy server)
proxycfg -d -p "YourProxyServer" ";ServerName;IPAddress; FQDN"

You can run both of these commands without requiring a restart of the
applications or OS.

Stephen Hutchinson

 

[bstrandberg]

Stephen,
thanks, that did the trick for me. Bria