How to Shrink WSS_Logging Database?

Issue:
SharePoint 2010/2013 always fill the "WSS_Logging.mdf" file continuously. If you are trying to shrink or empty the ".mdf" or ".ldf" files, you will not be able to shrink them.

Follow the below steps to shrink them immediately.

Solution:
1. Open a new Query window by right clicking the "WSS_Logging" database.
2. Paste the below query and execute it which will empty the unwanted contents from database.

DECLARE @TableName AS VARCHAR(MAX)
DECLARE table_cursor CURSOR
FOR 
SELECT TABLE_NAME 
FROM INFORMATION_SCHEMA.TABLES 
WHERE TABLE_TYPE = 'BASE TABLE'
AND TABLE_NAME LIKE '%_Partition%'
OPEN table_cursor
FETCH NEXT FROM table_cursor INTO @TableName
WHILE @@FETCH_STATUS = 0
BEGIN
DECLARE @SQLText AS NVARCHAR(4000)

SET @SQLText = 'TRUNCATE TABLE ' + @TableName

EXEC sp_executeSQL @SQLText

FETCH NEXT FROM table_cursor INTO @TableName 
END
CLOSE table_cursor
DEALLOCATE table_cursor


3. Once the above is query executed, your SQL DB is ready to shrink. (If the above query is not executed, then you will not be able to shrink the "WSS_Content.mdf" file.

4. Now right click on the database and go to the "shrink window" as mentioned below and shrink the DB to "50 MB".

5. Now the DB size would be re-sized to 50 MB.

Thats it...

AppFabric1.1-RTM-x64 not found or this package does not contain compatible update.

Error:
AppFabric1.1-RTM-x64 not found or this package does not contain compatible update.

Reason:
You will get this error when you are trying to install the Windows Server AppFabric v1.1 CU1[KB 2671763] directly on SharePoint 2013 server.

Solution:
Before trying to install this Windows Server AppFabric v1.1 CU1, you need to install the "Windows Server AppFabric". After installing the AppFabric, if you try to install the CU, you will not get this error.

Also make sure that the below services are in "Running" state in the server.

1. Windows Update service
2. Windows Firewall service

If you are facing any difficulty on installing Appfabric, please refer my other posts in this blog.

http://sensoft2000-sharepoint.blogspot.in/2014/09/windows-server-appfabric-is-not.html

http://sensoft2000-sharepoint.blogspot.in/2014/09/active-directory-rights-management.html

http://sensoft2000-sharepoint.blogspot.in/2014/09/another-appfabric-installation-error.html

That's it...

Another Appfabric installation error due to PSModulePath

Error:

Product: AppFabric 1.1 for Windows Server -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action Env_PSModulePath_powershell_i, location: C:\Program Files\AppFabric 1.1 for Windows Server\Microsoft.ApplicationServer.InstallHelper.exe, command: powershell.exe "-command \"$str = [System.Environment]::GetEnvironmentVariable(\\\"PSModulePath\\\",[System.EnvironmentVariableTarget]::Machine); $str = $str+\\\";C:\Program Files\AppFabric 1.1 for Windows Server\PowershellModules\\\"; C:\Windows\system32\setx.exe /MPSModulePath \\\"$str\\\"\"" "C:\Users\senthil\AppData\Local\Temp\AppServerSetup1_1_CustomActions(2014-09-28 20-02-35).log"

 (Or)
Unable to proceed the installation after restarting the Server by AppFabric.

Reason:

You will this error during the installation of Appfabric service in SharePoint server 2013. You need to fix 2 issues. 

1. Need to update the "PSModulePath" in the environment variable section
2. Enable the "Windows Firewall" service

Solution:

1. "PSModulePath" in the Environment variable will have extra double quote (") at end of the value. Appfabric installation will not be able to parse the value, if it contains the double quote. So we need to remove that additional character.   Follow the below screenshots to remove the extra double quote character

2. One more important thing is, we need to enable to the "Windows firewall" service which is mandatory for Appfabric to complete its full installation. Because

Appfabric will try to add few entries in the Windows firewall.  See the below screenshot for more info.

(This second one has killed me a lot)

Active directory rights management services client 2.0 setup wizard ended prematurely

Error:
Active directory rights management services client 2.0 setup wizard ended prematurely.

Reason:
You will get this error during your installation of SharePoint server 2013.
(Or)
During the installation of "setup_msipc_x64.msi" file (Microsoft Information protection and Control Client)

Solution:
Some of the below activities are required to install the "setup_msipc_x64.msi" file.

1. The logged-in user should be a Domain user  and should not be a  local user.
2. Should be a administrator in the current machine.
3. "windows Update" service should be in running state (services.msc)  (Mandatory)
4. "AppFabric" and "Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB 2671763)" should be installed
5. "AppFabric" should be configured which will create a new SQL server DB for Appfabric application and its caching activities
6. "Appfabric caching service" should be started.

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....


Update (on 28-Sep-2014)
Still if there is an error during the installation, then there might be an error in "Windows Update" service. This service should be enabled. So, you need to go to "services.msc" and enable the "Windows Update" service.

"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...

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...

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.

Unable to connect to the Synchronization Service.

Error:

----------------------------------
Synchronization Service Manager
-----------------------------------
Unable to connect to the Synchronization Service.

Some possible reasons are:
1) The service is not started.
2) Your account is not a member of a required security group.

See the Synchronization Service documentation for details.

Reason:
The Forefront synchronization service user does not have access rights in the required permission groups.

Solution:
1. Open the "Server Manager"
2. Go to the Groups Folder
3. Select the "FIMSyncBrowse" group  and double click on it.
4. Add the respective user and Click "OK" button.
5. Do the same steps to add the same user for "FIMSyncJoiners", "FIMSyncOperators", "FIMSyncPasswordSet" groups.
6. Logoff your server and Login again.
7. Now you can see that if you click on miiclient.exe file, it will be displayed without showing error.

For More information, see the below screenshot:

That's it...

Error: The Managed Metadata Service or connection is currently not available. The Applicaiton Pool or Managed Metadata web service may not have been started. Please contact your Administrator.

Error:

The Managed Metadata Service or connection is curretnly not available. The Applicaiton Pool or Managed Metadata web service may not have been started. Please contact your Administrator.

Reason:

The "SharePoint web services root" site may be stopped in your IIS. 

Solution:

Just follow the solution that I have given in my another post 

http://sensoft2000-sharepoint.blogspot.com/2010/10/error-security-token-service-is-not.html

Now, you will be able to see the MetaData service in your central admin.

Thats it...

Error: The Security Token Service is not available. The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.

Error:

The Security Token Service is not available. 
The Security Token Service is not issuing tokens. The service could be malfunctioning or in a bad state.

(Or) 

An exception occurred when trying to issue security token: Could not connect to http://localhost:32843/SecurityTokenServiceApplication/securitytoken.svc. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:32843. 

(Or)

The Managed Metadata Service '' is inaccessible.

Reason:

These are all unusual errors and you will get these kind of errors, if you have installed the SSL certificate on your SharePoint server. In my situation, I have installed SSL & Lync Server 2010 RC in my SharePoint 2010 server. 

Solution:

I found an very nice post about this issue in the below URL:

https://blogs.blackmarble.co.uk/blogs/rhepworth/post/2010/01/07/reassigning-the-correct-ssl-certificate-to-sharepoint-2010-web-services-iis-site.aspx

But unfortunately, the above post is not useful for me. Anyhow, it gave me some ideas about the actual issue. Finally I have found an simple solution. 

1. Go to InetMgr

2. Just start the "SharePoint Web Services" site and "SharePoint Web Services Root" application pool as per the below screenshot.

3. To make sure everything, do the "IISReset". 

Thats it....

Error: E-mail to owner could not be sent.

Error:

E-mail to owner could not be sent.

Reason:

You will get this error, when you are trying to send "Request Access" in SharePoint 2010. Because, the system could not send request to the specific portal administrator, since the email address of the portal administrator may be wrong or empty.

Solution:

1. Go to the "Site Actions" --> "Site Permissions" as per the below image.

2. Click on the "Manage Access Rights" option in the Ribbon Menu.

3. Provide the correct and valid email-id in the pop-up.

4. Now, you will be able to send request successfully and the success message will be displayed like below:

Thats it...

Issue: "Create or extend web application" link is missing in Central Admin

Issue:

"Create or extend web application" is missing in Central Admin.

Reason:

1. Because, the current browsing user may not have the rights to create the Web application.

2. You may be browsing within "Windows Server 2008"

3. You may be browsing within the MOSS server

Solutions:

Solution 1:

Browse the Url from outside MOSS 2007 server

Solution 2: (Suggested solution)

1. Right click on the browser icon.

2. Select "Run as Administrator" option.

3. Now, go to the central admin url and you can see the "Create or extend web application" link.

Thats it.