I don't know why this is happening and I have not seen this before but the installation always stops at Creating Metadata Service Application... No errors in the event log indicate why it's failing. The SQL database does get created and when close the powershell installation and start it again, the installer says the metadata service is already started and the application has already been created. The rest of the installation usually goes through fine but it recently got stuck on the search service application admin component initializing step..... blue dots for infinity. I checked the admin component in central admin and there it said that it could not be initialized because of an error. I also set the search service to an account other than farm so it might just be that I did not have the search service account set to local admin group, which is required. I found an article that said the charting components needed to be installed, but shouldn't this have been done through the prereqs step?
Oh well... giving it another shot and will report back.
UPDATE: After going to the central admin and clicking the link to manage the metadata service application, I see the error outlined in red (second one down the page) in the following article:
http://123it.blogspot.com/2011/02/issues-with-creating-managed-metadata.html
It suggests to specify the service application with the default but when I go into the default under associations, I don't see anything there. The metadata service application does show up in the Manage Service Applications section. Something is going wrong with the central admin association during the creation step. I only see this issue on one server that I am setting up and the server is a clean 2008 R2 SP1 but another clean R2 SP1 seems to be fine.
I also noticed a warning in the event logs:
Installation in the global assembly cache failed: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\policy\Policy.11.0.Microsoft.SharePoint.Security.dll
and an error:
Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists.
The managed metadata service is running and when I try to access the term store management tool in a site collection I get:
The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.
Oh well... giving it another shot and will report back.
UPDATE: After going to the central admin and clicking the link to manage the metadata service application, I see the error outlined in red (second one down the page) in the following article:
http://123it.blogspot.com/2011/02/issues-with-creating-managed-metadata.html
It suggests to specify the service application with the default but when I go into the default under associations, I don't see anything there. The metadata service application does show up in the Manage Service Applications section. Something is going wrong with the central admin association during the creation step. I only see this issue on one server that I am setting up and the server is a clean 2008 R2 SP1 but another clean R2 SP1 seems to be fine.
I also noticed a warning in the event logs:
Installation in the global assembly cache failed: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\policy\Policy.11.0.Microsoft.SharePoint.Security.dll
and an error:
Safe mode did not start successfully. This page has encountered a critical error. Contact your system administrator if this problem persists.
The managed metadata service is running and when I try to access the term store management tool in a site collection I get:
The Managed Metadata Service or Connection is currently not available. The Application Pool or Managed Metadata Web Service may not have been started. Please Contact your Administrator.
