Brand new Dell laptop, nuke and paved. Wiped the drive completely,
installed Windows XP Pro SP2 on it. Installed Office 2003 Premium.
Installed VS 2005 Team Edition for Software Developers Trial from MSDN
Subscriber Downloads with the only things unchecked are VB.NET, J# and
Crystal Reports. Installed without problems.
I go to install the Product Documentation and it copies all the files to the
laptop and when it starts merging the indices, at the specific status:
"Merging Help Namespace ms-help://MS.MSDNQTR.v80.en" it throws
"an unhandled win32 exception occurred in msiexec.exe [2932]."
There are no errors or warnings in the Application or System event logs.
Opening up MSDN Product Documentation after this error results in a
unhandled exception that is logged to the application Event log:
Type: Error
Source: Microsoft Document Explorer
Event ID: 1000
Description: "Faulting application dexplore.exe, version 8.0.50727.42, stamp
4333d0b3, faulting module ntdll.dll, version 5.1.2600.2180, stamp 411096b4,
debug?0, fault address 0x000111de.
Now, I've wiped the drive and reinstalled everything from scratch 3 times
now and it does the exact same thing. I take the EXACT SAME media, in this
case a DVD, and install it to a desktop and it installs successfully.
How can I get this installed or at least working on this laptop?
1. Running Repair on the Product Documentation installation exhibits the
exact same behavior as installing it fresh, ie., it causes an exception.
2. Mounting the ISO image downloaded from MSDN and repairing still errors.
3. Burning a new DVD from the newly downloaded ISO image from MSDN
Subscriber downloads still errors.
4. Clearing out my C:\Windows\Temp and repairing still errors.
5. Copying the \MSDN directory to the hard drive and installing from there
still errors.
Help?!
Regards,
todd
"WenJun Zhang[msft]" - 22 Nov 2005 09:49 GMT
Hi Todd,
I think there are 2 possible causes of this issue:
1) Defective media that hit I/O problem with the laptop DVD-ROM.
To elimate the possibility, you can test installation again from a shared
DVD-ROM on your desktop.
2) Corrupt windows installer on the laptop.
If installing from shared DVD-ROM still meets the same error, the problem
is probably on Windows Installer. You can enable installer trace to have a
check.
314852 How to Enable Windows Installer Logging in Windows XP
http://support.microsoft.com/?id=314852
Or directly reinstall it:
Windows Installer 3.1 Redistributable (v2)
http://www.microsoft.com/downloads/details.aspx?familyid=889482FC-5F56-4A38-
B838-DE776FD4138C&displaylang=en
Hope the suggestions will be of help. Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Todd Brooks - 22 Nov 2005 14:45 GMT
I tried mounting the ISO image from the network and installing and that
didn't fix it. I also tried copying the files to the laptop's hard drive
and installing from there. Neither of those options worked.
This is a brand new laptop with a newly installed Windows XP Pro
installation.
I was able to get the documentation to install last night, the only problem
was that I narrowed it down to the Developer Knowledge Base and Technical
Articles option in the custom library install. If I didn't install that
selection, it installed just fine. I'm thinking it might possibly be a
defective ISO, except that I was able to do complete installations on my
workstation without problems using the same ISO and same DVD.
Regards,
todd
> Hi Todd,
>
[quoted text clipped - 29 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
"WenJun Zhang[msft]" - 23 Nov 2005 08:46 GMT
Hi Todd,
Has the OS on laptop been fully patched? Have you also test after upgrading
to the new version Windows installer?
To perform further troubleshooting, you can consider use filemon to trace
the I/O of msiexec.exe when the error occuring:
http://www.sysinternals.com/ntw2k/source/filemon.shtml
1) Launch filemon,stop capture and click filter on its toolbar.
Remove * and input: msiexec.exe as the included string.
2) Change font if necessary(need restart filemon).
3) Start capture before the error occurs.
4) After problem is reproduced.
5) Stop capture and look into the log. See if there is any obvious I/O
error.
You can paste the trace here and I'll be glad to help on reviewing it.
Thanks.
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.