Package 'Microsoft SQL Management Studio Package' failed to load

i am working on sql server 2005. i removed dotnet framework 2.0 from my
system and again i installed it . Now i am getting a message Package 'Microsoft SQL Management Studio Package' failed to load , if i click
on ok it is closing.
so please give a solution and it is a trail version of 180 from
microsoft technologies

Quote:

Originally Posted by chandrasekharallu

i am working on sql server 2005. i removed dotnet framework 2.0 from my
system and again i installed it . Now i am getting a message Package 'Microsoft SQL Management Studio Package' failed to load , if i click
on ok it is closing.
so please give a solution and it is a trail version of 180 from
microsoft technologies

It wasn't a wise decision to uninstall .NET 2.0, as SQL Server is deeply integrated with .NET 2.0.

Try reinstalling SQL Server, but I'm not sure if it will correctly identify your trial period.

Package failure still causing partial load

I have a package that is failing because of a truncation error. Now, by default (and I leave this for ALL my packages) if one row fails processing the entire package should fail and nothing gets loaded into db. But instead I am actually getting a partial db load.

I have confirmed the "Rows per btach" value (blank) and the "Maximum insert commit size" value (0) for the OLE DB Destination Editor so I have no idea what is going on. Are there any other properties I should be checking?

Thanks.

Jason

Why are you surprised that there is a partial load? You'll have to set MICS to equal to or greater than the number of rows coming into the source to have it such that if one row is bad, the whole batch is aborted.

The settings you have now are likely committing each row as they are inserted.|||According to the documentation, a "value of 0 indicates that all data is committed in a single batch after all rows have been processed". This, to me, tells me that all rows will be written or none. Since I am getting a truncation error, should I not be getting zero rows written?|||Well, I'm not so sure that SQL Server can accept an arbitrarily large bulk load. That is, I believe there's a limit to the size of the batch, and if it's exceeded, it will have to issue a commit or fail. I'm not sure.

You could redirect error rows out of the OLE DB command and try to see where that error occurs (row number or something).|||

Thanks for the responses Phil.

I know exactly where the error is happening. Just that in the past (with other packages) the execution loaded everything or nothing. (No matter the number of rows in the source.) It is just that the behavior for this package is not what I am used to and I cannot figure out why it is doing a partial load when the settings (as far as I can tell) are telling it not to.

- Jason

|||

To be honest, I have been playing with those 2 properties in the OLE DB Destination, so I can get bigger batches but I only can get around 9K-10K rows per commit as maximum. Not sure if SSIS or Bulk_insert look at the available resources and decided what value to use. I have no gotten the time to dig into that.

|||

Rafael Salas wrote:

To be honest, I have been playing with those 2 properties in the OLE DB Destination, so I can get bigger batches but I only can get around 9K-10K rows per commit as maximum. Not sure if SSIS or Bulk_insert look at the available resources and decided what value to use. I have no gotten the time to dig into that.

I think that SQL Server can only handle a batch size of 256 MB.

http://msdn2.microsoft.com/en-us/library/ms143432.aspx

Package executes on test database but not in production database

hi!

I am able to run the package successfuly in test database. but not in production database. It throughs up error saying

Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted.
Description: Failed to open package file "D:\\TAHOE\\APPS\\SSISPackages\\Integration Services Packages\\ArchiveMain.dtsx" due to error 0x80070015 "The device is not ready.". This happens when loading a package and the file cannot be opened or loaded c
orrectly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.
End Error
Could not load package "D:\\TAHOE\\APPS\\SSISPackages\\Integration Services Packages\\ArchiveMain.dtsx" because of error 0xC0011002.
Description: Failed to open package file "D:\\TAHOE\\APPS\\SSISPackages\\Integration Services Packages\\ArchiveMain.dtsx" due to error 0x80070015 "The device is not ready.". This happens when loading a package and the file cannot be opened or loaded corr
ectly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format.

what is the problem here....

JAs

Has somebody dealt with this error before. If yes please help me out.

thanks,

Ja

|||what are you using to execute the package in the production db? code? dtexec? sql server agent?|||

i solved the problem. Anyway i am executing through dtexec. I trying to execute the package with different Databases. One with my test and other with production.The Test database was in my own machine. where as the production was pointing at remote server.So the package was in my machines folder path and worked correctly. when i tried to execute with the production database from my machine. It threw up error saying cannot find the pacakge path cos it was trying to scearch my my production servers machine.

Thanks for your reply,

jas

Package Configuration

Hello,

I'm developing some packages in SSIS and I need to implement a configuration file to load the server's connections and other parameters, so I can use this same connection for all packages.

Have anyone a step by step to perform this configuration ?

I exported a Connection Manager to a .dtsConfig file, but I don't know how to use this config file.

Any help is welcome !

Thanks,

Guber

As long as your package knows about the configuration (which it will do because that is where you created it) then it should just work!

Try editing the config file to contain some nonsensical value and run your package again. If it doesn't do what it is supposed to then you know the file is being used.

-Jamie