Project Server 2003

[Harvey]

Hi,

I am running Windows 2003 Server, SQL Server 2000 SP3, Project Server
2003 (no SP1) and Share Point 2003.

I have my project Server running at http://<blah>/ProjectServer

It works great....so I wanted to integrate SharePoint into it to use
tasks...

So I installed Sharepoint...

I can acces the admin module at http://<Blah>:7711

Works great, extended the virtual server, etc, etc... Created Project
site
I then ran the Project Server 2003 Share Point config....

It created the following in the Project site

http://<blah>/Project/MS_ProjectServer_PublicDocuments

I can access that site and it looks like a regular Share Point site
to me (it used the Project Server 2003 Templates by the way).

However, when I go into the Admin on the Project Server and attempt
to use the "Connect to SharePoint Server" option under "Manage
Windows SharePoint Services" I am out of luck....I get the following
message after typing in all the correct jax from the Project
SharePoint install wizard.

"There are no site templates installed on the specified server running
Windows Sharepoint Services. Verify that the Web server is properly
extended with Windows SharePoint Services"

OK - click it and I am back to the connect screen.

Please can you help me!!!

Harvey

 

[Juhani]

Please clarify

I am running Windows 2003 Server, SQL Server 2000 SP3, Project Server
2003 (no SP1) and Share Point 2003.

does this time you write Share Point 2003 mean Windows SharePoint Services ?

So I installed Sharepoint...

does this time you write Sharepoint mean SharePoint Portal Server 2003

Juhani

 

[Harvey]

Hi,

Yes I mean Windows Sharepoint Services, not NOT Windows Sharepoint Portal.

Thanks,

Harvey

 

[Harvey]

Hi,

Yes I mean Windows Sharepoint Services, NOT Windows Sharepoint Portal Server.

Thanks,
Harvey

 

[Harvey]

Hi,

Yes I mean Windows Sharepoint Services, NOT Windows Sharepoint Portal Server.

Thanks,
Harvey

 

[ddrhodes]

Did you already install wss sp1 from the windows update site? This messed up
one of my installs; however, you can try to run the wss configuration wizard
from the project server cd again. Then try to connect project server to it
and see what happens. The wss configuration wizard should install your
project templates.

General rules of engagement ;-):

Install wss first, run the wss configuration wizard from project server cd,
then install project server. Then install the project server sql update sp1,
then run the project server full-file sp1, then install wss updates.

Best of luck to you.

 

[Harvey]

I have not yet run the wss sp1, however I have run the wss configuration
wizard already. How I understand is that wss config wizard should have
installed the templates for Project Server already..

However, I did run the wss config wizard after the prject server
installation, I guess that does not matter?

Thanks
Harvey

 

[Harvey]

Can anyone help??

I have not yet run the wss sp1, however I have run the wss configuration
wizard already. How I understand is that wss config wizard should have
installed the templates for Project Server already..

However, I did run the wss config wizard after the prject server
installation, I guess that does not matter?

Thanks
Harvey

 

[Gaurav Wason]

Try to remove windows sharepoint services from the extended site and
re-install and run the configuration again. I has this issue resolved once
the exacy same way.

"Re-installing the extended site"

Gaurav

 

[Myron Bollman]

I had this same problem, with no solution for weeks, but finally,
To solve this problem, I had to:
1) Remove Windows SharePoint Service from (the ProjectServer) Vitrual Server
(using WSS central Administration)
2) Then, select virtual server and "Extend and map to an existing virtual
server" using the exsiting IIS AppPool
3) Use "Defined Managed Paths" to add "/sites" with (Wild inclusion) and add
"/" (root) as (Explicit inclusion), also make sure that "projectserver" and
"msadc" are listed under Excluded Paths.
4) Now go back to the "Connect to SharePoint server" screen and ad URLs and
Save Changes.

This was the method that finally solved it for me. It may be similar for you.