I am trying to design package which would copy all tables and stored procedures from one server to another. It used to be simple task in SQL 2000, there was wizard. However the new wizard does not work...
I wrote SSIS package, but when I execute I get the following error: "Can not apply value null to property Login..."
Any idea It seems to me that this new SQl2005 is not that simple to use like 2000. 2000 was a great product. I am considering to rollback to 2000. Very frustrated with the new one...
Execution of Package failed
Nasyua
Again, what is the protection level of your package
-Jamie
StanoB
No, but you need to have access to the objects that you are trying to transfer.
As you can see above, your connection string for the remote server does not contain a password. You say that somewhere you can see *****. Where can you see that
ProtectionLevel is a property of the package.
-Jamie
Scott Conrad
jcz1
This seems like a security issue. Check the connection string of your connection manager.
And remember - by default, passwords will not get stored in the package. If they do, they will be encrypted. Check the package's protection level.
-Jamie
PierreDSavard
There should be more to the error message than that. Please can you copy the full details It would help to know what task is failing.
-Jamie
Mark q jones
SqlServerName=sql2k501.discountasp.net;UseWindowsAuthentication=False;UserName=SQL2005_194896_jiptravelco_user;
It appears the password is set, since the password proprty shows; *****
This is the local server connection string:
SqlServerName=h001335;UseWindowsAuthentication=True;UserName=Administrator;
Connection Manager type: SMO Server for both
How do I check package protection level
troy anderson
rfreire
The password *** I saw in the properties of the Connection, same like Connection String, just another property.
Is there any update to SQL 2005 I may have missing How to get the latest SQL Server 2005 update
Peter Gummer
Lisha
Error: 0xC002F325 at Transfer Objects, Transfer SQL Server Objects Task: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".
Task failed: Transfer Objects
The package protection level is: EncryptSensitiveWithUserKey
I've verified that my connection passwords are being saved by closing the package and re-opening it, then right-clicking the connection and picking 'edit', then 'test connection'.
I'm guessing I have something misconfigured, but I just dropped the Transfer SQL objects object on the package, configured my source and destination, and set 'DropObjectsFirst', 'CopyData', 'CopyIndexes', 'CopyTriggers', 'CopyPrimaryKeys', and 'CopyForiegnKeys'. Then I selected my objects. However, that caused this error:
Error: 0xC002F363 at Transfer Objects, Transfer SQL Server Objects Task: Table "Clients" does not exist at the source.
Then, I just enabled 'CopyAllTables', 'CopyAllViews', and 'CopyAllStoredProcedures'. That let me get through the 'table doesn't exist' error, and on to the 'cannot apply value null' error.
If it makes a difference, my source database is SQL 2000, my target is SQL 2005.
Thanks for any ideas you might have as to what I'm doing wrong.
clevershark
Has anyone been able to find a solution I get the same error:
[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".
Tihomir Ignatov
AL C,
What is the protection level of your package
-Jamie
andizzle
msolgi
Thanks. Here it is:
Progress: Transfering objects. - 0 percent complete
[Transfer SQL Server Objects Task] Error: Execution failed with the following error: "Cannot apply value null to property Login: Value cannot be null..".
Is there any template I can use to transfer data from my server to the remote hosting server I have tried everything... I am new to this SSIS, I just need a simple way to transfer all data, so my server is updated with the laptop's development database. I do not really have time to study tons of pages. There use to be good DTS wizard in the previous version of SQL Server... It could drop the tables and do it all. This one I can't get to work, so trying to write this package...