Project Server 2003 & WSSWIZ.EXE

[ABG]

We are running Project Server 2003 SP2a and WSS SP2.

I have been able to extend a virtual server on the WSS (Windows SharePoint
Services) Administration page and then run WSSWIZ.EXE successfully and
everything in project PWA and Project PRO run great.

However, when I remove that database and add another WSS content database
(from another server that is running fine) onto this virtual server, it lets
me add it, but then I get the following error message when running WSSWIZ.EXE:
"SharePoint Configuration Wizard cannot create the
MS_ProjectServer_PublicDocuments site with the template that you have
selected. You must use the Project Workspace template or any other template
you have created by using the Project Workspace Template. Ensure that the
template has been installed into the correct directory, and then run the
SharePoint Configuration Wizard again."

Any suggestions will be greatly appreciated!

 

[Gary L. Chefetz [MVP]]

ABG:

You really need to explain why you're doing this. Also, is the "other
database" from a Project Server environment? Is it a fresh database? If it
has been used for other purposes, it would certainly explain the failure.

 

[ABG]

Thanks for your response Gary.

Well, we have an isolated Disaster Recovery network in place and we are
doing a DR test to see how everything works when migrating Project Server
from one box to another.

The Project Server Production environment databases restored and ran fine on
this DR network but the Test environment databases didn't.
However, we think we have found out what the issue was: IIS runs as a
service account that had to be manually added to the Active Directory server
on the DR network and since windows generates a unique security identifier
(SID) for each new user account that is created, we ended up with a service
account whose SID didn't match what the sharepoint project workspaces owners
had. We had to manually fix the 'site collection owners' on every site we
had (see http://support.microsoft.com/?kbid=823278&FR=1 for more info.).
Once we did that, everything started to work great.
We are still verifying this, learning a lot, and doing other tests.

Thanks!!