Tuesday, September 2, 2014

Windows Server Appfabric is not configured correctly

Issues:
The following error occured while loading the extended type data file: , C:\Program Files\AppFabric 1.1 for windows server\PowershellModules\ApplicationServer\Microsoft.ApplicationServer.Management.types.ps1xml : File skipped because of the following validation exception: AuthorizationManager check failed.

(Or)

Windows Server Appfabric is not configured correctly

Reason:
The above errors will occur during the installation of SharePoint Server 2013 software. All the SharePoint 2013 Pre-requisites will be installed successfully  except "AppFabric"  when executing the "Setup.exe". This pre-requisite should be installed manually and the steps are given below:

Solution Steps:
1. Uninstall the "AppFabric" through the control panel, if it is already installed fully/partially
2. Restart the server.
3. Download the "WindowsServerAppFabricSetup_x64.exe" file from internet
4. Copy the "WindowsServerAppFabricSetup_x64.exe" to "C:\" or "D:\" drive. (ex: "D:\")
4. Open the command prompt with "Administrator Privilege"
5. Go to the "SharePoint 2013" setup folder in command prompt (ex: "d:\SP2013Setup\")
6. Type the below command (based on the above mentioned example path)

prerequisiteinstaller.exe /AppFabric:D:\WindowsServerAppFabricSetup_x64.exe


7. You will see the below "SharePoint Products Preparation Tool" screen.

















8. In the middle of the installation, you will be asked to restart the server. Press "Ok" to restart.
9. After the restart, the system will resume the AppFaric installation
10. Finally you will get the "Installation complete" message.
11. Now you can start the "SharePoint 2013" installation without any issue.

Thats it....

Monday, December 30, 2013

"Search Service Host Controller" struck in "Starting" state

Errors:

Log Name:      Application
Source:        Application Error
Date:          12/30/2013 3:16:15 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXXXXXXXXXXXXXXX
Description:
Faulting application name: hostcontrollerservice.exe, version: 15.0.4420.1017, time stamp: 0x50672c2d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17965, time stamp: 0x506dcae6
Exception code: 0xe0434352
Fault offset: 0x000000000000bccd
Faulting process id: 0x1e2c
Faulting application start time: 0x01cf0543f8ebade4
Faulting application path: C:\Program Files\Microsoft Office Servers\15.0\Search\HostController\hostcontrollerservice.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 38fba41d-7137-11e3-bb81-005056a04313
Event Xml:

 
    hostcontrollerservice.exe
    15.0.4420.1017
    50672c2d
    KERNELBASE.dll
    6.1.7601.17965
    506dcae6
    e0434352
    000000000000bccd
    1e2c
    01cf0543f8ebade4
    C:\Program Files\Microsoft Office Servers\15.0\Search\HostController\hostcontrollerservice.exe
    C:\Windows\system32\KERNELBASE.dll
    38fba41d-7137-11e3-bb81-005056a04313
 

(Or)

Log Name:      Application
Source:        .NET Runtime
Date:          12/30/2013 3:16:15 PM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      XXXXXXXXXXXXXXXXXX
Description:
Application: hostcontrollerservice.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.CommunicationException
Stack:
   at Microsoft.Ceres.HostController.WcfServer.WcfService.StartService()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()


 
    Application: hostcontrollerservice.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.CommunicationException
Stack:
   at Microsoft.Ceres.HostController.WcfServer.WcfService.StartService()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()


(Or)

"Search Service Host Controller" struck in "Starting" state

Reason:
You will get this error when you are trying to start the "Search Service Host Controller" or Your Search may not be started due to this service.

Solution:
This issue killed me a lot.. :(
After a long research I have found that this "Search Host Controller" will work only if some of the supporting services are running.
So make sure that the below services are up and running in the "Services.msc" console.

1. Net. Tcp Port Sharing Service
2. Net. Tcp Listener Adapter
3. Remote Registry
4. Appfabric Caching Service

Also I have changed the user name in the "C:\program Files\AppFabric 1.1 for Windows Server\DistributedCacheService.exe.config". See the screenshot below.









Previously the "account" attribute had "Local Service" and I changed to the "farm Administrator" account.
I am not sure the last step also helped me to resolve the issue.

But now the "Search Service Host Controller" is working fine and the Search crawler is started the "Full crawl"

Thats it...

Sunday, December 29, 2013

Failed to connect to hosts in the cluster

Issue:

Use-CacheCluster : ErrorCode:SubStatus:Failed to connect to hosts in the cluster At line:1 char:1
+ Use-CacheCluster
+ ~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Use-CacheCluster], DataCacheException
    + FullyQualifiedErrorId : Microsoft.ApplicationServer.Caching.DataCacheException,Microsoft.ApplicationServer.Caching.Commands.UseCacheClusterCommand

Reason:

You will get this error when you are running the " Use-CacheCluster" command in powershell. The reason is the "Remote Registry" service might not be running.

Solution:
1. Go to "Run" window and type "Services.msc"
2. If the "Remote Registry" service is stopped, then make it as "Automatic" and "Start" the service.



Thats it...

Thursday, December 19, 2013

Cannot connect to the SharePoint site: http://MachineName:5000/sites/xyz/. Make sure that the Site URL is valid and that the current user has the necessary permissions to access the site.

Errors:

---------------------------
Microsoft Visual Studio
---------------------------
SharePoint Connection Error

Cannot connect to the SharePoint site: http://MachineName:5000/sites/dev/. Make sure that the Site URL is valid and that the current user has the necessary permissions to access the site.

Additional information:

"The remote server returned an error: (500) Internal Server Error."


(Or)

---------------------------
Microsoft Visual Studio
---------------------------
SharePoint Connection Error

Cannot connect to the SharePoint site: http://MachineName:5000/sites/dev/. Make sure that the Site URL is valid and that the current user has the necessary permissions to access the site.

Additional information:

"Cannot contact site at the specified URL http://MachineName:5000/sites/dev/."


Reason:
You might have provided entry to that SharePoint server in your "hosts" file. The "hosts" file will be under "c:\windows\system32\drivers\etc".

Solution:
1. Go to that folder and edit the "hosts" file in Notepad and remove the "mapping" for that server.
2. Reset the IIS.
3. Close and re-open the Visual Studio 2012.
4. Now create the Solution in Visual Studio and you will not see this error.

That't it....

Monday, December 2, 2013

"403 forbidden" Error when editing "Content Sources" in SharePoint 2013 to Configure the Search.


Errors:

"403 forbidden" Error when editing "Content Sources" in SharePoint 2013 to Configure the Search.

(Or)

"403 forbidden" error when adding "New Content Source" in SharePoint 2013 to Configure the Search.

(Or)

Faulting application name: hostcontrollerservice.exe, version: 15.0.4420.1017, time stamp: 0x50672c2d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.17965, time stamp: 0x506dcae6
Exception code: 0xe0434352
Fault offset: 0x000000000000bccd
Faulting process id: 0xeb0
Faulting application start time: 0x01ceefdd94d681b1
Faulting application path: D:\Program Files\Microsoft Office Servers\15.0\Search\HostController\hostcontrollerservice.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll

(Or)

Application: hostcontrollerservice.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ServiceModel.CommunicationException
Stack:
   at Microsoft.Ceres.HostController.WcfServer.WcfService.StartService()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Threading.ThreadHelper.ThreadStart()


Reason:
Microsoft only knows the actual reason. :) But the "Tasks" folder in the server does not have "Read" & "Write" access for the WSS_WPG account.

Solution:
You need to provide the Read & Write access permission to the "WSS_WPG" user in  "C:\Windows\Tasks" folder.

Monday, October 14, 2013

Procedure or function proc_SecGetIndividualUrlSecurityCheckEventReceivers expects parameter @MinLevel, which was not supplied.

Issues:

Unknown SQL Exception 201 occurred. Additional error information from SQL Server is included below.


Procedure or function 'proc_SecGetIndividualUrlSecurityCheckEventReceivers' expects parameter '@MinLevel', which was not supplied.











(Or)

Unable to delete the File or Folder or Library or List from SharePoint 2010 portal.

(Or)

Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.

Invalid object name 'TVF_Sites_NoLock_Id'.

(Or)

Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.

Invalid object name 'TVF_Docs_NoLock_Url'.
Invalid object name 'TVF_Docs_Url'.














(Or)

Unknown SQL Exception 208 occurred. Additional error information from SQL Server is included below.

Invalid object name 'TVF_EventCache_UpdLock_GTId'.
Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.

Reason:
The reason for these errors are you might have attached the SharePoint content database in the destination SQL Server and may trying to create a Web application based on this restored database.

(Or)

You might have updated / changed the "Versions" table value in SharePoint Content Database after restoring the destination SQL Server.

Solution:
You need to update or install the Latest SharePoint Server 2010 Cumulative Update (CU). In most of the cases, the installation of "SharePoint 2010 Oct 2011 CU" will solve the problem.

But make sure that you have restarted your server twice to take effect the fix.

Related Linkhttp://sensoft2000-sharepoint.blogspot.in/2013/09/this-content-database-has-schema.html


Thursday, September 26, 2013

This content database has a schema version which is not supported in this farm.

Error:
This content database has a schema version which is not supported in this farm.



Reason:
Once you have taken the backup from SharePoint 2010 content database, usually you will restore the database in the target SQL server.

After restoring the database, you will try to create new "Web Application" using the restored content database. In this stage, you will get the above error message.

Solution:
Your source SQL server schema and the destination SQL server schema might not be matched. So you need to update the "Versions" table values in the "Restored Database".

1. Open "Versions" table from any of the existing "Content database"  from the Target SQL Server machine in "Select" mode.












2. Now open the "Versions" table values of "Restored Content Database" in "Edit" mode  as mentioned below.



3. Replace the "Version" field value in "Restored Content Database" by "Existing Content Database" values from "Target SQL Server" machine.

4. Now you will be able to create new "Web Application".

Thats it...

Update (14-October-2013)
The actual reason for the above issue is the "Version Mismatch" of the SharePoint server. You need to apply the latest cumulative update (CU) of the SharePoint server in the destination SharePoint server.

In my case, I have updated the "SharePoint 2010 Oct 2011 CU" and then Restarted the Server twice. The application is started to work without any issue.