Monday, April 21, 2008

Deploying WSS/Moss 2007 to an Existing Install of Project Server 2007

An Angry Error

My team has been running Project Server 2007 for quite some time. While it was originally set up to allow project managers to sync their MS Project timelines in one place it eventually became our team portal for storing all team calendar/project/document data.

The problem with this was that there are quite a few WSS/MOSS features that the rest of us wanted to collaborate with that weren't available with the stock Project Server 2007 install.

As such we decided to install MOSS 2007 on the machine. There's pretty good documentation on how to go about doing this. I was walking through the document steps and I ended up installing MOSS which went fine. But when it came time to run the SharePoint Products and Technologies Configuration Wizard, I ran into this angry error (below) and that's what this blog entry is about.

System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) at Microsoft.SharePoint.SPGlobal.HandleUnauthorizedAccessException (UnauthorizedAccessException ex)

Error

The Fix

The solution ended up being quite simple (although exhaustive). I needed to add my credential as a Site Collection Administrator to EVERY site collection in the farm. I'm guessing that during the config process the Wizard tries to walk through all the site collections do setting detection among other things? I know the fix isn't pretty, but it's what got me over the finish line.

In case you forgot how to do this:

  1. Open up the SharePoint Central Administration site.
  2. Navigate to Application Management and click on Site collection Administrators.
  3. From there you set your credential as the Site Collection Administrator for each Site Collection in each Web Application.
  4. Run the SharePoint Products and Technologies Configuration Wizard again. You'll probably get prompted as to whether you want to overwrite your default site or simply not create a default site. Afterwards you the wizard should finish properly.
  5. I'd recommend going through the rest of the TechNet article to ensure that you're following the rest of the right steps, but hopefully you're out of the woods for now.Success

That's it. Hope she helps.

Best,
Tyler

6 comments:

Ashok said...

Thanks a lot for this post. It worked and solved my three day headache.

Anonymous said...

I would just add your admin account to the web application web policy -- that way it has access to all site collections without having to manually grant it access to each site collection.

Tyler Holmes said...

I hadn't thought of that. I always forget to use Policy to my advantage. Thanks for the tip!

Ludger said...

great job.
that helped me after hours of troubleshooting!

Tyler Holmes said...

No worries ludger, thanks for the feedback!

Anonymous said...

This is a great post and helped tremendously.

I would also like to add a qualifier for my experience: I found it necessary to give dbcreater and sysadmin roles to every site administrator account and the NT AUTHORITY\LOCAL SERVICE so the PSCONFIG -CMD SETUP could complete its 10 tasks. This may be overkill; but it got me through without ACCESS DENIED errors or CA crashing.