DISCONNECT BETWEEN PROJECTSERVER 2003 AND WSS 2.0

[David]

Gary or TWIMC,

Environment:
We've been using Project Server 2003 SP2A and Sharepoint 2.0 for 2 1/2 +
years with no COM problems using Risks, Issues, and Documents. We've added
new templates viewable at PWA-->ADMIN-->Manage Windows Sharepoint
Services-->Site Provisioning Settings-->Specify Root Web Setttings-->Site
Template. The Site Template drop down list the new templates and the Project
Workspace template. WSS and Project Server are installed on the same server.
SQL 2000 SP3a runs on a seperate server.

Our Issue/Question:
- As of 9/24/2007 our resources cannot access Risk and Issues through PWA.
- I can access the Sharepoint Sites directly through the WORKSPACE in
SharePoint.
- I can also access Risk and Issues through PWA-->ADMIN-->MANAGE WINDOWS
SHAREPOINT SERVICES-->SHAREPOINT SITES
- The user receives the following message when attempting to open RISKS and
ISSUES from PWA;

"The documents, risks and issues features in Project Web Access use Windows
SharePoint Services. A Windows SharePoint Services site needs to be created
for your project before you can share project documents or track project
risks and issues. Site creation takes a few minutes, so if the project was
just published, wait a few minutes and then visit the page again. Otherwise,
contact your server administrator."

Obviosely, the sites exist, but ProjectSever seems to think they do not.

From what I googled and read at asktheexperts there are broken COM OBJECTS
between Project Server and SHAREPOINT. Listed below are the actions which
caused this. What I would like to know is how do I reestablish communication
between SharePoint and ProjectServer without losing the WSS content?
Possible Cause of broken com objects.
1. Our Server Team identified a corrupt RAID Stripe on the Project Server.
2. A complete backup of the Project Server was taken.
3. A complete restore on a new RAID drive was completed.
4. To do this we removed the Project Server from the AD domain.
5. When the server was rebuit we added it back to the domain and recovered
the project server data and the project server systems data. The SQL
databases were not touched during this process and remained on a seperate
physical SQL Server.
6. The Project Server was then moved back into the same domain with the same
IP address. OU and GPOs were then reapplied.
7. I have verified that the Sharepoint Admin Account IFB\Project is an ADMIN
account on the Project and in the OLAP_ADMIN group on the Project Server.

Help please....Halo3 is out and I rather spend this weekend on that then
this! So if anyone can lend assistance it is greatly appreicated. I am game
to go through all the steps, Extending, Top Level Web Site Creation, running
ProxCfg, runinign PSComPlus and possibly WSSWIZ.EXE if it doesn;t blow are
WSS CONTENT database!.
Thanks,
David

 

[Dave]

I am not sure if you have tried this or not, in Manage Windows SharePoint
services sites, select the project name and click synchronize. You will have
to do this for each project. Please note that you will loose any custom
permissions you have set on the Workspaces

Hope this helps

Dave

 

[David]

Dave, thakns for the suggestion. Yes we have tried that. We can also link
to any Project Sharepoint Web Site successfully from PWA-->ADMIN-->MANAGE
WINDOWS SHAREPOINT SERVICES-->SHAREPOINTS SITES.

Ironically, when we click Synchcronize, I get a message indicating
"SHAREPOINT TEAM WEB SITE FOR PROJECT XYZ DOES NOT EXIST" even though we can
succesfully access any Sharepoint Site from this page. Weird! I think the
Project SERVER and the SHAREPOINT COM OBJECTS are broken.

If any one has suggestions on how to restore the COM OBJECTS between Project
Server and WSS ASAP without losing the WSS CONTENT DB it is greatly
appreciated. Thx.


David

 

[David]

Hey we finally resolved the WSS Missing Template issue. If the Project
Workspace template is missing and you’ve attempted all resolutions listed at
Microsoft and the forums see below.

If you receive the exact errors listed in KB Article 910345 at
http://support.microsoft.com/kb/910345 but step 1e fails with an error
message indicating a ‘TOP LEVEL WEB SITE ALREADY EXIST’ the steps below
resolved the issue for us.

1.Remove Windows SharePoint Services.

2.Reboot the Server.

3.Install Windows SharePoint Services. Refer to the DR Guide at
http://go.microsoft.com/fwlink/?LinkID=20234. (Refer to page 35 ‘Recovering a
Computer Running Windows SharePoint Services’, section ‘Installing Windows
SharePoint Services’. Follow the steps through Page 41 up to but not
including section ‘Recovering a Computer Running Project Server 2003’. Note;
On Page 41 in the DR GUIDE, under Section ‘To Update Project Web Access
Settings’ steps 4 and 5 failed for us. To resolve this follow the steps
below.)

4. Follow Step 2a – 2h in KB article 910345 at
http://support.microsoft.com/kb/910345.

5. Navigate to the Windows SharePoint Services Central Administration at
‘http://server nameort/defaut.aspx’.

6. On the WSS Central Administration page under section ‘Virtual Server
Configuration’ select ‘Configure virtual server settings’.

7. On the ‘WSS Virtual Server List’ page select your virtual server name,
usually ‘Default Web Site’.

8. On the WSS ‘Virtual Server Settings’ page under section ‘Virtual Server
Management’ select ‘Define Managed Path’.

9. On the WSS ‘Define Managed Path’ page only under section ‘Included Paths’
remove all the ‘URL Name Spaces’ which WSS manages. For us we needed to
remove ‘(root)’ and subsite ‘Sites’. Important; Write down the ‘URL Name
Spaces’ Paths and Types before removing. You will need to add the ‘URL and
Name Space Paths’ and their Types back in
Step 18 below.

10. Run the Project Server 2003 Installation CD.

11. Select option ‘Microsoft Windows SharePoint Services’.

12. Select option ‘Windows SharePoint Services Configuration Wizard’, click
next.

13. Select option ‘Configure additional Windows SharePoint Services Web
Sites for Microsoft Office Project Server 2003’, click next.

14. Your ‘Default Web Site’ should be highlighted, click next.

15. The next window should have an entry highlighted which indicates ‘sites
(Already configured for Microsoft Office Project Server 2003.)’, click next.

16. At this point the Configuration Wizard should crash giving you the
option to Cancel and lose all changes. Your goal is to lose the changes
thereby removing previous settings.

17. Now Repeat only steps 5 – 8 above. (Not 9)

18. Re-add the ‘URL Name Spaces’ and their Types managed by WSS. (These are
the URL Name Spaces and Types you recorded under step 9 above). Follow the
instructions on Define Managed Path page to add the ‘URL Name Spaces’ and
Types.

19. Now repeat Steps 10 – 15. This forces WSSWIZ to recreate the account
information that Project and WSS use for the Default Web Site. Fill in the
appropriate account info. When complete write down the ‘SharePoint Central
Administration URL’ and ‘Create Site under this SharePoint URL’ info then
click FINISH.

20. Navigate to PWA-->ADMIN-->MANAGE WINDOWS SHAREPOINT SERVICES-->CONNECT
TO SHAREPOINT SERVER.

21. Verify that the ‘SharePoint Central Administration URL’ is the same as
the one you wrote down in Step 19. If not then correct it.

22. Verify that the ‘Create Site under this SharePoint URL’ is the same as
the one you wrote down in Step 19. If not then correct it.

23. IMPORTANT! once you have verified and corrected the information in Step
21 and 22 click SAVE CHANGES at the bottom of the page. You should not
receive an error message at this point. If you do you are experiencing a
different issue then we did.

24. Now navigate to PWA-->ADMIN-->MANAGE WINDOWS SHAREPOINT SERVICES-->SITE
PROVISIONING SETTINGS.

25. Verify that the ‘Project Workspace Template’ has been created under
SPECIFY ROOT WEB SETTINGS-->SITE TEMPLATE. Click Save Changes at the bottom
of this page. If the Site Template field is still blank you are experiencing
a different issue then we did.

26. The Steps listed above resolved our Missing Project Workspace Template
Issue. I recommend these steps only for those who have exhausted all other
possibilities such as the steps in KB910345,
http://support.microsoft.com/kb/910345 , PSCOMPLUS, PROXCFG, WSSWIZ.EXE,
REMOVING SHAREPOINT and REINSTALLING, REMOVING SHAREPOINT AND PROJECTSERVER
2003 and REINSTALLING, MIGRATIONS etc…. NOTE; It was critical during this
fix that we retained our WSS CONTENT and CONFIGURATION DB. The steps above
accomplished this. Good Luck!