MSI unable to start the SQL instance service

Hi,
I am deploying a SQL on a three node active cluster setup. Each node will
have a SQL instance running in the cluster virtual server context. This is
the baseline setup required for deploying application databases on the three
SQL instances. Application databases are deployed using an MSI which creates
the database, roles, accounts etc.
The problem that I am facing is that when the Application Database MSI
executes, it will first recycle the SQL instance service to ensure that it is
up and running. At that point it is successfully able to stop the service but
fails to start the service giving the below error:
Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11920
Date: 10/12/2006
Time: 2:50:05 PM
User: myDomain\sql_account
Computer: SQLSERVER01
Description:
Product: Application Database -- Error 1920. Service 'MSSQL$\VS01'
(MSSQL$\VS01) failed to start. Verify that you have sufficient privileges to
start system services.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
The SQL service account has all the permissions on the machine. It is a
domain admin account with local admin privileges. It also has SystemAdmin
role on the SQL instance.
Can anyone tell me if there are any permissions that are missed that could
cause the above error?
Is there a security setting that I can check to validate permissions?
Thanks,
Mehul
The SQL service exists on all three nodes, but is only supposed to run on
one node at a time and then only under the control and direction of the
Cluster Service. You do not have to cycle the service to determine if it is
running, you can use the cluster.exe application or the WMI application
interface to determine if aclustered instance is running.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:6C83D7C2-0514-4195-A46E-FE6D9C0E8831@.microsoft.com...
> Hi,
> I am deploying a SQL on a three node active cluster setup. Each node will
> have a SQL instance running in the cluster virtual server context. This is
> the baseline setup required for deploying application databases on the
> three
> SQL instances. Application databases are deployed using an MSI which
> creates
> the database, roles, accounts etc.
> The problem that I am facing is that when the Application Database MSI
> executes, it will first recycle the SQL instance service to ensure that it
> is
> up and running. At that point it is successfully able to stop the service
> but
> fails to start the service giving the below error:
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 11920
> Date: 10/12/2006
> Time: 2:50:05 PM
> User: myDomain\sql_account
> Computer: SQLSERVER01
> Description:
> Product: Application Database -- Error 1920. Service 'MSSQL$\VS01'
> (MSSQL$\VS01) failed to start. Verify that you have sufficient privileges
> to
> start system services.
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> The SQL service account has all the permissions on the machine. It is a
> domain admin account with local admin privileges. It also has SystemAdmin
> role on the SQL instance.
> Can anyone tell me if there are any permissions that are missed that could
> cause the above error?
> Is there a security setting that I can check to validate permissions?
> Thanks,
> Mehul
|||Geoff,
The configuration is an Active-Active-Active one. Hence the SQL service will
run on each node.
"Geoff N. Hiten" wrote:

> The SQL service exists on all three nodes, but is only supposed to run on
> one node at a time and then only under the control and direction of the
> Cluster Service. You do not have to cycle the service to determine if it is
> running, you can use the cluster.exe application or the WMI application
> interface to determine if aclustered instance is running.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:6C83D7C2-0514-4195-A46E-FE6D9C0E8831@.microsoft.com...
>
>
|||Then you have three instances, which will show up as three different
services on each node. You still need to leave them under the control of
the cluster service.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:3D1AD5FD-FB0A-4C46-A858-E8523BBB61A4@.microsoft.com...[vbcol=seagreen]
> Geoff,
> The configuration is an Active-Active-Active one. Hence the SQL service
> will
> run on each node.
> "Geoff N. Hiten" wrote:
|||Geoff,
Yes this is correct.
If the SQL instance services need to be restarted, what is the recommended
way?
"Geoff N. Hiten" wrote:

> Then you have three instances, which will show up as three different
> services on each node. You still need to leave them under the control of
> the cluster service.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Mehul" <Mehul@.discussions.microsoft.com> wrote in message
> news:3D1AD5FD-FB0A-4C46-A858-E8523BBB61A4@.microsoft.com...
>
>
|||Use the cluster.exe command-line utility to stop and restart instances from
within a script.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Mehul" <Mehul@.discussions.microsoft.com> wrote in message
news:39DD3469-5CEE-49DC-9755-681B5701D0EF@.microsoft.com...[vbcol=seagreen]
> Geoff,
> Yes this is correct.
> If the SQL instance services need to be restarted, what is the recommended
> way?
> "Geoff N. Hiten" wrote: