Manually registering Remote exe & dlls???

[wendas]

We have created a remote ActiveX exe.. with a dll in it.. It works great on a client server.. but.. We must be doing something wrong.. We add it.. But then must manually register the dll and the ActiveX exe it does will not run without it.. The ActiveX has an error 70..something about Permissions.. The Dll has Object not open error.. 429 activeX cannot create object..

If you register the ActiveX exe & the dll on the client it then runs well...

We have done the following..
created a depends for the dll (this is not a remote though)
Made ActiveX exe remote.. did a make..
Standard exe calls the ActiveX by referencing the TLB
not the exe..
package & deploy pick up the TLB & VBR in the standard
exe..

If anyone can point us in the right direction we would appreciate it..

Thanks
Ann & Wenda

 

[SemperFiDownUnda]

Error 70 Permission Denied is often a case of a untrusted (non domian user) trying to start a process on a NT/W2k/XP machine. So if you have something like local win98 machine trying to access a COM object (EXE based or DLL in Component Services) on a Server then the server will spit the dummy. DCOM need trusted accounts to work. This is a big problem with Novell networks and the like.

About registering there are 2 things
1 ActiveX EXE's are self registering. DLL's should be registered via their setup package but can be registered by using Regsvr32.exe

 

[wendas]

Thanks.. But the client machine we are testing on is Win NT so it must be something else that is staring us in the face, but we can not see it..

Thanks for the tip about the dll. I think we got the Dll right.. (we manually stuck the dll into the package & deployment of the Standard Exe that calls these remote objects..

If possible, could you elaborate on ActiveX EXE being self registering.. We were hoping after putting an ActiveX exe on a server & directing the clients to point to that path, that we could update the ActiveX and wha-La.. The clients got the new version.. But one book we have talks about haveing to unregister & reregister on the clients using clireg32.. Well we tried an upgrade by upgrading the server exe & checking if the client could see it.. But.. the client was not happy with us.. We error.. 463 something about the class.. (Sorry can't remember the exact error)..

one step forward & two steps back.....

Wenda

 

[SemperFiDownUnda]

The client machine being NT doesn't matter. What I described basically is that COM under component services only works within a NT Domain. This is a problem I have here where all the machines are W2k but users don't log into a "NT Domain" but into the individual machines (Novell logs them in) thus DCOM won't work because non of the machines trust the users. IE (Error 70 : Permission Denied)

I should have been clearer on EXE's. EXE's are self registering but only on the machine they run on. IE if you run the EXE it looks in the registry to see if its interfaces are set up if not it registers them but only locally.