OCX Error on installing APP - Webclient

E

eMe

New Member
Hi, I'll try to speak my best english...

I'm developing an app which uses some dll and some ocx... when I "generate" the application so it creates an installer I add those files so they get register when the installation takes places.

I have make this proccess many times, but now I have replaced one ocx, everything goes fine, until an end-user executes the app...the cab file it's well generated, intallation finish successfully... but when the user executes it, the system doesn't find the ocx... I look for it in windows/system32 (depends on the OS, but it doesn't matter) and I don't find it...and I look for it in the cab file, finding it...

so, i think, the problem is that the ocx doesn't get copy to the file system of the end-user ...

I do not understand why with older versions oeverything goes fine, but in this one it doesn't copy the ocx... Do you know where the problem iS? any suggestion...
 
It appears to me that the problem is with registering the OCX, probably because the user does not have the rights to write to the registry.

Have you tried directly registering it on the PC , using 'regsvr32' . It may be failing because it points to a different path or as mentioned above the user does not have rights to register the OCX.

Cheers
Sunil.
 
I have read that in the .DEP associated to the .ocx you may find some info related to the .ocx...

Dest=$(AppPath)Somewhere in the web I have found that it means that I must include the .ocx under the application path... so in the weclient options I chose Aplication Specific and included the .ocx in may app folder..

BUUT

It didn't work!! :(

¿Any suggestions?
 
Well, I've found a log (I can't beleive no one knew about the existence of this log) in the end-user machine where says that it is registering the old .ocx (as if I hadn't change it...

So, the problem is theWebClient Application Assembler which doesn't generate correctly the installer :(

Anyone knows something about this?
 
It's been a while since I worked on Webclient, but from memory there is an option in the Webclient assembler , using which we can control whether to create an incremental installation file (cab) , or to re-create the whole installation file.

Maybe in your case , webclient doesnt get the reference to the new OCX because , it assumes that the old OCX has not been changed.

-Sunil
 
Hi, thanks for your answer...I'll look for it and see if end-users will need to reinstall completely the app or webclient will detect it as a new update.
 
FYI if you want to add ocx or dll to a newer version, changa the Version of the Intellistream.
 
You must log in or register to reply here.
Back
Top