How to move PWA from one SSP to another SSP in the same farm ?

T

Teddy

As subject description. I tried many ways but failed.
Is there someone who can help me on this issue.

Thanks
Teddy
 
P

Paul Conroy

Delete the existing PWA instance (but not the databases)

Recreate a PWA instance in the new SSP pointing the DB's those created by
the previous instance.
 
G

GHMontgomery

Another item of attention, when moving a PWA instance from one SSP to
another, is the WSS content database where the PWA project workspaces are
stored. If you do not take the proper precautions to relink your WSS content
database, you end up with PWA projects which have URLs defined but no
underlying site. You also end up with lost document, risk, and issue links
at the project level.

- Gina Montgomery
 
T

Teddy

Hi Gina,

You are right, that's what I met the issues. I got restored with workspace
lost and the PWA panel show me failed instead of provisioned once I change
the content database to original one, if I change the content database before
I create PWA, it then show me there's already PWA site there. I got no idea
to handle that. Do you know what's the best way to do a migration of PWA from
one SSP to another one ? I would appreciate if you don't mind to post the
detailed steps if possible.

Thanks
Teddy
 
G

GHMontgomery

Hi Teddy,

Unfortunately, I have not successfully performed the activity you are trying
to accomplish. I can say, however, that I believe this involves more than
just the PWA/SSP configuration. It is my understanding that the WSS Web
Application to which the SSP belongs needs to exist on the new server with
the same settings as on the original server. Then, you may be able to follow
the steps for moving a WSS 3.0 site to a new server since the PWA instance
is, in fact, a WSS 3.0 site.

There is an article on MSMVPS.com with instructions for "Moving a WSS 3.0
site to a new farm." I expect to test these instructions in a few weeks, but
have not had the time (or server resources) available to attempt this
approach since my last server maintenance.

Please let me know if you encounter success with your migration; you are not
alone in your efforts (and frustrations) with moving a PWA instance to a
different server. Thank you for posting this question as I think many will
benefit from the eventual solution (if someone can post it for us). :)

- Gina Montgomery
 
T

Teddy

About "Moving a WSS 3.0 site to a new farm" of MSMVPS.com, I actually did the
same steps to restore those web applications to my new farm, it works.
But for PWA, the one difference is we have to create a new PWA by the same
Project Server DBs below SSP PWA panel and get a way to associate the new
PWA site with the original content DB. That's the key.
And I've still not found a solution about that.

Teddy
 
P

Paul Conroy

you can bring the wss sites across using ststadm -o export / import from the
command line then use the wss relink tool from the resource kit to update the
URLs.
 
T

Teddy

I did export/import as Paul mentioned steps but got a page error after done
as following error message:
The enablesessionstate attribute on the page directive is not allowed in
this page.
Any ideas ?
 
T

Teddy

I did try several times and got the same error always. Is there any
suggestion ?

Teddy
 
T

Teddy

I've got it works, should be 5 steps
1. Export all workspaces
2. Delete Old PWA instance from Old SSP
3. Create new PWA on new SSP
4. Import workspaces
5. Reconnect workspaces

Thanks guys
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top