Service application database 2010 migration to 2013

If we want to migrate e.g. only Managed metadata service application database from 2010 to 2013 environment what will be exact steps?
(I know for content db we have to use Powershell Mount command).
But I guess in case of service application databases Mount command will not work, Can any one say if it true or not?
What are the steps involved to migrate such service application databases through Powershell?

See here for a guide:
http://technet.microsoft.com/en-us/library/jj839719%28v=office.15%29.aspx
In short, you create a new MMS and reference the copy of the MMS database you've moved to the new SQL instance for 2013.

Similar Messages

Service application pool recycling in SharePoint 2013

When to recycle service application pool in SharePoint 2013? is it necessary to do so?.
When I look at worker process section in inetmanager i see 25 GB is for reporting service application pool as used memory and for excel services application pool it is 11 GB
what does it mean? it is consuming this much amount of RAM? if so how we need to plan...do i need to recycle once in day? currently we are seeing slow performance. is it because of this? Please help.
Thanks, Ram Ch

Thanks for the response to both of you.
Trevor, I did all that you specified, result of that is the following forum questions raised by me.(it is same issue performance).
Private memory is used memory right? I am confused with unused memory you mentioned, can you please clarify.
and also please go through below questions raised by me for the same issue. Kindly help.
https://social.technet.microsoft.com/Forums/office/en-US/7de40349-4a31-4d7a-aced-0b80cc69c5b4/powerpivot-reports-are-getting-loaded-very-slow-very-often-in-sharepoint-2013?forum=sharepointadmin
https://social.technet.microsoft.com/Forums/office/en-US/68636329-4f48-4458-8645-31acca7f6d1c/sql-services-2012-reporting-services-performance-issue-powerview?forum=sqlreportingservices
https://social.technet.microsoft.com/Forums/office/en-US/9e558c89-0311-42c1-95dd-540f70914e00/powerpivot-reports-are-getting-loaded-very-slow-very-often-in-sharepoint-2013-sql-server-2012?forum=sqlkjpowerpivotforexcel
Thanks, Ram Ch

Showing search service application status error in SharePoint 2013

Hi All,
I'm unable to configure search service application in SharePoint 2013.When I go to CA > manage services , it is showing below issue.
On the place of started or stopped it shows 'error'. I'm using admin credentials here.
Then, when click on search service application, it shows details screen as follows
Thank you

HI,I would recommend to re-create the service application.please check the below links that gives you the solution of the issue.
http://expertsharepoint.blogspot.de/2014/07/the-search-service-is-not-able-to_19.html
http://expertsharepoint.blogspot.de/2014/07/the-search-service-is-not-able-to.html
Anil Avula[Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

Exchange 2010 Migration to 2013 Coexistence url's

Hello,
What exactly is required for the virtual directory url setup for Exchange 2010 coexisting with Exchange 2013? I have been searching online a lot preparing for my Exchange 2013 deployment and can't see to find a clear answer. The information
I have come across from TechNet and other sources is all over the place with some stuff saying the external url needs to be empty while others say it should match Exchange 2013's setup. Others say the internal url should be empty while
only the external should be populated. And I have even seen others say nothing on Exchange 2010 has to be touched and that Exchange 2013 will figure proxying out on its own once I configure the new url's on it.
So what is supposed to be setup for the ExternalUrl and InternalURL to in Excahnge 2010 for coexistence with 2013? Currently my
existing Exchange 2010 is internet facing with the plan of moving that to Exchange 2013 once that goes in as per Microsoft directions on implementing coexistence.

Read the article below from Ross Smith. There can't be better article than this:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
If exchange 2010 and 2013 are on same site, then you need to:
1. Remove External URL from Exchange 2010 CAS servers, retain the Internal URL
2. Move the SSL certificates from Exchange 2010 to Exchange 2013
3. Point the external URL to Exchange 2013 instead of Exchange 2010
4. Of course, you would need to re-configure Autodiscover, Web Services URLs on Exchange 2013 CAS servers.
Once this is done, for any mailbox that is hosted on Exchange 2010, Exchange 2013 would proxy the connections and deliver the content.
- Sarvesh Goel - Enterprise Messaging Administrator

Backup-SPFarm for PowerPivot Service Application

Hi
I am using Backup-SPFarm PowerShell cmdlet to take a backup of my service applications.
I am able to take the backup of all my services applications except PowerPivot Service Application.
Below is my command:
Backup-SPFarm -Directory $backupSAFolder -BackupMethod Full -Item "Farm\Shared Services\Shared Services Applications\SQL Server PowerPivot Service Application"
Error: Item Farm\Shared Services\Shared Services Applications\SQL Server PowerPivot Service Application not found.
I also cross checked with the correct Application service name (to check if i am not doing any typo mistake) using
Get-SPServiceApplication cmdlet. see the screenshot below.
Could somebody help me please.
My name is yogendra

You just need to take backup of service application databases from SQL server
http://msdn.microsoft.com/en-us/library/jj218793.aspx
op
2) Backup, Copy, Restore the Databases
The “SharePoint database-attach upgrade” process is a sequence of steps to back up, copy, and restore PowerPivot related content and service application databases to the SharePoint 2013 farm.
Set Database to read-only: In SQL Server Management Studio, right-click the database name and click
Properties. On the Options page, set the
Database read-Only property to
True.
Back up: Back up each content database and service application database that you want to migrate to the SharePoint 2013 farm. In SQL Server Management Studio, right-click the database name, click
Tasks, and click Back up.
File copy the database backup files (.bak) to the desired destination server.
Restore: Restore the databases to the destination SQL Server Database Engine. This step can be completed using SQL Server Management Studio.
Set Database to read-write: Set the
Database read-Only to False.
Migrate Schedules option1: SharePoint farm administrator
In the SharePoint 2013 Management Run the Set-PowerPivotServiceApplication cmdlet with the
-StartMigratingRefreshSchedules switch to enable automatic on demand schedule migration
. The following Windows PowerShell script assumes that there is only one PowerPivot service application.
$app=Get-PowerPivotServiceApplication
Set-PowerPivotServiceApplication $app -StartMigratingRefreshSchedules
After the Windows PowerShell script is run, the schedules are active and the schedules will run at the next appropriate time. However, the status one the schedule refresh page is not enabled. When the schedule runs the first time it will be migrated and
on the schedule refresh page, Enabled will be true.
If you want to check the current value of the StartMigratingRefreshSchedules property, run the following PowerShell script. The Script loops through all PowerPivot service application objects and display the name and property values:
$apps = Get-PowerPivotServiceApplication
foreach ($app in $apps){}
Get-PowerPivotServiceApplication $appp | format-table -property displayname,id,StartMigratingRefreshSchedules
http://msdn.microsoft.com/en-us/library/ee210616.aspx
If this helped you resolve your issue, please mark it Answered

Sharepoint foundation 2013 Search Service Application.

Hi all,
I want to configure search application for sharepoint foundation 2013. I have followed some of the web links.
But did not get success. Can you please provide me the working example of how to configure search application and run the crawl. And make sure the search is working correctly.
Thanks in advance for help.

Hi Vishwajeet,
According to your description, my understanding is that you want to configure SharePoint Foundation 2013 Search service application.
In SharePoint Foundation 2013, we cannot add the Search Service to SharePoint Foundation 2013 from the Central Administration GUI after selecting a manual configuration method. It seems that the ONLY way you can add the Search Service to SharePoint Foundation
2013 is by using the SharePoint Configuration Wizard.
More information, please refer to the link:
http://blog.ciaops.com/2012/12/search-service-on-foundation-2013.html
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Unable to delete search service application

We accidentally deleted the three databases related to Sharepoint Search. Luckily, this was done on the test server. So now I have the search service application but no related databases. I want to delete this search service application
and recreate it but it won't let me do it because during deletion it's looking for these databases and I get an error message that it can't find them. Is there any way to either recreate these databases or force deletion of this Search Service application?
thanks,

Hi,
If you have the backups for these databases related to SharePoint Search, you can try to restore them.
If you donot, you need to use STSADM.EXE command as below to delete the corrupted search service application:
Stsadm -o deleteconfigurationobject -id %GUID%
Reference:
http://blog.greenbrain.de/2013/11/removing-corrupted-search-service-from.html
http://blog.isaacblum.com/2011/08/08/force-delete-search-any-service-application-sharepoint-2010/
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Exchange 2013 / 2013 Coexistence - OWA rendering on 2010 CAS for 2013 Mailbox

So I'm running Exchange 2013 CU2v2 alongside Exchange 2010 SP3 (both on top of 2008 R2 SP1) and I'm having a bit of a weird thing happen when migrating test users from Exchange 2010 to 2013.
After migrating a user from a database on the 2010 server to a database on the 2013 server, when you access OWA (through a url pointing at the 2013 server), it still appears to render on the 2010 CAS (and functions normally). If you click ? > About it
shows properly that the mailbox server is the 2013 server, but the host address and client access server are still the old 2010 server. It seems that after a few hours it fixes itself. ECP, however, renders properly on the 2013 server immediately after migration.
The migration completes successfully with no errors, and outlook connects fine after migration, hitting the 2013 CAS.
I thought maybe this had to do with the Exchange Information Systems Cache, as in 2010 this was occasionally an issue:
http://www.terminal.com/blog/bid/70313/Moving-Mailboxes-During-an-Exchange-Migration
but the mailbox will still render on the 2010 CAS even after restarting the ExchangeIS service.
I should also note that this behavior DID NOT occur with Exchange 2013 CU1 alongside 2010, and only started happening after upgrading to CU2v2.
Does anyone have any thoughts as to why this is happening and what I can do to make it transition quickly to render OWA against the new mailbox? Thanks!

Exact same symptoms here;
Single site, 1 Exchange 2013 CU3 on 2012 Server, 1 Exchange 2010 SP3 as source for migration;
Exchange 2013 configured as external access 'cas' owa etc. and proxy to 2010.
Accessing an 2010 mailbox thu 2013 works correctly (OWA, ECP, ActiveSync, Outlook Anywhere etc.)
Created new mailbox on 2010, migrated to 2013 and this mailbox is accessed/proxied thru OWA 2010. Strangely this mailbox is hosted on the proxying 2013 server now but still gets proxied. ECP for this user does instantly connect to the correct 2013 server.
The 2010 OWA connecting to 2013 mailbox server: help | about:
Host address: https://ex2010.corp.local/owa
Version: 14.3.174.1
Proxy host address: https://ex2013/owa
Proxy version: 15.0.775.0
Proxy server name: ex2013
S/MIME control: not installed
Exchange Client Access server name: ex2010.corp.local
Exchange Client Access server .NET Framework version: 2.0.50727.5472
Client Access server version: 14.3.123.0
Client Access server platform: 64bit
Mailbox server name: ex2013.corp.local
Mailbox server Microsoft Exchange version: 15.0.775.0
Other Microsoft Exchange server roles currently installed on the Client Access server: Mailbox, Hub Transport
Authentication type associated with this Outlook Web App session: Basic
Authentication type for Exchange Client Access server to Client Access server proxy session: Negotiate
Public logon: Yes
So to me is that the 2013 server is still proxying to 2010 and the 2010 CAS is accessing the mailbox on 2013 ;).
This even when the mailbox is moved on the 2013 server itself!!
How strange is this?!
Regards,
Arian van der Pijl
Hello!

Reporting Services 2012 - "Database is up to date, but some sites are not completely upgraded"

Running SharePoint 2010 SP1 (Feb-Mar 2012 CU)
Is there any official word from Microsoft regarding the issue with SQL Server Reporting Services 2012 for SharePoint where 2 of the reporting service application databases show "Database is up to date, but some sites are not completely upgraded".
ReportingServiceDB - Database is up to date, but some sites are not completely upgraded
ReportingServiceDB_Alerting - Database is up to date, but some sites are not completely upgraded
I'm building the new Reporting Services into a new DEV environment and I'd like to know what the official word is from Microsoft. Is Reporting Services 2012 ready for production?
Thanks!

Hi mikea730,
Thanks for your psot.
Based on my research, I found a similar thread about this issue at Microsoft Contect site. For more information, please see:
http://connect.microsoft.com/SQLServer/feedback/details/721067/database-is-up-to-date-but-some-sites-are-not-completely-upgraded
It might be a known issue of SQL Server 2012. I would suggest opening a case with Microsoft Customer Support Services (CSS) (http://support.microsoft.com), so that a dedicated Support Professional can assist you
in a more efficient manner.
Regards,
Bin Long
Bin Long
TechNet Community Support

Unable to connect to database after migration from oracle 8 to 9i

Hi,
Our applications database was migrated from oracle 8 to oracle9i, The oracle_home path was updated to the newer version.
While accessing the databese using the new setup we are facing SQLLIB mismatch problem
the description of error is as follows
=======================================================
SQL-02107 Program too old for runtime library; please re-precompile it
Cause: Your program was precompiled by an older version of the Oracle Precompilers, which is incompatible with this release of SQLLIB.
Action: Precompile the program with a newer version of the Oracle Precompilers
=========================================================
Please help in this regard
~akhil

Hi Akhil,
Looks like some Tuxedo services are using Pro*C code. Therefore, you would need to recompile your Pro*C code using the newer compiler and then rebuild the Tuxedo servers.
HTH,
Ravi...
Hi,
Our applications database was migrated from oracle 8
to oracle9i, The oracle_home path was updated to the
newer version.
While accessing the databese using the new setup we
are facing SQLLIB mismatch problem
the description of error is as follows
======================================================
=
SQL-02107 Program too old for runtime library; please
re-precompile it
Cause: Your program was precompiled by an older
version of the Oracle Precompilers, which is
incompatible with this release of SQLLIB.
Action: Precompile the program with a newer version
of the Oracle Precompilers
======================================================
===
Please help in this regard
~akhil

DB Autogrowth settings - Service Applications and content DBs

Hi - is there any documentation out there that provides specifics for the initial size and autogrowth settings for the SP2013 service application databases?
I'm aware that the content DBs will vary and thus impossible to define settings except to note that autogrowth needs to be set in MB not %. But for service app DBs surely there must be some guidelines on initial sizing?
Thanks
J

Nope. If anything it's even harder to define.
A search service database might be a couple of hundred Meg for one customer and another may have to scale it out to multiple databases. MMS can vary hugely in scale and scope as can most of the other service apps.
The main thing to note for service apps is that they have custom fill levels for the index. That means you shouldn't use any one-size-fits-all re-index processes as you were able to do in 2010.
My general advice is not to bother with tuning the Service App databases. Only start worrying about them when you're really pushed on performance.

Advanced and complicated architectural situation: Shared Service Application with Workflow ?

Hi Forum,
I am currently encountering a peculiar situation in our SharePoint 2013 environment (Let's call it Farm-1), and I would really be thankful for your creative suggestions.
Whenever we create any simple workflow on our Farm-1, it NEVER worked, and we get the exception:
RequestorId: 26f1da47-f3e6-0816-0966-df958cd57c7d. Details: System.ApplicationException: HTTP 401 {"error_description":"The server was unable to process the request due to an internal error. For more information about the error, either turn on
IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework
SDK documentation and inspect the server trace logs."} {"x-ms-diagnostics":["3001000;reason=\"There has been an error authenticating the request.\";category=\"invalid_client\""],"SPRequestGuid":["26f1da47-f3e6-0816-0966-df958cd57c7d"],"request-id":["26f1da47-f3e6-0816-0966-df958cd57c7d"],"X-FRAME-OPTIONS":["SAMEORIGIN"],"SPRequestDuration":["252"],"SPIisLatency":["1"],"Server":["Microsoft-IIS\/8.0"],"WWW-Authenticate":["Bearer
realm=\"73b2c214-338d-4c93-937f-5852744a020d\",client_id=\"00000003-0000-0ff1-ce00-000000000000\",trusted_issuers=\"00000005-0000-0000-c000- ---
I have seen a handful of posts suggesting running the User Profile service and its Synchronization.
Also, I have see the presentation of: Spencer Harbar and Wictor Wilén on: (http://channel9.msdn.com/Events/SharePoint-Conference/2014/SPC356) where at minute 28:00 an slide 40 stating that as a requirement: User Profile Service Instance and Service Application,
Users must be populated in the Profile store and have valid User Principal Name (UPN).
My question is:
On our environment (Farm-1) we are consuming the User Profile service application from other separate SharePoint 2013 environment? Any workaround?
We really do not want to set up another User Profile service application onto our environment (Farm-1), Any possible workaround to make the current shared User Profile sufficient to run the workflows correctly?
What can be done?
Thank You

Hi ,
For troubleshooting this issue, let's verify the followings:
What action did you use in your workflow? Please test just using “Log to history list” action, compare the result.
Please go to Central Administration->User profile service application, check whehter the user that you run workflows has user profile in Manage User Profiles.
As you are using SharePoint 2013, what platform did you use when you created workflows? Please try to create a new workflow using SharePoint 2010 plaform.
Whether this issue occurred on all web applications in your Farm-1.
Please open a problematic site collection->Site settings->Manage site features, make sure the feature “Workflows can use app permissions” is activated.
If you met this issue only for SharePoint 2013 platform workflow, you can also try to re-register workflow service via Register-SPWorkflowService.
More information about register workflow service:
https://technet.microsoft.com/en-us/library/jj663115(v=office.15).aspx
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Failed to Upgrade User Profile from Sharepoint 2010 to Sharepoint 2013

I have upgraded the MMS service successfully. I tried to upgrade the user profile service from SharePoint 2010 to SharePoint 2013 farm using PowerShell script.
$applicationPool = New-SPServiceApplicationPool -Name "User Profile App Pool" -Account "Domain\accountname"
$upa = New-SPProfileServiceApplication -Name 'User Profile Service Application' -ApplicationPool $applicationPool -ProfileDBName 'SharePoint_ProfileDB' -SocialDBName 'SharePoint_SocialDB' -ProfileSyncDBName 'SharePoint_SyncDB'
Error in powersehell
New-SPProfileServiceApplication : Action 15.0.42.0 of
Microsoft.Office.Server.Upgrade.ProfileDatabaseSequence failed.
At line:1 char:8
+ $upa = New-SPProfileServiceApplication -Name 'User Profile Service
Application' ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidData: (Microsoft.Offic...viceApplication:
   SPCmdletNewProfileServiceApplication) [New-SPProfileServiceApplication], S
PUpgradeException
    + FullyQualifiedErrorId : Microsoft.Office.Server.UserProfiles.PowerShell.
   SPCmdletNewProfileServiceApplication
ULS Log
PartitionPropertiesCache.RefreshPartitionProperties: Encountered error: System.InvalidOperationException: Operation is not valid due to the current state of the object.
at Microsoft.Office.Server.Administration.UserProfileApplication.PartitionPropertiesCache.get_SqlSession()
at Microsoft.Office.Server.Administration.UserProfileApplication.PartitionPropertiesCache.RefreshPartitionProperties()
Can anyone explain, why I am getting this error. Thanks.

Hi Rashid,
Before Creating the Service Application, User Profile Service should be started as Central Administration -> Manage Services on server -> Start User Profile Service.
After the serivce is started, then test again, compare the result.
Also, you can upgrade User Profile service as the following article:
http://somethingaboutsharepoint.blogspot.com/2013/04/sharepoint-user-profile-service.html
In addition, here are two similar posts for this issue, please check if they are useful for you:
http://blogs.technet.com/b/saantil/archive/2013/03/31/sp-2013-error-when-upgrading-the-user-profile-service-application.aspx
http://blogs.architectingconnectedsystems.com/blogs/cjg/archive/2014/12/10/Action-15.0.14.0-of-Microsoft.Office.Server.Upgrade.ProfileDatabaseSequence-failed.aspx
Best Regards,
Wendy
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Work Management Service Application

does anyone have a step by step guide on how to create from scratch a work management service application, i have deleted mine due to issues with task syncs i think it was the configuration of this application that was causing this issue,
any help welcome.
Cheers

Hi,
According to your post, my understanding is that you wanted to create Work Management Service Application.
The following Service Applications must be provisioned before you can deploy the Work Management Service Application:
Search
User Profile
In addition to this, the Work Management service account must have some further permissions configured:
Full Control on the User Profile Service Application
Grant Access To Process Identity
To Create Work Management Service Application, Navigate to Application Management in SharePoint central administration, select Manage Service Application link. In Service applications page, create new Work Management Service Application, and specify the
details.
After re-create a new Work Management Service Application, we need to:
Create a new Application Pool, but use the same account as for the Application Pool hosting your My Sites/Social or Portal.
Run a crawl
Incremental, continuous or full crawl should suffice.
More information:
http://consulting.risualblogs.com/blog/2013/10/23/sharepoint-2013work-management-service-application/
http://sureshpydi.blogspot.in/2013/11/work-management-service-application-in.html
http://zimmergren.net/technical/tip-work-management-service-application-keeps-telling-us-last-updated-at-111901-1200-am-fixes
http://blogs.technet.com/b/praveenh/archive/2013/08/22/work-management-service-application.aspx
Best Regards,
Linda Li
Linda Li
TechNet Community Support

2010 to 2013 migration problem with service application

With a 3rd party migrator we are able to migrate a simple 2010 site to 2013. By simple UI level approach sites are migrated easily. But we have a large project where we have good amount of work done on various service applications.
We are facing problem to migrate entire 2nd SP2010 application with service applications. Do any one has idea of smooth migration of large service applications to 2013 with avepoint or quest tools?
If faced same problem then share steps.

The Microsoft guidance for upgrading a SP2010 farm to SP2013 is in the link below. Most of your existing SharePoint out of the box service applications can be upgraded also. This includes User Profile Service Application and the Search Service Application.
Custom service applications most likely not upgradeable. Hopefully the guidance was followed so there should be no problems.
http://technet.microsoft.com/en-us/library/cc262483(v=office.15).aspx
Blog | SharePoint Field Notes Dev Tools |
SPFastDeploy | SPRemoteAPIExplorer

Service application database 2010 migration to 2013

Similar Messages

Maybe you are looking for