If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Exit Code -1073741819

Has anyone seen the return code -1073741819 (0xC0000005 - supposedly Access Violation?) from an InstallShield project during the building of the project?

If I build the project using the InstallShield GUI, it compiles fine. If I compile it using the command line (IsCmdBld.exe) from a command prompt, it builds just fine.

However, when we build it using Visual Build Pro, Visual Build Pro says it fails with the return code -1073741819. It catches this return code in the middle of merging in the merge modules.

We tried just shelling the command line call to a command prompt as a work around and that worked fine to build it. However, then we get the following error when running that install: Internal error 2602. File, Global_Controls_MSMAPI32OCX_f0.7EBEDD2C_AA66_11D2_B980_006097C4DE24.

A number of weeks back when we upgraded to IS 11.5 from 10.5, we experienced the same problem. Uninstalling 10.5 and installing the 11.5 InstallScript Objects fixed both problems (return code -1073741819 and the Internal error). Now both problems have resurfaced for an unknown reason. No configuration changes have been made to the computer and none of the changes made to the installer are the cause (we rebuilt an old (good) build and it failed to build).

I've already been to that thread post. That is not a fix by any means. It simply captures the error code returned from InstallShield and allows you to ignore it. The problem is that the InstallShield build has still failed and my installer is not built. If the point of the step is to build that installer, what good is ignoring that it has failed?

Unfortunately, that fix did not work for InstallShield 12.0. I actually had to overwrite the MDAC28.msm from the 12.0 installation with the one from 11.5 to fix it. However, that is going to be a problem when we start wanting to support Vista as the 12.0 version of the MDAC28.msm was updated to support Vista.

It was built successfully on Saturday. Nothing changed between these times.

I can use IS UI to build it, but on build machine, we don't install IS 12 IDE

The most wiered thing is all our other 4 projects are built OK.
If I run IsSABld.exe from command line, no error generated. But it stops at "Building File table". Merge modules and others are not built into the msi. Even I remove all merge module references, I still get return code -1073741819

SP1 for IS 12 Stand Alone build engine

After installed IS 12 IDE to a new machine, open my Basic MSI project and click Build icon, I reproduced the build failure(return code was -1073741819). I think if I install IS 12 SP1, the problem will be gone. But the thing is we don't have a SP1 for IS 12 Stand Alone build engine.