Single Computer Install Issue

[Dominic Moss]

Can anyone on the newsgroup help me as the following problem has been
driving me nuts.

I have been trying to set up a Single Computer Install of Project Server
2003 and keep hitting problems. I am using exactly the same software as I
have used before to install 2 test instances of Project Server 2003 in a
Single Computer installation, in previous cases the install worked fine -
this time it doesn't, every time I install Project Server I compile a
document recording the actions taken, screen dumps and relevant notes, I
have compared previous examples with the document I have created in this
instance and can see no difference at all in my approach.

I have attempted the install on 5 seperate occasions in the past 10 days and
on each attempt I have started with a totally new and clean instance of
Windows Server 2003 which has IIS enabled and IE Enhanced Security disabled,
I have then installed Office 2003, Office 2003 Professional Service Pack 2,
Project Pro 2003, SQL Standard Edition then Service pack 3a, SQL Analysis
Services followed by the Service Pack 3a followed by Windows SharePoint
Services and finally Project Server 2003. I have created accounts as per the
install guide and followed all the prompts and worked through the install
process to completion and have then run the PSCom+ utility and also checked
the SOAP address in the pds.wsdl file

I have worked through the process exactly as per the guide published by
Microsoft Corporation and hit several problems.

On completion of the install process the "Configure Microsoft Office Project
Server" menu shortcut results in a blank page displaying in Internet
Explorer.

Entering http://localhost in IE results in a blank page.

Going to the WSS Central Administration Page the URL is
http://localhost:29082/default.aspx when I would expect it to be
http://servername/default.aspx

I can navigate to the Project Web Access login page but again its URL has
the http://localhost:29082/projectserver address and not the
http://servername/projectserver I would expect to see.

Entering Administrator and the password provided and verified during the
install process results in a 5006 error message, please try later. Deleting
the Administrator password in the MSP_Web_Resources table in the SQL
database does not resolve this issue. I have also attempted to re-build the
SQL database from the command prompt with no password set for the
Administrator and got an error message I did not make a note of.

In Microsoft Office Project Professional 2003 I can create a Project Server
account and entering the URL http://localhost:29082/projectserver results in
a "Succesful Connection" message which suggests that the Project Server
database exists and can be connected to, sadly I cannot use the Adminstrator
account to connect to it.

I am desperate to complete this trial install for my own testing purposes.
Any pointers as to how to solve this or things to check would be much
appreciated.

Thanks in advance

Dominic

 

[Gary L. Chefetz [MVP]]

Dominic:

See my comments in line with yours.

Can anyone on the newsgroup help me as the following problem has been
driving me nuts.

I have been trying to set up a Single Computer Install of Project Server
2003 and keep hitting problems. I am using exactly the same software as I
have used before to install 2 test instances of Project Server 2003 in a
Single Computer installation, in previous cases the install worked fine -
this time it doesn't, every time I install Project Server I compile a
document recording the actions taken, screen dumps and relevant notes, I
have compared previous examples with the document I have created in this
instance and can see no difference at all in my approach.

I have attempted the install on 5 seperate occasions in the past 10 days
and on each attempt I have started with a totally new and clean instance
of Windows Server 2003 which has IIS enabled and IE Enhanced Security
disabled,

I have then installed Office 2003, Office 2003 Professional Service Pack
2, Project Pro 2003,

These are noise. They're not integral to your installation so they serve
only to confuse


SQL Standard Edition then Service pack 3a, SQL Analysis

Services followed by the Service Pack 3a followed by Windows SharePoint
Services and finally Project Server 2003. I have created accounts as per
the install guide and followed all the prompts and worked through the
install process to completion and have then run the PSCom+ utility and
also checked the SOAP address in the pds.wsdl file

If you did everything in the correct order according to the installation
guide, you shouldn't need to touch the COM+ component

I have worked through the process exactly as per the guide published by

I beg to differ. See above comments.

On completion of the install process the "Configure Microsoft Office
Project Server" menu shortcut results in a blank page displaying in
Internet Explorer.

Not surprising as the statement two below indicates you installed to the
wrong virtual server, certainly not where the installation documents specify

Entering http://localhost in IE results in a blank page.

As it should

Going to the WSS Central Administration Page the URL is
http://localhost:29082/default.aspx when I would expect it to be
http://servername/default.aspx

The first URL looks to be correct, your expectation of the second URL is
incorrect

I can navigate to the Project Web Access login page but again its URL has
the http://localhost:29082/projectserver address and not the
http://servername/projectserver I would expect to see.

Here your expectation is correct, however you installed Project Server to
the SharePoint Central administration site rather than to the default
website, which seems to have been your intent. Based on your report, you
need to start over again.

 

[Dominic Moss]

Dear Gary,

Thanks for your input - I ran the PSCom+ Utility as I had not entered the
Analysis Services information during the install process so I have to admit
I did not follow the install process exactly as per the guide.

During the install I did select the Default Web Site option when prompted
during the Microsoft Office Project Server 2003 install process - the
dialogue box displayed offered either the Default Web Site or SharePoint
Central Administration sites as the only 2 options and I definitely selected
"Default Web Site". In the guide the screenshot shows only the Default Web
Site option being available, is this an issue? Default Web Site was the only
option available during the SharePoint Configuration process.

Dominc

 

[Gary L. Chefetz [MVP]]

Dominic:

The results you report indicate that you chose the SharePoint Central
Administration site. Otherwise, how did Project Server get installed there?
It is what it is, no?

 

[Dominic Moss]

Dear Gary,

Thanks for your continued input - I will try again and make doubly sure that
I select the "Default Web Site" option - I am pretty confident this is what
I did on my previous attempts. Do you have any observations about my having
both the Default Web Site and SharePoint Central Administration Web Site
options when the Microsoft guide shows a screen dump with only the Default
Web Site being available as a selection?

 

[Gary L. Chefetz [MVP]]

Dominic:

The Micrsosoft screen shot you refer to must have been shot prior to the WSS
installation.

 

[Dominic Moss]

Update:

I have tried again and have followed the Install Guide to the letter and
still have problems - I have compiled documentation covering the entire
install process and also another document outlining the issues arising which
I can provide if you are interested.

In the past I have managed to install on a Single standalone computer using
exactly the same software and approach, no problem - I am at a loss to
understand why this time I am feted not to succeed. This issue has been
tormenting me now for nearly 2 weeks and I am no nearer a resolution.

 

[Dominic Moss]

For the record I repeated the install process on a different server and
achieved success first time round following exactly the same steps as my
numerous previous attempts.

This would tend to suggest a hardware issue although what I don't know. The
recalcitrant server has an AMD AM2 X2 64 3600 processor if this is of any
significance. It is also not connected to any other computer or to the
internet, is there anything I need to do as far as the network card is
concerned, I recall issues covering "loop-back adapaters" when installing
Project Central years ago.

Whilst I have now got a trial instance of Project Server up and running I am
not having problems with project professional and will post the issue on
that newsgroup.