Moving project Wokspaces to another Box

[Cnegroni]

Hi:

I need to move an installation of Project Server 2007 to another machine
(Box). So I followed the recomendations given in this site:
http://blogs.msdn.com/brismith/arch...ving-a-copy-of-production-to-test-part-1.aspx (thank you "The Rogue Informa-nt").
Finally I was able to migrate the data from Box1 to Box2 (I restored the DBs
using WSS Central Admin Site and a full backup generated in Box1 and after
that I provisioned PWA). However when I try to access a Workspace from a
project the page fails (this is because I just moved the Project DBs:
Archive, Draft, Published and Reporting). So, to solve that my idea was to
create a new Workspace for every project in Box2 and use stsadm to import the
data from Box1. However, when I try to create a Project Workspace it appears
an error message showing ‘This project already has a Web site associated with
it’. So, how can I delete this information to be able to create an empty
Workspace and after that use stsadm to import the data from Box1? Or, there
is a better way to do this?

Any help would be appreciated.

Regards

Carlos Negroni

 

[Robert]

Carlos,

Did you change the actual URL's in ther Workspace settings?
Look at Server Settings/Workspace Settings and see what address's your sites
are using.


--
Project Consultant

REJ Company

(e-mail address removed)

 

[Cnegroni]

Robert:

Hi, thanks for the advise, I'm working on the issue and I'll let you know of
the results.

Regards

Carlos Negroni

 

[Piet Remen]

Hello Cnegroni. If your project server instance has many sites, you can
download the project server resource kit. Inside you will find a handy little
tool called the 'Project Workspace Site Relinker' to assist you in dong
exactly that. You may still need to manually link some sites but this can
help save some time. Download the kit from this link:

http://www.microsoft.com/downloads/...3C-6424-48E4-B87E-0861D1977BB7&displaylang=en

Regards,

Piet Remen

 

[Cnegroni]

Piet:

Hi, thanks for your advice. I tried to do that but the tool didn´t work (the
error message was: 'The request failed with HTTP status 401: Unauthorized')
and I couldn't find the reason for that so finally (according to an advice of
people from Microsoft) I had to export every site in the old server and after
that import each one of them in the new server (using stsadm). Well, I guess
this closes this subject.

Thank you very much.

Regards

Carlos Negroni

 

[Piet Remen]

Hi Cnegroni. The 401 error is directly related to ssecurity so if you ever
get to try this tool again, ensure you have top level access (farm
administrator for example)and run the tool on the application server to rule
out any security issues. Not sure but it may have .dll reference dependancies
that require it to be run on the app server. The main thing is you found a
solution but hope this may help anyone else next time.

Regards,

Piet Remen

 

[Piet Remen]

Hi Cnegroni. The 401 error is directly related to ssecurity so if you ever
get to try this tool again, ensure you have top level access (farm
administrator for example)and run the tool on the application server to rule
out any security issues. Not sure but it may have .dll reference dependancies
that require it to be run on the app server. The main thing is you found a
solution but hope this may help anyone else next time.

Regards,

Piet Remen

 

[Piet Remen]

Hi Cnegroni. The 401 error is directly related to ssecurity so if you ever
get to try this tool again, ensure you have top level access (farm
administrator for example)and run the tool on the application server to rule
out any security issues. Not sure but it may have .dll reference dependancies
that require it to be run on the app server. The main thing is you found a
solution but hope this may help anyone else next time.

Regards,

Piet Remen