Skip to main content

Category: Windows

AppFabric Caching Service crash (Solved)

Ned 2 Comments

AppFabric is a set of technologies that helps developers and administrators to build and scale web applications that run on IIS. It comes with hosting and caching features. In this post, I will focus on AppFabric Caching Service crash and possible fixes.

AppFabric Caching Service crash and fix
AppFabric Caching architecture (Source)

If you notice that the caching is not working as expected, check the Event Viewer logs located in the containers below:

  • Windows Logs > Application
  • Windows Logs > System​
  • Applications and Services Logs > Microsoft > Application Server-System Services​

In the Event Viewer logs, it is likely that you will see one or more of these error messages:

Event ID 111:
AppFabricCachingService.Crash Microsoft.ApplicationServer.Caching.DataCacheException: ErrorCode:SubStatus:Service initialization failed. No user action required.

Event ID 6:
30ecac98000000000000000000000000
Microsoft.Fabric.Common.OperationCompletedException: Operation completed with an exception —> System.TimeoutException: The operation has timed out.

Event ID 1026:
Application: DistributedCacheService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: Microsoft.ApplicationServer.Caching.DataCacheException

Event ID 1000:
Faulting application name: DistributedCacheService.exe, version: 1.0.4632.0
Faulting module name: KERNELBASE.dll, version: 10.0.14393.2636
Exception code: 0xe0434352
Faulting application path: C:\Program Files\AppFabric 1.1 for Windows Server\DistributedCacheService.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll

Event ID 36871:
A fatal error occurred while creating a TLS client credential. The internal error state is 10013.

For the solution of Schannel 10013 error, please check this post out.

Find the root cause of AppFabric Caching Service crash and solve it

Here are the possible causes and solutions of AppFabric Cashing Service crashes. You can implement each solution individually. They don’t depend on each other.

Service account

Check the account used for running AppFabric Caching service. If it is the server farm account, change it to a managed account (Instructions).

Best practice for the service account:

A single account should be used for all Service Applications, named Service Application Pool account. This allows the administrator to use a single IIS Application Pool for all Service Applications. In addition, this account should run the following Windows Services: SharePoint Search Host Controller, SharePoint Server Search, and Distributed Cache (AppFabric Caching Service). The SharePoint Service Application Pool account must be a domain user account. This account must not be a member of the Administrators group on any computer in the server farm.

Source

Account permissions

Provide Data Reader / Data Writer permissions to NT Authority\System on the SQL AppFabric Database.

Additionally, in PowerShell, execute Grant-CacheAllowedClientAccount command for NT Authority\System account on the cluster (Source).

Cluster nodes

Check if all nodes are online. If one node is not reachable, AppFabric Caching Service may crash

Other possible fixes

  • Disable the antivirus temporarily and try again
  • Make sure the operating system is up-to-date
  • Make sure the limit for number of servers allowed in the farm is not exceeded
  • Disable Windows Firewall temporarily and try again. If there is a non-Windows firewall, please open the following protocols and ports: SMB, SMB2 and ICMP protocols TCP ports (22233, 22234, 22235 and 22236) Or 445 and the ICMP protocol TCP ports (22233, 22234, 22235 and 22236)

DCOM 10016 Local Activation permission for the COM Server (Solved)

Ned 1 Comment

After installing Windows SharePoint Services in your server, you may see “DCOM 10016 Local Activation permission” error in Event Viewer. In addition, you may come across “10017” errors as well. Here are the error texts:

Microsoft-Windows-DistributedCOM 10016

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID X and APPID Y to the user A from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable).

This security permission can be modified using the Component Services administrative tool.

DCOM 10017

The application-specific permission settings do not grant Activation permission for the COM Server application with CLSID X to the user User_Name SID User_SID. 

How to solve “DCOM 10016 Local Activation permission” error

This error occurs when service account for Windows SharePoint Services does not have “Local Activation” permission. In order to solve this issue, follow the steps below:

  1. Go to “Start > Run”. Enter “dcomcnfg”
  2. Expand “Component Services > Computers > My Computer > DCOM Config”
  3. Click “View > Detail” from the top menu
  4. Scroll down and find the application ID {A9E69610-B80D-11D0-B9B9-00A0C922E750} (This ID is for IIS Admin service. Find the ID specified in the error message)
  5. Right Click it. Select “Properties > Security”. If you see that the options in this tab are greyed out, follow these instructions to activate them. If they are not greyed out, continue with Step 6
  6. Click Customize under “Launch and Activation Permission“.
  7. Click “Edit > Add”.  Add “domain\username”cservice account. After that, allow all permissions (The screenshot below shows Administrators butit should be “domain\username” in your system)
DCOM 10016 Local Activation permission

If it doesn’t work, you may need to assign “Impersonate a client after authentication” permission to the user account following the instructions in this page.

References:

DCOM config security tab greyed out (Solved)

Ned 1 Comment

When you try to edit permissions of a DCOM component, you may notice that the permission settings are greyed out. In other words, they are not editable. Here is what to do when DCOM config security tab greyed out.

DCOM config security tab greyed out
Options are not editable in DCOM Properties window

DCOM (Distributed Component Object Model) is a technology that software components use to communicate with each other through network. It is a competitor of CORBA (Common Object Request Broker Architecture). Both technologies lost the communication battle against HTTP requests and web browser usage.

What to do when DCOM config security tab greyed out

In order to edit DCOM properties, you need to assign permissions to your user account. Follow the steps below. Make sure to backup your registry before making any changes.

  1. Go to “Start > Run”. Enter “regedit”
  2. Go to the key that is associated with the DCOM component you want to manage (It is IIS Admin Service in this example): HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{A9E69610-B80D-11D0-B9B9-00A0C922E750} 
  3. Right click on it. Select “Permissions”
  4. Click “Advanced”
  5. Change the owner to “Administrator” or your user account
  6. Click “OK”
  7. Select “Full Control” for the “Administrators” group and owner you selected
  8. Go to “Start >  Run”. Search for “services”
  9. Find “COM+ System Application”. Right click on the service, then click “Restart”
DCOM config security tab greyed out

Source