SharePoint 2013 - Backup - Restore Managed Metadata from one farm to another

Below Powershell script can be used to back up and restore the terms from one sharepoint farm to another in sharepoint 2013.


For BackUp #Add-PSSnapin Microsoft.SharePoint.PowerShell

$mmsAppId= "Pass GUID- refer the first screen shot below to get the guid"

$mmsproxy = Get-SPServiceApplicationProxy -Identity  "GUID- refer the second screen shot for getting the guid "

Export-SPMetadataWebServicePartitionData -Identity $mmsAppId -ServiceProxy $mmsproxy -Path "C:\path\FileName.cab"


For Restore

move the  FileName.cab file to the new server.

Use the below PowerShell commands.

$mmsAppId= "GUID- refer the first screen shot to get the guid"

$mmsproxy = Get-SPServiceApplicationProxy -Identity  "GUID- refer the second screen shot for getting the guid "

Import-SPMetadataWebServicePartitionData -Identity $mmsAppId -ServiceProxy $mmsproxy -Path "C:\.\FileName.cab" -OverwriteExisting;

 

Screen Shot1:-Please get the guid from the circled section of the below sccreen

Screen Shot2:-You can get the guid from  highlighted section of the the pop up from below screen shot

SP 2013 Cannot complete this action as the Secure Store Shared Service is not responding. Please contact your administrator.

Cannot complete this action as the Secure Store Shared Service is not responding. Please contact your administrator.

Please make sure that the following services are running.
under Manage services on server
1)  PerformancePoint Service
 2) Secure Store Service
 3) Claims to Windows Token Service
4)Excel Calculation Services
 

“Microsoft SharePoint Foundation Web Application” status "Starting

Issue >“Microsoft SharePoint Foundation Web Application” status not changing
After doing iis reset and services restart, still “Microsoft SharePoint Foundation Web Application” status is displaying as “Starting”

SolutionRun the following command in powershell, with admin right

1. Get-SPServiceInstance –Server WebFrontEnd1
This command will display all the services and correspoinding GUID
2. Stop-SPServiceInstance -Identity 2f409eff-ccd2-488d-ba14-db2899a44505

Identity we will get from the step one.
After doing the above two steps refresh central admin, the status of the Microsoft SharePoint Foundation Web Application should change to stopped

SharePoint Timer Job + Access Denied + FBA

We have configured Form Based authentication on a SharePoint 2010 claims based site and is working fine.

However timer job account is running under "Claims based user" rather than the actual ""set up account". in other words timer job is running under ” i:0#.w|dev\"setuplogin” instead of “dev\setuplogin”. Which is creating access denied error

("because the current user is not a Farm Administrator" ).

Resolution
I resoled this issue by removing and adding the user again in services. initially the user was shown as dev\mylogin and it was not working. after i removed the user and addded again it was showing as mylogin@dev.com . so i presume its taking the correcct user now.

The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact you

I was getting the below error in sharepoint 2010 server. however when i look into the state service i could see the service is running.
The form cannot be rendered. This may be due to a misconfiguration of the Microsoft SharePoint Server State Service. For more information, contact your server administrator

Resolution
1)Checked the heath analyzer and found that there is an error which says "No database is associated with the state service applications"
2) run the powershell script which most of the people suggested. it didnt work out.
3) so deleted the existing state service from central admin and recreated.
4) attached the application to the state service

It worked this time

Remedy Webservice Error

I was getting the error while trying to submit data via remedy webservice. thought of bloging my finding as it may help some one
Error
"A user name must be supplied in the control record"

Resoulution
credentials were not passing before calling the webservice.
mywebservice.AuthenticationInfo auth = null;
auth = new mywebservice.AuthenticationInfo();
auth.userName = "id@myid.com";
auth.password = "mypassword";