KB886903: "Installation Source Is Not Available"

I -- like many, many others -- am trying to fight my way through the
installation of KB886903. Someplace I read that if I downloaded the
fix I could install it manually.

I downloaded NDP1.1sp1-KB886903-X86.exe and ran that in my c:\temp
directory. It appeared to extract a file named M886903.msp.
Continuing to follow instructions, I right-clicked the .msp file in
Explorer and select the Apply menu item - it then appeared to start to
install (there was a very quick popup, but too fast for me to read...)
and then errored out with: "Installation source not available" error.

Any idea what it's looking for? Wouldn't you think if a programmer was
putting out an error message saying that he/she couldn't find
something, they would tell you what they were looking for?

Anyway, is there any particular log that may reveal more helpful info
so that I can get past this problem and into the next one?

Thanks...

I have exactly the same problem. Does someone has a solution?

"" wrote:

> I -- like many, many others -- am trying to fight my way through the
> installation of KB886903. Someplace I read that if I downloaded the
> fix I could install it manually.
>
> I downloaded NDP1.1sp1-KB886903-X86.exe and ran that in my c:\temp
> directory. It appeared to extract a file named M886903.msp.
> Continuing to follow instructions, I right-clicked the .msp file in
> Explorer and select the Apply menu item - it then appeared to start to
> install (there was a very quick popup, but too fast for me to read...)
> and then errored out with: "Installation source not available" error.
>
> Any idea what it's looking for? Wouldn't you think if a programmer was
> putting out an error message saying that he/she couldn't find
> something, they would tell you what they were looking for?
>
> Anyway, is there any particular log that may reveal more helpful info
> so that I can get past this problem and into the next one?
>
> Thanks...
>
>

> I right-clicked the .msp file in Explorer and select the Apply menu item
> - it then appeared to start to install (there was a very quick popup,
> but too fast for me to read...) and then errored out with:
> "Installation source not available" error.

Did you check for any log files which might have been created?
Perhaps there would be sufficient supplementary clues there?

I would just search for all files changed on that day, then order
them by Date Changed and then look at the ones which were
changed while the update was running. Of course another way
to find out what is going on would be to run FileMon while the
update was running and capture at least all writes.


Also, it seems that the .msp file extension can get overloaded.

http://filext.com/detaillist.php?extdetail=msp

(Google web search for
msp "file extension" "msi.patch"
)

What is yours set to?

<example>
>assoc | find /i "msp"
..grp=MSProgramGroup
..msp=Msi.Patch

>ftype | find /i "patch"
Msi.Patch="%SystemRoot%\System32\msiexec.exe" /p "%1" %*
</example>


If that seems Ok and you can't get enough clues from the existing files
it looks as if you could generate your own command line and specify
some additional logging.

http://www.microsoft.com/resources/d...s/msiexec.mspx

(Google web search for
msiexec logging verbose
)


HTH

Robert Aldwinckle
---


<> wrote in message news: ups.com...
>I -- like many, many others -- am trying to fight my way through the
> installation of KB886903. Someplace I read that if I downloaded the
> fix I could install it manually.
>
> I downloaded NDP1.1sp1-KB886903-X86.exe and ran that in my c:\temp
> directory. It appeared to extract a file named M886903.msp.
> Continuing to follow instructions, I right-clicked the .msp file in
> Explorer and select the Apply menu item - it then appeared to start to
> install (there was a very quick popup, but too fast for me to read...)
> and then errored out with: "Installation source not available" error.
>
> Any idea what it's looking for? Wouldn't you think if a programmer was
> putting out an error message saying that he/she couldn't find
> something, they would tell you what they were looking for?
>
> Anyway, is there any particular log that may reveal more helpful info
> so that I can get past this problem and into the next one?
>
> Thanks...
>