sql server dts: Another #*%@ DTS bug and a couple of hours of development time down
the toilet:

1. Made significant changes to pkg. Ran successfully for test.

2. Saved package.

3. Tried to open package to run it but got "catastrophic failure"
message before the package was even displayed, and "the selected
package cannot be opened. The DTS Designer has been closed".

4. Utter string of obscenities, rage derived from powerlessness.

Are you aware that you may still be able to recover the original version?

Right-click on the package and select "versions"... the panel that comes up
is easy to use.

You may be familiar with this but I thought I'd mention it just in case you
weren't and before you got frustrated and deleted all versions of the
package.

[quoted text, click to view]

[quoted text, click to view]

Right. Strangely enough, it is only the latest version, containing the
changes, that is corrupted.

[quoted text, click to view]

What did you change, anything using Disconnected Edit for example? You can
do some nasty things this way.


--
Darren Green
http://www.sqldts.com

[quoted text, click to view]

What difference does it make? If I did, do you have a solution?

I almost always have to change things using DE because if you use the
front door editors Designer frequently chokes; it often can't parse a
perfectly good SELECT statement in a data pump, for example. However,
I didn't do anything that I don't do all the time, and I don't believe
that I changed anything that could have caused a problem.

But let met be clear- there is regardless NO excuse, NO EXCUSE
WHATEVER, for a software development tool to allow you to make a
change and save it in such a way that the document (in this case the
dts package) can never be opened again and edited (and fixed if there
is indeed something wrong with it). Imagine a programming language
interpreter that corrupts the source code file irretrievably if it has
a bug in it. That is not just an analogy, that is literally what
happened (assuming that I changed something in DE that caused this
problem).