Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Failed To Connect Database during Configuration Wizard

  Asked By: Cleveland    Date: Dec 12    Category: Sharepoint    Views: 9853

I've been wracking brain over this (Both Search Server Express and
Windows SPoint Services) for a while. The Config wizard always fails
to get past the DB creation phase. Logs can available if required,
but don't look very useful. Here's some of the particulars

I'm Using a VMWare instance as well.

2GB of memory (4gb on 64 bit XP system)

Fully Patched Win2k3 Server. Tried standard and enterprise

No known network issues.

Tried Local, Bridged and NAT Networking

Domain Admin Account. Also tried standalone local admin

Tried default SQL included and standard and enterprise, 2k5 and 2k,
local and network

Tried using the psconfig tool to create the DBs.

Tried pre-configuring the account in SQL with various and sundry
permissions

Everytime, it creates the DB's, all the tables, SPs, etc. but
fails to load any seed data, and tells me it can't connect to the DB
it just created.

I've seen reference to "checking the connection string" in the logs,
but there is nothing that even vaguely looks like a con string. I've
seen refernce to using stsadm to increase the logging, but that won't
work until I get further along the install path.

Share: 

 

10 Answers Found

 
Answer #1    Answered By: Katy Patton     Answered On: Dec 12

The user identities you list - are those for running the install/config,
the app pool(s) or both? Is this a Farm or Basic install?

 
Answer #2    Answered By: Ana Payne     Answered On: Dec 12

In short, Yes. I've tried every combo I can think of. I read the
install instructions. I read a few postings that basically seemed to
say "take the Basic defaults and it works". No joy. Then I branched
out to every conceivable option.

In general, I tried using the account  I logged in as, with Domain
Admin, or with Local Admin.

I think I've tried about 20 different install  combos, including new
images.

 
Answer #3    Answered By: Hema Hegde     Answered On: Dec 12

Can you send me the log? I can figure it out for you.

 
Answer #4    Answered By: Lacey Daniels     Answered On: Dec 12

Any help would be appreciated...........

 
Answer #5    Answered By: Megan Martin     Answered On: Dec 12

The logs  would be helpful. The error you are getting will be lost in
the log toward the bottom.

You have to run the install  as your network  administrator. You need
admin permissions to do everything over a network.

The easiest way to install this is all on one machine. It is not the
best way to go though.

Can you answer some questions please?



Has you virtual server  joined the domain? (can you view the drive you
db is on by using //sqlservername/c$

Are you installing MOSS(not free) or WSS(free)?

What version of sql  are you using?

Is your DB on a separate machine?

Is your DB on a separate VM?

What version of ASP do you have installed?

Have you verified that ASP.net is running?

Is ISS running/installed?





Start there. I have a similar configuration  so I know this will work
for you.

 
Answer #6    Answered By: Donta Kirkland     Answered On: Dec 12

Basically, I've tried every combo. Local, remote, Domain admin/
local admin  Domain User, local  User.

Tried WSS and search  Server Express (I'm looking for search). ASP.NET
is correct version, and enabled.

Running the system on WIn 2k3, sp2 IIS 6. Databases get created,
and then populated with objects, no data, and it dies sayaing it
connect to the database.

 
Answer #7    Answered By: Cade Velazquez     Answered On: Dec 12

Figured it out.. i was at a customer site and got the same error.. this is what
you do.. add the user you used for your DB connection  to the local
administrators group of the server  and then log on as that user on the server
and rerun the sharepoint configuration  tool again.. should work like a charm

 
Answer #8    Answered By: Ariana Christensen     Answered On: Dec 12

i'm also face with the same errors, could you please update me on
the solution as well?

 
Answer #9    Answered By: Kyle Anderson     Answered On: Feb 06

Hey Everyone,

I ran into this when i was trying to create a new farm using WSS3.0. I tried all the different things that Cleavland tried and was ripping my hair out. Anyway i found what worked for me was the following.

Make sure that the account you are using has the following rights:
- Local administrator on both the front end, and the SQL Backend servers
- server roles (dbcreator, public, security admin, and sysadmin) on the database server

Log into the front end server as that account

- Open a powershell command prompt and browse to the following location
- C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
- Run the following command
.\PSCONFIG.EXE -cmd configdb -create -server [sql database server goes here] -database [name of config database] -user [useraccount you're logged in as] -password [password of that account] -admincontentdatabase [name of the admin content database] -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd adminvs -provision -port 17012 -windowsauthprovider onlyusentlm -cmd applicationcontent -install

That seemed to work for me. You can use different flags to install. I found this information on the following page.

technet.microsoft.com/en-us/library/cc263093(v=office.14).aspx

Cheers,

 
Answer #10    Answered By: Kyle Anderson     Answered On: Feb 06

Hey Everyone,

I ran into this when i was trying to create a new farm using WSS3.0. I tried all the different things that Cleavland tried and was ripping my hair out. Anyway i found what worked for me was the following.

Make sure that the account you are using has the following rights:
- Local administrator on both the front end, and the SQL Backend servers
- server roles (dbcreator, public, security admin, and sysadmin) on the database server

Log into the front end server as that account

- Open a powershell command prompt and browse to the following location
- C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\BIN
- Run the following command
.\PSCONFIG.EXE -cmd configdb -create -server [sql database server goes here] -database [name of config database] -user [useraccount you're logged in as] -password [password of that account] -admincontentdatabase [name of the admin content database] -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd adminvs -provision -port 17012 -windowsauthprovider onlyusentlm -cmd applicationcontent -install

That seemed to work for me. You can use different flags to install. I found this information on the following page.

technet.microsoft.com/en-us/library/cc263093(v=office.14).aspx

Cheers,

 
Didn't find what you were looking for? Find more on Failed To Connect Database during Configuration Wizard Or get search suggestion and latest updates.




Tagged: