DTS package doesn't fully work in Win XP

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

SQL Server 2000 Forums

Import/Export (DTS) and Replication (2000)

DTS package doesn't fully work in Win XP

Author

Topic

kelvinteh
Starting Member

4 Posts

Posted - 2003-11-12 : 00:06:11

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. Apparently,
the files were successfully generated but there are no data in it. This only
happens in winXP.

I went to this website "Redistributing DTS with your program
(http://www.sqldts.com/default.aspx?225)" and found out that I only need 3 dll
files to execute my dts packages in win98.

The dll files which I registered are dtspkg.dll, dtspump.dll, axscphst.dll.
I'm using MDAC 2.8.

Can someone tell me what is my problem?

Your help is much appreciated.

kelvin

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2003-11-12 : 12:25:14

Does your DTS package execute fine on the WinXP machine using Enterprise Manager? You should start with Enterprise Manager for trouble shooting.

Tara

kelvinteh
Starting Member

4 Posts

Posted - 2003-11-12 : 20:21:16

I had checked from the microsoft website and it says that SQL 2000 Enterprise edition can't be
supported by win xp home/pro.

Does that mean that my application deployed to win xp (client) machines won't work too???

http://www.microsoft.com/sql/evaluation/sysreqs/2000/default.asp

kelvinteh
Starting Member

4 Posts

Posted - 2003-11-13 : 04:05:44

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/guidance.

regards,
kelvin

Stoad
Freaky Yak Linguist

1983 Posts

Posted - 2003-11-13 : 06:20:59

Very interesting but a bit confusing. Maybe you
just "neglected" assigning proper workflows inside
your package and dbf table is populated but at that
time the source table is still empty?

kelvinteh
Starting Member

4 Posts

Posted - 2003-11-13 : 21:29:09

The workflows are working fine. I forgot to mention that the adjustment has to be done in
the SQL Server 2000 Enterprise under Data Transformation Services. All the changes I did
were done in the dts packages properties.

Stoad
Freaky Yak Linguist

1983 Posts

Posted - 2003-11-14 : 03:39:17

Thanks for the useful info.

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources