Script failed for User / User.UserType: NoLogin is not a valid option for SQL Server 2005
Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance
I have converted a SQL Server 2000 DTS package to an SSIS one for SQL
Server 2005. When I execute the package that has CopyDatabaseUsers set
to true, I get the following errors that cause the package to stop:
[Transfer SQL Server Objects Task] Error: Execution failed with the
following error: "Script failed for User 'xyzUser'. ".
[Transfer SQL Server Objects Task] Error: Execution failed with the
following error: "User.UserType: NoLogin is not a valid option for SQL
Server 2005."
The SSIS package is copying from a 2005 database to a 2000 one. The
user that is failing appears to have been created with the WITHOUT
LOGIN clause. Looking up User.UserType (
http://msdn2.microsoft.com/en-
us/library/microsoft.sqlserver.management.smo.usertype.aspx) I see
that NoLogin is an enumerator of the type. How come it isn't valid for
2005? How do I work around this?
Many thanks.
.
Relevant Pages
- RE: Could not open global shared memory to communicate w/ performa
... Ah, SQL Server Destination. ... I NEVER use the SQL Server Destination in SSIS design. ... a package in BIDS (business Intelligence Development Studio, ... (microsoft.public.sqlserver.dts) - Re: Trying to get a SSIS Import wizard package to actually schedule and work.
... would like to explain that we are allowed to re-use the SSIS package ... files initially created by this package exit on the system. ... you can also attempt to use the "Transfer SQL Server Objects ... (microsoft.public.sqlserver.dts) - Error attempting to execute a DTS package from an ADP
... "The Microsoft Jet database engine could not find the object '<my UNC ... I can run the package fine from there. ... -I tried restarting the SQL Server agent using the same user ID as the ... The execution of the following DTS Package failed: ... (microsoft.public.sqlserver.dts) - Re: how to del/modify SSIS
... Use the Business Intelligence Development Studio to create an SSIS type project. ... From there you can ad your package directly from SQL Server. ... However, the recommended way to work with packages is to have them in project files and them deploy them as you wish, so consider using SSMS to export the package to file and add that file to your SSIS project. ... (microsoft.public.sqlserver.server) - Re: Execute SQL Task Error Capturing
... Execute package WithEvents and capture the OnError events. ... available during the current package execution. ... Log errors to SQL Server, package level option. ... (microsoft.public.sqlserver.dts) |
|