-
Hi,
this is doing my head in and any help would be greatly appreciated.
I have a program in VB6.0, NT4.0 which sets some settings in the registry. It works fine on my machine, but comes up with the dreaded 429 error when run from a remote (VB-less) install. The only funky part of the program is the bit that accesses the registry, and that is initiated by the following API call:
Code:
Private Declare Function RegOpenKeyEx Lib "advapi32" Alias "RegOpenKeyExA" (ByVal hKey As Long, ByVal lpSubKey As String, _
ByVal ulOptions As Long, ByVal samDesired As Long, ByRef phkResult As Long) As Long
I have all the DLL's I can think of in the directory. And I'm not too sure about what is involved in registering activeX's or whatever, so I haven't done much of that.
There is a similar API call used in the standard VB about dialog box, so if I create a blank project and add an about form, it also does not work on a remote install.
I've read all the stuff I can find (on the web and in MSDN) about this error, but not much of it makes sense to me, or help's me in solving this problem. Anyone got any ideas?
Mark.
[Edited by markdav on 04-09-2000 at 11:21 AM]
-
May be
Sometimes this error is caused by a dll or system file not being registered properly. The samething happened to me once everytime I tried to use a switchboard in Access. You might want to try reregistering the system files or dlls with the regsvr32 or equavilant for NT it should be in the windows directory and if you run it then it will give the helps on what command line arguments to use. I don't know if that is it but hopefully it will help.
