Welcome to MSDN Blogs Sign in | Join | Help

How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

I have heard from several customers who have run into problems installing Visual Studio 2005 because the component named Microsoft Document Explorer 2005 fails to install and Visual Studio setup quits when that happens.  I wanted to give a bit more information about what this component is and where logging information can be found to attempt to track down why this installation might fail.

Document Explorer 2005 is a redistributable package that delivers the 8.0 version of dexplore.exe.  This is the help viewer that is used by Visual Studio 2005, and by other products such as the Windows SDK.  In previous versions of Visual Studio, dexplore.exe was installed as a part of the main Visual Studio MSI or as a part of the MSDN MSI, but in VS 2005, it was separated into its own standalone package, and it is installed as a prerequisite before the main Visual Studio MSI.

The setup for Document Explorer 2005 uses the same external UI handler as the .NET Framework 2.0 redistributable and SDK (described in more detail in this blog post and in this blog post).

Visual Studio 2005 setup runs the setup package for Document Explorer 2005 in silent mode.  In cases where this package fails during Visual Studio 2005 setup, you can run dexplore.exe directly from the folder <VS install disc>\wcu\DExplore\ in order to see the error message that is being generated.

This package creates the following log files in the %temp% directory on a system:

  • dd_dexploreui*.txt
  • dd_dexploremsi*.txt

In both of these cases, the * in the name of the files is a randomly generated ending to ensure that each time you run setup it will create a unique file and not overwrite existing log files.

If you do not get any useful error information by running the setup package directly, it can be useful to examine the contents of these log files.  In particular, you can search for the string return value 3 in dd_dexploremsi*.txt and that will usually lead you to the error that causes the setup package to fail.

If you have trouble locating error information, please contact me or leave a comment on this blog post and I will try to help.

 

Published Friday, January 20, 2006 6:58 PM by astebner

Comments

Thursday, February 02, 2006 5:06 AM by Samuel Jack

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

My computer has just been running like treacle, and I noticed that dexplore was using 99% CPU - but I didn't even have the help browser or Visual Studio open. Any idea why? I just killed it in the end - would that hurt?

Thanks,

Sam
Friday, February 03, 2006 3:53 PM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Samuel - I haven't heard of this issue before, but it is possible there is a bug in dexplore.exe. Killing it should not be a problem in this scenario. If you are able to consistently reproduce this issue, I encourage you to report a bug at http://lab.msdn.microsoft.com/productfeedback/ so the team that owns that file will be able to take a look.

Wednesday, February 08, 2006 4:18 PM by Jon Galloway

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

I ran into problems installing VS2005 after the .NET 2.0 runtime had already been installed. I uninstalled the 2.0 runtime and the VS2005 install went smoothly.
Tuesday, February 28, 2006 5:23 PM by Edwin

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Do you know about this trouble in Delphi 2005 Architect?
Tuesday, February 28, 2006 10:35 PM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Edwin - What kind of trouble are you seeing with Delphi 2005?  I am not sure I understand what problem you are having or how it relates to the topic of this blog post.
Friday, March 10, 2006 8:20 PM by Aaron Stebner's WebLog

# Document Explorer 2005 setup fails with a 1935 or 2908 error

A while ago, I posted an item regarding a possible cause and resolution for 1935 or 2908 errors during...
Thursday, April 13, 2006 12:15 PM by Richard

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

I had the same problem, but with the Visual C++ Express 2005 edition, by a downloaded ISO file. Unfortunaly, this CD image doesn't contain the 'DExplore' folder, so I'm unable to reinstall it.

I tried to find the redistribuable package, but didn't found it. How can solve this problem ?

Note: I've currently a complete setup of Visual Studio.Net 2003, could the dexplore from 7.1 interfer with the new one ?
Thursday, April 13, 2006 8:42 PM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Richard - The Visual C++ 2005 Express Edition does not require Document Explorer to install or run correctly.  It sounds like you might be running into a different error than the one described in this blog post.  Can you please provide some more detail about exactly what error(s) you are seeing and I can try to help figure out how to fix it?
Friday, April 14, 2006 4:13 AM by Richard

# Install problem with VCExpress2005

Of course :-)

When I launched the installation process, I had several message boxes saying: 'The Application Data folder for Microsoft Document Explorer could not be created' (I guess for each sub-msi execution), but VCEexpress installation finished.

When I start VCExpress, I've the same message (in fact, each time I want to access the StartPage or  an help document).

The installation created a folder named Help8 in my 'Microsoft shared' folder, which contains dexplore.exe, and I've the same message when I launch it.

Thanks for support
Sunday, April 16, 2006 2:32 PM by smith

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

VS 2005 Pro a no-go on Vista64 Feb ctp. Same deal:  Windows Document Explorer.  dd_exploreXXXX file shows Error 1935: error during installation of assembly 'Microsoft.VC80.ATL, type="8.0.50727.42", etc.  WHat is rweally interesting is that many of the logged lines say "(x86)" which should not be the case on my 64bit AMD machine running Vista64.

And you can't use any Add/Remove programs in Vista because thsi program does not show up in the list of "user" programs OR in the Advanced Windows programs list.

The machine is a dual boot of XPPro32 and Vista Feb CTP.  Just for laughs I tried installing VS2005 and forcing the install path to the D: drive instead of the C:\ drive and it worked.   But remember that the D:\ drive under the Vista boot is actually the xp32's root drive (due to the virtualization of drive letters in a multiboot setup). Even odder is that when I do that I definietly get "(x64)" folders created in the XP32's Program Files folder.

I don't know how anyone is able to run VS2005 on a "pure" Vista64, it simply will not install for me.  Going back to what works, will check on Vista again AFTER it is RTM ;-)
Wednesday, April 19, 2006 12:23 AM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Richard - I am not sure what would cause the error you describe, because Document Explorer is not a prerequisite for any of the Express Editions.  You might want to use the steps listed at http://blogs.msdn.com/astebner/archive/2005/12/16/504906.aspx to manually remove and attempt to reinstall Visual C++ 2005 Express Edition.  I'm sorry I'm not able to be more helpful here.

Hi Smith - I have not heard of any issues installing VS 2005 on any recent Vista 64-bit builds.  I will try this out on my test machine the next time I have a 64-bit build installed and see if I can figure anythough out.  I'm sorry for the inconvenience that this has caused.  I hope it won't cause you to give up on future beta builds of Windows Vista.
Friday, May 05, 2006 8:29 PM by zhiwen li

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

my error code is 2908, could someone post the potential cause again? thanks
Friday, May 05, 2006 8:44 PM by Zhiwen Li

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

find this error message during installing Microsfot Document Explorer 2005:

"MSI (s) (AC:6C) [15:54:37:715]: Executing op: ComponentRegister(ComponentId={8E3A9B11-FBB5-4D8A-8B51-4A7A5FFB8717},KeyPath=C:\Program Files\Common Files\Microsoft Shared\MSEnv\PublicAssemblies\Microsoft.VisualStudio.VSContentInstaller.dll,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0)
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2908. The arguments are: {54A515BC-5DCD-4125-A877-357359D2D717}, , "

However I don't even find any dir of "\PublicAssemblies" under "C:\Program Files\Common Files\Microsoft Shared\MSEnv\", Can someone enlighten me the cause of this? thx
Friday, May 05, 2006 11:01 PM by zhiwen li

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

found it! the .net framework 2.0 screwed up on my system, reinstalled 2.0 rtm 50727, then the problem is fixed. thanks.
Thursday, June 22, 2006 1:17 PM by jcarlen

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi when i´m trying to deploy Vs2005 I get this application event error.

the description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: .NET Runtime version 1.1.4322.573- Config parser error: Error parsing C:\WINDOWS\system32\URTTemp\config\machine.config
Parser returned error 0x80070003.

then directly after i get this one.
Product: Microsoft Document Explorer 2005 -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2337. The arguments are: , ,

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

can you help me?
best regard
/johan
Friday, June 30, 2006 11:18 PM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Jcarlen - Typically that .NET Runtime event log entry is benign so that probably can be ignored.  Can you please zip and send me the log file named %temp%\dd_dexploremsi*.txt so I can try to take a look?  You can send it to Aaron.Stebner (at) microsoft (dot) com.
Tuesday, July 04, 2006 3:07 AM by jcarlen

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi. I solved the problem.
It was the Dot NEt 1.1 that needed to be restarted beför VS was installed.

But i have another problem when running Vs 2005 Team suite as a User i´m getting this message

The proper type libary could not be found in the system regitry. An attempt to repair this condition faild because you do not have the permissons to write to the system registry or because the libery could not be found.

I understand that this has to do with that i´m a user but do you know any workaround i working in a school so we are depolying vs to 100 machine it isn´t an option to run around to all coputers logging in as an Admin.

/Johan
Tuesday, July 04, 2006 10:46 PM by Frank Babz

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

I tried 3 failed times until I found your article.  Followed you suggestion to run dexplore.exe directly on the CD and it installed smoothly with NO error messages.  VS2005 now installed.  Go figure....
Wednesday, July 12, 2006 11:40 PM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Jcarlen - There is an article at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dv_vstechart/html/tchDevelopingSoftwareInVisualStudioNETWithNon-AdministrativePrivileges.asp that describes how to use VS .NET 2003 as a normal user.  I haven't been able to find a similar article for Visual Studio 2005 however.  I would suggest posting the exact error messages that you receive to the MSDN Forums (http://forums.microsoft.com) and see if some other folks have some advice that might be helpful.
Saturday, October 28, 2006 4:16 AM by zjm84812

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi,There 's some error while i'm installing vs.net 2005:

[10/28/06,16:10:18] Microsoft Document Explorer 2005: [2] Setup Failed on component Microsoft Document Explorer 2005

[10/28/06,16:10:24] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.

[10/28/06,16:10:24] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()

[10/28/06,16:10:47] VS70pgui: [2] DepCheck indicates Microsoft Document Explorer 2005 is not installed.

[10/28/06,16:10:48] VS70pgui: [2] DepCheck indicates Microsoft Visual Studio 2005 Team Edition for Software Developers - ENU was not attempted to be installed.

[10/28/06,16:10:48] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3

before installing 2005,I installed vs.net 2003 and I got an error while uninstall vs .net 2003 too... (I have deleted the keys of .net framework 2.0 in regedit before installing .net2005),what's the source of these problems? thanks  :)

Sunday, October 29, 2006 10:53 AM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Zjm84812 - The .NET Framework 2.0 is a required prerequisite for Visual Studio 2005.  You will need to reinstall/repair the .NET Framework 2.0 before you can install VS 2005.  That would also cause Document Explorer 2005 to fail.

What kind of error did you get while uninstalling VS 2003?  The log file %temp%\vsmsilog*.txt should show that error.  If you can zip and send it to me at Aaron.Stebner (at) microsoft (dot) com, I will try to take a look and see if I can figure anything out for you.

Friday, February 16, 2007 9:35 PM by Aaron Stebner's WebLog

# Visual Studio 2005 and .NET Framework 2.0 Setup Troubleshooting Guide

Where to get Visual Studio 2005 and the .NET Framework 2.0 Where to download the .NET Framework 2.0 redistributable

Tuesday, May 22, 2007 3:56 AM by ALZDBA

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

I've got issues during install of SQL2005 BI-dev-studio (=vs2005)

It says "the application datafolder for Microsoft document explorer could not be created" and "the application datafolder for Visual studio macros could not be created"

- Is this critical ?

- How can I solve this ?

(I'm using XP sp2 with a hidden x-drive and a mapped P-drive (refering to this x-drive)

Can this be an issue ?

)

Wednesday, May 23, 2007 11:16 AM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Alzdba - This error typically means that there was some kind of problem running the action dexplore.exe /setup or devenv.exe /setup during installation.  I would suggest running both of these command lines again manually to try to resolve this issue.  You can find dexplore.exe at C:\Program Files\Common Files\Microsoft Shared\Help 8 and devenv.exe at C:\Program Files\Microsoft Visual Studio 8\Common7\IDE.

Friday, June 08, 2007 9:14 AM by dzjien

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

This is the error i get when upgrading VS.NET 2003 to VS.NET 2005 (i only have an upgrade available, so uninstalling is not an option):

Error 1935.An error occurred during the installation of assembly 'EnvDTE,Version="8.0.0.0",PublicKeyToken="b03f5f7f11d50a3a",Culture="neutral",FileVersion="8.0.50727.42"'. Please refer to Help and Support for more information. HRESULT: 0x80070020. assembly interface: IAssemblyCacheItem, function: Commit, component: {DA28CA4A-27CA-486A-923F-5A4317BB70CE}

Have tried installing the MS document explorer directly from cd...still the error. Deleted the HKLM reg-key...still the error. What's next? :-(

Friday, June 08, 2007 11:26 AM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Dzjien - The error code you are receiving (0x80070020) means that the process cannot access the file because it is being used by another process.  You might want to reboot and then try one of the following workarounds to see if they help resolve this issue:

http://blogs.msdn.com/astebner/archive/2006/11/25/disabling-services-with-msconfig-to-work-around-setup-failures.aspx

http://blogs.msdn.com/astebner/archive/2006/09/04/solving-setup-errors-by-using-the-subinacl-tool-to-repair-file-and-registry-permissions.aspx

Hopefully one of these will help.

Monday, June 11, 2007 1:44 AM by dzjien

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Aaron!

Brilliant! Thanx! You just saved me a few more hours of digging......

Tuesday, June 26, 2007 1:23 PM by puneetgarg

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

hi Aaron,

      When i was installing visual studio 2005 i encountered the same error and i tried the stuff mentioned in ur blog that is executed dexplorer.exe directly didnt work, then i repaired

ms.net framework 2.0 then installed again but didnt work out.In my pc,ms visual J#.net redistributable package 1.1 is installed.It gave me the error first time after successfully finishing installation of parser 6.0 then it gave problem at dexplorer and didnt touch rest of things. that is setup of 2005.

I have previously tried to install vs.net 2003 that also gave error after installing all prerequisites.plz get me out of this prblm,it has already taken lot of time.

Wednesday, June 27, 2007 12:16 AM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Puneetgarg - I looked at the logs that you sent me via email, and both VS 2003 and Document Explorer 2005 are failing for the same reason on your system.  For VS 2003, I see the following error:

MSI (s) (60:A4) [16:44:25:437]: Invoking remote custom action. DLL: G:\WINDOWS\Installer\MSIB5A.tmp, Entrypoint: BeginTransaction

IHxRegisterSession::CreateTransaction() returned 8004036e.

BeginTransaction() ERROR: Attempt failed because another transaction was running.

For Document Explorer 2005, I see the following error:

06/26/07 18:10:22 DDSet_Status: BeginTransaction()->IHxRegisterSession::CreateTransaction() returned 8004036e.

06/26/07 18:10:22 DDSet_Error: BeginTransaction()->Attempt failed because another transaction was running.

Normally, if you reboot your system and try running setup again, it will resolve this error about another transaction running.  If that doesn’t help, I’d suggest trying to use MsConfig to disable unnecessary services and then trying to run setup again.  You can find information about how to do that at http://blogs.msdn.com/astebner/archive/2006/11/25/disabling-services-with-msconfig-to-work-around-setup-failures.aspx.

Hopefully this helps.

Thursday, October 11, 2007 3:03 AM by shaper

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi,

same problem with VS2008 Beta 2 and Vista x64. I had to repair Document explorer from disc and then it worked.

Sven

Tuesday, November 06, 2007 6:00 AM by Installing Visual Studio 2005 on Vista « Cow Powered

# Installing Visual Studio 2005 on Vista &laquo; Cow Powered

PingBack from http://cowpowered.wordpress.com/2007/11/06/installing-visual-studio-2005-on-vista/

Saturday, December 08, 2007 6:41 PM by cbandlam

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Check for C:\Documents and Settings\All Users\Application Data\Microsoft Help\Rgstrtn.lck. If you don't have another installation process going on, just delete it.

http://www.helpware.net/mshelp2/h2reg_FAQ.htm

My Office 2007 installation failed few days back and "apparently" it doesn't rollback properly. errrr....

2 agonizing hours. Hope this helps somebody.

Chaitanya

Monday, December 10, 2007 12:21 PM by Aaron Stebner's WebLog : Possible workaround for errors during installation of Document Explorer 2005 and 2008

# Aaron Stebner's WebLog : Possible workaround for errors during installation of Document Explorer 2005 and 2008

PingBack from http://blogs.msdn.com/astebner/archive/2007/12/10/6725685.aspx

Monday, December 10, 2007 1:51 PM by MSDN Blog Postings » Possible workaround for errors during installation of Document Explorer 2005 and 2008

# MSDN Blog Postings &raquo; Possible workaround for errors during installation of Document Explorer 2005 and 2008

PingBack from http://msdnrss.thecoderblogs.com/2007/12/10/possible-workaround-for-errors-during-installation-of-document-explorer-2005-and-2008/

Monday, March 17, 2008 10:45 AM by bobby_vtj

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Dudes,

 I have encountered the same problem, but to my surprise, just running the document explorer application (thats come in the product suite under folder \msdn\DExplore\DExplore.exe) has resolved the issue. Please see whether it can help you out. Further to your note I havn't uninstalled VS as such. When running the DExplore.exe select the 'Repair' mode

Thanks and Best Regards

Bobby J.

Saturday, November 08, 2008 8:09 PM by ajmm

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

this error code go out :

[11/09/08,16:43:38] Microsoft Document Explorer 2005: [2] Error code 1601 for this component means "No se tiene acceso al servicio de Windows Installer. Es posible que esto ocurra si está ejecutando Windows en modo a prueba de errores, o si Windows Installer no está correctamente instalado. Póngase en contacto con el personal de soporte técnico para obtener asistencia.

"

[11/09/08,16:43:38] Microsoft Document Explorer 2005: [2] Setup Failed on component Microsoft Document Explorer 2005

[11/09/08,16:43:42] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.

[11/09/08,16:43:42] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()

[11/09/08,16:43:51] VS70pgui: [2] DepCheck indicates Microsoft Document Explorer 2005 is not installed.

[11/09/08,16:43:51] VS70pgui: [2] Unknown component status forPaquete de idioma de Microsoft Document Explorer 2005 - Español

[11/09/08,16:43:51] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3

[11/09/08,16:43:51] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0

[11/09/08,16:43:51] VS70pgui: [2] Unknown component status forMicrosoft Visual J# 2.0 Redistributable Package

[11/09/08,16:43:52] VS70pgui: [2] Unknown component status forPaquete de idioma de Microsoft Visual J# 2.0 Redistributable - Español

[11/09/08,16:43:52] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition

[11/09/08,16:43:52] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0

[11/09/08,16:43:52] VS70pgui: [2] Unknown component status forMicrosoft SQL Server 2005 Express x86

[11/09/08,16:48:39] Microsoft Document Explorer 2005: [2] Error code 1601 for this component means "No se tiene acceso al servicio de Windows Installer. Es posible que esto ocurra si está ejecutando Windows en modo a prueba de errores, o si Windows Installer no está correctamente instalado. Póngase en contacto con el personal de soporte técnico para obtener asistencia.

"

[11/09/08,16:48:39] Microsoft Document Explorer 2005: [2] Setup Failed on component Microsoft Document Explorer 2005

[11/09/08,16:48:43] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.

[11/09/08,16:48:43] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()

[11/09/08,16:48:55] VS70pgui: [2] DepCheck indicates Microsoft Document Explorer 2005 is not installed.

[11/09/08,16:48:55] VS70pgui: [2] Unknown component status forPaquete de idioma de Microsoft Document Explorer 2005 - Español

[11/09/08,16:48:55] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3

[11/09/08,16:48:55] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0

[11/09/08,16:48:55] VS70pgui: [2] Unknown component status forMicrosoft Visual J# 2.0 Redistributable Package

[11/09/08,16:48:55] VS70pgui: [2] Unknown component status forPaquete de idioma de Microsoft Visual J# 2.0 Redistributable - Español

[11/09/08,16:48:55] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition

[11/09/08,16:48:55] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0

[11/09/08,16:48:55] VS70pgui: [2] Unknown component status forMicrosoft SQL Server 2005 Express x86

[11/09/08,17:00:53] Microsoft Document Explorer 2005: [2] Error code 1601 for this component means "No se tiene acceso al servicio de Windows Installer. Es posible que esto ocurra si está ejecutando Windows en modo a prueba de errores, o si Windows Installer no está correctamente instalado. Póngase en contacto con el personal de soporte técnico para obtener asistencia.

"

[11/09/08,17:00:53] Microsoft Document Explorer 2005: [2] Setup Failed on component Microsoft Document Explorer 2005

[11/09/08,17:11:05] Microsoft Document Explorer 2005: [2] Error code 1601 for this component means "No se tiene acceso al servicio de Windows Installer. Es posible que esto ocurra si está ejecutando Windows en modo a prueba de errores, o si Windows Installer no está correctamente instalado. Póngase en contacto con el personal de soporte técnico para obtener asistencia.

"

[11/09/08,17:11:06] Microsoft Document Explorer 2005: [2] Setup Failed on component Microsoft Document Explorer 2005

[11/09/08,17:11:12] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.

[11/09/08,17:11:12] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()

[11/09/08,17:11:20] VS70pgui: [2] DepCheck indicates Microsoft Document Explorer 2005 is not installed.

[11/09/08,17:11:20] VS70pgui: [2] Unknown component status forPaquete de idioma de Microsoft Document Explorer 2005 - Español

[11/09/08,17:11:20] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition

[11/09/08,17:11:20] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0

[11/09/08,17:21:04] Microsoft Document Explorer 2005: [2] Error code 1601 for this component means "No se tiene acceso al servicio de Windows Installer. Es posible que esto ocurra si está ejecutando Windows en modo a prueba de errores, o si Windows Installer no está correctamente instalado. Póngase en contacto con el personal de soporte técnico para obtener asistencia.

"

[11/09/08,17:21:05] Microsoft Document Explorer 2005: [2] Setup Failed on component Microsoft Document Explorer 2005

[11/09/08,17:21:11] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.

[11/09/08,17:21:11] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()

[11/09/08,17:21:18] VS70pgui: [2] DepCheck indicates Microsoft Document Explorer 2005 is not installed.

[11/09/08,17:21:18] VS70pgui: [2] Unknown component status forPaquete de idioma de Microsoft Document Explorer 2005 - Español

[11/09/08,17:21:18] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition

[11/09/08,17:21:18] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0

[11/09/08,19:59:35] Microsoft Document Explorer 2005: [2] Error code 1601 for this component means "No se tiene acceso al servicio de Windows Installer. Es posible que esto ocurra si está ejecutando Windows en modo a prueba de errores, o si Windows Installer no está correctamente instalado. Póngase en contacto con el personal de soporte técnico para obtener asistencia.

"

[11/09/08,19:59:35] Microsoft Document Explorer 2005: [2] Setup Failed on component Microsoft Document Explorer 2005

[11/09/08,19:59:42] setup.exe: [2] ISetupComponent::Pre/Post/Install() failed in ISetupManager::InstallManagerHelper() with HRESULT -2147023293.

[11/09/08,19:59:42] setup.exe: [2] Component error string not specified in ISetupManager::AddToActionResultCollection()

[11/09/08,19:59:53] VS70pgui: [2] DepCheck indicates Microsoft Document Explorer 2005 is not installed.

[11/09/08,19:59:53] VS70pgui: [2] Unknown component status forPaquete de idioma de Microsoft Document Explorer 2005 - Español

[11/09/08,19:59:53] VS70pgui: [2] Unknown component status for.NET Compact Framework 1.0 SP3

[11/09/08,19:59:53] VS70pgui: [2] Unknown component status for.NET Compact Framework 2.0

[11/09/08,19:59:53] VS70pgui: [2] Unknown component status forMicrosoft Visual J# 2.0 Redistributable Package

[11/09/08,19:59:53] VS70pgui: [2] Unknown component status forPaquete de idioma de Microsoft Visual J# 2.0 Redistributable - Español

[11/09/08,19:59:53] VS70pgui: [2] Unknown component status forSQL Server 2005 Mobile Edition

[11/09/08,19:59:53] VS70pgui: [2] Unknown component status forMicrosoft Device Emulator version 1.0

[11/09/08,19:59:53] VS70pgui: [2] Unknown component status forMicrosoft SQL Server 2005 Express x86

could you help me please

Sunday, November 09, 2008 5:32 PM by astebner

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Hi Ajmm - This 1601 error means that there is something wrong with the Windows Installer service on your system.  I'd suggest first trying to reboot and running the install again.

If that doesn't help, you can use the following steps to attempt to repair the Windows Installer service on Windows XP or Windows Server 2003 (these steps will not work on Windows Vista though, so there is no need to try them there):

1.  Click on the Start menu, choose Run, type cmd and click OK

2.  Run this command:  msiexec /unregister

3.  Run this command:  msiexec /regserver

4.  Reboot

5.  Try to install again

If you are running Windows Vista or the above steps do not help, then you may want to try to install Windows Installer 4.5 to see if that helps fix this error.  You can find the download location for Windows Installer 4.5 at http://www.microsoft.com/downloads/details.aspx?FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4.

Thursday, November 13, 2008 12:15 AM by vdpittman

# re: How to troubleshoot failure to install Document Explorer 2005 during VS 2005 setup

Aaron,

I just wanted to thank you for pointing me to  to the solution of a vexing problem, and share the solution with your other readers.

I was trying to install VS2005 Standard Edition on a brand new computer I had just purchased.  The computer is a HP CQ50 laptop, 32-bit dual-core (2x2GHz), 3GB RAM, running Vista Home Premium SP1.  

The VS2005 kit I have consists of two DVDs (VS) and two CDs (MSDN).  The install always hung up at the end of the first DVD, saying it was installing Document Explorer.  Often it would become totally unresponsive.

I followed your link to "Microsoft Visual Studio 2005 Setup Issues" (http://mdsn.microsoft.com/en-us/vs2005/aa718687.aspx)

I read the instructions in Section 1.3.6 ("Installing Visual Studio 2005 from CD fails. A network installation is requested.")

I copied the files to the hard disk, instead of a network share, edited the INI files as suggested, and the install worked.  I did have to restart the MDSN install after the VS install, but that has installed successfully too.

I had the wireless disabled, and was not connected to Ethernet... I don't know whether that made a difference or not.

This same kit had installed on my old XP/SP2 machine flawlessly about two years ago.

Thanks for pointing me in the right direction.  I am in your debt.

Many thanks!

Darrell Pittman

v-dapitt AT microsoft DOT com

Friday, June 19, 2009 1:12 PM by Aaron Stebner s WebLog How to troubleshoot failure to install | debt solutions

# Aaron Stebner s WebLog How to troubleshoot failure to install | debt solutions

PingBack from http://debtsolutionsnow.info/story.php?id=4037

Anonymous comments are disabled
 
Page view tracker