I am unable to open or create DTS package on the local box
(SQL Server 2000) .It throws up an error saying "The
specified module not found" .

It does not run when scheduled as a job .

However it works fine from the client .

I am not sure what the problem is ? Please advise ?

Hi Venkatesh
What version of SQL Server are you using?

Can you describe what the package does? What types of connections are you
making? If you have a provider present on the client that is not installed
on the server, you may get an error similar to this.

Can you create a simple DTS package using Pubs and Newpubs as the source
and target? Run it on the Server. Do you see the error? Can you schedule
it? If this works then it is something particular to the package that is
failing.

Was the Server and the client upgraded to the same service pack level?

Nick Schueler



--------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.

Hi Nick

The version is 2000 - 8.00.760 SP3a .
The DTS is a simple table copy from one database to
another .
It fails when run from the server however suceeds when
from a client .

The Microsoft Management Console version on the server is
Version 5.0 (Build 2195: Service Pack 4)

while its version on the client is

Version 5.1 Service Pack 1

Hi,

The person who installed SQL Server is able to execute the
packages from the server box .

I suppose this is something to do with the windows login
that installed SQL Server .

Does installing via administrator solve the problem ?

TIA,
Venkatesh

The fact that you can use the packages on the server but only from a
client/A.N.Other PC suggests that the tools on the Server are out of
shape. The fact that the person who installed the SQL Server can
execute DTS but you cannot suggests there is something in their profile
that is not in yours.

It suggests a dll is missing/not registered.

This could be either

1. One of the DTS dlls
2. MDAC
3. One from SQL Server.

Does the NT Event log give you a clue as to which module was being
loaded?

Try reregistering (as you) the DTS dlls

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