AutoSPInstaller script hangs at Managed Metadata

Apr 11, 2011 at 3:04 PM

Hi,

I have used the package from 9 April 2011.

 The last text lines that was output were:

- Provisioning Managed Metadata Service Application

- Creating SharePoint Hosted Services Application Pool...

- Starting Managed Metadata Service:

- Starting Metadata Service Instance...

- Waiting for Metadata service...Online

- Creating Metadata Service Application...

 

The CPU usage in TaskManager were zero for several minutes so I closed the window.

What has gone wrong?

Regards,

Bengt Nilsson, Sweden

Apr 12, 2011 at 7:08 AM

I started the script again before I left the work, and an hour later it managed to finish without any errors!

/Bengt

Apr 12, 2011 at 10:36 AM

When I looked at the Health Analyzer in SharePoint 2010 I got 2 problems

1. MissingWebPart WebPart class [8d6034c4-a416-e535-281a-6b714894e1aa]

Solution for MissingWebPart

http://social.technet.microsoft.com/Forums/en/sharepoint2010setup/thread/63378c77-7d10-44f6-9a7f-787d0927b1b3

2. Verify each User Profile Service Application has an associated Managed Metadata Service Connection

I have not found any solution for the above error.

Regards,

Bengt Nilsson, Sweden

 

Coordinator
Apr 12, 2011 at 12:32 PM

1. MissingWebPart / Missing Server Side Dependencies is pretty much resolved in the latest (Feb 2011) CU I believe.

2. This is likely because your Managed Metadata did not in fact provision. Either that or its proxy isn't part of the default proxy group (or the proxy didn't get created). Check under Application Management --> Configure service application associations.

Brian

 

Apr 12, 2011 at 1:26 PM
Edited Apr 12, 2011 at 1:32 PM

When I look at Application Management --> Configure service application associations

the Managed Metadata Service is not included in the default proxy.

 

In Central Administration I selected Application Management --> Manage service applications

The Managed Metadata Service is stopped and has NO proxy!

When I click on Managed Metadata Service I get the following message

The Service Application being requested does not have a Connection associated with the Central Administration web application. To access the term management tool use Site Settings from a site configured with the appropriate Connection.

How do I add a proxy?

AutoSPInstallerInput.xml has the following text and MetaDataDB has been created at the SQL server.

        <ManagedMetadataServiceApp Provision="True"
                                   Name="Managed Metadata Service"
                                   ProxyName="Managed Metadata Service">
            <Database>MetaDataDB</Database>
        </ManagedMetadataServiceApp>

Bengt

Apr 12, 2011 at 2:23 PM

The Application and System logs have the following warnings and errors that occured during the installation.

/Bengt

Log Name:      Application
Source:        MsiInstaller
Date:          2011-04-12 13:55:18
Event ID:      1001
Task Category: None
Level:         Warning
Keywords:      Classic
User:          NETWORK SERVICE
Computer:      SERVER.DOMAIN.LOCAL
Description:
Detection of product '{90140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM' failed during request for component '{1681AE41-ADA8-4B70-BC11-98A5A4EDD046}'
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-04-12T11:55:18.000000000Z" />
    <EventRecordID>25922</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER.DOMAIN.LOCAL</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data>{90140000-104C-0000-1000-0000000FF1CE}</Data>
    <Data>PeopleILM</Data>
    <Data>{1681AE41-ADA8-4B70-BC11-98A5A4EDD046}</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
  </EventData>
</Event>

Log Name:      Application
Source:        MsiInstaller
Date:          2011-04-12 13:55:18
Event ID:      1004
Task Category: None
Level:         Warning
Keywords:      Classic
User:          NETWORK SERVICE
Computer:      SERVER.DOMAIN.LOCAL
Description:
Detection of product '{90140000-104C-0000-1000-0000000FF1CE}', feature 'PeopleILM', component '{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}' failed.  The resource 'C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe' does not exist.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="MsiInstaller" />
    <EventID Qualifiers="0">1004</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-04-12T11:55:18.000000000Z" />
    <EventRecordID>25921</EventRecordID>
    <Channel>Application</Channel>
    <Computer>SERVER.DOMAIN.LOCAL</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data>{90140000-104C-0000-1000-0000000FF1CE}</Data>
    <Data>PeopleILM</Data>
    <Data>{1C12B6E6-898C-4D58-9774-AAAFBDFE273C}</Data>
    <Data>C:\Program Files\Microsoft Office Servers\14.0\Service\Microsoft.ResourceManagement.Service.exe</Data>
    <Data>(NULL)</Data>
    <Data>(NULL)</Data>
    <Data>
    </Data>
  </EventData>
</Event>


Log Name:      System
Source:        Microsoft-Windows-DistributedCOM
Date:          2011-04-12 13:55:18
Event ID:      10016
Task Category: None
Level:         Error
Keywords:      Classic
User:          NETWORK SERVICE
Computer:      SERVER.DOMAIN.LOCAL
Description:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{000C101C-0000-0000-C000-000000000046}
 and APPID
{000C101C-0000-0000-C000-000000000046}
 to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
    <EventID Qualifiers="49152">10016</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-04-12T11:55:18.000000000Z" />
    <EventRecordID>14422</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>System</Channel>
    <Computer>SERVER.DOMAIN.LOCAL</Computer>
    <Security UserID="S-1-5-20" />
  </System>
  <EventData>
    <Data Name="param1">machine-default</Data>
    <Data Name="param2">Local</Data>
    <Data Name="param3">Activation</Data>
    <Data Name="param4">{000C101C-0000-0000-C000-000000000046}</Data>
    <Data Name="param5">{000C101C-0000-0000-C000-000000000046}</Data>
    <Data Name="param6">NT AUTHORITY</Data>
    <Data Name="param7">NETWORK SERVICE</Data>
    <Data Name="param8">S-1-5-20</Data>
    <Data Name="param9">LocalHost (Using LRPC)</Data>
  </EventData>
</Event>

Coordinator
Apr 13, 2011 at 3:05 AM

Actually none of these events are specific to AutoSPInstaller; I have seen them on nearly every SharePoint installation. You can track them down to DCOM Launch and Activation permissions, lots of folks have blogged/posted about them and the fixes if you search around a bit.

Brian

Coordinator
Apr 13, 2011 at 3:35 AM

Re: "How do I add a proxy?" - just delete your bad Metadata service app, then delete the MetaDataDB in SQL if it still exists, and re-run the script to try to recreate the Metadata Service App. It should create the proxy at the same time and associate it properly.

Brian

Apr 13, 2011 at 7:20 AM

Thanks for your help!

Bengt

Apr 13, 2011 at 8:13 AM
brianlala wrote:

Actually none of these events are specific to AutoSPInstaller; I have seen them on nearly every SharePoint installation. You can track them down to DCOM Launch and Activation permissions, lots of folks have blogged/posted about them and the fixes if you search around a bit.

Brian

I found this (and some more...):
http://www.mattgrovesblog.com/2009/10/dcom-error-10016-with-sharepoint-2010.html#axzz1JJY8AQa5

Bengt

Jun 16, 2011 at 2:05 AM
Edited Jun 16, 2011 at 2:24 AM

I had the same problem that BengtNilsson describes where the AutoSPInstaller hangs when it goes to create the managed metadata service application.

After stumbling around a little I finally looked in the event log (genius I know) - found a sql login error for my SPFarmAdmin account.

Then I remembered I deleted and readded that farm admin AD account and forgot to give it dbCreator security admin rights.

Once I added those to the sql account for my farm admin AD account - I didn't get that lockup on the metadata service creation.

Andy