Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > Visual Basic > VB 2005 > Pro Visual Basic 2005
Password Reminder
Register
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
Pro Visual Basic 2005 For advanced Visual Basic coders working in version 2005. Beginning-level questions will be redirected to other forums, including Beginning VB 2005.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the Pro Visual Basic 2005 section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
 
 
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old September 8th, 2006, 08:38 AM
Registered User
 
Join Date: Sep 2006
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default Error 80040154

I am trying to execute a DTS package from my code. If I run it on my local machine it runs fine. If I install it onto another machine, using ClickOnce, I get this error. Before I execute the package, I can actually do a Select query. So, I know that getting to the database is not an issue. In the application files, inside the publishing tab, I set the Interop.DTS.dll file set to Include(Auto) as required. I also have the Copy Local set to true on the References tab. Any help anyone can give will most definitely be appreciated. Thanks.

  #2 (permalink)  
Old September 8th, 2006, 10:21 AM
Friend of Wrox
 
Join Date: Nov 2004
Location: Port Orchard, WA, USA.
Posts: 1,621
Thanks: 1
Thanked 3 Times in 3 Posts
Default

I really don't understand why people post error [u]numbers</u> (as if the people providing help have memorized eighty million error numbers!), but withhold the [u]text</u> of the error (like "File not Found," "Column not Found in Collection," etc.).

Would you be so kind as to tell us what the error is? (The [u]text</u> of the error, that is?)
  #3 (permalink)  
Old September 8th, 2006, 10:43 AM
Registered User
 
Join Date: Sep 2006
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

The error displayed is "Retrieving the COM class factory for component with CLSID {guid} failed due to error 80040154. First post, sorry for the inconvenience.
  #4 (permalink)  
Old September 8th, 2006, 11:20 AM
Friend of Wrox
 
Join Date: Nov 2004
Location: Port Orchard, WA, USA.
Posts: 1,621
Thanks: 1
Thanked 3 Times in 3 Posts
Default

Is this a web application?

Regarding the error text:
    I guess you really couldn't have done much different than you did (though the rest of the error text does help to establish context).
    Apparently even Microsoft is reluctant to tell us what the story is, falling back on using just numbers.
    It’s like that ridiculous error message we get when a file can't be found, "File not found." For crying out loud! [u]What</u> file?!? I mean: the OS was just looking for it—by name; would it be [u]so</u> hard for MS to have caused the error message to include the name of the file it was just looking for?
    This irritates me so much that in my code, when I am opening anything, I [u]always</u> add an error handler that actually adds the name of the sought-after resource. (Sorry, just a side rant...)
  #5 (permalink)  
Old September 8th, 2006, 12:29 PM
Registered User
 
Join Date: Sep 2006
Location: , , .
Posts: 3
Thanks: 0
Thanked 0 Times in 0 Posts
Default

Its not a web app, its just a standard windows application. I know, in regards to the side rant, it ticks me off also. I am completely lost on this issue, as is everyone else I work with.

  #6 (permalink)  
Old September 13th, 2006, 01:06 PM
Wrox Author
Points: 13,255, Level: 49
Points: 13,255, Level: 49 Points: 13,255, Level: 49 Points: 13,255, Level: 49
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
 
Join Date: Oct 2005
Location: Ohio, USA
Posts: 4,104
Thanks: 1
Thanked 64 Times in 64 Posts
Send a message via AIM to dparsons
Default

I found this on Experts Exchange, similiar situation:

You can try using the "depends" tool (Forgive me, the file path is where it resides in VS2003, though it should be similiar in 05)

The tool can be found here: (You may need to install the VC++ tools)
C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Tools\Bin

Open the COM dll in that utility and it will tell you want all dependecies it has. Anything that shows up with RED will indicate that the referenced binary could not be found or does not exists.


"The one language all programmers understand is profanity."
  #7 (permalink)  
Old May 30th, 2007, 10:44 AM
Registered User
 
Join Date: May 2007
Location: , , .
Posts: 1
Thanks: 0
Thanked 0 Times in 0 Posts
Default

This has some thing maybe even remotely to with 64 bit isnt it?

 


Thread Tools Search this Thread
Search this Thread:

Advanced Search
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

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Insert Query Error & Run-Time Error 3022 DavidWE Access 1 July 31st, 2008 11:17 AM
Ch 4: Parse error: syntax error, unexpected T_SL hanizar77 BOOK: Beginning PHP5, Apache, and MySQL Web Development ISBN: 978-0-7645-7966-0 0 June 23rd, 2008 09:17 PM
hi i got runtime error 13 Type Mismatch error sriharsha345 Access VBA 2 February 21st, 2008 09:30 AM
Parse error: syntax error, unexpected T_STRING ginost7 Beginning PHP 1 November 9th, 2007 02:51 AM
CAPICOM - Error 80040154 glosrob C# 0 June 20th, 2007 04:19 AM



All times are GMT -4. The time now is 10:11 AM.


Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.