Installer (Not typical)

  • Thread starter Thread starter Kevin Jones
  • Start date Start date
K

Kevin Jones

This this whole thing, and carefully. There are many
details that will elimilate possible responses if just
skimmed.

Hello, I am finding an error with Installer, but this is
one that I wasn't aware was possible, nor know what causes
it. I myself am a MCP, but I can't solve this one. I
Attempted to the "Microsoft Office 2003 Developer
Resources" with the Microsoft Installer. However,
immediately after I give the goahead to begin, I get the
error "Installation ended prematurely because of an
Error". I know it connot be the Installer Service because
it attempted to install. Service Problems cause MSI
Packages to never run in the first place. However, just
for the hay, I did it anyways, and got the same problem.
There I thought maybe the download got corrupted, so I
downloaded it again uncached. Same problem. I ran a file
compare utility, they were identical so a download
corruption is not likely.
I was beginning to get frustrated, so I did debugging on
the installer service right when it began till the error.
I found these error ocdes and descriptions, but I don't
know how to possibly resolve them.

Installer Code: 0xB2A (2858)
Installer Code: 0xB14 (2836)
Thread Exit Code: 0x643 (1603)

The first code 0xB2A is described as: "The data for the
bitmap Puzzle is not valid."

The Second: "The control Restore on the dialog FatalError
can not take focus."

Both indicate a problem with the package. The thread exit
code is just a simple error message. Could I really have
downloaded the package, twice, with a problem? I doubt
that, so does anyone have any ideas, or something that
would cause this? I have a tight policy setting on my
computer, but I lifted all on Installer to see if it would
help, none. Are there other security settings that might
do that? and what is the "Bitmap Image". If it is
referring to an actual photo image, I will be dissapointed
if I cannot install because the Office Logo is preventing
me.
 
it is possible that the package is indeed a bad MSI and the vendor needs to
recompile it
Try on another PC and see what happens

I had similar issues with other software MSI packages that I asked the
vendors too look into and magically they were fixed.
 
Back
Top