Add a Project server to a Sharepoint Portal server

You have to install Project server on every server on the farm that has had Sharepoint installed.  It won't work until you do.

I did an install of Project Server on both servers (there only was the MOSS server). On the existing Sharepoint server I can start the Project  Application Service. But on the new server, which should become the server for running the Project Application Service, it does not start (Status is "Starting").

Is the server running the project application service a member of the MOSS 2007 web farm?  If not it won't work.

It sounds like the Project server is part of the farm since it shows up in Central admin.

This could be permissions,
Check that the user who owns the process running Central admin (W3P) is in the administrator group on the project server box. Also the IIS admin group - they will likely need to be a member of that group.
Are the machines in the same domain?

I did add the server (with name Project) to the farm with the SharePoint Products and Technologies Configuration Wizard. The strange thing is, that when I try to add the server to the farm the first time, I get a event id 104:
An exception of type System.InvalidOperationException was thrown.  Additional exception information: 1387
System.InvalidOperationException: 1387
   at Microsoft.SharePoint.Win32.SPNetApi32.NetLocalGroupAddMember(String groupName, String userName)
   etc...
The second time I try, the server is added with no problem.
When I look in Central Adminstration, Operations, Servers in Farm, it shows the Project server with under Services Running: Not Configurerd. When I click on the server I get this:

Service      Comment      Status       Action
Central Administration      Service running on server: SPAPP       Stopped  Start  
Project Application Service                      Starting  
Windows SharePoint Services Search  Service running on server: SPAPP             Starting  
Windows SharePoint Services Web Application  Service running on server: SPAPP       Starting  

Spapp is the original Sharepoint server.

There are a number of accounts in the domain related to Sharepoint (with attached services):

SaMossDB: Microsoft Office Project Server Events Service, Microsoft Office Project Server Queue Service, Windows SharePoint Services Timer
SaMossSearch:      Office SharePoint Server Search, Windows SharePoint Services Search
SaMossSSP
SaMossPortal

They are all member of Domain Users.

I noticed something else. In the IIS Manager on the Sharepoint server onder Web Service Extensions I see Windows Sharepoint Services V3. They are not present on the new server.
@tedbilly
This server should be member of the web farm. But how do I check this?
@idicker:
How do see which user runs the Central Admin process?
There does not seem to be an IIS admin group in the domain.
Both machines are in the same domain.

If you need further information, please let me know.

Thanks,

Jac

The IIS Manager on the Sharepoint server (spapp) shows that the Application Pool Identity for Sharepoint Central Administration V3 is user SaMossDB. On the Project server, this pool is not visible.

on the project server box - try adding the SaMossDB account to the local administrators group and also the IIS_WPG group and the WSS_ADMIN_WPG group.

I added SaMossDB. The current situation is on the Project server is:

Local group:
* Adminstrators:
Members
Administrator
PLB\Domain Admins
PLB\SaMossDB

*IIS_WPG
Members:
IWAM_PLE-PROJECT
NT AUTHORITY\NETWORK SERVICE (S-1-5-20)
NT AUTHORITY\SERVICE (S-1-5-6)
NT AUTHORITY\SYSTEM (S-1-5-18)
PLB\SaMossDB
PLB\SaMossSSP

* WSS_ADMIN_WPG
Members:
BUILTIN\Administrators
PLB\SaMossDB
PLB\SaMossPortal

I did rerun the SharePoint Products and Technologies Configuration Wizard and even rebooted the box, but I see no difference.

On the new Project Server that you added, you did install SharePoint 2007 on it as well correct?  They both have to have SharePoint and Project to work in the farm.

@nbradley
Thanks for your reply, but what do you mean with Sharepoint? I did install Microsoft Office Project Server 2007 and this does install Microsoft Windows SharePoint Services 3.0 on the server.

Could the initial error when running the SharePoint Products and Technologies Configuration Wizard after installation of Project Server be significant? From the PSCDiagnostics_<cut>.log:

07/31/2007 15:11:22  6  ERR                      Failed to connect to the configuration database.
An exception of type System.InvalidOperationException was thrown.  Additional exception information: 1387
System.InvalidOperationException: 1387
   at Microsoft.SharePoint.Win32.SPNetApi32.NetLocalGroupAddMember(String groupName, String userName)
   at Microsoft.SharePoint.Administration.SPProvisioningAssistant.AddGroupMember(String username, Int32 group)
   at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionProcessIdentity(String strUserName, SecureString secStrPassword, IdentityType identityType, Boolean isAdminProcess, Boolean isWindowsService, String strServiceName, Boolean dontRestartService)
   at Microsoft.SharePoint.Administration.SPProcessIdentity.ProvisionInternal(SecureString sstrPassword, Boolean isRunningInTimer)
   at Microsoft.SharePoint.Administration.SPApplicationPool.ProvisionInternal(SecureString sstrPassword)
   at Microsoft.SharePoint.Administration.SPApplicationPool.Provision()
   at Microsoft.SharePoint.Administration.SPWebServiceInstance.Provision()
   at Microsoft.SharePoint.Administration.SPFarm.Join()
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
   at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
   at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

The error occurs at step 2 of 8.

Jac

You HAVE to install Sharepoint Portal Server 2007 on all servers in the farm and connect them all to the farm.  Then install Project Server 2007 on all servers that have had the full install of Sharepoint Portal Server 2007 and that have been connected to the farm.
The copy of WSS 3.0 installed by Project Server is not sufficient.

The SaMossMySIte user is likely - based on the name - to be for the Mysites feature of sharepoint - controlled from shared services.

If you want to use Project Server with Sharepoint you HAVE to do what I described.  Sharepoint Portal Server 2007 automatically load balances core services.

@tedbilly
Thanks. I will do that.

I'm receiving the error message:
There is a problem establishing a connection with the Web server running Windows Sharepoint services.
As a result, I have been unable to open a Sharepoint Project Page for MS Schedules.
Any suggestions?