PDA

View Full Version : What does "fatal error -5056" mean



Josh Korn
07-20-2006, 04:21 PM
For some completely unknown reason, I'm now getting the following:

ISDEV : fatal error -5056 : Internal Build Error

on every attempt to build.

Does anyone know what this means and what I can do to fix it?

Thanks
Josh

MichaelU
07-20-2006, 05:21 PM
I'm not sure about details of why the error is occurring, but it's tied to initializing the Merge Module section of our build process. Have you changed your merge module directories, or added a new merge module since the build would complete successfully? Or perhaps a file has been corrupted; you might try running our installation in repair mode.

Josh Korn
07-21-2006, 03:02 PM
you might try running our installation in repair mode.

Michael: that did the trick.

Wish I knew what caused the problem, so I could relay it to you. FYI, the prime suspect seems to be Rational Functional Tester, which took the past several days to install. "We have means and opportunity, but so far, no motive".

Josh

RaggieSoft
08-25-2006, 01:01 AM
I'm getting the same error and figured out how to fix it (thanks to old InstallShield 5.0 Express docs in the search feature :)

Regsvr32 "<PROGRAMFILES>\Common Files\Microsoft Shared\MSI Tools\mergemod.dll"

where <PROGRAMFILES> is (usually) C:\Program Files

This fixes the MSM Merge Tool COM Server (mergemod.dll) that InstallShield uses by reregistering it with the system. Tested on IS 12 Premier using an InstallScript MSI project (and no need to run msiexec /fecums nor did I need to restart IS)

Maybe Macrovision could release a tool to do this quick fix so that when the error happens, reregister the file, then offer the user the chance to rebild the setup.

Christopher Painter
12-22-2006, 10:55 PM
I experienced this today. It was caused by uninstalling InstallShield 12 Colloboration.

As I previously pointed out:

http://community.macrovision.com/showpost.php?p=365879&postcount=15

There is a defect in the InstallShield installation program. It violates the component rules by installing a Microsoft shared resource using a component GUID that is different then the one Microsoft uses in their install.

Since I was running Vista I had to run CMD as Admin and regsvr32 the DLL like the previous post before my project ( which doesn't even contain any merge modules ) would build.

DLee65
03-05-2007, 12:50 PM
I had the same thing today casused by a similar issue that Chris saw. I uninstalled collaboration for IS 11.5 and install Collaboration for IS 12 Premier. Registering the DLL as mentioned above fixed the problem for me without having to restart the IS 12.

MartinMarkevics
03-05-2007, 06:42 PM
You're right, we should either use the same component GUID or copy it to a different location (without registering it - like we already do for the Standalone builder). We will probably do the latter, but either way it will be fixed in the next release.

SteveP55419
07-10-2007, 09:19 PM
RaggieSoft,

Don't know if you'll see this but thanks for that post. It saved me.

Steve

Carl Cook
09-09-2007, 10:01 AM
MartinMarkevics
fixed in the next release

And that might be just about when? I presume my 12 express will update itself shortly to correct this fatal problem that prevents users from building even one file setups?


================= Logging started at 9/9/2007 01:10:10 AM ==================
Created release folders
AdminExecuteSequence table successfully built
AdminUISequence table successfully built
AdvtExecuteSequence table successfully built
AdvtUISequence table successfully built
InstallExecuteSequence table successfully built
InstallUISequence table successfully built
Directory table successfully built
Feature table successfully built
FeatureComponents table successfully built
Component table successfully built
Loading File table
ISEXP : fatal error -5056: Internal build error
Express\SingleImage - 1 error(s), 0 warning(s)
================= Logging stopped at 9/9/2007 01:10:10 AM ==================
Log file has been created: <file:C:\My InstallShield Express Projects\EquityControllerLibrary\Express\SingleImage\LogFiles\9-9-2007 01-10-10 AM.txt>


BTW, when I've checked for updates using the menu, it has never told me there was an update. It shows me a desktop modal dialog telling me there are no updates, and if I minimize it what do I discover? There is ANOTHER copy of that same desktop modal dialog, still blocking view and not minimizable with all buttons disabled. If I dismiss the first, they both dismiss. Very strange.

I have good reason to be a bit cynical about getting a fix, because I can crash Installshield 12 (I have Express) in TWO MOUSE CLICKS. And I have been able to do so since day one and no fix was ever produced. You can crash it too! Start it, select "Help | Search...". Here is the exception info on *THAT* bug:

Exception ACCESS_VIOLATION (0xc0000005)
at address 0x6df03558 trying to read address 0x00000080.

File : C:\Program Files\Macrovision\IS12 Express\System\isdev.exe
Version : 12.0.0.53157
Exception : c0000005
Address : 6df03558
Access Type : read
Access Address : 00000080

Registers : EAX=00000080 CS=001b EIP=6df03558 EFLGS=00010202
: EBX=00000001 SS=0023 ESP=02d6fce0 EBP=02d6fce0
: ECX=7fffff00 DS=0023 ESI=0012e77c FS=003b
: EDX=02d8ad14 ES=0023 EDI=00000000 GS=0000

Stack Trace : 6df1e59e 6df1fb4c 6df1ba29 76f51a10
: 76f51ae8 76f51c03 76f53656 771c0e6e
: 76f43c74 6df148f4 6df1bde3 760e3833
: 7719a9bd 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000


Sorry if this seems rude, but I am frustrated trying to use your product. It is buggy and never once a fix.

Carl Cook
09-09-2007, 10:06 AM
and since I'm mentioning bugs in your product, if I do a static dependency scan I get:

Exception ACCESS_VIOLATION (0xc0000005)
at address 0x676dc5a6 trying to read address 0x00000000.

File : C:\Program Files\Macrovision\IS12 Express\System\isdev.exe
Version : 12.0.0.53157
Exception : c0000005
Address : 676dc5a6
Access Type : read
Access Address : 00000000

Registers : EAX=0012d12c CS=001b EIP=676dc5a6 EFLGS=00010246
: EBX=00000000 SS=0023 ESP=0012d04c EBP=0012d09c
: ECX=0012d104 DS=0023 ESI=0012d104 FS=003b
: EDX=00000000 ES=0023 EDI=679b98c4 GS=0000

Stack Trace : 040c0000 fff70ae8 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000

Carl Cook
09-09-2007, 10:31 AM
btw, rereg'ing the mergemod.dll did fix the fatal error -5056 : Internal Build Error.

MartinMarkevics
09-10-2007, 03:32 PM
Regarding the mergemod.dll issue, it is fixed in InstallShield 2008 (both Express and Pro\Premier editions).

Carl Cook
09-18-2007, 02:45 PM
Some companies support the current release and fix bugs in one major release back to help the people (that pay their salary) who have not yet upgraded, or cannot upgrade for other reasons. Some vendors leave bugs in products and then ask you for a lot more money to upgrade to fix 'em so you can get the next batch of bugs that will be fixed in the next release for more money yet, and onward forever.

I guess we remain a relatively small multi-national company because we don't treat our customers that way. Well, at lease our employees sleep well at night knowing they well serve the customers that provide the fiscal fuel that propels the company upward.

Not naming names, of course. Just suggesting policies for other software companies to consider.