I am having several problems. I first started to get a problem when
applying servvice pack 3a to my existing sql server. When I was trying
to execute activeX scripts it got the error "ActiveX scripting was not
able to initialize the script execution engine". I figured the service
packed screwed it up. I followed the directions on sqldts.com to
reregister all the listed dts .dlls and reinstalled windows scripting
host 5.6. And I still had the problem. Next I figure I would do a
clean install of Microsoft Sql Server. I ran the uninstall from the
Add/Remove programs. Reinstalled it. Now when I go into old dts
packages they are all blank. If i create a new one and drag and drop a
dts icon from the left side it gives the error "File Not registered".
Again, I figure I'd try to unstil sql server with a clean uninstall and
followed online msdn to remove it completely including the registeries.
I reinstalled everything. and I still had the problem. I found on
sqldts.com all of the files needed to be registered on the machine and
needed to be in the resource directly. I have registered every single
dts file, made sure every file is needed for dts, but I still have NO
LUCK =(. I ran filemon to see what registery it might fail on when I
open an existing dts package and found it failed numerous times on
trying to find a file called custtasks.tlb. I did reregister the
custtask.dll before I did this and it does find the custtask.dll in
filemon. I googled custtask.tlb and have no clue what it is for and
nothing on google boards talk about it or even on just normal
google.com. So I don't knwo if this is the reason for the dts packages
being blank or which registery is missing/screwed up. Please can
someone help me figure out this problem? Again, I have reregistered
all the dts pkg files needed and that isn't the problem.

Thanks,

David

David,

You have left a ton-o-questions here - I wasn't positive which version
you were on so i searched and found that it seems that sql 2000 is on
sp4 now?

http://blogs.x2line.com/al/archive/2005/05/06/945.aspx

Another side question was - are these DTS packages stored as .dts
files? When you reinstalled did you apply the sp3a immediately or after
you tried to open a .dts?

Are you sure you were using the official SQL2000 enterprise / developer
or possible using desktop edition mistakenly - somewhat difficult to
tell what is on the box in the first place; maybe that's all known and
standard - just spare thoughts.

Cheers
http://rickhathaway.blogspot.com/

I did a system restore to two days previous and I was able to fix
everything but one problem. I fixed it all to this point. I can see
dts packages now. I am now getting the error message:
""ActiveX scripting was not able to initialize the script execution
engine"

I reregistered all the .dll the link below lists, but I still can't
execute AxtiveX Scripts from dts packages.

http://www.sqldts.com/default.aspx?224

This was the original problem that led me to uninstall sqlserver and
reinstall it. I

David



Slice wrote:
[..]

I did a system restore to two days previous and I was able to fix
everything but one problem. I fixed it all to this point. I can see
dts packages now. I am now getting the error message:
""ActiveX scripting was not able to initialize the script execution
engine"

I reregistered all the .dll the link below lists, but I still can't
execute AxtiveX Scripts from dts packages.

http://www.sqldts.com/default.aspx?224

This was the original problem that led me to uninstall sqlserver and
reinstall it. I

David

I just wrote a long message the dang thing timedout. So here is the
shorter version. I just ran a system restore and noticed when running
enterprise manager I was getting errors that .rlls were missing, which
they were. So what I did was reinstalled the the Client tools and I
was able to see the dts packages again. Everything is working perfect
now, but I am back to my original problem. I get the error ""ActiveX
scripting was not able to initialize the script execution engine"
everytime I try to execute a ActiveX script inside a DTS. I tried
reregistering the files dtspump.dll, dtspkg.dll and axscphst.dll that
the link http://www.sqldts.com/default.aspx?224 suggests to do, but no
luck. Please do you have any ideas on how to fix this problem?

I would consider other avenues such as "can you execute any VBA coding"
such as that which is found in an "Access Database-module" or in a
windows scripting host command file (.wsf). I may have something to do
with credentials used to run the sqlservice or sqlagent, or even
security settings on ActiveX for the web browser?

Just a few quesses.

Good Luck!

One other stab in the dark - verify db user login rights and
permissions to msdb and master databases there dts does some of it's
work.

Hi,

I had the msde sqlserver installed on my machine originally. Then I
had the Standard edition EM Tools installed, but according to my boss
the EM client Tools are same no matter what version. Just some
versions don't allow you to install it. Well, I tried installed Sql
Server Sp3a to my machine. I later found out one of the dbas thought I
had standard addition. I don't. So sp3a SE was installed. I have
msde on my machine. Well, after all this screwed up my machine. I
just did a system restore to two days ago and then all my sql server
client tools were missing a lot of the .rlls. So I just ran the msql
server client tools standard edition installation and it is working
again. I know can see my dts packages fine. Everything is working
perfect now except for one problem. I still can't execute DTS packages
that have activeX Scripting I am getting the error:

"ActiveX scripting was not able to initialize the script execution
engine". Just to make sure it wasn't the .dll I reregistered the
dtspkg.dll, dtspump.dll and the axscphst.dll. Please do you have any
ideas on how to get this to work?

I have full administrator rights. It use to work. Problem started
after a sp3a update to the wrong server pack standard edition and it
should have been msde edition.

David

I ran the windows xp professional system restore three days back
instead of two days back this time and it fixed my problem.

David