Attempted to read or write protected memory

One of the packages we've created a while ago is now, suddenly, giving us a strange error:
There was an error displaying the layout.
Additional Information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (msddsp)
When I click on the help icon, I get:
Event ID: DDSErrorDeserializeDiagram
Source: Microsoft.DataTransformationServices.Design.SR
I should note that I am using custom components, none of which have been changed since the last time this package worked.
When I click ok, all my components have the information icon. No names are displayed (although all are accessible from the properties window) ... When I double click them, I still get the custom UI for my component, and all the properties are there and correct.
Other packages using the same tools work fine.
Any ideas/suggestions?
Thanks,
Steve
I am having a similar problem - did anyone find a solution to this?

Attempted to read or write protected memory

One of the packages we've created a while ago is now, suddenly, giving us a strange error:
There was an error displaying the layout.
Additional Information: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (msddsp)
When I click on the help icon, I get:
Event ID: DDSErrorDeserializeDiagram
Source: Microsoft.DataTransformationServices.Design.SR
I should note that I am using custom components, none of which have been changed since the last time this package worked.
When I click ok, all my components have the information icon. No names are displayed (although all are accessible from the properties window) ... When I double click them, I still get the custom UI for my component, and all the properties are there and correct.
Other packages using the same tools work fine.
Any ideas/suggestions?
Thanks,
SteveI am having a similar problem - did anyone find a solution to this?

Attempt to fetch logical page error

Hello,
I have recently moved some packages I had been working on from my development to production environment. Having come across many configuration related errors, I believed my latest one to be of this type. However I'm recieving one I've never seen before:

"Attempt to fetch logical page (1:95152) in database 8 failed. It belongs to allocation unit 72057594043301888 not to 72057594045661184.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly"

This package works fine on the development db, however I don't even know where to start tracking this issue down. Any thoughts?

Thanks,
Adrian CrawfordI just googled that message and got a link to an article by Bob Dorr who works for PSS supporting SQL Server.
In other words - I suspect this is a SQL Server engine problem, not a SSIS one.

-Jamie|||This sounds like you have a database problem. If it is SQL Server then you should probably post this to the relational engine forum. Again if this is SQL Server, you might try running DBCC on the database to see if that shows any problems.

Matt|||Thanks for the responses, I'll see if anyone knows about this in the database engine forum.
Adrian

Attempt to fetch logical page error

Hello,
I have recently moved some dts packages I had been working on from my development(sql2k5) to production environment(sql2k5). Having come across many configuration related errors, I believed my latest one to be of this type at first. However I'm recieving one I've never seen before:

"Attempt to fetch logical page (1:95152) in database 8 failed. It belongs to allocation unit 72057594043301888 not to 72057594045661184.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly"

This package works fine on the development db, however I don't even know where to start tracking this issue down. Any thoughts? I have tried the SSIS forum and they believe it to be a db engine issue.

Thanks,
Adrian CrawfordThere was a low-level problem with one of my tables involved in the dts on production. I found the specific table by running DBCC checkdb. At that point I dropped and recreated the table which has fixed the problem.
Adrian