Share via


SQL Server 2016 - Copy Database Failure

Question

Saturday, October 22, 2016 7:01 AM | 1 vote

Hi,

I hope someone can help me. 

I have just installed SQL Server 2016 and want to copy my databases across from SQL Server 2012, on the same machine, but it fails.  I was able to copy databases from one machine to another using SQLServer2012, but that was before installing 2016.

I have given the latest list of error from the Event Log.

I have tried initiating the copy from both servers using both Windows Authentication and SQL Server Authentication.  With this error list I initiated it from SqlServer2012 with Windows Authentication.

I used the Sql Management Object Method to transfer the data.

With the 1st error, EventID 10016, although I am an administrator, have even added my user account name and given it Full Control in the permissions in the registry to try and get around the problem.  I am, however, not sure what to give Launch permissions to in the DCOM-Config Components.  I thought it might be the DTS Task Host and DTS Package Host components but no change.

Many thanks,

Source: DistributedCOM           EventID: 10016

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID

{FDC3723D-1588-4BA3-92D4-42C430735D7D}

 and APPID

{83B33982-693D-4824-B42E-7196AE61BB05}

 to the user MECER-PC\Sue SID (S-1-5-21-255691563-1771286175-784415985-1001) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

******************************************

Source: SQLISPackage130           EventID: 12550     (Twice)

  Event Name: OnError

 Message: Failed to connect to server MECER-PC\MSSQLSERVER2012.

StackTrace:    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()

   at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.OpenConnection(Server& server, ServerProperty serverProp)

InnerException-->Login failed for user 'NT Service\SQLAgent$MSSQLSERVER2016'.

StackTrace:    at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, DbConnectionPool pool, String accessToken, Boolean applyTransientFaultHandling)

   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)

   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)

   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionFactory.TryGetConnection(DbConnection owningConnection, TaskCompletionSource`1 retry, DbConnectionOptions userOptions, DbConnectionInternal oldConnection, DbConnectionInternal& connection)

   at System.Data.ProviderBase.DbConnectionInternal.TryOpenConnectionInternal(DbConnection outerConnection, DbConnectionFactory connectionFactory, TaskCompletionSource`1 retry, DbConnectionOptions userOptions)

   at System.Data.SqlClient.SqlConnection.TryOpenInner(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.TryOpen(TaskCompletionSource`1 retry)

   at System.Data.SqlClient.SqlConnection.Open()

   at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)

   at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()

 Operator: NT Service\SQLAgent$MSSQLSERVER2016

 Source Name: MECER-PC_MSSQLSERVER2012_MECER-PC_MSSQLSERVER2016_Transfer Objects Task

 Source ID: {8A917DAB-6013-4C78-ADA6-4222F3E10408}

 Execution ID: {29315BBE-16D5-4298-9A9B-9188DC0E71AA}

 Start Time: 10/22/2016 7:50:19 AM

 End Time: 10/22/2016 7:50:19 AM

 Data Code: 0

***************************************

Source: SQLISPackage130           EventID: 12551

  Event Name: OnTaskFailed

 Message:

 Operator: NT Service\SQLAgent$MSSQLSERVER2016

 Source Name: MECER-PC_MSSQLSERVER2012_MECER-PC_MSSQLSERVER2016_Transfer Objects Task

 Source ID: {8A917DAB-6013-4C78-ADA6-4222F3E10408}

 Execution ID: {29315BBE-16D5-4298-9A9B-9188DC0E71AA}

 Start Time: 10/22/2016 7:50:19 AM

 End Time: 10/22/2016 7:50:19 AM

 Data Code: 0

    

***************************************

Source: SQLISPackage130           EventID: 12549

  Event Name: OnWarning

 Message: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED.  The Execution method succeeded, but the number of errors raised (1) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.

 Operator: NT Service\SQLAgent$MSSQLSERVER2016

 Source Name: CDW_MECER-PC_MSSQLSERVER2012_MECER-PC_MSSQLSERVER2016_11

 Source ID: {624744FD-CE58-4DBE-BE0C-4B784637329C}

 Execution ID: {29315BBE-16D5-4298-9A9B-9188DC0E71AA}

 Start Time: 10/22/2016 7:50:19 AM

 End Time: 10/22/2016 7:50:19 AM

 Data Code: -2147381246

**************************************************

Source: SQLAgent$MSSQLSERVER2016          EventID: 12549

SQL Server Scheduled Job 'CDW_MECER-PC_MSSQLSERVER2012_MECER-PC_MSSQLSERVER2016_11' (0x77B58091408A0844A64ABCA54B6FA826) - Status: Failed - Invoked on: 2016-10-22 07:50:18 - Message: The job failed.  The Job was invoked by User MicrosoftAccount\my account'.  The last step to run was step 1 (CDW_MECER-PC_MSSQLSERVER2012_MECER-PC_MSSQLSERVER2016_11_Step).

All replies (4)

Saturday, October 22, 2016 8:16 AM

This may help you.

Take registry backup and do activity.

https://shauncassells.wordpress.com/2015/09/28/windows-10-event-10016-fix-the-application-specific-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-with-clsid-d63b10c5-bb46-4990-a94f-e40b9d520160-and-a/

Please click Mark As Answer if my post helped.


Saturday, October 22, 2016 10:15 AM

I think you are having a permissions issue.

Your copy is failing as it is running under the security context of 'NT Service\SQLAgent$MSSQLSERVER2016'

I suspect you are using the detach and attach method where you need to setup a proxy account that can access the file system on both servers. If the database is not too large perhaps you should try the use SQL Management Option, otherwise configure and SSIS proxy account as illustrated here.

https://www.packtpub.com/books/content/copying-database-sql-server-2005-sql-server-2008-using-copy-database-wizard


Saturday, October 22, 2016 11:40 AM

Hi Vishe,

I did as the link said....

I went into regedit via the Administrator Command Prompt and firstly could not save changes to HKEY_CLASSES_ROOT\AppID\9CA88EE3-ACB7-47c8-AFC4-AB702511C276} - Denied

and couldn't find

HKEY_CLASSES_ROOT\CLSID\D63B10C5-BB46-4990-A94F-E40B9D520160} in the registry.

I see that the first is the RuntimeBroker.exe but have no idea what the second is.

Any suggestions?

Thanks, Sue


Saturday, October 22, 2016 12:00 PM

Hi Hilary,

It does seem to be a permissions issue and I did use the SQL Management Option, but thanks for the link on how to configure the SSIS proxy account.