MM Mscomctl.ocx want to close an application before proceeding
Hi,
An application that was recaptured using wise 6. During the capture, some merged modules were created. One of them is MSCOMCTL.OCX. During our staging process, this file is used by our internal process. MSI fails with an error, asking to close this application before proceeding with the update of the OCX.
I am wondering, is there a way to tell WISE to pass this check and for example, to overwrite it on reboot?
Thks
An application that was recaptured using wise 6. During the capture, some merged modules were created. One of them is MSCOMCTL.OCX. During our staging process, this file is used by our internal process. MSI fails with an error, asking to close this application before proceeding with the update of the OCX.
I am wondering, is there a way to tell WISE to pass this check and for example, to overwrite it on reboot?
Thks
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
You're going to have to fudge it, I'm afraid.
If it were me, I'd probably install the OCX using another name, then set up the PendingFileNameOperation registry entry so that it gets renamed during the next start-up. I'd check the objects, class IDs and such between the two versions, just to make sure nothing major has changed (I don't think anything substantial changed between versions) but you may want to keep it simple by unregistering the old one and re-registering the new.
If it were me, I'd probably install the OCX using another name, then set up the PendingFileNameOperation registry entry so that it gets renamed during the next start-up. I'd check the objects, class IDs and such between the two versions, just to make sure nothing major has changed (I don't think anything substantial changed between versions) but you may want to keep it simple by unregistering the old one and re-registering the new.
Posted by:
unreal2me
13 years ago
Hi VBSCab,
I was afraid you would say that. I remember having some other packages with the same Com modules and versions as this one and never heard of a problem with our staging process. I am wondering why it happens with this one and not the other one.
Let me know if you have an idea. I'll dig a little more.
Thks,
I was afraid you would say that. I remember having some other packages with the same Com modules and versions as this one and never heard of a problem with our staging process. I am wondering why it happens with this one and not the other one.
Let me know if you have an idea. I'll dig a little more.
Thks,
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.