Got it!
I thought I had tried different combinations of the XML file but 
apparently not. New morning, fresh start.
It works when I remove:
<ServiceConfigFailureActions OnInstall="yes">
        <Failure Action="1" Delay="20000"/>
</ServiceConfigFailureActions>

Thanks for the logging tip, had no idea such thing existed.

 > since you now have the problem of your install being hard coded 
(MSSQL$SQLEXPRESS)
Yes I understand exactly what you mean. At this point though I have to 
limit various variables to a small set of possibilites and the SQL 
Server instance is one of them. The initial versions of the server 
software must have a local SQL Server Express installation with the 
default name SQLEXPRESS. The database inside will also have to have a 
known name.
I have made a database creation wizard (DDL & DML) in C# 
(next-next-finish type) which makes thorough checks on the SQL Server 
installation/instance and informs the person installing if anything is 
deviating from what should be.
I will now look into having IS2011 install and create this SQL Server 
instance.

Again, thanks!

/Jerra

On 15.2.2011 21:36, Christopher Painter wrote:
> BTW, I noticed that you are having your service have a dependency on a 
> database
> instance.   I'm not sure I would do this.
>
> I would suggest coding the service to spin up it's thread and return from the
> OnStart() ( assuming .NET terminology ).   Then in the thread I would have a
> connection manager that maintains the connection to the database and bubbles 
> up
> any state issues that are a problem.
>
> Basically I'm not sure this is a problem for the database to solve.   
> Especially
> since you now have the problem of your install being hard coded ( tightly
> coupled ) the one specific service name  which could be different depending on
> how things get deployed in the field.   (E.g.  MSSQL$SQLEXPRESS would be a
> different name for full blown SQL server )
>
> ---
> Christopher Painter, Author of Deployment Engineering Blog
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
>
>
> ----- Original Message ----
> From: Christopher Painter<chr...@deploymentengineering.com>
> To: General discussion for Windows Installer XML toolset.
> <wix-users@lists.sourceforge.net>
> Sent: Tue, February 15, 2011 1:21:58 PM
> Subject: Re: [WiX-users] Error 1939 when using<util:ServiceConfig>  on Windows
> Server 2008 R2
>
> Jerra-
>
> Read:
>
> http://support.microsoft.com/kb/223300
>
> you can also say  msiexec /i foo.msi /l*v install.log
>
> ---
> Christopher Painter, Author of Deployment Engineering Blog
> Have a hot tip, know a secret or read a really good thread that deserves
> attention? E-Mail Me
>
>
>
> ----- Original Message ----
> From: Jerra<beddel...@gmail.com>
> To: General discussion for Windows Installer XML toolset.
> <wix-users@lists.sourceforge.net>
> Sent: Tue, February 15, 2011 10:10:22 AM
> Subject: Re: [WiX-users] Error 1939 when using<util:ServiceConfig>  on Windows
> Server 2008 R2
>
> Thank you for your reply.
>
>> should be more information in the log file about the error.
> I have to ask you, which log file is that? Do you mean the event viewer
> / application log?
>
> /Jerra
>
>
> On 13.2.2011 18:02, Rob Mensching wrote:
>> If there is a problem in the WiX ServiceConfig custom actions then there
>> should be more information in the log file about the error. If the problem
>> is in the Windows Installer's service actions then it becomes an annoying
>> game of hide and seek to track down all the issues because the Windows
>> Installer error reporting is basically the same for all things that go
>> wrong.
>>
>> My recommendation is that since it works on one OS, try to narrow down what
>> is different on the other OS.
>>
>> On Fri, Feb 11, 2011 at 4:13 AM, Jerra<beddel...@gmail.com>   wrote:
>>
>>> Hi all,
>>> first email to this list. I have no experience of installers, Wix and
>>> what have you. I have managed so far by getting help by googling and
>>> also by some helpful individuals but now I am stuck.
>>>
>>> I have a C# Windows Service project. I have a Install Shield 2011
>>> Express project for installing this Windows Service. Because IS2011 do
>>> not directly support such installations I have made a Merge Module in
>>> Wix which I install via the IS2011 project.
>>> The final IS2011 installer has been working well (Windows 2003, Windows
>>> 2008 R2, Windows XP).
>>>
>>> I have since realized I need to add dependencies and recovery options
>>> for this Windows service. This I did by adding the elements :
>>> - ServiceDependency
>>> - ServiceConfig
>>> - ServiceConfigFailureActions
>>> - util:ServiceConfig
>>>
>>> I tried installing on a Windows Server 2003 32-bit and it worked OK. All
>>> properties were set for the service as expected.
>>> Installing on a 64-bit Windows Server 2008 R2 I get this error message:
>>> "Error 1939. Service 'xyz' (xyz) could not be configured. This could be
>>> a problem with the package or your permissions. Verify that you have
>>> sufficient privileges to configure system services."
>>>
>>> This is the portion of the XML file concerning the Windows Service:
>>> <ServiceInstall Id="installWS" Name="xyz" DisplayName="xyz"
>>> Description="abc" Start="auto" Type ="ownProcess" ErrorControl ="normal"
>>> Vital="yes">
>>>                      <ServiceConfig DelayedAutoStart="yes" OnInstall="yes"/>
>>>                      <util:ServiceConfig FirstFailureActionType="restart"
>>> SecondFailureActionType="restart" ThirdFailureActionType="restart"
>>> RestartServiceDelayInSeconds="60" />
>>>                      <ServiceConfigFailureActions OnInstall="yes">
>>>                        <Failure Action="1" Delay="20000"/>
>>>                      </ServiceConfigFailureActions>
>>>                      <ServiceDependency Id="MSSQL$SQLEXPRESS"/>
>>>                    </ServiceInstall>
>>>                    <ServiceControl Id="controlWS" Name="xyz" Remove="both"
>>> Stop ="both" Start="install" Wait ="yes"/>
>>>
>>>
>>> By blocking/removing these elements the installation works fine on the
>>> Windows Server 2008 R2.
>>> - ServiceConfig
>>> - ServiceConfigFailureActions
>>> - util:ServiceConfig
>>>
>>> After installation if done, I can then open up the Windows service "xyz"
>>> and manually set the recovery for the service to "restart" without any
>>> error messages.
>>>
>>>
>>> Any help greatly appreciated.
>>>
>>>
>>> Kind Regards
>>> Jerra
>>> -------------------------------
>>> Visual Studio Professional 2010
>>> Install Shield 2011 Express
>>> Wix 3.5&   Votive
>>> Windows XP
>>>
>>>
>>>
> ------------------------------------------------------------------------------
>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>>> Pinpoint memory and threading errors before they happen.
>>> Find and fix more than 250 security defects in the development cycle.
>>> Locate bottlenecks in serial and parallel code that limit performance.
>>> http://p.sf.net/sfu/intel-dev2devfeb
>>> _______________________________________________
>>> WiX-users mailing list
>>> WiX-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/wix-users
>>>
>>>
>>
>>
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
> ____________________________________________________________________________________
>
> Don't pick lemons.
> See all the new 2007 cars at Yahoo! Autos.
> http://autos.yahoo.com/new_cars.html
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
>
>
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to