Installation won't run. Error# 0004:000-200

[NewsArchive]

Hi

One of our customers, reports that one of our SetupBuilder installations
can't run on his Vista machine.

The error message is:
This application has encountered a problem and needs to close. Please
contact the vendor of this installation.

Error#: 0004:000-200

And the title is: SetupBuilder 6.6.2016

I have attached a screenshot.

The installation works fine on my own Vista-machine, and I know that
other customers has it working too.

Any clue on what the cause might be?

TIA

Kasper

[NewsArchive]

Hi Kasper,

> One of our customers, reports that one of our SetupBuilder installations
> can't run on his Vista machine.
>
> The error message is:
> This application has encountered a problem and needs to close. Please
> contact the vendor of this installation.
>
> Error#: 0004:000-200
>
> And the title is: SetupBuilder 6.6.2016
>
> I have attached a screenshot.
>
> The installation works fine on my own Vista-machine, and I know that
> other customers has it working too.
>
> Any clue on what the cause might be?

Just to check. This really *IS* an installation compiled with Build 2016,
correct? It is *NOT* an installation compiled with Build 2098?

http://www.lindersoft.com/forums/showthread.php?t=8925
http://www.lindersoft.com/forums/showthread.php?t=8924

If it is an install compiled with Build 2016, then that specific machine
does not allow to expand the installation engine because the CreateFile
Windows API fails with an invalid handle error. The new SetupBuilder builds
would provide us with more information in this area. It can be caused by
some kind of "protection" software.

Hope this helps.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Thank you for the quick response.

> Just to check. This really *IS* an installation compiled with Build 2016,
> correct? It is *NOT* an installation compiled with Build 2098?

I don't know anymore :-| I compiled it some time ago, and haven't the
actual installation I used for compilation at hand anymore.

Can I see it from the setup.exe?

> If it is an install compiled with Build 2016, then that specific machine
> does not allow to expand the installation engine because the CreateFile
> Windows API fails with an invalid handle error. The new SetupBuilder builds
> would provide us with more information in this area. It can be caused by
> some kind of "protection" software.

I will recompile the installation with the new SB (as soon as I have
installed it on my new machine), and will return when I know if that
makes any difference.

Best regards

Kasper

[NewsArchive]

Hi Kasper,

> Thank you for the quick response.
>
>> Just to check. This really *IS* an installation compiled with Build
>> 2016, correct? It is *NOT* an installation compiled with Build 2098?
>
> I don't know anymore :-| I compiled it some time ago, and haven't the
> actual installation I used for compilation at hand anymore.
>
> Can I see it from the setup.exe?

No. But if you have compiled it "some time ago" then I am sure it was not
Build 2098 (released three weeks ago on April 11, 2008).

> I will recompile the installation with the new SB (as soon as I have
> installed it on my new machine), and will return when I know if that makes
> any difference.

Please keep us posted.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich

The installer in question, is checking .Net framework exsistence, and if
it is missing, suggests to download and install it. Afterwards i
registers som .Net objects for COM Interop.

Normally it is called by ShellExecuteEx from my program (if the COM
objects are not registered), but my supporter asked them to check for
security software and temporarily disable it, and then run the installer
directly from the program folder.

I don't know if they disabled any security software (but I don't think
so), but they got the installer to run, and everything works now.

I compiled the installer with the new SB (no problems), but since the
problem was solved in the meantime, the customer never got the new
version, so I guess we won't learn anything this time :-)

Thank you for your help and time - problem is solved.

Best regards

Kasper

[NewsArchive]

Hi Kasper,

Thanks you for the update and the good news!

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 6.7
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner