Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SPS2003 Installation Problem

Status
Not open for further replies.

sorehead

Technical User
May 24, 2001
29
GB
Hi,

First the important stuff:

Windows 2003 Server fully updated.
MS SQL 2000 SP3

I'm trying to install SPS 2003 without the MSDE component, and after I choose this and specify the location of the installation, I'm presented with a screen asking me to specify an "existing Windows account as the configuration database administration account which must be a member of the Power Users group blah blah". So I've already created an account on the local machine, added it to the power users group, created an account in SQL logins with the same username/password giving it security admin and db creator permissions, and db owner rights to all the db's. Every time I input the credentials at this screen, I get the standard error message saying that the NT account details could not be validated. I've tried every admin account I have, I've put the specially made account in the local and domain admin groups and it *still* won't go past this point.

What I need to know is:

- Exactly what permissions/security accesses/etc does this account need?
- Am I doing something fundamentally wrong? (It kind of feels like I am.....)
- Any other bright ideas?

The install with MSDE is fine, and I've googled the problem without success. I've also been through the MS (no) help files.

Thanks, any questions/further info - just ask.

 
I've got it working just fine every time I've installed. Local admin rights on the server has always been sufficient. You mention SQL user rights - this is something I've never had to do. What authentication mode have you got SQL in?
 
Mixed mode auth for SQL. Does the "instance" of SQL have to be of a particular name? (I just leave it as default). Does the sa password have to be particular?

I'm thinking it's something to do with the domain rights though, as if I try my personal (enterprise admin) logon, all works fine. Curious.
 
Ach, no bother. Default instance with blank sa password here.

One think just struck me - are you actually installing SP while logged in as this user? I've generated an "_sharepoint" Domain user with local admin rights on the SP server which I use to do all the installations, including SQL.
 
Now that's something I've not tried yet. Cheers - will report back.
 
Well this didn't work, but I have it working off domain accounts that duplicate my personal account. Just busy removing rights to see when it stops functioning.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top