I have used the package and deployment wizard for an app I am working on. It installs fine, but as soon as you attempt to log in it gives
Error 429
ActiveX component can't create object.
Any help would be very much apprecaited.
Printable View
I have used the package and deployment wizard for an app I am working on. It installs fine, but as soon as you attempt to log in it gives
Error 429
ActiveX component can't create object.
Any help would be very much apprecaited.
more than likely you are missing a dll..
check all the components and references you have set in your project and make sure the coresponding dll/tlb/ocx
is included in your install package.
here is the explanation straight from the help that list some other possible causes
Creating objects requires that the object's class be registered in the system registry and that any associated dynamic-link libraries (DLL) be available. This error has the following causes and solutions:
The class isn't registered. For example, the system registry has no mention of the class, or the class is mentioned, but specifies either a file of the wrong type or a file that can't be found.
If possible, try to start the object's application. If the registry information is out of date or wrong, the application should check the registry and correct the information. If starting the application doesn't fix the problem, rerun the application's setup program.
A DLL required by the object can't be used, either because it can't be found, or it was found but was corrupted.
Make sure all associated DLLs are available. For example, the Data Access Object (DAO) requires supporting DLLs that vary among platforms. You may have to rerun the setup program for such an object if that is what is causing this error.
The object is available on the machine, but it is a licensed Automation object, and can't verify the availability of the license necessary to instantiate it.
Some objects can be instantiated only after the component finds a license key, which verifies that the object is registered for instantiation on the current machine. When a reference is made to an object through a properly installed type library or object library, the correct key is supplied automatically.
If the attempt to instantiate is the result of a CreateObject or GetObject call, the object must find the key. In this case, it may search the system registry or look for a special file that it creates when it is installed, for example, one with the extension .lic. If the key can't be found, the object can't be instantiated. If an end user has improperly set up the object's application, inadvertently deleted a necessary file, or changed the system registry, the object may not be able to find its key. If the key can't be found, the object can't be instantiated. In this case, the instantiation may work on the developer's system, but not on the user's system. It may be necessary for the user to reinstall the licensed object.
You are trying to use the GetObject function to retrieve a reference to class created with Visual Basic.
GetObject can't be used to obtain a reference to a class created with Visual Basic.
Access to the object has explicitly been denied.
For example, you may be trying to access a data object that's currently being used and is locked to prevent deadlock situations. If that's the case, you may be able to access the object at another time.
I have just created a distribution, test installed on another (clean) pc and have same problem.
Whilst looking into this you may be able to help me by answering a few questions:
1 - Is the machine you are test loading your app onto a Win 95 machine ?
2 - Are you using ADO ?
3 - If using ADO what type of connection are you using i.e. ODBC, OLE DB ?
4 - What service pack of vb6 are you using if any ?
As soon as I can work out a fix I will let you know as I am fairly sure we are suffering the same problem.