Problem with SP4 [Crosspost from microsoft.public.sqlserver.dts]

Hello
sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
posting there, I realised that this issue would probably appeal to a much
wider audience than the original newsgroup, hence my crossposting. Thanks for
not flaming me ;-)
Hello,
I am experiencing the following problem with DTS:
on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
the following upgrades:
- Windows SP2 --> no problem with DTS
- SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
small table anymore into an Excel spreadsheet)
I did repeat the test, and the problem was shwon to be consistent. I could
track it down to registering a few dlls of dts to have the machine behaving
correctly again.
Questions:
- did somebody also experienced something similar? If so, is any solution
known?
- does registering the dlls from DTS solve completely the problem? Are there
any related problems with other tools?
With kind regards,
EmmanuelHello,
as a follow-up, I most probably found the origin of the problem: a problem
with the image of the machine which I used to rebuild the PC. Namely, when
using sysprep, some permissions errors did probably occur (this is a know
problem), and using SubInAcl (a tool from Microsoft) did solve the problem.
Not that I'll trust this image anymore, though ...
Regards,
Emmanuel
"Emmanuel" wrote:
> Hello
> sorry, this is a crosspost from microsoft.public.sqlserver.dts. After
> posting there, I realised that this issue would probably appeal to a much
> wider audience than the original newsgroup, hence my crossposting. Thanks for
> not flaming me ;-)
>
> Hello,
> I am experiencing the following problem with DTS:
> on a box running Windows XP SP1 and SQL Server 2000 client tools only, I did
> the following upgrades:
> - Windows SP2 --> no problem with DTS
> - SQL Server SP4 --> DTS no longer works (for instance, I cannot export a
> small table anymore into an Excel spreadsheet)
> I did repeat the test, and the problem was shwon to be consistent. I could
> track it down to registering a few dlls of dts to have the machine behaving
> correctly again.
> Questions:
> - did somebody also experienced something similar? If so, is any solution
> known?
> - does registering the dlls from DTS solve completely the problem? Are there
> any related problems with other tools?
> With kind regards,
> Emmanuel
>