Other problems with installing

Dec 29, 2009 at 2:40 PM

Hi,

I tried to install Nodexl but it doesn´t work. I tried the last 4 versions . Everytime I get the Error MSG during the instalation: Error 1001: The file was not found ( German: Error 1001: Die Datei wurde nicht gefunden.) I have no idea what file ? I have double cheked every thing which I need for installing Nodexl. I repaired my Office 2007, VST2008. Installed Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.

I installed NodeXl on a laptop and it works fine. May be somebody knows waht Error 1001: The file was not found. means.

thanks for helping me

Dec 30, 2009 at 3:31 AM

1. Is there a "Details" button in the error message dialog box that gives you additional information?

2. Did you unzip the downloaded NodeXL Zip file into some folder, and then run the unzipped Setup.exe from that folder?  I ask because Windows Explorer can make it look like a Zip file is unzipped when it actually isn't, and that can cause problems on some machines.

-- Tony

Dec 30, 2009 at 10:39 AM

Hi Tony,

1. there is no "Details" button. Nothing except the OK button.

2. Yes, I Zip the file into a folder. I also try different locations and drives.

The error happens by the end of the installation process .

Mo

 

Jan 2, 2010 at 4:09 AM

There is something odd on your computer that is causing this, and unfortunately the cryptic error message that Windows is giving us isn't telling me much.

Windows has a feature called "Windows Installer Logging" that can be turned on in situations such as this to help programmers figure out what the problem is.  When you turn this feature on, Windows creates a log file in your Temp folder that details everything it does as it attempts to install a new program, and (hopefully) useful error information when the installation fails.  You can turn the feature on by either editing the registry, or (better) using the Local Group Policy Editor.  Here is an article that explains how to do this:

http://support.microsoft.com/kb/223300

You can open the Local Group Policy Editor by clicking Start, Run, and entering gpedit.msc.  You will want to use "vx" for the logging options.

Once you turn on Windows Installer Logging, run the NodeXL setup program again.  When it's done (meaning after it fails with the mysterious "1001" error message), look in your Temp folder for a new file that looks like MSIxxxxx.LOG.  Let me know when you get to that point and I'll send you an email address where you can send me the file.

Let me know if you have any trouble turning on Windows Installer Logging or finding the file it produces.

Thanks,
    Tony

Jan 3, 2010 at 5:58 PM

Hi, I have the same problem. I post here only the Error parts of the log.

MSI (c) (68:2C) [17:02:26:296]: Note: 1: 2727 2:  
DEBUG: Error 2826:  Control Line1 on dialog FolderForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FolderForm, Line1, to the right
DEBUG: Error 2826:  Control Line2 on dialog FolderForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FolderForm, Line2, to the right
DEBUG: Error 2826:  Control BannerBmp on dialog FolderForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FolderForm, BannerBmp, to the right
Info 2898. For VSI_MS_Shell_Dlg13.0_0_0 textstyle, the system created a 'MS Shell Dlg' font, in 0 character set, of 13 pixels height.
Action 17:02:27: FolderForm. Dialog created
MSI (c) (68:5C) [17:02:28:093]: Note: 1: 2727 2:  
MSI (c) (68:5C) [17:02:28:125]: Doing action: FindRelatedProducts
Action 17:02:28: FindRelatedProducts. Searching for related applications
Action start 17:02:28: FindRelatedProducts.
Action ended 17:02:28: FindRelatedProducts. Return value 1.
DEBUG: Error 2826:  Control Line1 on dialog ConfirmInstallForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: ConfirmInstallForm, Line1, to the right
DEBUG: Error 2826:  Control Line2 on dialog ConfirmInstallForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: ConfirmInstallForm, Line2, to the right
DEBUG: Error 2826:  Control BannerBmp on dialog ConfirmInstallForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: ConfirmInstallForm, BannerBmp, to the right
Action 17:02:28: ConfirmInstallForm. Dialog created
Action ended 17:02:28: WelcomeForm. Return value 1.
MSI (c) (68:6C) [17:02:28:671]: Doing action: ProgressForm
Action 17:02:28: ProgressForm. 
Action start 17:02:28: ProgressForm.
MSI (c) (68:6C) [17:02:28:671]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'ProgressForm' 
DEBUG: Error 2826:  Control Line1 on dialog ProgressForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: ProgressForm, Line1, to the right
DEBUG: Error 2826:  Control Line2 on dialog ProgressForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: ProgressForm, Line2, to the right
DEBUG: Error 2826:  Control BannerBmp on dialog ProgressForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: ProgressForm, BannerBmp, to the right
Action 17:02:28: ProgressForm. Dialog created
Action ended 17:02:28: ProgressForm. Return value 1.
MSI (c) (68:6C) [17:02:28:718]: Doing action: ExecuteAction




MSI (s) (74:DC) [17:02:41:984]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI12.tmp, Entrypoint: ManagedInstall
DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog, 
Error 1001. Error 1001. Could not create a persistence object for the specified file.
MSI (s) (74!B8) [17:03:01:281]: ? ? ??? ? ? ? ????? ????? ???????? A
MSI (s) (74:DC) [17:03:01:281]: Leaked MSIHANDLE (14) of type 790531 for thread 2488
MSI (s) (74:DC) [17:03:01:281]: Note: 1: 2769 2: _34382FCE_99B1_4765_9200_446E0A1F4149.install 3: 1 
DEBUG: Error 2769:  Custom Action _34382FCE_99B1_4765_9200_446E0A1F4149.install did not close 1 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: _34382FCE_99B1_4765_9200_446E0A1F4149.install, 1, 
Action ended 17:03:01: InstallExecute. Return value 3.


MSI (s) (74:B0) [17:03:01:359]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI13.tmp, Entrypoint: ManagedInstall
DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog, 
Error 1001. Error 1001. An exception occurred during the Rollback phase of the installation. This exception will be ignored and the rollback will continue. However, the machine might not fully revert to its initial state after the rollback is complete. --> The savedState dictionary does not contain the expected values and might have been corrupted.
MSI (s) (74!DC) [18:18:07:828]: ?¦?¦???¦?¦?¦?¦?????¦?????¦????????¦A
MSI (s) (74:B0) [18:18:07:828]: Leaked MSIHANDLE (16) of type 790531 for thread 5084
MSI (s) (74:B0) [18:18:07:828]: Note: 1: 2769 2: _4C94BC51_02BD_4147_9A80_F4D6762B441F.rollback 3: 1 
DEBUG: Error 2769:  Custom Action _4C94BC51_02BD_4147_9A80_F4D6762B441F.rollback did not close 1 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: _4C94BC51_02BD_4147_9A80_F4D6762B441F.rollback, 1, 
Rollback: _1EA389DE_E03A_429F_AAE4_C3BD350A5AEE.commit
MSI (s) (74:78) [18:18:07:828]: Executing op: ActionStart(Name=_1EA389DE_E03A_429F_AAE4_C3BD350A5AEE.commit,,)


MSI (c) (68:6C) [18:18:35:296]: Note: 1: 2235 2:  3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'FatalErrorForm' 
DEBUG: Error 2826:  Control Line1 on dialog FatalErrorForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalErrorForm, Line1, to the right
DEBUG: Error 2826:  Control Line2 on dialog FatalErrorForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalErrorForm, Line2, to the right
DEBUG: Error 2826:  Control BannerBmp on dialog FatalErrorForm extends beyond the boundaries of the dialog to the right by 3 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: FatalErrorForm, BannerBmp, to the right
Action 18:18:35: FatalErrorForm. Dialog created
Action ended 18:18:38: FatalErrorForm. Return value 1.
Action ended 18:18:38: INSTALL. Return value 3.


Jan 4, 2010 at 11:04 AM

Hi Tony,

Happy new year!

My log ist not so helpful :

Error 1001. Error 1001. Die Datei wurde nicht gefunden.
Error 1001. Error 1001. Während der Rollbackphase der Installation ist eine Ausnahme aufgetreten. Diese Ausnahme wird ignoriert, und der Rollback wird fortgesetzt. Der ursprüngliche Zustand des Computers wird jedoch möglicherweise nicht vollständig wiederhergestellt, nachdem der Rollback beendet ist. --> Das Wörterbuch savedState enthält nicht die erwarteten Werte und ist möglicherweise beschädigt.
=== Logging stopped: 04.01.2010  11:53:30 ===

Here in englisch:

Error 1001. Error 1001. File not found.
Error 1001. Error 1001. An exception occurred during the Rollback phase of the installation. This exception will be ignored and the rollback will continue.An exception occurred during the Rollback phase of the installation. This exception will be ignored and the rollback will continue. However, the machine might not fully revert to its initial state after the rollback is complete. -->The savedState dictionary does not contain the expected values and might have been corrupted.

 

Jan 5, 2010 at 12:53 AM

awaitzbe:

I need the entire log file.  Can you please temporarily edit your CodePlex profile to allow others to contact you?  Once you do that, I'll send you an email address where you can send me the log file, and then you can disallow contacts again.

Thanks,
    Tony

Jan 21, 2010 at 1:18 PM

Done!
Please contact me and I will send you the full log.
Thank you!

 

Feb 4, 2010 at 2:28 PM

Hi Tony,
I tried to install the latest version of NodeXL (from today), but the problem persists.
Please check it out, I am waiting a long time to use NodeXL again in my PC.
Thanks!

Feb 4, 2010 at 6:30 PM

I have not been able to figure out the cause of this error, so I've posted a question on the Microsoft developer forums.  I'll let you know if someone else is able to shed some light on the problem.

http://social.msdn.microsoft.com/Forums/en-US/vsto/thread/5bb02ebf-7638-45cb-85a3-7c4107cfe3a3

-- Tony

Feb 8, 2010 at 6:26 PM

awaitzbe:

A moderator on the Microsoft developer forum suggested a possible problem with other system software that NodeXL requires.  If you don't mind doing a little detective work, Microsoft provides a troubleshooting tool that can help track down this type of problem.  Here is what you do:

1. Download VSTO_PT.exe from http://www.microsoft.com/downloads/details.aspx?FamilyID=46b6bf86-e35d-4870-b214-4d7b72b02bf9&displaylang=en.

2. Run VSTO_PT.exe to install the VSTO Troubleshooter.

3. Run VSTOTroubleshooter.exe.  On my machine, this got installed at "C:\Program Files\Microsoft VSTO Power Tools 1.0\VSTO Troubleshooter\VSTOTroubleshooter.exe".  (It has no Start menu item or desktop shortcut.)

4. In the Microsoft VSTO 2008 Client Troubleshooter window, click Analyze System, then Save Results to File.

5. Send me the file.

Thanks,
    Tony

 

Feb 9, 2010 at 9:40 AM

Ok, I sent you the file and I am also uninstalling Visual Studio 2010 and its Beta2 x86 Runtime, maybe it's redirecting some dll and making problems. I will notify you if this solves or not.
Thank you,
awaitzbe

Feb 9, 2010 at 11:49 PM

You didn't mention that the troublesome machine has Visual Studio 2010 Beta installed on it.  In that case, all bets are off, and I don't think I'm going to be able to help you track down the NodeXL setup problem.  I wouldn't go so far as to uninstall Visual Studio 2010, because even after an uninstall, who knows what the state of the machine will be?

I can only suggest that you use NodeXL on a stable machine, if you have one available.

-- Tony

Feb 11, 2010 at 8:45 AM

I didn't know Visual Studio could be related to the problem, as other installations on this machine went fine. Anyway, thank you for your help.

Feb 11, 2010 at 5:16 PM

I can't say for certain that the Visual Studio Beta is causing the problem, but from what I've gathered, the problem can be caused by having the wrong version of one of the Visual Studio assemblies.  If I discover that the problem is elsewhere, I'll let you know.

Thanks,
    Tony