It appears that I'm not the only one to report this
problem now. I'm hoping that my subject will raise some
attention from people who care (MS). In any case, since
installing XP-SP2, we've had a number of DTS packages
start failing, with no change to the data or DB
structures. If fact, uninstalling SP2 will bring the
packages "back to life", functioning without error.
Everything is being done locally, with NT
Authentication. We have isolated the error to arbitrary
tables that have a Text field defined and used in a
DataPump. If the Text field is removed from the
transformation everything is hunky-dory. With the text
field included, an "Unspecified Error" occurs on line X.
Not fun. Anybody else want to chip in?

When you say "Arbitrary tables" do you mean that not all tables with a TEXT
column exhibt the error behaviour?

Can you give me a repro guaranteed to blow on your box?

This is the first thing MS will ask for. If I can repro then I can see if I
can ask somebody to have a look.

I am on XP SP2 SQL Server 2K SP 3



--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.Konesans.com


"josh" <smith-josh (AT) aramark (DOT) com> wrote

Allan,
Thank you for your offer. Yes, I do mean that not
every table with a text field fails every time... but
sometimes! I am e-mailing you an extremely simplified
version of what I've been working on. Please let me know
if you don't get the files. Just to fill in a bit more
detail. The original DTS package was using a Source
Query that selected from three tables and inserted into a
different database on the same (local) server. The test
files I have created work on just one database, but the
Destination table Owner is different than the source.
Perhaps this has something to do with the error.?? The
exact same mdf, ldf and dts files produce an error on my
XP SP2 box every time, and work beautifully on my XP box
w/o SP2 every time.
Have fun.

Josh mailed me privately with his problem which we have now fixed (or it
was)

The TEXT field has not been initialised so there is an invalid pointer in
there.

If for all TEXT fields you have that have no values do this

UPDATE <table>
SET TEXTFIELD = ''


it should work.

Test it first obviously


--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.konesans.com - Consultancy from the people who know


"Abdul Hafeez" <ahafeez_75 (AT) hotmail (DOT) com> wrote