dbTalk Databases Forums  

DTS Package throws error on Client Machines only

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss DTS Package throws error on Client Machines only in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
WhiskRomeo
 
Posts: n/a

Default DTS Package throws error on Client Machines only - 06-11-2004 , 05:59 PM






I have a package that executes fine from the server where SQL Server in installed.
However, the below code generates an error (see below code) when executed from a workstation on the client. This is a Windows .Net application.

All other data access work just fine.

Can anyone explain this? Why would we have to register a COM Object?

Bill
*********************************
Dim strMsg As String
Dim strPkgName As String
Dim oPkg As DTS.Package2

strPkgName = "PPS_BatchImport"
strDestPath = tbFileToImport.Text

oPkg = New DTS.Package2 '<--ERROR OCCURS HERE

************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040154): COM object with CLSID {10020202-EB1C-11CF-AE6E-00AA004A34D5} is either not valid or not registered.
at PPS.frmBatchImport.btnMoveToStaging_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

--
William R

Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: DTS Package throws error on Client Machines only - 06-12-2004 , 01:03 AM






Do you have DTS installed on the client?

If not then this is the problem. DTS is a client side app.

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

Also please do not post the exact same message under different subjects.
This is likely to irritate some and possibly stop them giving you the help
you need.



--
--

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


"WhiskRomeo" <wrlucasD0N0TSPAM (AT) Xemaps (DOT) com> wrote

Quote:
I have a package that executes fine from the server where SQL Server in
installed.
However, the below code generates an error (see below code) when executed
from a workstation on the client. This is a Windows .Net application.

All other data access work just fine.

Can anyone explain this? Why would we have to register a COM Object?

Bill
*********************************
Dim strMsg As String
Dim strPkgName As String
Dim oPkg As DTS.Package2

strPkgName = "PPS_BatchImport"
strDestPath = tbFileToImport.Text

oPkg = New DTS.Package2 '<--ERROR OCCURS HERE

************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040154): COM object with
CLSID {10020202-EB1C-11CF-AE6E-00AA004A34D5} is either not valid or not
registered.
Quote:
at PPS.frmBatchImport.btnMoveToStaging_Click(Object sender, EventArgs
e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)

--
William R



Reply With Quote
  #3  
Old   
WhiskRomeo
 
Posts: n/a

Default Re: DTS Package throws error on Client Machines only - 06-12-2004 , 11:22 AM



Both time that I posted this message, the response I got from the system consisted of words to the effect -- An error has ocurred posting your message. Your message could not be posted and . . .

So if this is confirmation, I get when I post. Don't be surprise that I might try again.

Regarding the actual problem. I was in error in pointing out which line it errored on. Here is the line.

oPkg.LoadFromSQLServer((local), , , _
DTSSQLServerStorageFlags.DTSSQLStgFlag_UseTrustedC onnection _
, , , , _
strPkgName)

Of course, local has no meaning on the client machine. I changed local to the name of the computer where SQL Server 2000 is installed. I am waiting to hear from the client. I could only verify that with this change this still works, from the server.
--
William R


"Allan Mitchell" wrote:

Quote:
Do you have DTS installed on the client?

If not then this is the problem. DTS is a client side app.

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

Also please do not post the exact same message under different subjects.
This is likely to irritate some and possibly stop them giving you the help
you need.



--
--

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


"WhiskRomeo" <wrlucasD0N0TSPAM (AT) Xemaps (DOT) com> wrote in message
news:42E9E482-6BE4-45A7-B26F-8E4D96C5293A (AT) microsoft (DOT) com...
I have a package that executes fine from the server where SQL Server in
installed.
However, the below code generates an error (see below code) when executed
from a workstation on the client. This is a Windows .Net application.

All other data access work just fine.

Can anyone explain this? Why would we have to register a COM Object?

Bill
*********************************
Dim strMsg As String
Dim strPkgName As String
Dim oPkg As DTS.Package2

strPkgName = "PPS_BatchImport"
strDestPath = tbFileToImport.Text

oPkg = New DTS.Package2 '<--ERROR OCCURS HERE

************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040154): COM object with
CLSID {10020202-EB1C-11CF-AE6E-00AA004A34D5} is either not valid or not
registered.
at PPS.frmBatchImport.btnMoveToStaging_Click(Object sender, EventArgs
e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)

--
William R




Reply With Quote
  #4  
Old   
WhiskRomeo
 
Posts: n/a

Default Re: DTS Package throws error on Client Machines only - 06-12-2004 , 11:32 AM



PS:
I meant to thank you for your response.

I have looked at the link you sent me. If my first solution does not work, I will investigate ways to launch a DTS package from a stored procedure which is executed from within SQL Server therefore these client files should not be needed.

Only as a last resort will I implement having to manually install and register files on each client. How sad is this soultion?

Bill


Here is the exact message.

An error occurred while sending your post
--------------------------------------------------------------------------------

We're sorry, but there was a problem with the system and your post was not received. The error has been reported to Operations and will be investigated as soon as possible. Please try again later

--
William R


"Allan Mitchell" wrote:

Quote:
Do you have DTS installed on the client?

If not then this is the problem. DTS is a client side app.

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

Also please do not post the exact same message under different subjects.
This is likely to irritate some and possibly stop them giving you the help
you need.



--
--

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


"WhiskRomeo" <wrlucasD0N0TSPAM (AT) Xemaps (DOT) com> wrote in message
news:42E9E482-6BE4-45A7-B26F-8E4D96C5293A (AT) microsoft (DOT) com...
I have a package that executes fine from the server where SQL Server in
installed.
However, the below code generates an error (see below code) when executed
from a workstation on the client. This is a Windows .Net application.

All other data access work just fine.

Can anyone explain this? Why would we have to register a COM Object?

Bill
*********************************
Dim strMsg As String
Dim strPkgName As String
Dim oPkg As DTS.Package2

strPkgName = "PPS_BatchImport"
strDestPath = tbFileToImport.Text

oPkg = New DTS.Package2 '<--ERROR OCCURS HERE

************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80040154): COM object with
CLSID {10020202-EB1C-11CF-AE6E-00AA004A34D5} is either not valid or not
registered.
at PPS.frmBatchImport.btnMoveToStaging_Click(Object sender, EventArgs
e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventAr gs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons
button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage (Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(M essage& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)

--
William R




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.