1. Error 1001 Fix

Hi LBennett610, 1. Have you made any recent changes on the computer? When was the last time it was working fine? Do you have any security software installed on the computer?

What was the result of SFC scan on the computer? Check and make sure that Windows installer service is running on the computer. A) Click Start, click Run then type services.msc and then press Enter to open Services.

B) Right-click the Windows Installer service, and then click Properties. C) If the Startup type box is set to Disabled, change it to Manual. D) Click OK to close the Properties window. E) Right-click the Windows Installer service, and then click Start. The service should start without errors.

Error 1001 on uninstall. It is working,on double clicking the installer is throwing the ERROR 1001 and installation. Wise, Advanced Installer, etc.

F) Click the File menu, and then click Exit. The file InstallUtilLib.dll is related to.Netframework on the computer. Check the version of.Netframework installed on the computer by using the Add remove programs list. Also check if there are any updates for.Netframework available in Windows update and install them,check if it helps.

If the above step fails then refer the below Microsoft article and try the steps mentioned, check if it helps. When you try to install an update for the.NET Framework 1.0, 1.1, 2.0, 3.0, or 3.5, you may receive Windows Update error code '0x643' or Windows Installer error code '1603'.

I have a.Net solution in Visual Studio 2008 that consists of 3 VB.Net projects and a C# project. I created a setup project that pulls it all together into an MSI installer.

Error 1001 Fix

Works perfectly. Until I added an installer class in my main project and added a custom action to the setup project to invoke it.

The resulting MSI works perfectly under Vista, calling the custom action and installing fine. When I run the installer under XP or Server 2k3, it gets right to the end and I get the following error: Error 1001. Unable to get installer types in the C: Program Files MyApp MyApp.exe assembly Running the MSI on an XP Pro box with installer logging enabled I get the following log entry when it burps: MSI (s) (CC!50) 15:40:42:796: Creating MSIHANDLE (28) of type 790531 for thread 2640 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.

Unable to get installer types in the C: Program Files MyApp MyApp.exe assembly. Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information. Any assistance in nailing this bug would be greatly appreciated!

My custom action uses the following CustomActionData - '/INSTALLDIR='TARGETDIR/ ' /SQLSERVER=TXTSQLSERVERNA ME /SQLUSER=TXTSQLUSERNAME /SQLPASSWORD=TXTSQLPASSWO RD' and I notice that if I remove the trailing '/' from the INSTALLDIR part I get the above error when installing on Vista. Not sure if this is related but thought I'd mention it JIC. There are specific icons available for vista messages that are not found in xp. I thnk you should perform a version check of the os and have 2 routines for your action based on OS rather than one. You can most of the items needed for this in the Environment.OSVersion assemblies or do a little testing with the following code. This was converted from: Dim osInfo As System.OperatingSystem = System.Environment.OSVersion Select Case osInfo.Platform Case System.PlatformID.Win32Windows ' Platform is Windows 95, Windows 98, Windows 98 Second Edition, ' or Windows Me. Select Case osInfo.Version.Minor Case 0 Console.WriteLine('Windows 95') Exit Select Case 10 If osInfo.Version.Revision.ToString = '2222A' Then Console.WriteLine('Windows 98 Second Edition') Else Console.WriteLine('Windows 98') End If Exit Select Case 90 Console.WriteLine('Windows Me') Exit Select End Select Exit Select Case System.PlatformID.Win32NT ' Platform is Windows NT 3.51, Windows NT 4.0, Windows 2000, or Windows XP.

Select Case osInfo.Version.Major Case 3 Console.WriteLine('Windows NT 3.51') Exit Select Case 4 Console.WriteLine('Windows NT 4.0') Exit Select Case 5 If osInfo.Version.Minor = 0 Then Console.WriteLine('Windows 2000') Else Console.WriteLine('Windows XP') End If Exit Select End Select Exit Select End Select Select all. I have answered my own question. For anyone that may be battling with the same issue here's the fix (workaround). Turns out the problem was Crystal Reports (isn't it always?).

In my project I have a number of forms with Crystal Reports viewers on them, they are stored in a folder named 'Reports'. Within the 'Reports' folder I also store.RPT report files that are loaded into the report viewers at runtime. I'm using Visual Studio 2008 and the main app is VB.Net. The report files are created using the standalone version of Crystal Reports XI Release 2 SP3.

When the.RPT files are included in the project.AND. I have a custom installer class present, my MSI installer throws the error mentioned in my original question (Error 1001). If I exclude the.RPT files from the project, the installer runs fine. I have tested this theory in a fresh cut down solution and the issue is repeatable. Once again Crystal Reports wastes days of my time.

It also bloats my installer from 7Mb to 90Mb when I add the Crystal Merge Modules. What a steaming heap of CR. For anyone with a similar issue but not exactly the same, the only way I could nail the issue (logging and debugging wasn't an option in this case due to the vagueness of error messages) was to copy the entire solution and systematically cut out swathes of code, rebuilding the installer and testing as I went. As soon as the reports were eliminated the error went away which zeroed me onto the actual cause.

Once again Crystal Reports wastes days of my time the good rule of thumb - reject whatever is pushed at you, 'cause this can't be anything but spam. Crystal reports in visual studio, throwing c'mons to buy full version - reject. Obfuscator throwing c'mon's - reject. Whatever is pushed, is practically always a junk - be it the miracles sold at 'as seen on tv', stock tips in your mailbox, trial tools included with visual studio, or trial antivirus preinstalled on new laptop.

It's never anything but spam - in general. I had the same error but the cause was due to the formatting of the CustomActionData and using TARGETDIR. I changed my formatting and it worked.Wron g: /TARGETDIR=TARGE TDIRWro ng: /TARGETDIR=TARGE TDIR /LAUNCHAPPLICATION=LAUNCH APPLICATIO NWrong: /TARGETDIR=TARGE TDIR/LAUN CHAPPLICAT ION=LAUNC HAPPLICATI ONC orrect: /TARGETDIR='TARG ETDIR ' Correct: /TARGETDIR='TARG ETDIR ' /LAUNCHAPPLICATION=LAUNCH APPLICATIO NR emeber to use a space between paramters. You need a space before each new /. For the crystal Reports induced problem that I had, i found an additional workaround that allows the reports to be included in the project: Make sure the Crystal Reports Redistributables are added as a pre-requisite to the setup project - you can then include the.RPT files in your project and the installer won't give 1001 errors. Alternatively make sure that CRRedist2008x86.msi (or x64) is installed on the client machine before hand.

LeonWyk: Any chance you could re-post your workaround without the HTML tags? Looks like a useful suggestion! I had the same error but the cause was due to the formatting of the CustomActionData and using TARGETDIR. I changed my formatting and it worked.

Linkin park end of the world. When you read the news Does it make you sick? Murder, money, and politics Gonna fill you up Get your bullshit fix It's the End Of The World Grab your crucifix. Jan 20, 2010 Mix - Linkin Park - End of the World (Dead by Sunrise) YouTube; Linkin Park - Fire (Dead by Sunrise). Oct 09, 2010 Linkin Park: Waiting For The End Live at Carson Honda Civic Tour 2012 - Duration: 5:21. The Winx Club vs Linkin Park - Waiting For The End of This Magical World of Wonder (S4 Part 2) the_winx_club_vs_linkin_park_-_waiting_for_the_end_of_this_magical.

Wrong: /TARGETDIR=TARGETDIR Wrong: /TARGETDIR=TARGETDIR /LAUNCHAPPLICATION=LAUNCH APPLICATIO N Wrong: /TARGETDIR=TARGETDIR/LAU NCHAPPLICA TION=LAUN CHAPPLICAT ION Correct: /TARGETDIR='TARGETDIR ' Correct: /TARGETDIR='TARGETDIR ' /LAUNCHAPPLICATION=LAUNCH APPLICATIO N Remeber to use a space between paramters. You need a space before each new /.