Después de horas de pelea instentando instalar un servicio de windows con el installShield LE (limited edition) y visual studio 2013 siempre obtenía "error 1001" durante el intento de registro del servicio en el sistema. He pasado horas buscando por foros, web oficial.... y al final el error era:
¡¡En la pestaña 'Service' de installShield al crear el servicio DEBE TENER EL MISMO NOMBRE QUE LA PROPIEDAD 'SERVICENAME' DEL SERVICIO!!
Los pasos hasta llegar a este punto se pueden seguir en el artículo:
Información de interes de la pagina oficial de la empresa creadora de installShield Flexera
fuente:
https://community.flexerasoftware.com/showthread.php?193911-Error-1001-during-installation
-
Error 1001 during installation
I'm new in installshield , i created basic msi project using installshield 2010 .. build is succeeded , but unofrortunately when i tried to install the application and when it is about to finish the installtion , it gets two errors "Error 1001" then the installation rollback .. i wasted alot of time searching for a solution for that error , but i failed 
can any one help me 
thanks in advance
-
Error 1001 is often due to a problem in a .NET Installer Class. Unfortunately for .NET Installer Classes this single error code corresponds to several different underlying problems. In general I prefer to avoid use of .NET Installer Classes because they do not conform well with Windows Installer best practices.
Michael Urman - Staff Software Engineer - Flexera Software: InstallShield Team
-
but i'm using the installer class to attach the db used by my application , is there a way instead of installer class to attach the db ??!!
thanks for reply
-
Two issues I ran into using installer classes that resulted in getting the "1001" error:
- Make sure the correct version of InstallUtilLib.dll is installed in the MSI. If installing on a 32-bit OS, you'll need the 32-bit version. If installing on a 64-bit OS, you'll need the 64-bit version. Search the InstallShield help for where you specify the version of InstallUtilLib.dll.
- Within your installer class make sure you call the base class method of every method you're overriding. For example, in your Install() method, make sure the first thing you do is call base.Install().
Other than that, I would simplify my installer class to determine if it's a problem with the installer loading the class vs. a problem with the logic inside the class. Adding some logging inside your installer class helps too.
-
for installutillib.dll , i didn't find in installshield help what is the correct version for my OS , i have windows xp professional and i'm using installutill version "2.0.50727.3053 " , is that right?
for the installer class i'm sure that i call the base class method of every method i'm overriding
thanks
New User (0 Posts)
Reply With Quote
No hay comentarios:
Publicar un comentario