InstallAware

Hi,

Like this post http://www.installaware.com/forum/viewt ... f=2&t=6221 I'm getting an Access Violation in module SHLWAPI.dll. Our installations are built with Installaware NX, build 8.24.12

In my case the error happens in line 565, which is Apply Install, same as the other post.

It doesn't happen on all computers at every site, but some of the details of the shlwapi.dll on the machines that fail are:
Win 7 Pro 64bit SP1, shlwapi.dll dated 2010-11-21 4:24pm, v6.1.7601.17514, 438kb
XP SP3 32bit, shlwapi.dll dated 2009-12-08 10:23pm, v6.00.2900.5912, 463kb

I don't believe it is a problem with shlwapi.dll directly, as the Win 7 64bit file above is exactly the same as mine (I replaced mine with their supposedly faulty one, though it was already the same date, size and version) and had no issues with the install. That could mean it's another dependency of shlwapi.dll, but it's not that specific file.

One possibility I have thought of, is that we are using the native engine for the installation. We DO NOT change to Windows Installer at any stage during the installation. Does this still require an "Apply install" command? Or does everything happen in-line anyway, so maybe if there's nothing to do the dll has an error?

Thanks,

Bob

Dear Bob,

The Apply Install command functionalities, if used in conjunction with NATIVE ENGINE, are based on the value of the DELAYUNTIL_APPLYCHANGES pre-defined variable.

This variable has no effect unless the native code setup engine is being used. Initially FALSE. If this variable is set to TRUE, the native code setup engine will attempt to emulate the behavior of the Windows Installer setup engine by deferring the execution of setup actions until Apply Install has been called

However, the Apply Install command is still necessary to commit the installation log to disk, as well as perform a final set of installation related tasks - even though the majority of the installation (such as file copying) could already be complete. (Please refer to InstallAware documentation for more details).

By the way, I don't believe the cause of your issue can be generated by the installation process itself.
Very probably it could be related to some specific tasks that are non correctly handled.
The error only tells you that a Violation has occurred with the module "shlwapi.dll", but this doesn't mean that the module is definitely the cause.

SHLWAPI library is responsable of all Windows shell operations as; Registry, Files handling and many others.

Do you have any possibility to reproduce the issue with a sample project?

Regards