Guys, Actually i was move database server virtual to physical and exist 1 job that execute one package... when i ran the job, i've got that: Message Executed as user: SERVER01\SQL. ...sion 9.00.5000.00 for 64-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 14:16:39 Error: 2012-11-19 14:16:40.26 Code: 0xC001000E Source: Description: The connection "" is not found. This error is thrown by Connections collection when the specific connection element is not found. End Error Error: 2012-11-19 14:16:40.54 Code: 0xC001000E Source: DTSSQL Description: The connection "" is not found. This error is thrown by Connections collection when the specific connection element is not found. End Error Error: 2012-11-19 14:16:40.54 Code: 0xC02020EA Source: DTSSQL Log provider "SSIS log provider for SQL Server" Description: The connection manager "" is not found. A component failed to find the connection manager in the Connections collection. End Error Error: 2012-11-19 14:16:40.54 Code: 0xC001000E Source: DTSSQL D... The package execution fa... The step failed. I was look http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/2af470ac-d76d-4162-849f-a5e0411aa053, but i not get sucess :( note: I have not installed SSIS, any problem?

It looks like that the connection manager used for logging to a SQL Server table (Source: DTSSQL Log provider "SSIS log provider for SQL Server) isn't available anymore. Any overrides in the jobstep?Please mark the post as answered if it answers your question | My SSIS Blog: http://microsoft-ssis.blogspot.com | Twitter

SSISJoost, I using Windows Authentication in SSIS connection manager... i was deleted and created.. but its continue... There's your problem right there. Each object in SSIS uses a unique identifying number (SID) that is referenced in the packages XML code. Once you deleted the old connection manager, each object using that connection manager got orphaned. It doesn't matter that you created a new one with the same name. That new connection manager has a new SID and isn't recognized by those other objects. You need to open up each task / item and re-add the connection manager to each task so that they use the SID of the new one. That should fix your issue.MCITP:DBA, MCDBA, MCSA

If your package is corrupted, the best you can do is start over with the original package (you do have a backup copy, right?) and make the changes you need to make from there. Try not to delete the connection manager if you just need to make a change to it. That's better for your sanity than deleting and recreating it. BTW, deleting and recreating the connection manager will not resolve the problem if you aren't opening up every File System Task, T-SQL Task, Data Flow Source / Destination and clicking through all the tabs to make sure they reconnect. Pin open your error list and go through each task object one by one. It will tell you when you've forgotten to fix something.MCITP:DBA, MCDBA, MCSA

Did you check the config? (Right click the white space in the work area). Sometimes you can just refresh or recreate that and fix the problem. R, J

Did you check the config? (Right click the white space in the work area). Sometimes you can just refresh or recreate that and fix the problem. R, J The config file is the other place the issue could be hiding. You really need to start making backups of your packages. It's the only way to make sure you have a good copy if you screw something up.MCITP:DBA, MCDBA, MCSA

Which connection manager were you deleting? THe source or destination?MCITP:DBA, MCDBA, MCSA

If you create a new connection to the same source and a new connection to the same destination, does that solve your problem?R, J

Open the Source - Query, click through all the screens and then close it by hitting OK. Do the same with the File Destination object. If you use config files, open the config file (from within the package), deselect all connection managers. Close the windows with the OK button (Do NOT use Cancel or the X). Then reopen the config file manager (from within the package) and re-select your connection managers, adding them back in from scratch. If you have any objects on the Control Flow, or any other Data Flow Tasks, you need to open up each object and do the same thing as step 1. When you're done. Save the package. Check to see if you have any expressions that might use the connection managers or any variables that mess with the connection strings. If not, you should be able to close and reopen the package without error. And if all else fails, you need to recreate the package from scratch because the package may be so corrupted at this point that there's no saving it.MCITP:DBA, MCDBA, MCSA

note: I have not installed SSIS, any problem? I just caught this last bit. That actually might be part of your problem. If you don't have SSIS installed locally, then Visual Studio might not be reading the package correctly. I'm assuming you have VS installed, yes? Which version / edition?MCITP:DBA, MCDBA, MCSA

not, i done that... i've no idea what i do now... the big problem at my work with that bcz need import daily and nothing... do you have teamviewer? It seems to me that you're not understanding what steps I'm trying to walk you through. You're responding to this thread way to quickly to have done anything that I've asked you to do. At this point, I suggest you have the boss hire a local consultant to come in and fix the package for you, and maybe give you a little training on how to build and troubleshoot SSIS packages.MCITP:DBA, MCDBA, MCSA

I'm not asking you to execute stuff. I'm asking you to fix the metadata on all objects. If you've already done that and it's still failing, you need to either hire an expert to come in and fix the issue for you or recreate the package from scratch.MCITP:DBA, MCDBA, MCSA