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

We have created a new UAT environment for the deployment purposes and everything is new. Suddenly the requirement comes up for managed metadata. As this environment is newly built so we have not created all the service applications and work/create as per the requirement arises.

Note:

If you find a different solution, please report it as a comment to this post. Be sure to double-verify it: undo your solution and verify that the problem comes back, then redo it and verify that the problem goes away.

Problem Description:

Creation of new service application named as ‘managed metadata’

I have created a new service application by providing the following data:

1.   Name of the service application Example. Managedmetedata_DEVSP

2.   Name of the application pool

3.   Selecting the appropriate service account from the dropdown which has sufficient privileges to create the SA.

4.   Click OK

Now the service application is created without any issues.

As soon as I clicked on it then I got the following ERROR MESSAGE:

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:

Make sure the managed metadata service is already started.

How to check this:

a)   Central Administration

b)   Manage services on server

c)   Managed metadata service

d)   Start

Once the service is in started mode then check the results again by clicking on the managed metadata service application, it has to open the page without any errors\exceptions.

If you face the same error message as mentioned above then please execute IISRESET once and that’s it.

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you.

Your backup is from a different version of Microsoft SharePoint Foundation and cannot be restored to a server running the current version

Problem Description:

Requirement comes up to transfer the backup of one site collection from production to development environment.

-          Took the backup of the site collection by using PowerShell command without any issues

-          As soon as I tried restoring the backup then I faced the following error message

Error Message:

Your backup is from a different version of Microsoft SharePoint Foundation and cannot be restored to a server running the current version. The backup file should be restored to a server with version '14.0.0.6134' or later.

Checkpoints:

-Compare the development SP version with the production version and found out the following info:

Development- 14.0.6123.5006

Production- 14.0.6120.5006

-it’s quite obvious from the above versions that it’s not going to work L and we should be ready to hear the answer “It seems that you need to update your development server with the same patch which is running in production and then you can restore the backup” / upgrade your destination farm to the same version of the source farm, After your farms are at the same product version, the restore will succeed.

Resolution:

You must be wondering as How exactly I have achieved this resolution?

Here are the details:

-Restored Production backup to staging application but in a separate database

-Took that database and restored to development environment – which automatically place that DB to the same version

-Attached the database to default application, that’s it- issue resolved J

Site is up and running, easily restored to the development environment without any waiting time.

If you have any queries/questions regarding the above mentioned information then please let me know, thank you.

The SharePoint Health Analyzer detected an error. One or more services have started or stopped unexpectedly

Problem Description:

The SharePoint Health Analyzer detected an error. One or more services have started or stopped unexpectedly.

Error Message:

The following services are managed by SharePoint, but their running state does not match what SharePoint expects: SPAdminV4. This can happen if a service crashes or if an administrator starts or stops a service using a non-SharePoint interface. If SharePoint-managed services do not match their expected running state, SharePoint will be unable to correctly distribute work to the service.

SharePoint was unable to automatically repair this error.

To stop or start a service managed by SharePoint, use the SharePoint service management interface in the SharePoint Central Administration Site. If a service has crashed, restart the service manually on the affected servers by running "net start [service name]" from a command prompt. For more information about this rule, see http://go.microsoft.com/fwlink/?LinkID=142683.

Checkpoints:

- All services are running fine.

- All SharePoint sites as well as web applications are running without any issues.

Reason:

Basically it’s a clear cut indication that the one of the required service is un-reachable.

Resolutions you can try as there are multiple things by which we can resolve this issue:

- Check the administration service is running or not in services console. if its stopped/disable then please restart it.

- try to reboot the server and check the results again.

- try restarting the services by using command prompt

- after the above things and if you are still facing the problem then please check the SP logs and surely you will find the  exact error which will tell you the root cause behind it.

If you have any issues/queries regarding the above mentioned information then please let me know, Thank you

Product applies to:

- SP2010

- SP2013

- SharePoint Foundation 2010

SharePoint Pro | Update

Windows PowerShell Scripts for SharePoint: Info on Files, Pages,Web Parts

By Michael T. Smith

As I discussed in "Inventorying SharePoint Using PowerShell," Windows PowerShell is a valuable tool that you can use to inventory top-level SharePoint objects. That article shows you how to get lists of farm features, web applications, site collections, and sites using PowerShell cmdlets. In this article, I will explain how you can use PowerShell to obtain information from SharePoint about lists, libraries, files, and pages. Here are some of the tasks we will explore:

• Find lists and libraries based on just about any feature (e.g., versioning, content approval, date created).
• Find all libraries that use a selected content type.
• Find all items based on a selected column (including finding all documents created by a user).
• Find all documents of a certain type (e.g., .docx).
• Find all files larger than a certain size.
• List all libraries, their file counts, and total file size.

A reminder before we get started: Just because you can use PowerShell does not mean that you can ignore SharePoint security. See "Inventorying SharePoint Using PowerShell" for the basic security requirements. You will need to have at least read permissions to the content you want to explore. You can add the account you're using with PowerShell as a site collection administrator to every site collection or use SharePoint Central Administration user policies to give your account full read permissions in each application (select Central Administration, Application Management, then select an application, then click User Policy).

 

To read the rest of the article, click here.

Top 10 SharePoint 2013 Features Cheat Sheet

By Caroline Marwitz

See if any of the new or improved features listed below for SharePoint 2013 catch your eye. Then head over to Microsoft's SharePoint site for a deeper dive.

1. Authentication

• OAuth support. This web authorization protocol means that a user or web app can request authorization to get temporary access to specific network resources.
• Default claims-based authentication for new web apps. A new Windows PowerShell cmdlet, Convert-SPWebApplication, helps you migrate from Windows classic-mode authentication to claims-based authentication.
• Distributed Cache Service for login tokens. A dedicated cache helps avoid the need for additional configuration and makes for less memory utilization in the web front-ends.
• Enhanced logging.

To read the rest of the article, click here.

SharePoint Pro Magazine Tips and How-To's

Integrate Windows 8 Applications with SharePoint 2010, by Todd Baginski

SharePoint Pro | Updates

SharePoint 2013's Secret Weapon

By Dan Holme

Over the last two weeks, I’ve laid out an analysis of Office 365 and what it means to enterprises large and small.  But there’s one piece that I left out—quite intentionally—that today deserves to be brought to light: apps.  Not just any apps.  Killer apps.  Solutions to problems that transcend SharePoint… problems that have plagued businesses for years.  Now that Office 365 is released, I’d like to lay out my prediction for an exciting near-term future for SharePoint 2013 and Office 365 apps. 

From time to time I will highlight apps that I think are particularly noteworthy.  Today, I’d like to talk about a few—in particular a pair of apps that address very common business meeting and organizational challenges: MEETINGS and MY VIEW, which revolutionize your ability to leverage the Microsoft stack to manage effective meetings, and to roll up tasks and calendar entries across your SharePoint and Exchange worlds into a single view that can surface on any computer, tablet, or phone.

Before we jump to that discussion, I’d like to thank everyone at Penton—the organization behind SharePointProMag.com—for all their work on our BRAND NEW SITE, launched today with a great new engine that my colleagues—for example Paul Thurrott at SuperSite for Windows—have been raving about.  I think you’ll love the new look, and how easy it is (finally!) to register to make comments, and to find content you’re looking for!  So whether you have time now to read about a couple of apps that could change your work life, do jump to the new site to check it out!

To read the rest of the article, click here.

How to Use SharePoint Developer Dashboard for Monitoring Page Performance

By Asif Rehmani

Have you noticed any SharePoint pages in your environment that load slower than the others? Want to know why? The SharePoint Developer Dashboard can provide the answer. Its name makes it sound like it’s only for developers. However, it's an extremely useful tool for IT professionals as well as SharePoint site owners.

To read the rest of the article, click here.

Additional Resources

Why Data Quality Matters—A DBA and IT Perspective | April 3
To applications, data is everything. Allan Hirt explains how keep it clean inside and outside the application.

March 21 | Upgrading to Windows Server 2012 Hyper-V the Right Way
Join us as we talk about how to upgrade your existing hypervisor environment to contain the great new functionality available in Windows Server 2012 Hyper-V.

SharePoint Pro Magazine Tips and How-To's

SharePoint Security 101: What you need to know to secure SharePoint, by Randy Williams