package path referenced an object that cannot be found

I am running Final Relase of 2005 version 9.00.1399. I built an Integration Services package saved it closed up, came in the next day opened the project and I get 46 Warnings and the message on all of them is similar:

"Warning loading Package.dtsx: The package path referenced an object that cannot be found: "\Package\Truncate Temp Table.Properties[Connection]". This occurs when an attempt is made to resolve a package path to an object that cannot be found."

The problem is that I had an Execute SQL Task that I named Truncate Temp Table for a while, but subsequently changed the name before I saved it at the end of the day. So the task called Truncate Temp Table doesn't exist anymore and it is still trying to find its properties. I have tried running Clean, Build, and Rebuild.

How do I get the package path to refresh with the current package design?

Thanks!

Hi,

If you got this solved I'd love to know how you did it! I am having the same problem!

Thanks,

PMR

|||

Hi..

Try regenerate the package id of your SSIS package, and save it...

ref : http://support.microsoft.com/?kbid=906564

|||

Hi KamiNoChikara,

I don't know if this will help or not, but version 9.00.1399 is not the latest version. SP1 addressed a host of SSIS issues, and is available at http://www.microsoft.com/downloads/details.aspx?FamilyID=cb6c71ea-d649-47ff-9176-e7cac58fd4bc&DisplayLang=en.

Hope this helps,
Andy

|||

KamiNoChikara wrote:

I am running Final Relase of 2005 version 9.00.1399. I built an Integration Services package saved it closed up, came in the next day opened the project and I get 46 Warnings and the message on all of them is similar:

"Warning loading Package.dtsx: The package path referenced an object that cannot be found: "\Package\Truncate Temp Table.Properties[Connection]". This occurs when an attempt is made to resolve a package path to an object that cannot be found."

The problem is that I had an Execute SQL Task that I named Truncate Temp Table for a while, but subsequently changed the name before I saved it at the end of the day. So the task called Truncate Temp Table doesn't exist anymore and it is still trying to find its properties. I have tried running Clean, Build, and Rebuild.

How do I get the package path to refresh with the current package design?

Thanks!

My guess is that you have something external to the package that is referencing this path. Are you using configurations by any chance?

-Jamie

package path referenced an object that cannot be found

I am running Final Relase of 2005 version 9.00.1399. I built an Integration Services package saved it closed up, came in the next day opened the project and I get 46 Warnings and the message on all of them is similar:

"Warning loading Package.dtsx: The package path referenced an object that cannot be found: "\Package\Truncate Temp Table.Properties[Connection]". This occurs when an attempt is made to resolve a package path to an object that cannot be found."

The problem is that I had an Execute SQL Task that I named Truncate Temp Table for a while, but subsequently changed the name before I saved it at the end of the day. So the task called Truncate Temp Table doesn't exist anymore and it is still trying to find its properties. I have tried running Clean, Build, and Rebuild.

How do I get the package path to refresh with the current package design?

Thanks!

Hi,

If you got this solved I'd love to know how you did it! I am having the same problem!

Thanks,

PMR

|||

Hi..

Try regenerate the package id of your SSIS package, and save it...

ref : http://support.microsoft.com/?kbid=906564

|||

Hi KamiNoChikara,

I don't know if this will help or not, but version 9.00.1399 is not the latest version. SP1 addressed a host of SSIS issues, and is available at http://www.microsoft.com/downloads/details.aspx?FamilyID=cb6c71ea-d649-47ff-9176-e7cac58fd4bc&DisplayLang=en.

Hope this helps,
Andy

|||

KamiNoChikara wrote:

I am running Final Relase of 2005 version 9.00.1399. I built an Integration Services package saved it closed up, came in the next day opened the project and I get 46 Warnings and the message on all of them is similar:

"Warning loading Package.dtsx: The package path referenced an object that cannot be found: "\Package\Truncate Temp Table.Properties[Connection]". This occurs when an attempt is made to resolve a package path to an object that cannot be found."

The problem is that I had an Execute SQL Task that I named Truncate Temp Table for a while, but subsequently changed the name before I saved it at the end of the day. So the task called Truncate Temp Table doesn't exist anymore and it is still trying to find its properties. I have tried running Clean, Build, and Rebuild.

How do I get the package path to refresh with the current package design?

Thanks!

My guess is that you have something external to the package that is referencing this path. Are you using configurations by any chance?

-Jamie

Package execution failed but no error (SQL2005)

I made an Integration Services Package which runs well if I start it manually
(also from SQL server Management Studio).
Now I have created a new job for the SQL server agent which need to run my
package.
After starting the job, it ends after a few seconds:
"The package execution failed" is the only message there is.
I assume it has something to do with security but for the test I am logged
in as a domain administrator which has all rights to all databases.
Can someone give some clues about how to solve this?
Thanks
Two possibilities come to my mind:
1- SQL Server run under its own account; so you should check the permission
for this account on both Windows and SQL-Server side (for example, does this
account has an explicit access to the database?)
2- You are using things like a network drive (Z:\Repertory\...) instead of
an UNC file name (\\Server\Repertory\...) which are specific to the login
account and unknown to other accounts.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Frans" <Frans@.discussions.microsoft.com> wrote in message
news:6EBD9795-92BA-435C-BCC7-CFEBDC6EAF2F@.microsoft.com...
>I made an Integration Services Package which runs well if I start it
>manually
> (also from SQL server Management Studio).
> Now I have created a new job for the SQL server agent which need to run my
> package.
> After starting the job, it ends after a few seconds:
> "The package execution failed" is the only message there is.
> I assume it has something to do with security but for the test I am logged
> in as a domain administrator which has all rights to all databases.
> Can someone give some clues about how to solve this?
> Thanks

Package execution failed but no error (SQL2005)

I made an Integration Services Package which runs well if I start it manuall
y
(also from SQL server Management Studio).
Now I have created a new job for the SQL server agent which need to run my
package.
After starting the job, it ends after a few seconds:
"The package execution failed" is the only message there is.
I assume it has something to do with security but for the test I am logged
in as a domain administrator which has all rights to all databases.
Can someone give some clues about how to solve this?
ThanksTwo possibilities come to my mind:
1- SQL Server run under its own account; so you should check the permission
for this account on both Windows and SQL-Server side (for example, does this
account has an explicit access to the database?)
2- You are using things like a network drive (Z:\Repertory\...) instead of
an UNC file name (\\Server\Repertory\...) which are specific to the login
account and unknown to other accounts.
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)
"Frans" <Frans@.discussions.microsoft.com> wrote in message
news:6EBD9795-92BA-435C-BCC7-CFEBDC6EAF2F@.microsoft.com...
>I made an Integration Services Package which runs well if I start it
>manually
> (also from SQL server Management Studio).
> Now I have created a new job for the SQL server agent which need to run my
> package.
> After starting the job, it ends after a few seconds:
> "The package execution failed" is the only message there is.
> I assume it has something to do with security but for the test I am logged
> in as a domain administrator which has all rights to all databases.
> Can someone give some clues about how to solve this?
> Thanks

Package executing error

I wrote package using Integration Services and tried execute it on Visual Studio 2003 (Visual Basic). Package was loaded, but execute method has failed without any error messages. When I tried to run it on Visual Studio 2005, execution was successful.

Codes:

Dim App As DTSLib.IDTSApplication90 = New DTSLib.Application

Dim p As DTSLib.IDTSPackage90 = App.LoadPackage("d:\temp\Package.dtsx", True, Nothing)

p.Execute()

What can be the reason of the trouble?

Thanks,

Alexander

Only one .NET runtime can live in one process. Visual Studio 2003 uses .NET 1.1, and SSIS requires .NET 2.0 - so SSIS fails if the process has already loaded .NET 1.1.

You can use config file to change the .NET version used by applications developed with .NET 1.1 and force them to use .NET 2.0, but it will break Visual Studio debugging.

So it is highly recommended to use Visual Studio 2005. In Visual Studio 2005 you can also use managed API for SSIS - in Microsoft.SqlServer.ManagedDTS assembly, which is more convinient than using interop from DTSLib.