May 7, 2013 at 11:24 PM
Edited May 8, 2013 at 1:46 PM
I got this error while i'm trying to install SP 2013 with AutoSPInstaller (new install):
- Attempting to join farm on "AutoSPInstaller_Config"...
- No existing farm found.
- Creating config database "AutoSPInstaller_Config"...
New-SPConfigurationDatabase : Failed to call GetTypes on assembly
Microsoft.Office.InfoPath.Server, Version=22.214.171.124, Culture=neutral,
PublicKeyToken=71e9bce111e9429c. Derived method 'RequiresWebPartClientScript'
in type 'Microsoft.Office.InfoPath.Server.Controls.WebUI.BrowserFormWebPart'
from assembly 'Microsoft.Office.InfoPath.Server, Version=126.96.36.199,
Culture=neutral, PublicKeyToken=71e9bce111e9429c' cannot reduce access.
- New-SPConfigurationDatabase -DatabaseName "$configDB"
- CategoryInfo : InvalidData: (Microsoft.Share...urationDatabase:
SPCmdletNewSPConfigurationDatabase) [New-SPConfigurationDatabase], SPUpgra
- FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletNewSPCon
- Script halted!
- Error creating new farm configuration database
I've search a lot to get information about this error, but didn't find nothing
. I'm new to SP and SQL Server... Anyone have an idea?
- the passphrase seem policy compliant
- the farmadmin and the install user both have access to SQL Server (with server roles)
- we're using a supported version of SQL Server (2008 R2)
- a config database is created, but install failed (we have to delete it to rerun the script)
Hi David, I wanted to reply because I was having this exact same issue. I had to install the following cumulative update to get it to work.
I hope this helps you and any one else that has run into this error.
rickallford, thanks for posting that; I do recall something about doing a slipstream with the CU, and that is a good point. I just installed the CU after the script failed trying to config the farm for the first time, thus SharePoint was already installed
but not configured. Then re-ran the script after deleting the database from the SQL server, worked fine after that. only other issue I had was when it tried to do the remote install on the other servers in the farm, but that is neither here nor there (I will
look into this at a later date).
I haven't figured out the slipstream script (SharePoint Auto Source Builder found
) that can create an installer with all of that stuff built in. My main intention for mentioning it here was because in doing my research I never found an answer that said this is what
you needed to do to correct or this was the solution to this issue. The Auto source builder might be might next goal to learn how that works and what I can use it for.