Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Interop / September 2005

Tip: Looking for answers? Try searching our database.

Error 430 - Class does not support Automation or does not support.

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Chad - 08 Sep 2005 21:24 GMT
Hello Everyone,

I'm having an issue with a .NET COM Interop Assembly within VB 6.  When I
try to create a new instance of a class, in VB 6.0, I receive the following
error: "Error 430 - Class does not support Automation or does not support the
expected interface".

I created .NET COM Interop DLL for the purpose of creating SQL Reporting
Subscriptions within Visual Basic 6.0.  Everything was working fine.  I was
able to create new Reporting Services Subscriptions through the VB 6.0
application.  I haven't touched the project from about two months. Now when
execute the application, I receive an Automation Error.  I have tried
unregistering the and registering the assembly, gave the assembly and new
GUID and removed and re-added the reference but still no luck. I then
compiled the application and manually installed it on a clean machine.  
Everything worked.  I was able to run the application and create subscription.

Here is what I found out so far:

I only receive the automation error on my machine.
The error occurs whenever I try to create a new instance of an object within
the assembly.
I can create a new instance of an object within the assembly using the
CreateObject method.
The Assembly's Classes and the methods do show up in the object browser.
I have tried uninstalling and reinstalling Visual Studio 6.0 and the .NET
Framework 1.1.
I receive the same error within Access VBA.

Any help would be greatly appreciated.

Thanks
Chad
Chad McKee - 13 Sep 2005 21:14 GMT
Hello Everyone,

I solved my issue with the automation error.  I had SQL Server 2005 Beta
3 installed on my machine.  As soon as I uninstalled it, the component
started working again.  Must of been some conflict with the .NET
Framework Version 2.0 Beta.

Thanks

>Hello Everyone,
>
[quoted text clipped - 30 lines]
>Chad
>  

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.