Re: 2005 SSIS issue
- From: "moondaddy" <moondaddy@xxxxxxxxxxxxx>
- Date: Sat, 19 Nov 2005 02:48:02 -0600
Getting no where fast. I found a post on Google where a company had a
similar error. change changed the security from sql to windows on the
server and then things worked for them. I did that and corrupted the server
because the databases (master, temp, etc.) where probably still expecting
sql - sa. So I uninstalled sql server (not SSIS, etc.) and re-installed it
and this time used windows security. (don't know if this introduced
corruption) Then I created 2 new databases on sql server 2005; test1 and
test2. in test1 I created a table called customers and 2 columns, name and
id. then I went into SSIS, created a project and package, and a Transfer
SQL Server Objects Task control.
At least this time it ran... but that's because nothing was selected to
import (but at least it ran right?). Next on only one property I selected
copy all tables and after it hung for about 3 minutes I got the following
test in the output window:
SSIS package "Package.dtsx" starting.
Error: 0xC002F325 at Transfer SQL Server Objects Task, Transfer SQL Server
Objects Task: Execution failed with the following error: "ERROR :
errorCode=-1071636471 description=An OLE DB error has occurred. Error code:
0x80040E37.
An OLE DB record is available. Source: "Microsoft SQL Native Client"
Hresult: 0x80040E37 Description: "Invalid object name 'dbo.Customers'.".
helpFile=dtsmsg.rll helpContext=0
idofInterfaceWithError={8BDFE893-E9D8-4D23-9739-DA807BCDC2AC}".
Task failed: Transfer SQL Server Objects Task
SSIS package "Package.dtsx" finished: Success.
so in short it complained about "Invalid object name 'dbo.Customers'.".
I hope there's some good (helpful) advise out there....
Thanks.
--
moondaddy@xxxxxxxxxxxxx
"Peter Yang [MSFT]" <petery@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:NVqzXwB7FHA.3580@xxxxxxxxxxxxxxxxxxxxxxxx
> Hello Moon,
>
> Based on my experience, this issue could occur if the logins in SQL 2005
> server and original SQL 2000 server is different.
>
> My suggestion is that you transfer logins between the servers before you
> try to import datqabase again.
>
> SQL 2K transfer login article does work for SQL2005 since sp_addLogin is
> still supported.
>
> HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
> (246133)
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;246133
>
> TransferLogins task in SSIS (DTS) to no longer transfers the SQL
> Passwords.
> From the BOL, the SQL login is transferred, but a random password is
> assigned. This requires the DBA to reset the password for each SQL users.
>
> Best Regards,
>
> Peter Yang
> MCSE2000/2003, MCSA, MCDBA
> Microsoft Online Partner Support
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================
>
>
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> --------------------
> | From: "moondaddy" <moondaddy@xxxxxxxxxxxxx>
> | Subject: 2005 SSIS issue
> | Date: Fri, 18 Nov 2005 00:05:43 -0600
> | Lines: 25
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2900.2670
> | X-RFC2646: Format=Flowed; Original
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
> | Message-ID: <#QwgbYA7FHA.444@xxxxxxxxxxxxxxxxxxxx>
> | Newsgroups: microsoft.public.sqlserver.dts
> | NNTP-Posting-Host: cpe-24-175-64-176.houston.res.rr.com 24.175.64.176
> | Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
> | Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.dts:62091
> | X-Tomcat-NG: microsoft.public.sqlserver.dts
> |
> | I'm new to SSIS and have not been able to import a database from sol 2k
> onto
> | 2005, however, I did manage to restore a backup from 2k into 2005. Now
> I'm
> | practicing creating a SSIS package to copy all objects and data from
> this
> db
> | in 2005 (db1) into a new db in 2005 (db2).
> |
> | I added a Transfer SQL Server Objects Task into the Control flow window
> and
> | set the appropriate source and destination databases etc. I double
> clicked
> | on it and set most of the props to true and everything looked pretty
> good.
> | I clicked on OK so I was back at the Transfer SQL Server Objects Task.
> Then
> | I right clicked and selected Execute Task. it only ran about 1 second
> and
> | in the execution results window I saw the error:
> |
> | [Transfer SQL Server Objects Task] Error: Execution failed with the
> | following error: "Cannot apply value null to property Login: Value
> cannot
> be
> | null..".
> |
> | Where can I find this property called 'Login'?
> |
> | Is there anything else you can think of that I need to do to make this
> run?
> |
> | Thanks.
> | --
> | moondaddy@xxxxxxxxxxxxx
> |
> |
> |
>
.
- Follow-Ups:
- Re: 2005 SSIS issue
- From: Peter Yang [MSFT]
- Re: 2005 SSIS issue
- References:
- 2005 SSIS issue
- From: moondaddy
- RE: 2005 SSIS issue
- From: Peter Yang [MSFT]
- 2005 SSIS issue
- Prev by Date: Re: 2005 SSIS issue
- Next by Date: Re: Send Mail Task iteratively in DTS package
- Previous by thread: Re: 2005 SSIS issue
- Next by thread: Re: 2005 SSIS issue
- Index(es):
Relevant Pages
|
