perkinm wrote: My observation: This is more than annoying, it is an inaccurate interpretation of the ServiceName that can be clearly and distinctly specified in the Service Project's ServiceInstaller module. This needs to be fixed! I can only assume such bugs are commonplace in the full version of InstallShield which is why I for certain cannot ask my boss to shell out the money for it. I am searching for a way to develop my project in VS2013 and build the setup in VS2010. This way, I get the best of both worlds. If it is possible, I don't know, but it will require some hacking for sure. ... View more

Yes, that worked (took so long because I had other things to do). Apparently InstallShield is hardcoded to use the Service1 installer class. You should really make this clear in the tool that you have this requirement. Now my problem is that InstallShield leaves out a dll file from the installation. The dll was added (with nuget) to the service after I created the ISLE project, but in ISLE I have already added the Primary output to the Files section. Why isn't the dll included? Another dll file added with nuget prior to creating the ILSE project is included in the msi file, though. The log has this to say: Adding file 'Common.Logging.dll' that is a dependency of component 'MonService.Primary_output' Adding file 'log4net.dll' that is a dependency of component 'MonService.Primary_output' But Quartz.dll is not included and my service cannot start because of that. Also, the log always says this: ISEXP : warning -6245: One or more of the project's components contain .NET properties that require the .NET Framework. It is recommended that the release include the .NET Framework. But in the Requirements section, .NET 4.5 Full Package is ticked. If that isn't enough, what is? ... View more

I don't even use Installer Classes (at least not consciously). I just want my binary to be installed and registered correctly in the registry so when it is started, it is NOT called Service1. ... View more

Is there any free installer/setup project type for Visual Studio 2013 that works well with services? ... View more

Seeing as error 1001 means error in custom action and that is supplied by Flexera so I guess Flexera has to help me out here. ... View more

I have investigated a bit more. I enabled MSI install log and got a huge log file. This is a short extract of the lines just before and after the error: MSI (s) (F8:10) [14:44:33:283]: Creating MSIHANDLE (24) of type 790536 for thread 18192 MSI (s) (F8:14) [14:44:33:284]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI57C4.tmp, Entrypoint: ManagedInstall MSI (s) (F8:08) [14:44:33:284]: Generating random cookie. MSI (s) (F8:08) [14:44:33:287]: Created Custom Action Server with PID 10532 (0x2924). MSI (s) (F8:3C) [14:44:33:318]: Running as a service. MSI (s) (F8:3C) [14:44:33:319]: Hello, I'm your 32bit Elevated custom action server. MSI (s) (F8!CC) [14:44:33:597]: Creating MSIHANDLE (25) of type 790531 for thread 10956 Error 1001. MSI (s) (F8!CC) [14:44:37:156]: MSI (s) (F8:14) [14:44:37:157]: Leaked MSIHANDLE (25) of type 790531 for thread 10956 MSI (s) (F8:14) [14:44:37:157]: Note: 1: 2769 2: _CD211F54BBAE331F5EBCBFBB104809B0.install 3: 1 Info 2769. Custom Action _CD211F54BBAE331F5EBCBFBB104809B0.install did not close 1 MSIHANDLEs. CustomAction _CD211F54BBAE331F5EBCBFBB104809B0.install returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) MSI (s) (F8:14) [14:44:37:161]: Closing MSIHANDLE (24) of type 790536 for thread 18192 Action ended 14:44:37: InstallFinalize. Return value 3. So, while I as a user see error 1001, a different error is noted in the log file and that error code is 1603. According to the isl file, this maps to IDS_ERROR_66 which has this to say: The file [2][3] is being held in use{ by the following process: Name: [4], ID: [5], Window Title: [6]}. Close that application and retry. I have no idea which file is being references or why. The installation folder doesn't even exist upon installation start. ... View more

The error as logged in the Windows Event log: The description for Event ID 11001 from source MsiInstaller cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer. If the event originated on another computer, the display information had to be saved with the event. The following information was included with the event: Product: MonService -- Error 1001. (NULL) (NULL) (NULL) (NULL) (NULL) the message resource is present but the message is not found in the string/message table It occurs twice, once during install and once during rollback of the install. ... View more

I did find another place where I forgot to set ServiceName (has to be set quite a few places) but once I did that, the installer always fails with error 1001 (i.e. during install). And as error 1001 is the most common error, it is of course not explained anywhere. How do I analyse this problem any further? Can anyone please provide a skeleton Windows Service project created in VS2013 with .NET 4.5 including a working ISLE installer, that when installed and started, does NOT use the service name Service1 nor does rely on the service class being called Service1? ... View more

Thank you for taking your time to try to help me, but your suggestions did not help. I already have named my service MonService using the ServiceName property in ProjectInstaller.cs->serviceInstaller1. I have successfully built 6 other services that are named correctly when installed using Microsofts old setup project. It just doesn't work with ISLE. The ServiceName property seems to be ignored. ... View more

Or is it possible to ad post-install scripts? And pre-remove scripts? If so, then I could make my own commands to register the exe file as a server and unregister it upon remove. So, basically make the "sc create ..." and "sc delete ..." commands myself. The current solution is pure ****. ... View more

I got it to work. The error is due to Flexera forcing your service to be called Service1 somewhere in their scripting engine. For reference, nowhere at all in my project does the name "Service1" exist yet once installed, when I manually start my service, the event log says "Service1" is installed. Even when using the -> 3 Configure the Target System -> Services section, the service added must be called Service1 despite Flexera's help text stating the service must match the name given in the service's Properties dialog box. Flexera? Could you please fix this bug? We can't have all our services being started be logged as "Service1"!!! ... View more

I do get 3 warnings during build, though: 2>ISEXP : warning : -7235: InstallShield could not create the software identification tag because the Tag Creator ID setting in the General Information view is empty. 2>ISEXP : warning : -6245: One or more of the project's components contain .NET properties that require the .NET Framework. It is recommended that the release include the .NET Framework. 2>ISEXP : warning : -6248: Could not find dependent file libc.dll, or one of its dependencies of component MonService.Primary_output The first one is valid as the Tag Creator ID is empty. I assume this is blocking the install. The second one is true as well, but as .NET is installed on my pc, this should present any error during install. The third (and last) warning I simply do not understand as I have not reference libc.dll in my project. Is this the culprit? ... View more

So I added the service in both Files view and Services view and build the project. Then I tried to install it only to be greeted with "Error 1001" during install. What am I supposed to deduct from that error? ... View more