• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1163
  • Last Modified:

Executing Remote DTS Package from MS Access Client

I am writing an MS Access 2003 application which needs to execute a DTS package on the server from a client machine.  
The following code attempts to execute the LoadFromSQLServer method on the created DTS.Package object.
The error "Invalid Class String" occurs at the "LoadFromSqlServer" line.  The LoadFromSQLServer method executes successfully on my development
machine where the client and server are on the same machine.
Based on research on EE and the Net I have taken the following steps so far to resolve the problem:
* Manually copied over the DTS DLL and RLL files from my development machine to the test client machine and registered them as documented
in the "redist.txt" file on my SQL Server distribution disks.  System Admin is currently getting the SQL Server install disks for me to
I can try to install the SQL Server Client Tools on the client to make sure that all DLLs and RLLs are present and registered.
* Found that the error may be due to the package containing unregistered Analysis services steps.
So I created a test DTS package that contains only a DTS Connection object. The error persisted.

As I said, I have attempted to research all applicable solutions on EE and elsewhere.  Any suggestions out there?

I also have a more general question (or set of related questions):
When the LoadFromSQLServer method is executed, where does the package get executed i.e. where does the package execution process run,
on the client or the remote SQL Server?  If on the client then do all executables included in the package command line tasks have to be installed
on every client from which the package is executed (thus making each client nearly as "heavy" as the server)?

Thanks for your help.

Client: Windows XP, MS Access 2003
Server: Windows 2003 Server, SQL Server 2000

MS Access VBA Code:

    Const DTSSQLStgFlag_Default = 0
    Const DTSStepExecResult_Failure = 1
    Const DTSSQLStgFlag_UseTrustedConnection = 256
    Dim objPkg As DTS.Package
    Dim objStep As DTS.Step
    Dim strMsg As String
    Dim ADOErr As ADODB.Error
    Dim strError As String
    Dim boolRC As Boolean
    boolRC = False
    On Error GoTo Gen_ErrorHandler
    Set objPkg = CreateObject("DTS.Package")
    With objPkg
        .LoadFromSQLServer "RemoteServer", "", "", DTSSQLStgFlag_UseTrustedConnection, "", "", "", "DTSPackageName"
    End With
  • 3
  • 2
1 Solution
Run the DTS package on the server from a stored procedure using


to issue a dtsrun dos command. That way you don't need to install anything on the clients, and the package will run on the server.
ogdenbtAuthor Commented:
So the solution looks something like:

From MS Access client:
* Connect to the remote SQL Server
* Execute a stored procedure on the remote SQL Server  (I expect to use ADO to do so)
* The executed stored procedure contains an "xp_cmdshell" statement like:
      xp_cmdshell 'dtsrun RemoteServer\local /E /N DTSPackageName'
* The dtsrun command line RemoteServer refers to the remote SQL Server;
the DTSPackageName refers to the DTS Package on that server
* The dtsrun command line /E switch allows a trusted connection
* The dtsrun command line may include /L or /W switches to log or write the result status to
determine the outcome of the package execution respectively

THE dtsrun COMMAND EXECUTES ON THE RemoteServer, NOT THE CLIENT (making the client "light"
as you described)

Is this essentially what you are proposing?
You got it :)
ogdenbtAuthor Commented:
I will give that a shot, thanks very much for your help.
No problem. Post back with how you get on, and if you need any assistance. Good luck.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now