My goal is run the SSIS Transfer Logins task weekly to pickup newly
created domain accounts from one server to the other. We have SQL 2005
w/ SP1 on both servers with a high availability mirror configured
between the servers. We would like to run Scenario 1 as weekly job but
that does not seem to produce the desired results. Scenario 2 works
but, I really do not want to have to open the SSIS package, pick the
user(s) then run. It would be faster to just create them I believe. Any
insight would be appreciated.

Thanks,

Ian in SD

Scenario 1

Authentication - Windows

LoginsToTransfer - AllLoginsFromSelectedDatabases
DatabasesList - Collection
IfObjectExists - Skip
CopySids - False
Result -
SSIS package "MigrateLogins.dtsx" starting.
Information: 0x4002F304 at Transfer Logins Task, Transfer Logins Task:
"There are no logins transferred.".
SSIS package "MigrateLogins.dtsx" finished: Success.

Authentication - SQL
Same configuration as above
Same result as above

Scenario 2

Authentication - Windows

LoginsToTransfer - SelectedLogins
LoginsList - Collection
IfObjectExists - Skip
CopySids - False

Result -
SSIS package "MigrateLogins.dtsx" starting.
Information: 0x4002F304 at Transfer Logins Task, Transfer Logins Task:
"Transferred "1" logins.".
SSIS package "MigrateLogins.dtsx" finished: Success.


Authentication - SQL

LoginsToTransfer - SelectedLogins
LoginsList - Collection
IfObjectExists - Skip
CopySids - False

Result -
SSIS package "MigrateLogins.dtsx" starting.
Error: 0xC002F325 at Transfer Logins Task, Transfer Logins Task:
Execution failed with the following error: "Script transfer failed. ".
Error: 0xC002F325 at Transfer Logins Task, Transfer Logins Task:
Execution failed with the following error: "Cannot apply value null to
property Login: Value cannot be null..".
Task failed: Transfer Logins Task
SSIS package "MigrateLogins.dtsx" finished: Success.