none
SharePoint 2013 new installation errors

    Question

  • I am a SharePoint newb and have attempted my first installation. I am receiving quite a few error messages that I believe to be related. Cursory research indicates problems with database connectivity and/or account permissions.

    Specific errors are ID #3760, 5214, and 6398.

    Installation specifics:

    SharePoint 2013 Ent. (Farm), SQL 2012 Std. installed on same Hyper-V machine.

    Account specifics:

    sql_admin- domain account. Also local machine admin account. Used this account to install SQL 2012.

    sharepoint_admin- domain account. Also local machine admin account. Used this account to install SharePoint. This is also the account I use to log in to SharePoint with and access the Central Administration site.

    sharepoint_farm- domain account. Also local machine account (added to local as I read it needed to be in order to run user profile synchronization). This was specified as my database access account when I installed SharePoint.

    sharepoint_service- domain account only. This is the service account I specified during the Farm Configuration wizard.

    I am not looking for any person to resolve all of my issues here. But rather I am looking for someone that can suggest some kind of "big picture" issue that I am overlooking.

    Thanks in advance to anyone willing to take a look at this and point me in the right direction.

    Friday, January 11, 2013 5:02 PM

All replies

  • Are the specific errors listed SharePoint errors or SQL errors? At what point do you receive the errors?

    I would use the same account for installing SQL Server 2012 and SharePoint 2013 (I'd use sharepoint_admin in your case). Also, ensure that this account has the correct roles in the database.

    To do this open SQL Server Management Studio and connect to your instance.

    • Expand Security > Logins.
    • Right-click DOMAIN\sharepoint_admin and select Properties.
    • Choose the Server Roles page.
    • Check the dbcreator and securityadmin server roles.


    Friday, January 11, 2013 6:12 PM
  • I totally agree with your recommendation of using the same account for SQL and SP as this appears to be the root of all my issues.

    I was just trying to follow the model of least priviledge.

    Many other sources recommended the same segregation of sql and sharepoint admin accounts. Microsoft does not address this. Documentation for SQL and SharePoint is separate.

    Thank you my friend for your response.

    Friday, January 11, 2013 7:49 PM
  • Christopher...depending on your needs, your initial setup was to the letter by the book, only thing that could be missing that I see is the SQL roles for the setup account and maybe, firewall (TCP 1433,  UDP 1434) and loopback check if you are accessing the server using anything else than the server name.

    All else will be handled during the setup, the service accounts will be granted the proper rights.
    Like you said, the UPS service account needs to be local admin, but only during the provisioning of the UPS synch service(starting it)

    If you are getting started with SharePoint, do it the proper way, I'm sorry hhancock, but that is bad advice, do not use one account for every role, and especially not for SQL and SharePoint, that is not the way to do it in any 'real' environment and you might as well start by doing it right.
    This article is the guideline and it is best practice (sounds like what you followed from the beginning):

    Initial deployment administrative and service accounts in SharePoint 2013
    http://technet.microsoft.com/en-us/library/ee662513.aspx

    If...you are looking for just an easy way out, run it all using one domain admin account...but you will learn nothing and you will not stumble upon the Little issues you need to learn about. Keep security tight, from the beginning, you will gain more that way in the long run.

    Thats my 2 cents :-)

    Good luck, I hope you will enjoy many years of SharePointing...

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download 'The SharePoint Branding Project' here
    Download 'The final guide to Alternate Access Mappings' free whitepaper here
    Download 'The final guide to SharePoint 2010 Site Settings' free whitepaper here
    Download 'The final Kerberos guide for SharePoint technicians' free whitepaper here

    Friday, January 11, 2013 9:36 PM
  • Thanks for the reply Thomas.

    I reinstalled SQL and SharePoint on the same account and have the exact same issues! (errors 3760, 5214, and 6398). So separate SQL admin and SharePoint accounts is not the problem.

    On the first install, when I used a separate SQL Admin account, I the left that account role at defaults. Then I added the SharePoint admin account with the dbcreator and securityadmin roles.

    That only leaves me with your suggestion of possible firewall issues. But since SQL and SharePoint are on the same box, that cannot possibly be the issue. Would you agree?

    Friday, January 11, 2013 10:39 PM
  • Hi.

    Assumptions is the mother of all f___ups...:-) Never assume that you have to or don't have to.

    Do it like this. My recommendation...
    Start over, I know, it will take more time, but you will feel better having done it the right way. Install SQL using a SQL service account(domain user) and then install the SharePoint bits with its own service account (domain user).
    The account you are using to install SharePoint must be a member of the local administrators group. Before you run the Configuration Wizard the first time, to create the farm and the databases, add your account(you are logged on with) to the roles DB_Creator and Security_admin. That part hhancock got right.
    All other permissions for the farm account/database access account(same thing) will be granted during setup.

    Again, Before running the wizard, configure the local firewall to allow incoming on TCP 1433 and UDP 1434.

    Now, run the Configuration Wizard and select to create a new farm...

    Good luck

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download 'The SharePoint Branding Project' here
    Download 'The final guide to Alternate Access Mappings' free whitepaper here
    Download 'The final guide to SharePoint 2010 Site Settings' free whitepaper here
    Download 'The final Kerberos guide for SharePoint technicians' free whitepaper here

    Friday, January 11, 2013 10:52 PM
  • Okay Thomas. I am going to give this another shot.

    I did everything you suggested on my first install before I posted.

    I wanted to send you a link to the directions I followed but for some reason I am getting a BS error for not being able to add a link to this thread.

    I will make sure the ports are open.

    Stand by...

    Thanks again.

    Friday, January 11, 2013 11:59 PM
  • Thomas, please don't bail on me as you are my only link to sanity (although that ship may have already sailed :)Insanity=doing the same thing and expecting different results.

    Actually, I did do the same thing with different results. I am now down to event id 5214 and 6398 (no 3760).

    SQL accounts:

    sql_admin- roles: public, sysadmin

    sharepoint_admin- roles: dbcreator, public, securityadmin

    sharepoint_farm- roles: dbcreator, public, securityadmin

    sharepoint_service- roles: public

    SQL was installed with the sql_admin account

    SharePoint was installed with sharepoint_admin account.

    Used sharepoint_farm account as database access account.

    All appears okay to this point. Now I ran the "how do you want to configure your sharepoint farm wizard".

    I used an (domain) account sharepoint_service. This is not a local account nor do I believe it should be.

    Is this where the wheel came off the wagon?

    Saturday, January 12, 2013 2:23 AM
  • Can you provide the actual error you're encountering as Event IDs can be linked to multiple different errors.

    As far as least privledged, you should have the following domain accounts:

    SQL_Service - runs SQL Server services, is not a Local Administrator on the SQL Server

    SharePoint_Setup - Is a Local Administrator on the SharePoint Server and sysadmin role on the SQL Server.  Use this account to install SharePoint and run the Config Wizard.

    SharePoint_Farm - Is a Local Administrator on the SharePoint Server for UPSS provisioning.  Specify this account as the "Database Access" account in the Config Wizard.

    If your SharePoint_Setup account has the sysadmin role on the SQL Server instance, it will appropriately configure SQL (setting MDOP = 1 and adding SharePoint_Farm with the dbcreator/securityadmin roles automatically).

    For the most part, Todd Klindt's service account guide is still accurate for SharePoint 2013: http://toddklindt.com/blog/Lists/Posts/Post.aspx?ID=237


    SharePoint - Nauplius Applications
    Microsoft SharePoint Server MVP
    MCITP: SharePoint Administrator 2010

    -----------------------
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.


    Saturday, January 12, 2013 3:13 AM
    Moderator
  • Hi.

    I'm in a different timezone...had to sleep for a bit :-)

    No, all account should be domain accounts, no local accounts.
    Came to Think of it, did you by any chance install SQL and SharePoint on a domain controller? That would cause all kinds of problems...and is unsupported.

    For the last step you mentioned, the account you are asked for during the wizard, that is the farm account/db access account. In your case SharePoint_farm.

    SharePoint_service is what I assume(!) the account prepared to be used by the Service Applications later on.

    If this still keeps stopping, could you give us more detailed steps, like what you are doing at every moment, what account you are using and so on.

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download 'The SharePoint Branding Project' here
    Download 'The final guide to Alternate Access Mappings' free whitepaper here
    Download 'The final guide to SharePoint 2010 Site Settings' free whitepaper here
    Download 'The final Kerberos guide for SharePoint technicians' free whitepaper here

    Saturday, January 12, 2013 8:11 AM
  • Thomas, all accounts are domain accounts. And no, I am not trying to install on a domain controller. There is nothing else besides SQL and SharePoint on the machine.

    I have been desperately trying to send you a link to the exact instructions I have been using to install SQL2013/SharePoint 2013.

    But I am getting a error saying "body text cannot contain images or links until we verify  your account.

    The link is at: www dotnetfunda com/articles/article1257-installing-sharepoint-2010.aspx

    Please put a dot where the spaces are.

    It should only take you a moment to review this. Do you see anything inherently wrong with these instructions?

    Sunday, January 13, 2013 10:47 PM
  • Here are the errors:

    Event ID 5214

    Insufficient SQL database permissions for user 'Name: CHRISCONWAY\sharepoint_service SID: S-1-5-21-3710878042-1344467293-1554560293-1142 ImpersonationLevel: None' in database 'SharePoint_Config' on SQL Server instance 'SV01SP'. Additional error information from SQL Server is included below.

    The EXECUTE permission was denied on the object 'proc_putObjectTVP', database 'SharePoint_Config', schema 'dbo'.

    Event ID 6398

    The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID 76b1e39d-0a0c-42db-a27c-e742053100b0) threw an exception. More information is included below.

    Unexpected exception in FeedCacheService.BulkLMTUpdate: Region not found..

    Sunday, January 13, 2013 10:52 PM
  • Is CHRISCONWAY\sharepoint_service a sysadmin in SQL?

    SharePoint - Nauplius Applications
    Microsoft SharePoint Server MVP
    MCITP: SharePoint Administrator 2010

    -----------------------
    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Monday, January 14, 2013 12:17 AM
    Moderator
  • Hi. Can it be that you have the accounts mixed up? _service should never directly access the DBs, the farm/db access account handles that. Could you retrace your steps and add here, step by step, what account you add where and so on? And if you restart, remove the DBs first. Regards

    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download 'The SharePoint Branding Project' here
    Download 'The final guide to Alternate Access Mappings' free whitepaper here
    Download 'The final guide to SharePoint 2010 Site Settings' free whitepaper here
    Download 'The final Kerberos guide for SharePoint technicians' free whitepaper here

    Monday, January 14, 2013 12:18 AM
  • No, the sharepoint service is not sysadmin in SQL. The only role for that is Public.
    Monday, January 14, 2013 3:48 PM
  • I selected the Complete installation option and "Run The SharePoint Products Configuration Wizard now.

    On the connect to a server farm window I select “Create a new Server Farm” and clicked on next.

    In the database access account I specified SharePoint_Farm account and on the following page I entered a passphrase.

    At the end of this scenario SharePoint installation was successful.

    After the finish button I got to the "initial farm configuration wizard" window and clicked on “start the wizard”.

    I selected "create new managed account". This is where I entered the SharePoint_Service account.

    Monday, January 14, 2013 4:01 PM
  • Thomas. Thanks for all of your help.

    Unless you say otherwise, I am going to assume my install of SQL/SharePoint is sound.

    If neccesary, I will open a seperate thread on the two remaining errors (#5214 and 6398).

    Others are having the same problem with the error event #6398:

     I still can't post a link here, but Google this: "SharePoint 2013 so many 6398 errors".

    Tuesday, January 15, 2013 12:07 AM