Enterprise portal installation error : The Application Pool or Managed Metadata Web Service may not have been started


Some times during the Enterprise portal installation the setup fails due to following issue :  
ERROR  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

Resolution 1


Make sure the managed metadata service is already started or not.
Go to SharePoint Central Administration site -> Application Management ->  Manage Services on server -> Managed meta data ->Start.
NOTE: After start the Service once reset the iis by running Command prompt as admin and execute command "IISRESET".

Resolution 2
We have to give the "Permission"

Go SharePoint Central Administration site -> Application Management -> Service Application -> Manage Service Application.
Highlight the Managed Metadata Service that your web application is associated with. (Do not click on the link, just click somewhere else on that row to highlight it).



Click on Permissions button in the ribbon area. Add the application pool account used by your web application and give it at least ‘Read Access to Term Store. click "OK"

Now check, Managed metadata working fine.


Resolution 3
If the above don't work than you may have to look at the Internet information service (iis) Manager and make sure that Share point web service is started in the Application pool and a admin user account is set in its identity.


Comments

Post a Comment

Popular posts from this blog

D365: SSRS Report Development/ Customization

Image
Hi guys, Today in this blog I will be demonstrating the procedure for the SSRS Reports development and customization in D365FO. Before proceeding with the Development or customization make sure that you have created a new model for your customization since we will be using extensions approach in our customization because An extension enables you to add functionality to existing model elements and source code. Coming back to the main objective of this blog which is to Develop SSRS reports in D365. One point to keep in mind is that there is no change on How you develop query based report and RDP based report in D365FO . The only change is you have to use extensions for standard report. If you are developing brand new report based on custom tables, there is no change. So in this Blog I will discuss How to customize an existing SSRS Report in D365 using Extensions approach step by step: Step#1:  The first step is to create a new model, Below are the steps to create a new model: Navigate to
Read more

D365: X++ code to add custom lookup on worker to show specific workers team workers only

/// <summary>             ///             /// </summary>             /// <param name = "_formReferenceControl"></param>             /// <returns></returns>             public Common lookupReference( FormReferenceControl _formReferenceControl)             {                 SysReferenceTableLookup      sysTableLookup = SysReferenceTableLookup ::newParameters( tablenum ( HcmWorker ), _formReferenceControl, true );                 Query                        query = new Query ();                 QueryBuildDataSource         queryBuildDataSource;                  QueryBuildRange              queryBuildRange;                 HcmPosition                  hcmPositionPareant;                 HcmPositionHierarchy         hcmPositionHierarchy;                 utcdatetime                  _validFrom = DateTimeUtil ::utcNow();                 utcdatetime                  _validTo    = _validFrom;                 H
Read more

Error message when you log on to a Microsoft Dynamics AX 4.0 client: "You are not a recognized user of Microsoft Dynamics AX"

When you log on to a Microsoft Dynamics AX 4.0 client after you restore a database, you receive the following error message: You are not a recognized user of Microsoft Dynamics AX. Contact your system administrator for help. This problem occurs if you restore a Microsoft Dynamics AX 4.0 environment in a different Active Directory directory service environment. This problem occurs when one or more of the following conditions are true: The security identifier (SID) is incorrect. The network alias is incorrect. The network domain is incorrect Resolution To resolve this problem, run the following script in SQL Query Analyzer after you restore the database. Note  You must obtain a SID in the current Microsoft Dynamics AX 4.0 environment. --Extract the user's SID from the current installation to update the restored database. select id, SID, Networkdomain, networkalias from userinfo where Id = 'admin'-- networkalias = '<UserAlias>' To extract t
Read more