2013 – Crawl errors: The process cannot access the file because it is being used by another process. (Exception from HRESULT: 0x80070020)

after we’ve done the installation of CU february 2020 (KB4484263), we’re getting lots of crawl errors with Exception code:

HRESULT:0x80070020 – The process cannot access the file because it is being used by another process.

We have SharePoint 2013, Windows Server 2012

Microsoft has recommended that we have to configure the antivirus software to exclude folders/subfolders from antivirus scanning as per: https://support.microsoft.com/en-gb/office/certain-folders-may-have-to-be-excluded-from-antivirus-scanning-when-you-use-file-level-antivirus-software-in-sharepoint-01cbc532-a24e-4bba-8d67-0b1ed733a3d9?ui=en-us&rs=en-gb&ad=gb

But nothing helps.

Maybe someone has the same error and can help us. 🙂

Thanks Katharina

c++ – DirectX 11 C2661 & C2664 errors constructing SpriteBatch / SpriteFont

I keep having these two errors:

enter image description here

  • Error C2664 ‘DirectX::SpriteBatch::SpriteBatch(const DirectX::SpriteBatch &)’: cannot convert argument 1 from ‘ID3D11DeviceContext *’ to ‘DirectX::SpriteBatch &&’ C:Program Files (x86)Microsoft Visual Studio2019CommunityVCToolsMSVC14.26.28801includememory 2068

  • Error C2661 ‘DirectX::SpriteFont::SpriteFont’: no overloaded function takes 2 arguments C:Program Files (x86)Microsoft Visual Studio2019CommunityVCToolsMSVC14.26.28801includememory 2068

I used this source,

std::unique_ptr<SpriteBatch> spriteBatch;
std::unique_ptr<SpriteFont> spriteFont;

spriteBatch = std::make_unique<SpriteBatch>(deviceContext);
spriteFont = std::make_unique<SpriteFont>(device, L"myfile.spritefont");

spriteFont->DrawString(spriteBatch.get(), L"Hello, world!", XMFLOAT2(x, y));

I tried wrapping my: ID3D11Device & ID3D11DeviceContext with Microsoft::WRL::ComPtr<>, but still throws error. Seems there’s some issue with the <memory>.

I tried:

ComPtr<ID3D11Device> device = nullptr;
ComPtr<ID3D11DeviceContext> deviceContext = nullptr;


Reason: cannot convert from 'ID3D11DeviceContext *' to 'DirectX::SpriteBatch'
No constructor could take the source type, or constructor overload resolution was ambiguous.

centos – Logical volume corrupting causing I/O errors after writing an arbitrary amount of data to the disk

I am using a CentOS 7 VM running on vSphere. My primary logical volume where the errors are occurring is formatted in ext4. When the VM is created from our standard image, all is fine but after working on it for a while or adding some data to the disk something goes wrong and the volume starts throwing input/output errors. I relaunched the VM several times from a standard image we use to run many other VMs on the same server. Originally I was using real data but to rule out any issues with the data I began using dummy data I generated. After loading roughly 10GB of data onto the server the volume would begin showing buffered I/O errors in dmesg before the transfer even completed.

I had our virtualization team create a new CentOS image and this time I was able to get 20 GB or so of data I needed onto the server without errors. I then went to build an app I was trying to deploy with docker and during the download of the docker image the VM began to throw I/O errors and kernel panicked. After the kernel panic the VM was unresponsive, bash was still running but it couldn’t even locate ls or dmesg to check the error logs. I am unsure where to go from here. I have spent the better part of a week reinstalling the vm trying to pinpoint what is causing the issue. I have had no issue with all of my other docker based deployments either.

Virtualization team says they don’t think the issue is at a hardware or vSphere level as none of the other VM’s running on the system have encountered this issue. I would appreciate any indications of what to do next regarding trouble shooting this issue before I need to resort to a plan B and deploy on a Windows VM.

macOS Catalina: Install Slows and Errors on MacBook Pro (13-inch Mid 2012)

For around 6 months I had intermittent issues with my MacBook Pro (13-inch Mid 2012) where it was randomly ending up on the folder with a question mark icon, or the no-entry icon.

It used a 250GB Samsung 840 SSD – which I had installed in 2014 – and I figured it must have finally been at its end-of-life.

I’ve replaced it with a 1TB Crucial MX500 SSD; the swap went smoothly and as expected.

Now, I’m having problems installing macOS Catalina at all.

After installing the new drive I did the following steps:

  1. Downloaded the latest macOS Catalina from the App Store on my iMac
  2. Created a new Catalina Install drive using Terminal createinstallmedia
  3. Booted from the USB on the MacBook Pro
  4. Formatted the drive to APFS in DiskUtility
  5. Used the macOS install button, accepting terms etc..

The installer gets to around 50% normally (in around 5 minutes), but then it slows down dramatically, with the estimated time floating around 5-7 minutes constantly. The loading bar continues to move incredibly slowly (using the ol’ cursor on the boundary of the loaded section to track progress).

This goes on for well over an hour, and at around 70% it fails with the error:

An error occurred while preparing the installation. Try running this application again.

I’ve taken the following troubleshooting steps so far:

  1. Reset SMC
  2. Reset NVRAM, PRAM
  3. Recreated the install USB pendrive
  4. Re-recreated the install usb on another USB pendrive
  5. Used different USB ports
  6. Online-recovery (defaults to Mountain Lion, which got all the way through the progress bar then loads to a folder with a question mark at mid-install auto-reboot)
  7. Cloning the old Samsung SSD to the new Crucial SSD in DiskUtility
  8. Numerous power-cycles, and letting the machine sit for a bit etc.
  9. Run health-checks on the old and new SSDs, both return no issues

The machine had otherwise been running great. Fast as always with no known issues with RAM, or battery life, etc.. I can’t think of what else to try at this point.

The machine’s also in near-new condition, it’s been very well looked after. All the ports etc are clean and in good working order, as are the charge cables.

There are no Apple stores or authorised repair centres where I live (boat/flight required for the closest, which isn’t an option due to Covid lockdown).

Any ideas on what to try next would be greatly appreciated, I’d very much like to see this MacBook working again.

Many Thanks


install fail point
point where install slows drastically

javascript – Errors while creating stories for a React component in a Next.js + Flow Setup

I’m trying to create stories (for storybook version 6.0.0-beta.37) for a component (called Editor) within a complex web-application involving React, Next.js, the Flow transpiler and many more.

There’s both an Editor component as well as a component EditorWithTranslation = withTranslation(Editor) where withTranslation wraps its argument with the consumer of a translation-context. I tried to create a component for both Editor and EditorWithTranslation.

The story for the Editor component doesn’t use contexts but it just passes the translation property as such:

// @flow

import React from 'react';

import Editor, { type EditorProps } from './Editor';

export default {
    component: Editor,
    title: 'Editor',
    includeStories: /.*Story$/,

export const editorDefaultProps: EditorProps = {
    foo: 'foo-test',

    translation: {
        bar: 'bar-test',

export function EditorDefaultStory() {
    return <Editor {...editorDefaultProps} />;

When I attempt to display the “Canvas” tab of this story from storybooks web-interface, this error message is shown:

Element type is invalid: expected a string (for built-in components)
or a class/function (for composite components) but got: undefined. You
likely forgot to export your component from the file it’s defined in,
or you might have mixed up default and named imports.

Check the render method of storyFn.

What does this error message mean? What’s going on? How can I fix the error?

The story for EditorWithTranslation wraps the component with a provider of the translation-context, using a decorator:

// @flow

import React from 'react';

import EditorWithTranslation, { type EditorWithTranslationProps as EditorWithTranslationDefaultProps } from './EditorWithTranslation';

import { Provider as TranslationProvider } from '../../translation/Context';

export default {
    component: EditorWithTranslation,
    title: 'EditorWithTranslation',
    includeStories: /.*Story$/,
    decorators: ((storyFn: any) => <TranslationProvider>{storyFn()}</TranslationProvider>),
    // I also tried this but I think it leads to the same error:
    //decorators: ((StoryFn: any) => <TranslationProvider><StoryFn/></TranslationProvider>), 

export const editorWithTranslationDefaultProps: EditorWithTranslationDefaultProps = {
    foo: 'foo-test',

export const EditorWithTranslationDefaultStory = () => <EditorWithTranslation {...editorWithTranslationDefaultProps} />;

Attempting to display the “Canvas” tab of this story, leads to the following error message:

can’t access lexical declaration `Provider’ before initialization

What does this error message mean? What’s going on? How can I fix the error?

I also tried to understand the cause of these errors by creating a separate, minimal sample project with React, Next.js, Flow and Storybook but the errors didn’t occur and everything worked fine.

web api – API Design: Errors passed between APIs

I work as a developer on a few different APIs that make calls to each other.
Let’s take two and call them API-USER and API-BUSINESS.

A user application makes calls to API-USER, which in turn makes calls to API-BUSINESS

Right now, when API-BUSINESS returns an error the API-USER receives it as a generic error and passes it through to the user.

The concern is that this approach could lead to issues when breaking changes are introduced to the errors in API-BUSINESS.

Are there some API patterns or practices that can lead to a more durable approach to passing errors between APIs?

Is there a better vocabulary to use when talking about this type of error passing?

views – I have a ton of errors for a non-existent config entity name in dblog when I refresh cache

When I refresh my cache, my dblog is shooting out a ton of errors for the type “view”.

I received a ton of these warnings:

A non-existent config entity name returned by FieldStorageConfigInterface::getBundles(): entity type: paragraph, bundle: rs, field name: field_website

I migrated my D7 site to D8. One of the things migrated are migrating all my field_collections to paragraphs, could this be the issue?

I disabled all my custom views and the error still persists.

Any idea what could be the issue?


composer – Magento 2 replace dotmailer/dotmailer-magento2-extension errors with compiler error

We have added the following to composer json in M 2.3.5

    "replace": {
    "dotmailer/dotmailer-magento2-extension": "*",

Then we run php bin/magento setup:di:compile

And are presented with this error

Repositories code generation... 1/8 [===>------------------------]  12% 1 sec 88.5 MiB
PHP Fatal error:  Interface 'DotdigitalgroupEmailBlockAdminhtmlEngagementCloudEmbedInterface' 
not found in /var/www/html/m2/m2_dev/vendor/dotmailer/dotmailer-magento2-extension-chat/Block/Adminhtml/StudioChatWidget.php on line 13

Question: Is there more we need to do to disable Dotdigital?

node.js – Discord.js snipe command not working, no errors on terminal

I’m trying to make a snipe command, and everytime I use the command the return message “I couldn’t find any last deleted messages.” is what I get even if there was a message that was deleted. There are no errors appearing on the terminal so I’m a little lost at what to do.

This is what the command looks like

const msg = bot.snipes.get(message.channel.id)
if(!msg)return message.channel.send("I couldn't find any last deleted messages.")

const embed = new Discord.MessageEmbed()

And I’ve defined the set with

bot.snipes = new Map();
bot.on('messageDelete', function(message, channel){
        content: message.content,
        author: message.author.tag,
        image: message.attachments.first() ? message.attachments.first().proxyURL : null

Any help would be greatly appreciated, thank you very much!

dual boot – How to permanently fix errors with ntfs volume to be mounted in RW mode. Need ntfsfix everytime

I have one SSD disk with installed Windows 10 and Ubuntu 20.04 on the same disk.
I also have the second HDD drive with NTFS filesystem which should be shared between Windows and Ubuntu.
I put the entry to /etc/fstab to automatically mount the HDD disk, however it is mounted in read only. If I run “ntfsfix /dev/sdb2” and reboot Ubuntu – the disk is mounted in RW mode as I want.

However, if I use Windows (just boot it and shutdown) and after that boot Ubuntu – I have the same error with HDD – it is not mounted in RW, and in read only mode. So I again need perform “ntfsfix”, reboot Ubuntu.

Is there any way to fix this error permanently? I know that it is possible to perform “ntfsfix” during the every Ubuntu boot, but this solution seems to me not elegant.
Turning off the Hybernate on Windows seems not the solution as the HDD is not system, and not used by Windows system.

The HDD volume I mount is not system, it is just for data/media files. The HDD has 3 partitions (two small unallocated and unformatted 1mb and 45mb before and after the main partition, and one main partition /dev/sdb2 with the whole disk space)