Re: Error -2147217900: failed to create SQL database

You are right on. This is exactly the cause for the below given error log.

We ran profiler to see what commands is the MSI passing to create the DB.
Then we manually tried to run that command in Query analyzer, that throwed
reference to the disk dependency.

Thanks Tom/Geoff for your quick response.

--Mehul

"Tom Moreau" wrote:

When you rebuilt the cluster, did you add disk resources as dependencies for
SQL Server? If not, then SOL Server cannot see the disks.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Mehul" <Mehul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CCA03ACA-2B83-488C-B479-11406C9E2D1C@xxxxxxxxxxxxxxxx
Geoff,
On a different note, we rebuilt the SQL cluster network today. However when
I run the MSI, I am seeing the below given error this time:

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date: 10/16/2006
Time: 4:06:34 PM
User: myDomain\SQLServerAccount
Computer: SQLServer
Description:
Product: Database -- Error 26201. Error -2147217900: failed to create SQL
database: ApplicationDb, error detail: CREATE DATABASE failed. Some file
names listed could not be created. Check previous errors..

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Any thoughts on what this error is, and what could be causing this?

--Mehul

"Geoff N. Hiten" wrote:

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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:39DD3469-5CEE-49DC-9755-681B5701D0EF@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3D1AD5FD-FB0A-4C46-A858-E8523BBB61A4@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6C83D7C2-0514-4195-A46E-FE6D9C0E8831@xxxxxxxxxxxxxxxx
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











.

Relevant Pages

  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... But SQL does not have a pointer data type or the ... > being told to design a database. ... But why is little Cindy Lou Who employee ...
    (comp.databases.theory)
  • Re: DBMS and lisp, etc.
    ... Naively implemented with SQL, again for 10 ... (1 query for the initial orders, 1 query for each order for its ... soon as you upgrade to the SQL database. ... (eq (order-customer orderA) ...
    (comp.lang.lisp)
  • Re: dbdebunk Quote of Week comment
    ... > a lot of really bad SQL programmers. ... a surrogate key should support the primary key. ... But SQL does not have a pointer data type or the ... > being told to design a database. ...
    (comp.databases.theory)
  • Re: dbdebunk Quote of Week comment
    ... But SQL does not have a pointer data type or the ... More and more programmers who have absolutely no database training are ... But why is little Cindy Lou Who employee ...
    (comp.databases.theory)
  • Re: Just say no to threads [Was: Software architecture]
    ... they knew there was going to be a database in the app. ... Now my colleague just spent a couple/three weeks designing an SQL ... Turns out they have a flat file of sample information, ...
    (comp.object)