Attempting to re-create PWA site gives error "....name already exi

[Richard Ward]

Hi,
I am attempting to move a PWA instance from one WSS 3 farm to another. I
moved the databases on an initial test OK, but when I come to try to create
the PWA site again I am given the following error:
"The Project Web Access site specified can not be created because a site by
that name already exists."
and
"The database specified is already used by another project server. Enter a
different server or database name and try again."

These are the steps that I went through
1) Installed WSS 3.0 SP1 and confirmed functionality
2) Installed Project Server 2007 SP1
3) Created Shared Service Provider
4) Created Web Application to house the PWA site
5) Create a PWA site called "projectserver" using existing DBs transfered
from current live server. Address to access this would be
http://projectserver/projectserver
6) Tested the PWA site and found some issues.
7) Deleted the PWA site using the Shared Service Admin page
8) Deleted and re-created the "projectserver" Web Application
9) Restored another copy of the project server databases (over the existing
ones)
10) Attempt to create the PWA site using exactly same settings as in step 5

Errors detailed are generated when clicking "OK" on the PWA creation page.
No errors are logged in the Event Viewer on the server.

I have tried restarting the server that hosts Project Server, but this has
not fixed the issue.

Please can somebody let me know what I can take as next steps to
troubleshoot this.

Regards,
Richard Ward
Network Administrator
Warwick International Computing Systems

 

[Andrew Lavinsky]

1) Did you move the content database(s) over as well? If so, what happens if
you don't move your content dbs over, but create PWA fresh?
2) What happens if you provision PWA under a different name, same databases?

This sounds similar to what would happen if you tried to provision PWA into
a site collection where the PWA site had already been created in a different
environment.

To prevent that from happening, I would typically recommend deploying PWA
and the project workspaces into separate site collections.

Not sure if this is your specific issue, but that would be my first guess.