Register DLL failure breaks silent installation - Advanced Installer Community
kissack
Posts: 57
Joined: Fri Feb 04, 2011 11:45 am

Register DLL failure breaks silent installation

Hello,

I was asked to permit the installation via command line. We have some feature based DLLs that should be registered. They currently don't register on test machine, but when installing with full GUI I can simply click "ingore" and the installation finishes successfully.
However, when I install in silent mode and the same DLLs fails, the entire installation is rolled-back and nothing is installed.

Is there a way to mark this registration so that in case of a failure the setup will continue in silent mode.

Thank you.
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Register DLL failure breaks silent installation

Hello,
They currently don't register on test machine, but when installing with full GUI I can simply click "ingore" and the installation finishes successfully.
I'm not sure why you get that error if you your .DLLs are not registered.
Have you enable the Auto register file (DLL, OCX, etc) from the DLLs Registration tab? Also, can you please send us the .AIP (project file) and a verbose log of the installation to support at advancedinstaller dot com so we can have a better view of this?

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
kissack
Posts: 57
Joined: Fri Feb 04, 2011 11:45 am

Re: Register DLL failure breaks silent installation

The reason why the DLLs don't register (fail to register) is because there are some other components missing on the machine. More specifically Oracle Client.

Of course the DLLs marked as Auto register file (DLL, OCX, etc) in the DLLs Registration tab.
What I need is that the setup won't rollback like in the case of failure during full GUI (after clicking ignore).
Any more insights ?
Dan
Posts: 4530
Joined: Wed Apr 24, 2013 3:51 pm

Re: Register DLL failure breaks silent installation

Hello,

I'm afraid you cannot suppress the related error message. I'm not aware of any policy error which allows that.
Since you ignore the registration of the related .DLLs because it fails on the target machines where no Oracle Client is installed then you can condition their installation on the related machines.

In order to see if the Oracle Client is installed you can perform a Search operation. In order to achieve that you can go in the Search page and use the New Extended Search >> Registry key exists toolbar button to define a search. So, the search will be successful if the specified registry key exists. That means the public property that is associated with the search operation(by default it is RESULT_PROPERTY ) will be 1 if the registry key entrance exist.

Then, in the Organization page in the “Condition” field of each component which have been associated to the related .DLLs you can add the search name as a installation condition.

Please let us know if that helped.

Best regards,
Dan
Dan Ghiorghita - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”