Quick Fix: “The document could not be opened for editing. A Microsoft SharePoint Foundation Compatible application could not be found to edit the document” by Jim Adcock

Problem:
A user tries to open an InfoPath form in the application instead of the browser, and get an error message:

The user can open in the browser just fine, and has been able to open the forms previously with no problem. User is able to download the form to their desktop and open the form in InfoPath. But when they try to open the form in the application from the context menu, the above error is shown.

In researching the error, I found a support posting that provided a clue to the problem. In it, the user is instructed to enable Add Ons in their Internet Explorer:

1. Go to Tools in IE, click Internet Options
2. Click Programs at the top
3. Click “Manage add-ons” near the bottom
4. Click Publisher, then you can see all of Microsoft Corporation together
5. Scroll to SharePoint names (May be one or several)
6. Make sure they are all enabled by clicking on the name; the Enable button is towards the bottom.
7. Then click OK and OK and restart IE

Can you guess what the problem was?
Read more of this post

Migrate managed metadata from one environment to another in SharePoint 2010

What will be the requirement?

Your user will be raising a ticket for to create a replica of the production site in development environment.

Quite easy - correct? You can easily implement this by using PowerShell but now the problem starts from here. If your site collection admin has created a term store in production site then you will not get those in development environment. Hmm- seems to be difficult now, isn’t it?

Reason: Managed metadata terms and term sets each have a unique guid and the guids don't match up

Nothing to worry about as we have a solution for that :)

Let me brief some details as local terms can be created by 2 ways:

-centrally i.e. @Central Administration Level

-Locally i.e. @site collection level

Let me talk about ‘Centrally’ first: There are some ways by which you can implement this.

-By using Export and Import

-By using Database method

Let’s discuss about the first method i.e. Export and Import

Export Example:

$mmsAppId= "e1c96163-7767-4497-8e92-51eb154f0c70"

$mmsproxy = Get-SPServiceApplicationProxy -Identity "4d4b3094-a9ad-4cee-99f4-392d489a1657"

Export-SPMetadataWebServicePartitionData -Identity $mmsAppId -ServiceProxy $mmsproxy -Path "E:\backups\SP2010_Backups\mms.bak"

You must be wondering as how to get this App ID Guid Placeholder and Proxy ID Guid Placeholder. It’s very easy-please refer the following steps:

How to get App ID Guid:

-Central Administration

-Application Management

-Manage Service Applications

-Managed Metadata Service Application

-refer the browser now and copy the guid which is after tsid=

How to get Proxy ID Guid:

-Open the PowerShell console

-execute this command-  Get-SPServiceApplicationProxy

-You will see a list of proxy id’s and you need to copy ID that belongs to managed metadata.

Follow the same process in Import also and get the guids. Obviously they will be different as they belongs to different farm i.e. target farm.

Import Example:

$mmsAppId= "d7b7b20c-aed1-4cag-ba6a-45baa9d6adf2"

$mmsproxy = Get-SPServiceApplicationProxy -Identity "df8606f1-cfca-4283-89db-9270e0a5adec"

Import-SPMetadataWebServicePartitionData -Identity $mmsAppId -ServiceProxy $mmsproxy -Path "\\SP2010_SQL\SP2010\mms.bak" –OverwriteExisting

Database approach:

-Backup the managed metadata database in your source farm

-Delete the MMS service in your target farm

-Restore the managed metadata database to your target farm

-Create a new MMS service in your target farm

-Ensure correct service accounts have full control of MMS

How to move local term stores?

We can easily move the local term stores by using the following tool:

http://termsetimporter.codeplex.com/releases/view/59975

Documentation is already provided on the above site only so I will not go much deeper in reference to this tool but it’s very easy and user friendly too.

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

Error in creating a SharePoint Wiki site in SharePoint 2010

Problem Description: Error in creating a SharePoint Wiki site in SharePoint 2010

Creating a subsite underneath site collection by using ‘enterprisewiki’ throws an exceptions.

Please refer the following exceptions which is a series of error messages and helpful to understand the cause behind it.

Error Messages:

Error#1: Failed to activate site-scoped features for template 'ENTERWIKI#0' in site ‘http://sharepoint2007/sites/SP2010Projects’.    a41b91e6-385b-42a9-a10f-c69e15de613a

Error#2: Failed to activate web features when provisioning site at url " http://sharepoint2007/sites/SP2010Projects" with site definition "ENTERWIKI#0"

               

Error#3: Failed to apply template "ENTERWIKI#0" to web at URL " http://sharepoint2007/sites/SP2010Projects".  a41b91e6-385b-42a9-a10f-c69e15de613a

Error#4: SPContentTypeBindingElement.ElementActivated(). ContentType '0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39004C1F8B46085B4D22B1CDC3DE08CFFB9C' not found on web ' http://sharepoint2007/sites/SP2010Projects'.              a41b91e6-385b-42a9-a10f-c69e15de613a

Error#5: specified argument was out of the range of valid values. Parameter name:content type not found(‘0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF39004C1F8B46085B4D22B1CDC3DE08CFFB9C’).

Analysis:

Wiki template is a dependency section of Publishing Infrastructure as per the following articles:

http://technet.microsoft.com/en-us/library/ee721051.aspx  

http://technet.microsoft.com/en-us/library/ee837434.aspx

Resolution:

Activate publishing infrastructure at the site collection level as well as at the site level.

How to do this:

Activate Publishing Infrastructure @site collection level:   

-Open the site

-site actions

-Site settings

-site collection Administration

-activate “SharePoint Server Publishing Infrastructure”

Activate Publishing Infrastructure @site level:   

-Open the site

-site actions

-Site settings

-site actions

-manage site features

-activate “SharePoint Server Publishing Infrastructure”

That’s it; your issue will be resolved.

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

I would be more than happy to help you as well as resolves your issues, Thank you.

Product Applies To:

SharePoint Server 2010

SharePoint Foundation 2010

SharePoint workflow solutions – Surface Tablet door prize

Able Solutions next event — Automate Business Processes using SharePoint and Nintex — is just 2 weeks away! If you haven't already registered, I would encourage you to do so now.

We will be hosting lunch at the Microsoft Office in Alpharetta on April 30 to take a deep dive into the things you really want to know about using Nintex to enhance your SharePoint deployment. You'll hear from our top consultants and a key customer or two. One attendee will go home with a free Windows Surface!

Click this link to register today: https://clicktoattend.microsoft.com/en-us/Pages/EventDetails.aspx?EventID=168956

 

Creating customized search results in SharePoint 2013

With the launch of SharePoint 2013 came some exciting new features and improvements in the realm of Web Content Management (WCM). Content authoring improvements like Image Renditions and the ability to drag and drop navigation items directly onto a page create a better experience for content authors, while branding advancements like the new Design Manager and Device Channels further empower web designers. Throw in Managed Navigation, Cross-site Publishing, Catalog-enabled lists and libraries, Category pages, clean URLs and the ability to capture a video thumbnail straight from the video and it is clear that WCM has received quite the facelift courtesy of SharePoint 2013.

Read the full tip here...