The given key was not present in the dictionary

Topics: General Questions
Jul 18, 2014 at 2:21 PM
For

a new SharePoint 2013 with SP1 agaist SQLServer 2012 Sp1 install I am seeing:
  • Creating config database "AutoSPInstaller_Config2"...
    New-SPConfigurationDatabase : The given key was not present in the dictionary.
    At C:\dev\ps\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:1651 char:13
  • New-SPConfigurationDatabase -DatabaseName "$configDB" -DatabaseServe ...
    • Registering managed account DOMAIN\SP_DANDevAppPool...
      New-SPManagedAccount : The given key was not present in the dictionary.
      At C:\dev\ps\AutoSPInstaller\SP\AutoSPInstaller\AutoSPInstallerFunctions.ps1:2076 char:17
  • New-SPManagedAccount -Credential $credAccount | Out-Null
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Fortunately the fix is easy

http://leowu70.blogspot.co.uk/2011/06/error-new-spconfigurationdatabase-given.html


But I am a bit confused as for this client I have having to do this for
  • SP_Install
  • SP_Farm
  • SP_Services ( SQL account)
  • SP_PortalAppPool
  • SP_MySItesAppPool
----- Do I do have to do the rest?
Jul 18, 2014 at 2:43 PM
If you are planning to use claims/ADFS you will need to heed Steve Peschka's warning in http://blogs.technet.com/b/speschka/archive/2010/06/12/key-not-found-in-dictionary-error-when-validating-user-accounts.aspx

Otherwise, I almost certain that you:
1) Did not have to do SP_install, your installation was already running OK.
2) Have to do this for all managed accounts. So, You have to do it for the search service account if different from the ones that you listed.
3) Do not have to do this for cache read, cache write or search crawl accounts or user profile import.

You will have to test this thoroughly though.

I am familiar with some other issues with user profile sync not starting caused by Windows 2003 Domain controllers. http://blogs.msdn.com/b/yvan_duhamel/archive/2010/06/29/you-get-a-system-security-securityexception-when-you-try-to-start-the-fim-synchronization.aspx

If you are still using windows 2003, this must retire soon. It is already out of support.
Jul 18, 2014 at 2:54 PM
Thanks for your reply... Just doe a claims SP2013 install for another client on SQLserver 2008R2 and not add this issue at all. I have even checked their system as REad is not set on most accounts ....

Yep search failed just now .... will get ops ot fix this ...

tedious and I am meant to be producing a high level plan!
Jul 22, 2014 at 4:04 PM
Once ops added the relevant Read Permissions to the managed accounts - the install was successful. However, the client has decided we re-install but this time against SQL2014 ......