Failed to connect to database (Configuration Wizard)

[Mike Walsh]

If this is over a previously installed then deleted copy of MOSS then the MS
document says to use

psconfig -cmd configdb -create -database <uniquename> to create a new config
database

Mike Walsh
WSS FAQ www.wssv3faq.com / wss.collutions.com
No private questions please (additions to FAQ welcome)

Hi,
I've installed a fresh copy of MOSS, and ran the configuration wizard.
I'm trying to connect to an existing SQL server to create a new config db
(craete new farm)
I supply the instance name ("sqlserver\instancename") and credentails
("domain\sqladmin") but keep getting "Failed to connect to the database
server" (see full error below). SQL instance is up and runining, SQL
managment studio installed on the moss machine has no problem to connect
to
the same instance.
help?
---------------------------
SharePoint Products and Technologies Configuration Wizard
---------------------------
Failed to connect to the database server or the database name does not
exist. Ensure the database server exists, is a Sql server, and that you
have
the appropriate permissions to access the database server. To diagnose the
problem, review the extended error information located at C:\Program
Files\Common Files\Microsoft Shared\Web Server
Extensions\12\LOGS\PSCDiagnostics_12_20_2006_17_10_44_859_1832613818.log.
Please consult the SharePoint Products and Technologies Configuration
Wizard
help for additional information regarding database server security
configuration and network access.

[Jukka Paajanen [MSFT]]

Hi,

(Sorry for the late response)

The user running the configuration wizard / psc MUST have SQL rights (Sql
login, security admin, and db creator if the db hasn't been precreated). The
initial dbs will be created using this account and this account will give
permissions to the specified db account in the db. I.e. in your case,
sqladmin didn't need to have any SQL rights prior to use. Most like
implication is that config wizard / PSC should have been run as sqladmin,
but another account (only dedicated to Sharepoint db access) used for the
account specified in the wizard. This is by design and to my knowledge
explained in the docs.

JP

This is exactly what I did and it solved the problem.
It seems like the wizard has a problem with impersonation.
When I logged in with domain\sqladmin which I also set as a local admin in
the moss machine, the wizard had no problem connecting to the sql and
creating the new db.

I had the same error when installing RTM.
I did not use psconfig.
You could try to log in with domain\sqladmin in order to install, it
should
work.
Hervé

Hi,
I've installed a fresh copy of MOSS, and ran the configuration wizard.
I'm trying to connect to an existing SQL server to create a new config
db
(craete new farm)
I supply the instance name ("sqlserver\instancename") and credentails
("domain\sqladmin") but keep getting "Failed to connect to the database
server" (see full error below). SQL instance is up and runining, SQL
managment studio installed on the moss machine has no problem to
connect to
the same instance.
help?
---------------------------
SharePoint Products and Technologies Configuration Wizard
---------------------------
Failed to connect to the database server or the database name does not
exist. Ensure the database server exists, is a Sql server, and that you
have
the appropriate permissions to access the database server. To diagnose
the
problem, review the extended error information located at C:\Program
Files\Common Files\Microsoft Shared\Web Server
Extensions\12\LOGS\PSCDiagnostics_12_20_2006_17_10_44_859_1832613818.log.
Please consult the SharePoint Products and Technologies Configuration
Wizard
help for additional information regarding database server security
configuration and network access.

[unknown]

I am getting the same error. However, all of my SQL services are being started by a Domain Admin account. I am logged on the the MOSS box with that Domain admin account. And I STILL get the error

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

[yoni]

I'm definitely not a sql admin but I think that the fact the services are ran
under a specific account does not grant that account with required sql rights
as Michael specified.
In my case, I specifically created a domain account (myDomain\sqlAdmin) and
gave it admin rights in the sql. I then logged in with that account (which
was also set as a local admin on the moss machine) and completed the
configuration wizard.
Maybe that can work for you...

Post by unknown
I am getting the same error. However, all of my SQL services are being started by a Domain Admin account. I am logged on the the MOSS box with that Domain admin account. And I STILL get the error
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

[yoni]

I'm definitely not a sql admin, but I think that the fact the sql services
are started using a specific account, doesn't mean that the account has the
necessary sql permissions (or any sql permissions).
In my case, I have created an AD user (i.e. myDomain\sqlAdmin), gave it full
sql admin rights, and set it as a local admin on the moss machine. I then
logged in to the moss machine using that account and completed the
configuration wizard.
Maybe that can work for you...

Post by unknown
I am getting the same error. However, all of my SQL services are being started by a Domain Admin account. I am logged on the the MOSS box with that Domain admin account. And I STILL get the error
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

[unknown]

Connection between DB and MOSS server Error ,
enable TCP/IP and Named space protocol in SQL Server Network Configuration option




yon wrote:

I'm definitely not a sql admin, but I think that the fact the sql services are
13-Apr-07

I'm definitely not a sql admin, but I think that the fact the sql services
are started using a specific account, doesn't mean that the account has the
necessary sql permissions (or any sql permissions)
In my case, I have created an AD user (i.e. myDomain\sqlAdmin), gave it full
sql admin rights, and set it as a local admin on the moss machine. I then
logged in to the moss machine using that account and completed the
configuration wizard
Maybe that can work for you..

"Michael" wrote:

Previous Posts In This Thread:

On Wednesday, December 20, 2006 10:23 AM
yon wrote:

Failed to connect to database (Configuration Wizard)
Hi,

I've installed a fresh copy of MOSS, and ran the configuration wizard.
I'm trying to connect to an existing SQL server to create a new config db
(craete new farm)
I supply the instance name ("sqlserver\instancename") and credentails
("domain\sqladmin") but keep getting "Failed to connect to the database
server" (see full error below). SQL instance is up and runining, SQL
managment studio installed on the moss machine has no problem to connect to
the same instance.

help?

The error message:

---------------------------
SharePoint Products and Technologies Configuration Wizard
---------------------------
Failed to connect to the database server or the database name does not
exist. Ensure the database server exists, is a Sql server, and that you have
the appropriate permissions to access the database server. To diagnose the
problem, review the extended error information located at C:\Program
Files\Common Files\Microsoft Shared\Web Server
Extensions\12\LOGS\PSCDiagnostics_12_20_2006_17_10_44_859_1832613818.log.
Please consult the SharePoint Products and Technologies Configuration Wizard
help for additional information regarding database server security
configuration and network access.

On Wednesday, December 20, 2006 12:04 PM
Mike Walsh wrote:

If this is over a previously installed then deleted copy of MOSS then the MS
If this is over a previously installed then deleted copy of MOSS then the MS
document says to us

psconfig -cmd configdb -create -database <uniquename> to create a new config
databas

Mike Wals
WSS FAQ www.wssv3faq.com / wss.collutions.co
No private questions please (additions to FAQ welcome

"yoni" <***@discussions.microsoft.com> wrote in message news:4D8B2E86-1EAF-48D1-8AB3-***@microsoft.com...

On Thursday, December 21, 2006 4:17 AM
Her wrote:

I had the same error when installing RTM.I did not use psconfig.
I had the same error when installing RTM
I did not use psconfig
You could try to log in with domain\sqladmin in order to install, it shoul
work

Herv?

"yoni" wrote:

On Thursday, December 21, 2006 9:46 AM
yon wrote:

This is exactly what I did and it solved the problem.
This is exactly what I did and it solved the problem
It seems like the wizard has a problem with impersonation
When I logged in with domain\sqladmin which I also set as a local admin in
the moss machine, the wizard had no problem connecting to the sql and
creating the new db

"Herv??" wrote:

On Tuesday, January 02, 2007 8:53 PM
Jukka Paajanen [MSFT] wrote:

Hi,(Sorry for the late response)The user running the configuration wizard /
Hi

(Sorry for the late response

The user running the configuration wizard / psc MUST have SQL rights (Sql
login, security admin, and db creator if the db hasn't been precreated). The
initial dbs will be created using this account and this account will give
permissions to the specified db account in the db. I.e. in your case,
sqladmin didn't need to have any SQL rights prior to use. Most like
implication is that config wizard / PSC should have been run as sqladmin,
but another account (only dedicated to Sharepoint db access) used for the
account specified in the wizard. This is by design and to my knowledge
explained in the docs.

JP

"yoni" <***@discussions.microsoft.com> wrote in message news:EB3C275D-D782-449B-8840-***@microsoft.com...

On Thursday, April 12, 2007 11:52 AM
Michael wrote:

Same Problem
I am getting the same error. However, all of my SQL services are being started by a Domain Admin account. I am logged on the the MOSS box with that Domain admin account. And I STILL get the error

On Friday, April 13, 2007 12:48 PM
yon wrote:

I'm definitely not a sql admin but I think that the fact the services are ran
I'm definitely not a sql admin but I think that the fact the services are ran
under a specific account does not grant that account with required sql rights
as Michael specified.
In my case, I specifically created a domain account (myDomain\sqlAdmin) and
gave it admin rights in the sql. I then logged in with that account (which
was also set as a local admin on the moss machine) and completed the
configuration wizard.
Maybe that can work for you...

"Michael" wrote:

On Friday, April 13, 2007 12:54 PM
yon wrote:

I'm definitely not a sql admin, but I think that the fact the sql services are
I'm definitely not a sql admin, but I think that the fact the sql services
are started using a specific account, doesn't mean that the account has the
necessary sql permissions (or any sql permissions).
In my case, I have created an AD user (i.e. myDomain\sqlAdmin), gave it full
sql admin rights, and set it as a local admin on the moss machine. I then
logged in to the moss machine using that account and completed the
configuration wizard.
Maybe that can work for you...


"Michael" wrote:


Submitted via EggHeadCafe - Software Developer Portal of Choice
Get Silverlight 4 Installed: Tips and Tricks
http://www.eggheadcafe.com/tutorials/aspnet/05910e41-3846-4db9-8e1b-f54c56a64ed9/get-silverlight-4-install.aspx

[Sunil [MSFT]]

Hello Unais,

This is because of the insufficient permissions for SharePoint farm account
on the SQL Server.

Make a note of the SharePoint farm account. To do that follow:
Log on to SharePoint Server > Run > Services.msc
Locate a Service on the right hand side "Windows SharePoint Services
Timer", Right Click and Click Properties
Click "Log on" tab and note down the account listed there. That is the
account which has to be added to SQL Server with specific Server wide roles.

Log on to SQL Server, open Management Studio > in the Dialog box Enter
Localhost or Server name
Click Security > Logins > on the right hand side, right click and select
"New login" > Enter Domain\Username in the Login name text box.
Click Server Roles in the left hand side > Select "dbcreator"
"securityadmin"
Click OK and make sure that the account is added.

Log on to SharePoint Server with SharePoint Farm Account (Noticed above)
and perform following test to find out is you still have some permission
issue.

When an application failed with a database/datasource connectivity problem,
the first thing to check is if the box really cannot connect to the
database/datasource using a "generic" way. The simplest technique is "UDL
Test" using the OLE DB providers installed on the box . For example, if the
application is failing to connect to a SQL Server 2000 or 2005, just follow
the steps below :

1) Create a new empty text file like "test.txt" (For example, right mouse
click on an empty place on your desktop, select "New" and "Text Document")

2) Rename the file as "test.udl"

As soon as you renamed the file, text file icon should change to a UDL
icon

3) Double click on test.udl file and you'll receive a window titled "Data
Link Properties"

You'll get all the installed OLE DB Providers on the box when you've
switched to the Provider tab. If the OLE DB Provider for the
database/datasource you're interested in is in the list, select the OLE DB
Provider and click on "Next"and you'll switch to "Connection" tab and will
be ready to play with the OLE DB Provider. The rest depends on the OLE DB
Provider you selected.

You'll need the name of the SQL Server (or instance name) you're trying to
connect to the textbox in the 1st part. "Use a specific user name and
password" is selected by default in the 2nd part and this means "SQL
Authentication". You'll need to enter a SQL Server username here. If you
select "Use Windows NT Integrated security" radio button, then the Username
and Password textboxes will be disabled and the credential that you logged
on to the machine will be used while connecting to SQL Server. Be sure that
your SQL Server is in "mixed" mode (Please refer to SQL Server Books Online
for the details )

You can either click on "Test Connection" directly to test the connection
or click on the combobox to enumerate the available databases/catalogs on
the server.

If you click on "Test Connection", you should receive "Test connection
succeeded" message if you can connect to the SQL Server.

For more detailed instructions:
http://blogs.msdn.com/farukcelik/archive/2007/12/31/basics-first-udl-test.as
px

Install Office SharePoint Server 2007 on a stand-alone computer
http://technet.microsoft.com/en-us/library/cc263202.aspx

Steps to Configure a basic MOSS 2007 Farm (RTM)
http://blogs.technet.com/josebda/archive/2006/11/07/installing-rtm.aspx

Sunil [MSFT]