PRB: DTS Package Fails with "Unspecified Error" Error Message When You Use Transfer Logins Task to Move a SQL Server Login (305365)



The information in this article applies to:

  • Microsoft SQL Server 2000 (all editions)

This article was previously published under Q305365

SYMPTOMS

When you use a Data Transformation Services (DTS) Transfer Logins Task to move a SQL Server login that is based on a local Microsoft Windows NT account, the DTS package fails with this error message:
"Unspecified Error".
Here is an example of the DTS package output log:
Package Name: (null)
Package Description: (null)
Package ID: {6014C46B-F76E-4072-8266-466A2B8CA45D}
Package Version: {6014C46B-F76E-4072-8266-466A2B8CA45D}
Package Execution Lineage: {8333062F-A287-48B0-8E8C-3A4EF9A18CB8}
Executed On: SERVER2
Executed By: administrator
Execution Started: 8/7/2001 5:11:03 PM
Execution Completed: 8/7/2001 5:11:05 PM
Total Execution Time: 1.131 seconds

Package Steps execution information:

Step 'DTSStep_OMWCustomTasks.OMWTransferLogins_1' failed

Step Error Source: Microsoft Data Transformation Services (DTS) Package
Step Error Description:Unspecified error
Step Error code: 80004005
Step Error Help File:sqldts80.hlp
Step Error Help Context ID:700

Step Execution Started: 8/7/2001 5:11:03 PM
Step Execution Completed: 8/7/2001 5:11:05 PM
Total Step Execution Time: 1.131 seconds
Progress count in Step: 0
Task Log for this step:
-----Start Task Log-----

Error = 1 (00000001), Description = Script    Login    BUILTIN\Administrators    
Error = 1 (00000001), Description = Script    Login    test    
Error = 1 (00000001), Description = Script    Login    sa    
Error = 1 (00000001), Description = Script    Login    server1\test    
Error = 1 (00000001), Description = Transfer    Login    BUILTIN\Administrators    
Error = 1 (00000001), Description = Transfer    Login    test    
Error = 1 (00000001), Description = Transfer    Login    sa    
Error = 0 (00000000), Description = Transfer    Login    server1\test    

-----End Task Log-----
				

CAUSE

Local Windows NT accounts are comprised of MachineName\UserName. Because the destination computer name is different, the transfer fails. Even if the machine names are the same, the security identifier (SID) of the local Windows NT account cannot be specified and are not likely to be the same.

RESOLUTION

If you plan to use the DTS Transfer Logins Task to move logins between servers, keep the following points in mind:
  • Logins to transfer cannot be based on a local Windows NT account.

  • Logins can either be Windows NT domain accounts or standard SQL Server logins.

  • Windows NT Domain accounts must be valid on both the destination and the computer that is running SQL Server. If the servers are in different domains, you can accomplish this through a trust relationship.

STATUS

This behavior is by design.

Modification Type:MajorLast Reviewed:10/16/2003
Keywords:kbprb KB305365