MOSS 2007 domain account install requirements

I would like someone to explain the initial domain accounts needed to setup MOSS2007 with out getting concurency errors, permission denied errors or, "Only the site admin is allowed to querry from the profiles db." This is my 9th MOSS installation in 3 days and there was no combination of domain accounts that have worked.

My first installation.

1. Installed Windows 2003 r2, SQL standard x86, .net 3.0 then installed Sharepoint 2007.

2. I used a domain acount FESGWIRE as the service account for all SQL services and all accounts in MOSS2007. The account was also a local administrator.

First the installation complains about some random web application at port 15097 and suggest that it must be registered as a Kerberos service provider when I selected NTML and port 40000 for the admin service. Not sure what that was. However when I created the SSP an error event is thrown : Office SharePoint Server EID: 7888 - The program attempted to update an object that was updated by another user. This causes the synchronization for the Shared Services Provider to fail. After that sql consumes 100 of the processor until I reimage.

The Second Installation

1. All the same as above however I used a different domain account FHOUPB for the Office Search and the WSS3 Search.

This time the installation went with out error however after creating the SSP it kept throwing errors claiming that the account FHOUPB was not granted a certain right denied the logon. (Microsoft's documentation states that MOSS will take care of all permissions granted after the installation - Well I guess they are wrong). After trying to import the user profiles from the domain and getting (Error: You can not update or run a querry from the profileDB unless you are a site admin) Sharepoint search decides to throw an error every minute that for some reason it cannot explain.

So I yearn to hear that some one has installed Sharepoint on the same server as SQL using the complete mode and actually getting it to work. Also please include the exact type of accounts used and their permissions on the server. Please help!!!!!!!!!!!!!!!!!!!!!11

[2191 byte] By [bababab] at [2008-3-7]
# 1
I am getting a error creating the 1st SSP, now. Using the same method and users I used to setup Beta2. Have you had any luck?
Aspiff120 at 2007-9-4 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 2

Yes actually I have. I have been able to get rid of all of the errors and SQL transaction locking except for

exception in SearchUpgradeProvisioner Keyword Config System.InvalidOperationException: jobServerSearchServiceInstance is null at Microsoft.Office.Server.Search.Administration.SearchUpgradeProvisioner..ctor(SearchServiceInstance searchServiceInstance) at Microsoft.Office.Server.Search.Administration.OSSPrimaryGathererProject.ProvisionContentSources()

This is what I did. Pick one domain account and give it administrator access on web front end. On the SQL server for that same account select dbcreator, securityadmin, and sysadmin server roles for that login. Now install sharepoint 2007 and use that account for everything (don't worry you can go back afterwards and change the content accounts). In this way at least the database is set up properly and you do not have to go to the command line to redo the databases.

Then follow this article

http://dotnetaddict.dotnetdevelopersjournal.com/mosssetup.htm

bababab at 2007-9-4 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 3

(don't worry you can go back afterwards and change the content accounts).

I have been trying to do that for the last couple of weeks!!!! could you please tell me where to do it from? what i need is to change the account MOSS is trying to access SQL with !!! because i am getting this error in my lof about a wrong username: domain.org\adminstrator. I figured out the problem is from the .org thing. but... where to change it !!!! if you can tell me it would be very appreciated !. thanks a lot.

Georges.

GeorgesKhalil at 2007-9-4 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 4
Make sure your account is in both SQL server Security, Logins. That user should have rights to the DB it connects to from your SSP service. You can cheat by making it a SQL DB Admin for all the Sharepoint DBs. If the user is a Domian use not just SQL make sure your SQL server has both Microsoft and SQL Loggins enabled. You also might want to take a look at DNS and make sure each server can see the DCs. Also look for deploySharepointserver2007.doc under downloads....
Aspiff120 at 2007-9-4 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 5
well, the thing is, i have my domain administrator set up to be dbOwner on all DBs !!!, isn't that enough ?
GeorgesKhalil at 2007-9-4 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...
# 6
I don't think you meant domain administrator but I know what you mean and you would think it is enough. What exact error are you getting? There are many ways to set the accounts because there are alot of services and processes running that access the database.
bababab at 2007-9-4 > top of Msdn Tech,SharePoint Products and Technologies,SharePoint - Setup, Upgrade, Administration and Operation...

SharePoint Products and Technologies

Site Classified