IIS uninstalled by mistake - Project Server 2003

[ng]

Hi

Unfortunately a client has uninstalled IIS by mistake on a server
hosting a busy Project Server 2003 installation. Sharepoint WSS is
also being used for issues, risks, docs etc.

No IIS backups exist. The PS and WSS databases are still intact of
course. All services and SQL are on the same box.

I have the PS 2003 Disaster Recovery document.

I am assuming that the best route would be uninstall and reinstall
project server to recreate the sites/app pools either on the existing
server or on a new server after moving over the databases or even to
install PS on a new server and connect to the existing databases
(making the existing server just the database server).

I wondered if anyone would have any comment on this - presumably no
magic shortcuts in this kind of situation? Aspects to consider or
watch out for? App pools?

Brian

 

[sbendigo]

I did this once and had to reinstall everything. It would be interesting to
know if there is a shortcut.

 

[James Fraser]

Hi

Unfortunately a client has uninstalled IIS by mistake on a server
hosting a busy Project Server 2003 installation. Sharepoint WSS is
also being used for issues, risks, docs etc.

No IIS backups exist. The PS and WSS databases are still intact of
course. All services and SQL are on the same box.

I have the PS 2003 Disaster Recovery document.

I am assuming that the best route would be uninstall and reinstall
project server to recreate the sites/app pools either on the existing
server or on a new server after moving over the databases or even to
install PS on a new server and connect to the existing databases
(making the existing server just the database server).

I wondered if anyone would have any comment on this - presumably no
magic shortcuts in this kind of situation? Aspects to consider or
watch out for? App pools?

Brian

Some of the SharePoint links (both in Project Server and in
SharePoint) store the server name in a few places, so things will be
easiest if you can restore to a server with the exact same name and
urls.

Also, I disagree with one of the Disaster Recovery Guide's
recommendations: The DR Guide recommends specifying the existing
ProjectServer database during the reinstallation. This will overwrite
some pieces of the configuration. I prefer to reinstall with a blank
database and then point the new installation at the previously used
ProjectServer database. This will preserve more configuration. (Use
the EditSite tool to change the database access settings.)


James Fraser

 

[ng]

Thank you for useful advice advice James

Brian

Some of the SharePoint links (both in Project Server and in
SharePoint) store the server name in a few places, so things will be
easiest if you can restore to a server with the exact same name and
urls.

Also, I disagree with one of the Disaster Recovery Guide's
recommendations: The DR Guide recommends specifying the existing
ProjectServer database during the reinstallation. This will overwrite
some pieces of the configuration. I prefer to reinstall with a blank
database and then point the new installation at the previously used
ProjectServer database. This will preserve more configuration. (Use
the EditSite tool to change the database access settings.)

James Fraser- Hide quoted text -

- Show quoted text -

 

[Nico Oosthuysen]

Hi Brian,

Your approach sounds like the way I would have done it...

As you say, if you have the DB's and the server is still intact, you should
be able to just:

--Reinstall IIS, with ASP.net
--Reinstall SharePoint, extend the Default Web Site with a temporary DB
--Remove the Temporary DB, and connect your Content DB
--Install Project Server, selecting the option to "connect to existing
database"
--Just do not provide any parameters on the SharePoint page (use the
"provide this information later" option", as when you provide this
information during setup when connecting to an existing database it will
remove all of your links to the SharePoint Workspaces