Run-error 429
Hi,
I just did a simple update of a few dlls files thro wise 7.0. It install fine but when you try to run the app, the run-time error '429' appears.
Does that mean the client's source is dodgy??
How can I check if the dlls files corrupted??
Your advise is much appreciated!
I just did a simple update of a few dlls files thro wise 7.0. It install fine but when you try to run the app, the run-time error '429' appears.
Does that mean the client's source is dodgy??
How can I check if the dlls files corrupted??
Your advise is much appreciated!
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
dunnpy
14 years ago
Ray,
Do the dll files need to be registered?
Have you tried manually registering them with regsvr32?
If it works after manually registering them then it's probably Wise and the SelfReg table not performing the registration task.
Search the AppDeploy for wisecomcapture - which is the perferred method of dealing with dll registration with WPS.
If it's not this, then please provide further information regarding the dll files and package your working with so the board can offer further advice.
Thanks,
Dunnpy
Do the dll files need to be registered?
Have you tried manually registering them with regsvr32?
If it works after manually registering them then it's probably Wise and the SelfReg table not performing the registration task.
Search the AppDeploy for wisecomcapture - which is the perferred method of dealing with dll registration with WPS.
If it's not this, then please provide further information regarding the dll files and package your working with so the board can offer further advice.
Thanks,
Dunnpy
Posted by:
anonymous_9363
14 years ago
Error 429 is produced by VB programs and simply means that the program was unable to create an object it required. This normally means that either a DLL/OCX or one of its dependencies was missing and/or not registered correctly.
As ever, ProcMon will show you which CLSID is being accessed right before the error appears. Once you know that, you can work backwards to find the relevant DLL/OCX.
Lastly, this forum is concerned not with generic errors but with errors returned by the Windows Installer engine.
As ever, ProcMon will show you which CLSID is being accessed right before the error appears. Once you know that, you can work backwards to find the relevant DLL/OCX.
Lastly, this forum is concerned not with generic errors but with errors returned by the Windows Installer engine.
Posted by:
RayCon
14 years ago
Posted by:
anonymous_9363
14 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.