Environment is a single SharePoint 2007 server (MOSS) and a SQL db server farm. Once upon a time a previous SP admin installed Project Server on the SP server, but it was never used. Some action was taken so that now SharePoint sees a site collection which was obviously used for projects (obvious by the naming of the collection) that make the collection inaccessible (via browser).
The plan is to clean up this SharePoint environment and upgrade to 2010 (on new hardware). There is no desire to use Project Server. I have heard that project server cannot be uninstalled safely from the SP server.

Is that true?

Would there be a problem with just 'ignoring' project server in production, not install it on the new 2010 hardware and SharePoint will just never know it existed in the old environment?

If not, what do I have to do to detach project server from SP in the new environment?

2 Answers 2


I had this same scenario.

There is not way to remove it in a supported fashion. You would need to remove the bits and update the database schema that project modifies. There is no tool I know of that does this for you. In addition there are the version number issue within the database. When you uninstall Project from your servers, it also has a tendency to remove your IIS configuration, so anything not configured by SP will be lost unless you back it up prior.

Becouse of the requirements for Project server changed in 2010, your only upgrade path is to SharePoint Server Enterprise 2010 w/ Project Server 2010. Nothing else is supported, and you will get errors when attempting to utilize the upgrade tool.

You are looking at migration scenario for your data. We purchased the AvePoint tool, but Quest and other companies have comparable products. Currently AvePoint is giving the tool away with 100GB of data (its priced on data migrated).

So if its less than that, you could utilize the free tool. If its more you'll need to purchase the difference. It is worth it vs. trying to migrate it yourself.

If no Project Server features are used in the site collections you would like to migrate, it is possible to do a database attach upgrade. Make sure no project server content (lists, etc) are used. A valid option is to clean up the site collections and migrate the sites through database attach. For feature cleanup there exists a tool on codeplex you can run on the sharepoint server:


After cleaning up you can do a "simple" a database attach migration and no need for an extra tool:


  • Thanks for your response...even though it isn't the one I wanted to hear. To clarify, if we migrate/move the data rather than do a database attach then we can get to a SP2010 server without Project Server, correct?
    – tony
    Commented Jun 21, 2011 at 16:08
  • @tony That is correct. You will first stand up an empty 2010 farm and migrate (copy) over the data. If it is just data, no version history, metadata, workflows, etc. you could probably do it your self, but for capturing all that other stuff look at AvePoint, Quest, or MetaLogix. Commented Jun 21, 2011 at 16:29
  • Thanks again Jesus. Luckily I can do a test run on a vm before setting up the production farm. Your info will save me a lot of time because I would have done a db attach.
    – tony
    Commented Jun 21, 2011 at 16:52

As long as no features from project server are referenced in the web app's content db you plan to migrate, you're in the clear when you do a backup restore of the content db to the new farm. Check your site collection(s) if no features related to project server are activated.

  • Thanks Colin. hmm, the services were stopped so the site collection doesn't display. I could start the project server events and queue service to check, but my guess is that site collection will have features enabled. The default site collection does not have any project server features enabled. This raises ANOTHER related question...could I just DELETE the project server site collection from Central Admin and then do the db attach?
    – tony
    Commented Jun 21, 2011 at 17:16
  • Is it in the same web app / content db as the sc you want to migrate? Then deleting it should remove most of the references to project server related features from the content db / config db.
    – Colin
    Commented Jun 21, 2011 at 18:08
  • yes it is the same web app and content db. thank you.
    – tony
    Commented Jun 21, 2011 at 18:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.