Linking Project Server 2003 to Windows Sharepoint Services

[Rob M]

I am building a fresh server using Windows Server 2003, and have successfully installed Sharepoint, and am now installing Project Server 2003. I have followed the installation manual carefully (don't think I missed any steps!) and am at the point where I am trying to enter the details from the Sharepoint Configuration Wizard to the screen 'Connect to Sharepoint Screen' in Project Web Access. The Sharepoint Central Admin UR

I am using is http://ws2003sv1:11691 and this port shows up as such in IIS. Clicking the Test URL button brings the site up. The URL for the site creation is http://ws2003sv1:10000/sites where the port number 10000 relates to a virtual server I have created and extended specifically for Project Server. When I try the link for the Public Documents this too works and displays the customised Sharepoint template for Project Server

The problem I have is that when I click Save Changes it refuses, with the error 'Project Server cannot connect to the specified Web server running Windows Sharepoint Services. Please check the HTTP protocols and the port numbers in both URLs.

The port numbers and URLs are clearly both OK, and Project Server is running on the same server as Sharepoint! I think the problem relates to the use of HTTP and the fact that our network has a proxy server. However using the Proxycfg utility doesn't seem to make any difference..

Any suggestions as to the solution to this would be much appreciated!

 

[Gary L. Chefetz [MVP]]

Rob:

What about the account you're using for STS in Com+ ? Account name good?
Password good? Database rights good?

I am building a fresh server using Windows Server 2003, and have

successfully installed Sharepoint, and am now installing Project Server
2003. I have followed the installation manual carefully (don't think I
missed any steps!) and am at the point where I am trying to enter the
details from the Sharepoint Configuration Wizard to the screen 'Connect to
Sharepoint Screen' in Project Web Access. The Sharepoint Central Admin URL

I am using is http://ws2003sv1:11691 and this port shows up as such in

IIS. Clicking the Test URL button brings the site up. The URL for the site
creation is http://ws2003sv1:10000/sites where the port number 10000 relates
to a virtual server I have created and extended specifically for Project
Server. When I try the link for the Public Documents this too works and
displays the customised Sharepoint template for Project Server.

The problem I have is that when I click Save Changes it refuses, with the

error 'Project Server cannot connect to the specified Web server running
Windows Sharepoint Services. Please check the HTTP protocols and the port
numbers in both URLs.'

The port numbers and URLs are clearly both OK, and Project Server is

running on the same server as Sharepoint! I think the problem relates to the
use of HTTP and the fact that our network has a proxy server. However using
the Proxycfg utility doesn't seem to make any difference...

 

[Rob M]

As far as I can tell all these are OK. I had previously taken an image of the setup prior to installing Project Server, and have copied this to another PC for a 2nd attempt. This time, I have kept the server off the network to avoid issues with the proxy server. I got to the same point and now get an error telling me that the changes can't be saved as the account being used is not in the Sharepoint Central Administrators Group, yet according to Sharepoint Central it is (I am using the default Windows Server Administrator account, as well as a seperate domain account I created specifically for the purpose of managing the Project Server site). I wonder if this is a different manifestation of the same problem, which maybe results from the setup of Windows Server (which I was not involved with). Is this likely? The next alternative is to start with a completely clean install of Windows Server 2003...

 

[Gary L. Chefetz [MVP]]

Rob:

Did you run proxycfg? You must run this regardless of whether you're on the
network or not.

As far as I can tell all these are OK. I had previously taken an image of

the setup prior to installing Project Server, and have copied this to
another PC for a 2nd attempt. This time, I have kept the server off the
network to avoid issues with the proxy server. I got to the same point and
now get an error telling me that the changes can't be saved as the account
being used is not in the Sharepoint Central Administrators Group, yet
according to Sharepoint Central it is (I am using the default Windows Server
Administrator account, as well as a seperate domain account I created
specifically for the purpose of managing the Project Server site). I wonder
if this is a different manifestation of the same problem, which maybe
results from the setup of Windows Server (which I was not involved with). Is
this likely? The next alternative is to start with a completely clean
install of Windows Server 2003...

 

[Lars Hammarberg]

When you say "avoid issues with the proxy server" - do you mean that you've
created a new proxy entry or that you removed the entry pointing to the one
you're disconnected from?

PS <--> WSS requires a proxy entry even though you don't have a server for
proxy running anywhere.
Do a IISRESET from a cmd prompt after setting the proxy and before trying
the admin page in PWA again.
--

/Lars Hammarberg
www.camako.se
MSProject Premier Partner

As far as I can tell all these are OK. I had previously taken an image of

the setup prior to installing Project Server, and have copied this to
another PC for a 2nd attempt. This time, I have kept the server off the
network to avoid issues with the proxy server. I got to the same point and
now get an error telling me that the changes can't be saved as the account
being used is not in the Sharepoint Central Administrators Group, yet
according to Sharepoint Central it is (I am using the default Windows Server
Administrator account, as well as a seperate domain account I created
specifically for the purpose of managing the Project Server site). I wonder
if this is a different manifestation of the same problem, which maybe
results from the setup of Windows Server (which I was not involved with). Is
this likely? The next alternative is to start with a completely clean
install of Windows Server 2003...

 

[Rob M]

We have a proxy server on the network I am using - and I have tried using proxycfg to set up the correct details. I have tried using the proxy server name, its IP address, setting it to no proxy server - you name it! While I do get a variation in the errors for Saving the URL changes the only variation is to indicate a problem with the proxy settings. If I change back from no proxy server to using the current proxy server (and bypassing local addresses!) I come back to square one with the original error.

 

[Gary L. Chefetz [MVP]]

Exactly what command string did you type for the Proxycfg utility? What did
you type for no proxy at all?

We have a proxy server on the network I am using - and I have tried using

proxycfg to set up the correct details. I have tried using the proxy server
name, its IP address, setting it to no proxy server - you name it! While I
do get a variation in the errors for Saving the URL changes the only
variation is to indicate a problem with the proxy settings. If I change back
from no proxy server to using the current proxy server (and bypassing local
addresses!) I come back to square one with the original error.