2 project server sites on one server

[Eichelmännchen]

Hello NG.

We use MSP Server 2003 and MSP Professional 2003.
On our server we run two different project server sites created using the
site edit tool. Both sites have a 3 way database. The former one works
perfecty.

The site which has been created afterwards works in Web Access but it is not
possible to connect to it from Project Professional. The following message
appears: "Unexpected server response. The project server has returned an
unexpected server response. Click the "View" button to view the server
response as an error page in your browser." But the browser is only white.

I can login to Web Access using my ID (in default adminitrator group) but I
cannot login with MSP Professional.
The error already occurs when testing the path in the Project Server Account
Tool. But it is the same as in Web Access and there it works. So it cannot be
because of the trusted sites. It is not a local client problem and not
because of the permissions in PWA.

Does anyone know what I can check additionally?
I'm thankful for every answer.

Sylvia

 

[Earl Lewis]

Did you specify a different port for each site to answer to? Usually your first installation will use port 80. Any subsequent installations need to have a different port to listen on, like 81, or something not already used.

Earl
Hello NG.

We use MSP Server 2003 and MSP Professional 2003.
On our server we run two different project server sites created using the
site edit tool. Both sites have a 3 way database. The former one works
perfecty.

The site which has been created afterwards works in Web Access but it is not
possible to connect to it from Project Professional. The following message
appears: "Unexpected server response. The project server has returned an
unexpected server response. Click the "View" button to view the server
response as an error page in your browser." But the browser is only white.

I can login to Web Access using my ID (in default adminitrator group) but I
cannot login with MSP Professional.
The error already occurs when testing the path in the Project Server Account
Tool. But it is the same as in Web Access and there it works. So it cannot be
because of the trusted sites. It is not a local client problem and not
because of the permissions in PWA.

Does anyone know what I can check additionally?
I'm thankful for every answer.

Sylvia

 

[Eichelmännchen]

Hello Earl.

I couldn't specify a different port.
We have one web site which is called "Intranet" with port 80.
Project server is a virtual directory beneath it and the site edit tool
created the new site IOserver on the same level automatically. So they both
have port 80 and i cannot change it.

I allowed anonymous access to the new site and get a different message now.
"Cannot connect. Project server was unable to establish a connection with
the selected Project Server. This could be caused by a loss of network
connectivity, invalid user name or password, lack of an enterprise global
template, or problems with the Project Server or database, or your Project
Server may not have enterprise features enabled."

Enterprise features are enabled and I have all possible permissions. The
network is ok also.

Do you have any idea?

Sylvia

 

[Earl Lewis]

Sylvia,

You should not be enabling anonymous access. You should disable the anonymous access checkbox in the IIS directory security settings and make sure that the option to use integrated windows authentication is selected in the lower half of that same window.

Earl
Hello Earl.

I couldn't specify a different port.
We have one web site which is called "Intranet" with port 80.
Project server is a virtual directory beneath it and the site edit tool
created the new site IOserver on the same level automatically. So they both
have port 80 and i cannot change it.

I allowed anonymous access to the new site and get a different message now.
"Cannot connect. Project server was unable to establish a connection with
the selected Project Server. This could be caused by a loss of network
connectivity, invalid user name or password, lack of an enterprise global
template, or problems with the Project Server or database, or your Project
Server may not have enterprise features enabled."

Enterprise features are enabled and I have all possible permissions. The
network is ok also.

Do you have any idea?

Sylvia

 

[Eichelmännchen]

Hi Earl.

Thank you for answering.
I found the problem. We have a three way database and these weren't
configured correctly. Each one was configured like using only one db. Of
cource it couldn't work this way.

Now it works ok.

Bye Sylvia

 

[Earl Lewis]

Sylvia,

I was confused by the statement in your first post that you have a 3-way database. What exactly do you mean by that?

Earl
Hi Earl.

Thank you for answering.
I found the problem. We have a three way database and these weren't
configured correctly. Each one was configured like using only one db. Of
cource it couldn't work this way.

Now it works ok.

Bye Sylvia