Package Wont Open

I have just created a package to import data from excel files, and perform some simple sql statements. I saved the package, and when I try to re-open it, I get the following error:

"Error Source: Microsoft OLE DB Provider for SQL Server
Error Description: [DBNETLIB][ConnectionOpen (Connect()).] SQL Server does not exist or access denied."

And after I hit th "OK" button, I get the next error msg:

"The selected package cannot be opened. The DTS Designer has been closed"

Is my package completely lost? Can I open it elsewhere, or by changing some properties somewhere? Also, is there something I can do to avoid this in the future?! I hope all my work isn't lost ...

Any help would be greatly appreciated!

BrianClose Enterprise Manager, reopen it, and see if you can read the DTS package. You can still ping the server can't you?|||Thanks for the quick response.

I closed and re-opened enterprise manager, to no avail. I'm working with my localhost and there is no problem pinging. Everything else seems fine, just can't open this package. Any other thoughts?|||It sounds like it got corrupted somehow. I've never actually had this happen. Been doing DTS packages a long time. If you had saved it previously, right-click on the package and look at versions. See if you can look at any of the previous versions.|||I have no idea what's going on, craziness I say. I only had one version when I checked. I've gone through creating these packages all different ways. They save no problem, but I can't re-open them. Any other thoughts? Thanks!sql

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 Configuration

I have created a package configuration to read the connectionstring for the oledb connection manager.

Saved the file as Environment.dtsConfig in the same directory as the other packages.

Do the packages refer to the configuration file automatically?

Does it make a difference if I use the dtexec to start the ssis packages since there is now a configuration file?

Thanks

Yes and no.

You can check what Configurations are "bound" to a package, open the package and then go to the Configurations menu option in the designer. The first dialog shows you all configurations that will be applied to that package.

There is no difference in the way you use DTEXEC now that the package has a configuration.

Package changes made and saved revert to prior state when package closed and re-opened

I copied and added an existing package as a new package to a project and have been having trouble with settings reverting to those for the original package after I modify and save the changes for the new package. Sometimes happens with the save itself, other times it happens when I close and re-open the package. Most cases are with connections that revert back to the original file reference, but there are also control flow and data flow elements that keep reverting back to either settings from the original package or defaults that result in the re-opened package being in error. Not sure how to get around this issue short of developing the new package from scratch which I'd rather not do since it is fairly complex. Any help anyone can provide is appreciated. Thanks.If I were you I'll try saving a copy of that problematic package in another folder. Open the original problematic package, and then do a save.

Then using a file-comparison tool like Winmerge, text-compare the original and copy packages. If they remain the same, perhaps something is totally wrong with your BI Studio.

Another thing to check is if those "reverting" properties are saved in an external XML configuration file. It is possible that for some reason that dtsconfig file has been set to readonly, hence your package picking up the original values over and over again.

Goodluck.|||

Thank you. The external XML configuration file was not set as readonly. I had a dtsconfig file that was common to all packages which a co-worker suggested may be the cause of my problem, but I'm not so sure that is the case. He also suggested disabling the use of a configuration file for the package I was having a problem with which I did, but I still have the issue of connection strings for connection definitions reverting to their original setting for the path and file name. This isn't too big a problem because at execution time I pass the actual path and file name in a user variable, but at definition time I have to always reset the path/filename.

I haven't tried the comparison option yet, but if disabling the configuration file doesn't solve my run time issues, I'll try that next. Thanks again.

|||Jeff, when you copy a package, you need to generate a new GUID for it. On the background of the control-flow, select properties. Then underneath the Identification section, select the Generate New ID option in the ID field. This should solve your problem.|||

Phil, Thank you for your help. I reset the package id as you suggested and also re-enabled package configurations and created a package specific configuration file. That seems to have solved the problem of data flow component definitions reverting to default values. However, I am still seeing some of the issues I had before - the file specification for a connection definition keeps reverting to that for the package from which the new package was copied. Am I misinterpreting how the connection definitions from one copy of a package to another work? Are they global to the two packages or are they independent copies? I thought that by creating a configuration file specific to the new package that the connection definitions would be independent of the source package.

I also get a message each time I re-open the new package that the connection string for the database connection and database datasource are not identical and need to be synchronized. I select OK to do the synchronization, but it doesn't seem to take.

Thanks again for your help. Any further insight you can provide is appreciated.

|||

Jeff-B wrote:

Phil, Thank you for your help. I reset the package id as you suggested and also re-enabled package configurations and created a package specific configuration file. That seems to have solved the problem of data flow component definitions reverting to default values. However, I am still seeing some of the issues I had before - the file specification for a connection definition keeps reverting to that for the package from which the new package was copied. Am I misinterpreting how the connection definitions from one copy of a package to another work? Are they global to the two packages or are they independent copies? I thought that by creating a configuration file specific to the new package that the connection definitions would be independent of the source package.

I also get a message each time I re-open the new package that the connection string for the database connection and database datasource are not identical and need to be synchronized. I select OK to do the synchronization, but it doesn't seem to take.

Thanks again for your help. Any further insight you can provide is appreciated.

Between the two copied packages, are you using different package config files? If you are sharing the same config file, then you'll run into the scenario you are describing.|||I had been using the same config file, but I created a new, separate config file for the new package assuming that was what I needed to do to make package specific changes to the connection definitions. When I created the new config file, I selected all the elements shown to be available (variables, connection definitions, etc.) and then began to make changes to connection defintions, but the changes don't seem to take. As soon as I do a save, the file specifications for connections revert to the settings for the original source package.|||Resolved most of my remaining issues by not using a config file. I realize that is not a proper solution, but for now it works. I need some additional work with config files before using them in my project.