T
Tweedy
We lost our config file for the farm and didn't have a good SharePoint
backup, only database backups. So we reloaded all of the databases and
rebuilt the farm. In order to restore the SSP, we went into central admin,
clicked on Shared Services Admin, then on Restore SSP. Most everything came
back, including the 240 GB search index (whew!), but our PWA site was no
longer listed in the SSP. The browser is unable to access
https://server/pwa. The message it gets is
"PSI Auth: SiteId f4f29540-08da-4040-88b0-ca4d848baf6a was not found in the
ProjectSiteCollection for this SSP"
All four of the Project Server databases are intact. At this point, we
cannot use either central admin or stsadm to manipulate anything in
SharePoint to get it to "remember" the PWA site (or we just don't know how).
We tried backing up and deleting the pwa site, but SharePoint still thinks
the site exists when we try to do projcreatepwainstance. Running
projupdatepwainstance says the site does not exist. Hmmm. The problem
appears to be that the declared explicit inclusion managed path gives MOSS
this "hant" syndrome. If you're not southern, a "hant" is a ghost.
Partial solution: Exported all the project subsites
https://server/pwa/sitename; deleted the site at server/pwa; deleted the
explicit inclusion path in Central Admin for server/pwa; recreated pwa site
in SSP with existing DBs; imported all the project subsites.
With this "solution," we lost all of the docs in the server/pwa/shared
documents library, which fortunately did not hurt much in this case, but not
ideal.
Any suggestions for future problems?
Thanks.
backup, only database backups. So we reloaded all of the databases and
rebuilt the farm. In order to restore the SSP, we went into central admin,
clicked on Shared Services Admin, then on Restore SSP. Most everything came
back, including the 240 GB search index (whew!), but our PWA site was no
longer listed in the SSP. The browser is unable to access
https://server/pwa. The message it gets is
"PSI Auth: SiteId f4f29540-08da-4040-88b0-ca4d848baf6a was not found in the
ProjectSiteCollection for this SSP"
All four of the Project Server databases are intact. At this point, we
cannot use either central admin or stsadm to manipulate anything in
SharePoint to get it to "remember" the PWA site (or we just don't know how).
We tried backing up and deleting the pwa site, but SharePoint still thinks
the site exists when we try to do projcreatepwainstance. Running
projupdatepwainstance says the site does not exist. Hmmm. The problem
appears to be that the declared explicit inclusion managed path gives MOSS
this "hant" syndrome. If you're not southern, a "hant" is a ghost.
Partial solution: Exported all the project subsites
https://server/pwa/sitename; deleted the site at server/pwa; deleted the
explicit inclusion path in Central Admin for server/pwa; recreated pwa site
in SSP with existing DBs; imported all the project subsites.
With this "solution," we lost all of the docs in the server/pwa/shared
documents library, which fortunately did not hurt much in this case, but not
ideal.
Any suggestions for future problems?
Thanks.