Showing posts with label SP2010. Show all posts
Showing posts with label SP2010. Show all posts

16 April, 2013

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.

15 April, 2013

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

07 April, 2013

Configuring Content type hub in SharePoint 2010 step by step


Configuring Content type hub in SharePoint 2010 step by step
Content Type Hub is like a repository where we can store the content types in a site collection and can be shared among all site collections in a web application and multiple web applications in a farm.
It is one of the features available in Managed Metadata service in SharePoint 2010
Create a site collection name it as content type hub


Site collection: ContentTypeHub
Now configure this content type hub site collection in Managed Metadata services
Click on Manage Service applications under Application Management section
It will display all the services
Select the Managed Metadata service and click on Permissions

Add the Administrator




Click on Administrators




Select the Full control permisssions


Click on Properties








Now enter the URL of content type hub site collection here


Click ok and again select the managed metadata service ..click on properties


Select the Managed Metadata Service Connection and click on properties

Select all the checkboxes

Click ok
Now publish the Managed metadata service by clicking on Publish


   Select the check box..publish this service application to other farms


Click ok
Now open the content type hub site collection
Navigate to site action --> site settings
Click on site collection features under Site collection administration
Now content type syndication hub feature is already activated

Click on site content types under Galleries section
Now create a custom content type and name it as Cricket Content type





To publish this content type…click on Manage publishing for this content type
Select the publish radio button


Click ok
Now Cricket content type is published and it is available for all site collections in a web application and all web applications in a farm
Create a site collection “Australia” check this new content type “Cricket content type” is available.
Now navigate  to site actions à site settings
Click on Site content types under Galleries section
Cricket content type is available in custom content types section


Create a site collection in another web application to check whether cricket content type is available
Now navigate  to site actions à site settings
Click on Site content types under Galleries section
Cricket content type is available in custom content types section






03 April, 2013

What is the difference between a PU, a CU and a COD?

I thought of Sharing this Article written By Stefan to my Readers . Its really good to understand what is

Service Pack
Cumulative Update (CU)
Public Update (PU)
Critical On Demand Fix (COD)

Service Pack

What is it: A service pack is a combination of previously released fixes, fixes which have only been released in context of the service pack and potentially new functionality added to the product.
What is included: new fixes, new functionality, all previously released fixes (older Service Packs, CUs, PUs)
Multilingual: No. You need separate Service Packs for each installed language
What is the prerequisite: Usually there is no prerequisite to install a service pack.
When to install: it is recommended to evaluate and install Service Packs as soon as possible.
Impact on future fixes: CUs and PUs released more than 12 months after the last service pack can only be installed if the Service Pack has been installed before
Installation Sequence: no specific sequence. You can install a service pack on top of CUs and PUs released later.
Release Cycle: no specific release cycle
Cumulative Update (CU)

What is it: A cumulative update includes fixes for problems with our product that have been reported by customer in context of support cases.

What is included: New and all previously released fixes (CUs and PUs) since the oldest supported service pack (within the first 12 month after a Service Pack has been released the CU includes also fixes released after the previous service pack)

Multilingual: Yes. The CU package includes fixes for all languages.

What is the prerequisite: The oldest supported service pack. Within the first 12 months after releasing a SP you can install on the latest SP and the previous one. CUs released more than 12 months after the newest SP require the newest SP to be installed.

When to install: CUs should only be installed to resolve specific issues fixed with the CUs as mentioned in each CU KB article: "Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.". Or if adviced to install by Microsoft Support.

Impact on future fixes: In general a CU is not a prerequisite of future CUs and PUs. But in some situations a CU can be a prerequisite of a COD (see below).

Installation Sequence: no specific sequence.

Release Cycle: every second month (February, April, June, August, October, December)
Public Update (PU)

What is it: A public update usually includes security fixes for the product or fixes for problems which affect a broad number of customers.

What is included: please review the KB article for each public update in detail to see which fixes are included.

Multilingual: Yes. The PU package includes fixes for all languages.

What is the prerequisite: Usually the oldest supported service pack. Within the first 12 months after releasing a SP you can install on the latest SP and the previous one. PUs released more than 12 months after the newest SP usually require the newest SP to be installed.

When to install: As a PU includes security fixes it is recommended to evaluate and install PUs as soon as possible.

Impact on future fixes: In some situations a PU can be a prerequesit of future CUs and PUs. E.g. the March 2013 PU for SharePoint 2013 will be a prerequesit for all future CUs (and potentially PUs) for SharePoint 2013.

Installation Sequence: A PU can only be installed on a system which does not already have the included fixes applied through another source - e.g. through an earlier released CU. As PUs are advised to be installed by all customers while CUs should only be installed by customers affected by one of the fixes incuded in the CU the test cycle for a PU is much longer than for a CU. That means a PU released in March can be superseeded by a CU released earlier (e.g. February CU or December CU). Also in some situations a CU requires an earlier released PU to be installed first - otherwise the fix will not install.
Release Cycle: once a month (if required)
Critical On Demand Fix (COD)

What is it: A COD is a fix which is provided only to a small number of customers affected by a critical problem directly through Microsoft Support to provide a quick relief. The code change in the COD will be included in one of the next CUs and it is advised to install that CU on top of the COD as soon as it has been released.

What is included: only the specific fix for a specific issue.

Multilingual: Usually not.

What is the prerequisite: Usually the CU that was used as the baseline to develop the COD. Microsoft Support will provide guidance which CU is required to be install as a prerequisite for the COD.

When to install: Only if advised by Microsoft Support.

Impact on future fixes: A COD will not have an impact on future CUs or PUs. But the next CU can potentially revert the the code change introduced in the CU. See Installation Sequence.

Installation Sequence: As the COD will be released as soon as possible to a small number of affected customers it might happen, that the next CU released shortly after before or after the COD will not include the code change introduced by the COD. Customers which need the fix in the COD have to wait for the CU which will include the fix included in the COD. Microsoft Support will provided guidance on which CU can be installed on top of a COD.

Release Cycle: on demand
   
http://blogs.technet.com/b/stefan_gossner/archive/2013/03/21/common-question-what-is-the-difference-between-a-pu-a-cu-and-a-cod.aspx