Showstopper

[NewsArchive]

Hi All

I am suddenly getting an error when creating an install set:

Compiler error GEN1081: manifest embedding process failed. Error Code: 50

Any ideas? I am up the creek without a paddle with this one. Was
working a few minutes ago and now poof?

Cheers
Andre

[NewsArchive]

Hi Andre,

> I am suddenly getting an error when creating an install set:
>
> Compiler error GEN1081: manifest embedding process failed. Error Code: 50
>
> Any ideas? I am up the creek without a paddle with this one. Was working
> a few minutes ago and now poof?

EXE already manifested and "Skip if file is already manifested" not marked?

Friedrich

[NewsArchive]

EXE not manifested. It compiled a few minutes ago and now it has
crashed. It has left a .lsp file in the target folder.

Andre

[NewsArchive]

Andre,

> EXE not manifested. It compiled a few minutes ago and now it has crashed.
> It has left a .lsp file in the target folder.

Error 50 only comes up if the FindResource Windows API for resource type 24
(manifest) is not NULL. If the function succeeds (not NULL), the return
value is a handle to the specified resource's information block. In your
case, the return value is not NULL and so the EXE has a manifest in the
resource. Otherwise, you would not see Error 50.

Try to recompile your .EXE. Perhaps your protection software doesn't like
your .EXE and does strange things in the real-time monitoring process (e.g.
after a definition update a few minutes ago). A recompile of your .exe
generates a different binary contents and perhaps this can already help.

BTW, always enable the "Permanent" and "Skip file...." options in the
"#embed UAC application" and "code-sign application" directives.

Friedrich

[NewsArchive]

Does anyone have any idea what could have gone wrong? Compiling away
and SB crashed and now nothing works. Anyone seen this before?

Andre

[NewsArchive]

Andre,

> Does anyone have any idea what could have gone wrong? Compiling away and
> SB crashed and now nothing works. Anyone seen this before?

Perhaps you have received a "bad" definition update from your (real-time
monitoring) protection vendor and this blocks your system now.

Friedrich

[NewsArchive]

Friedrich

Very interesting. Of course I know squat about any of this. It crashed
after the exes were manifested so it generated the error. The permanent
and skip did the trick on the manifests. There was no ways that SB was
going to rerun the scripts without skipping - the only other way would
be to recompile all the exes - there are about 30 of them.

Thanks

Andre

[NewsArchive]

Andre,

> Very interesting. Of course I know squat about any of this. It crashed
> after the exes were manifested so it generated the error. The permanent
> and skip did the trick on the manifests. There was no ways that SB was
> going to rerun the scripts without skipping - the only other way would be
> to recompile all the exes - there are about 30 of them.

Protection software systems always watch and monitor the "embed manifest"
function very closely because this function "manipulates" the binary
contents of a file. The protection software "injects" itself into the
running (compilation) process. IMO, the protection software did not like
something in your last .exe and so it brought the whole system down (that's
where the .lsp file is coming from).

Please check if there are temporary files laying around in the
CSIDL_APPDATA\Lindersoft\SetupBuilder 10\Tmp folder now. If yes, remove the
files.

Friedrich

[NewsArchive]

Thanks for the explanation. All sorted now.

Andre