Installation error – Specified value is not supported for the {0} parameter

PS Error

I’ve been installing SharePoint foundation in the customer’s environment and everything went smoothly, I’ve asked customer to create users in AD, server in domain and internet access. I was able to install all prerequisites without problem also connect to SQL using the client tools. Then I whipped out powershell and started to create the farm and CA. The main gotcha soon appeared. After running the first cmdlet the error showed:

PS C:\> New-SPConfigurationDatabase -DatabaseName SHP_Config -DatabaseServer SQL
2012SPPS -AdministrationContentDatabaseName SHP_AdminContent

cmdlet New-SPConfigurationDatabase at command pipeline position 1
Supply values for the following parameters:
FarmCredentials
Passphrase: **********
New-SPConfigurationDatabase : Specified value is not supported for the {0} parameter.
At line:1 char:28
+ New-SPConfigurationDatabase <<<< -DatabaseName SHP_Config -DatabaseServer SQL2012SPPS -AdministrationContentDatabaseName SHP_AdminContent
+ CategoryInfo : InvalidData: (Microsoft.Share…urationDatabase:
SPCmdletNewSPConfigurationDatabase) [New-SPConfigurationDatabase], ArgumentException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPConfigurationDatabase

I’ve tried everything, including turning off firewalls, granting sysadmin rights to farm admin, install account. None of that worked out. The onlz thing that it did was that it created Configuration Database on the SQL server. Then I’ve tried to search everywhere, trace the network etc. The result – NULL, nada. So, with the grim in my face, I’ve launched the configuration wizard and let it install the farm … but … as soon as it got to the same point, it crashed with the same error.

So then email communication with started – the result was this:

No, we don’t have native AD. We have LDAP but it is exactly the same as AD.

Well… although it could be true from the outside view, the application layer that AD provides is missing. And that’s the problem. SQL or Navision doesn’t have issue with this as I’ve found out but SharePoint has.

For SharePoint you have to have native Active Directory. Full stop.

Leave a Reply


*