SharePoint 2013 installation headacks
This blog describes some problems that I faced when installing a SharePoint 2013 server
When creating a site collection with a custom solution
The solution for this problem is to create a new Server AppFabric Cache host and can be found on msdn .
First I created a new SQL database with the name CacheClusterConfigurationDB
After that I used the following powershell scripts to create a new Server Appfabric on the server.
New-CacheCluster -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True" -Size Small
Register-CacheHost -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True" -Account "ServerName\cachehost" -CachePort 22233 -ClusterPort 22234 -ArbitrationPort 22235 -ReplicationPort 22236 -HostName ServerName
Add-CacheHost -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True" -Account "ServerName\cachehost"
Add-CacheAdmin -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True" -Account "ServerName\cachehost"
Add-CacheAdmin -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True"
Use-CacheCluster
Set-CacheHostConfig -Hostname ServerName -cacheport 22233
Also I changed the user under the AppFabric Caching Service to an local account that I used for the scripts
Errors encountered
The following error showed upWhen creating a site collection with a custom solution
Unexpected Exception in SPDistributedCachePointerWrapper::InitializeDataCacheFactory for usage 'DistributedViewStateCache' - Exception 'System.InvalidOperationException: SPDistributedCachePointerWrapper::InitializeDataCacheFactory - No cache hosts present in the farm.
The solution for this problem is to create a new Server AppFabric Cache host and can be found on msdn .
First I created a new SQL database with the name CacheClusterConfigurationDB
After that I used the following powershell scripts to create a new Server Appfabric on the server.
New-CacheCluster -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True" -Size Small
Register-CacheHost -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True" -Account "ServerName\cachehost" -CachePort 22233 -ClusterPort 22234 -ArbitrationPort 22235 -ReplicationPort 22236 -HostName ServerName
Add-CacheHost -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True" -Account "ServerName\cachehost"
Add-CacheAdmin -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True" -Account "ServerName\cachehost"
Add-CacheAdmin -Provider System.Data.SqlClient -ConnectionString "Data Source=ServerName\SQL2012;Initial Catalog=CacheClusterConfigurationDB;Integrated Security=True"
Use-CacheCluster
Set-CacheHostConfig -Hostname ServerName -cacheport 22233
Also I changed the user under the AppFabric Caching Service to an local account that I used for the scripts
Comments
http://www.razorse.com