Unexpected exception in FeedCacheService.IsRepopulationNeeded: Unable to create a DataCache. SPDistributedCache is probably down..

My SharePoint Server out of the blue started throwing event ID 6398. The error is :

  • Unexpected exception in FeedCacheService.IsRepopulationNeeded: Unable to create a DataCache. SPDistributedCache is probably down..

I ran Get-CacheHost and it was listing an old SharePoint Server plus the new one. Trying to remove it resulted in the famous “CacheHostInfo is null” error.

The Service on SharePoint Central Admin also gave the same error “CacheHostInfo is null”.

I went and checked the DistributedCacheService.exe.config file and the information was listed. I also checked the registry key for AppFabric and it had no information, so I copied the information listed in the Config file and pasted it in the Registry.

I exported the config file, removed the old server and then imported the config again. After that I ran the following commands:

$SPFarm = Get-SPFarm
$cacheClusterName = “SPDistributedCacheCluster_” + $SPFarm.Id.ToString()
$cacheClusterManager = [Microsoft.SharePoint.DistributedCaching.Utilities.SPDistributedCacheClusterInfoManager]::Local
$cacheClusterInfo = $cacheClusterManager.GetSPDistributedCacheClusterInfo($cacheClusterName);
$instanceName =”SPDistributedCacheService Name=AppFabricCachingService”
$serviceInstance = Get-SPServiceInstance | ? {($_.Service.Tostring()) -eq $instanceName -and ($_.Server.Name) -eq “Server Name”}
$serviceInstance.Delete()
Add-SPDistributedCacheServiceInstance
$cacheClusterInfo.CacheHostsInfoCollection

This took a few minutes to run. When it was completed the AppFabric service started under services.msc and when I went to the Services under SharePoint Central Management it was also started.

Hope it helps

**Update**

It seems like this is a bug in SP1 for SharePoint. Randomly I get the same error and today I started having these errors logged every 5 min.

What I did was open up the SharePoint Management Shell as Administrator and then execute the following commands:

  • Stop-CacheCluster
  • Export-CacheClusterConfig
  • Import-CacheClusterConfig
  • Start-CacheCluster

This seems to work but for how long? The April CU for SharePojnt has not been released as yet. Hopefully it fixes this error.

Advertisements

Repair Exchange 2010 EDB to Access to Corrupted Mailbox Data

MS Exchange Server, an email server developed by Microsoft, is a contact manager-cum-calendaring software, which being a part of the Microsoft server line of products, runs on Windows server operating systems. Among the various versions of the Exchange Sever available today, Exchange Server 2010 is the most popular one. Nevertheless, it takes immense care to work efficiently.

Just like its previous versions, Exchange Server 2010 also possesses an EDB file (i.e. Exchange Database file) to store user’s Outlook mailbox data, including emails, contacts, calendar, tasks, notes, and other valuable information. Since the EDB file contains complete Outlook mailbox, you can actually figure out how significant it can be at the corporate level. Continue reading

PSConfig Stuck at 10%

After I rebuilt my SharePoint Server I moved across one last database. After a restart SharePoint reported that the database was in compatibility mode.

I opened up an elevated SharePoint PowerShell and ran the following command:

  • PSConfig.exe -cmd upgrade -inplace b2b -force

PSConfig went through the steps and got stuck on Step 3. This has to be a permission problem. Remembering that on my old server I made changes to the registry permissions.

I ran regedit and navigated to the following key:

  • HKEY_LOCAL_MACHINE\Software\Microsoft\Shared Tools\Web Server Extensions\15.0\Secure

If you right click on the secure key and click permissions you will see the WSS_ADMIN_WPG and WSS_WPG users. I granted both full access.

Immediately after I made this change the upgrade commenced and was successful.

Hope it helps

SharePoint 2013 SP1 Upgrade failure

I downloaded SP1 for SharePoint 2013 and applied it. After the reboot everything seemed normal. I then ran the products and configuration upgrade and it failed directly on step 2. I enabled all the services it stopped and saw if I could open up my sites.

The configuration site opened but when I tried to open up my main site it gave the famous “Sorry, Something went wrong” error.

I checked the event logs and saw that it was giving an error regarding the SharePoint Foundation 1033 language pack.

I ran a repair from “Programs and Features” and this failed with the same error regarding the language pack.

I then mounted the SharePoint 2013 ISO, tried to run a repair from there with the same error.

I then tried to uninstall SharePoint 2013 and I got the same error. I was not going to waste time so I built a brand new SharePoint Server.

After applying all updates and bringing SharePoint 2013 up to SP1 I had a plain site. Now the work began. I backed up all databases from the “old” SharePoint server and then restored them one by one on the “New” Server.

I then ran the products and Configuration wizard again and chose my SharePoint Farm config. It took a while but the setup was successful.

After that I was able to login to Central Management but not onto my site. I was missing my certificate, I imported this into IIS again, ran an IISReset and tried to open my site again. It failed with a custom error. I then checked the logs and it was complaining about the user profile service. I removed this and after I did this my site opened. I recreated the user profile site again.

After this SharePoint was slow, this could only mean that the DB’s needed to be upgraded as they were in compatibility mode.

After I ran PSConfig and did the upgrade SharePoint was now running like it should, however there was one thing missing. I needed to separate my page file from the C:\ drive. I did this, ran a reboot and after this no errors logged and everything well.

It is alot of work firstly setting up a new server but also moving the content DB’s and making sure everything works again.

Hope it helps

DPM 2012 SP1 Backing up SQL 2012 Database Error

I migrated SharePoint to a new server with SQL 2012 SP1 and setup backups with DPM.

The initial setup went fine as DPM could see the Farm, however after the protection group was setup the backups failed immediately with the following error:

  • Unable to Configure Protection

Not a problem, what I have seen from documents seems like a bug in DPM 2012 trying to backup SQL 2012.

To fix this, open up SQL Management Studio, Navigate to Security, expand logins and locate the following account:

  • NT Authority\SYSTEM

Right click on this account and select properties. Go to server roles and tick “sysadmin”. Apply these changes. Now go back to DPM and do a consistency check. It should now backup the databases.

If that fails, delete the protection group and create it again.

Hope it helps