Hi,

I have a dts package in my VB application which works fine in WIN98,
but when I tried to run it in WIN XP Home, my dts package doesn't fully
work - only certain parts and the worst thing is that it doesn't give me
any error.

I'm supposed to use my dts package to generate some dbf files. The actual
problem is all my dbf files are properly generated except for 1 file.
This only happens in XP.

The dll files which I registered on both OS are dtspkg.dll, dtspump.dll,
axscphst.dll.

Can someone tell me what is my problem? Are there suppose to be any more dlls
to be registered?

Your help is much appreciated.

kelvin

There are more dlls and you can find them here

Redistributing DTS with your program
(http://www.sqldts.com/default.aspx?225)

--

Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"kelvin" <kelvinteh (AT) yahoo (DOT) com> wrote

I went to the website mentioned before.

I've registered the 3 dlls (dtspkg.dll, dtspump.dll, axscphst.dll) in
my win98
and it works fine. So base on this fact, I imported these 3 dlls to my
winXP home and registered them but things don't turn out to what I
want it to be.

In my Visual Studio, I only made references to:-

1. Microsoft DTSDataPump Scripting Object Library(dtspump.dll)
2. Microsoft DTSDataPackage Object Library (dtspkg.dll)

I couldn't find any reference for axscphst.dll. Is this the reason why
it failed in winXP even though I did register these 3 dlls in win XP?

I found the solution to this problem.

It's not the dll that's missing.

It's actually the priority of task in the OS.

I changed the DTS execution parameters.

1st change:
I limit the maximum no of task executed in parallel to lower than 2.
Originally
it was 4.

2nd change:
I set the priority class of the DTS package to high. Originally it was
normal.

Once I have done these 2 changes my results were no longer weird. All
my data
in dbf files are properly populated.

I suppose that the OS is concurrently executing too many tasks hence
may have 'neglected' the execution packages, maybe. This is the reason
I could
think of.

Hopefully this helps those who are encountering the same problems as I
did.

Thanks to those who have tried to post your opinions.

regards,
kelvin