Error when importing widget in Chrome/ALL browsers

Importing and other background tasks require a few components to be running correctly that I recommend checking;

1. The job server must be running, and it must be configured to use the same filestorage path in its app.config as in the web node's web.config.
2. A message bus (ideally the included Socket Message Bus Server) must be running, and both the job server and the web node(s) must be connected to it. This can be verified in Administration > Site > Message Buses > Socket Message Bus > Diagnostics. All web nodes and the job server should be listed and green.

Beyond that, I'd inspect any exceptions logged when this occurs.

They all seem to be running fine.

Does the job server require any special write permissions to the filestorage folder?

Yes, it requires the same write permissions as the web app. Are you seeing exceptions logged when this occurs?

No, I can't see any exceptions. Just asking.

Can you please share a diagnostic export as well as a screenshot of the bus diagnostics from the same time that this occurs?

Here is the screenshot of the bus diagnostics. What is a diagnostic export?

It's in Administration > About. Please ensure it's an export from the same time as this occurs.

Here you go

./cfs-file/__key/communityserver-discussions-components-files/2858/diagnostics.xml

Here you go

./cfs-file/__key/communityserver-discussions-components-files/2858/diagnostics.xml

Bump!

The diagnostics identify that the scheduling of the upload tasks is taking place correctly. I do see some errors from the job service identifying memory limitations when communicating with the database, such as

"System.Data.SqlClient.SqlException (0x80131904): There is insufficient system memory in resource pool 'internal' to run this query."

While these aren't happening coincidentally, they could be related to an overall issue with the job server deployment. I'd recommend reviewing any limitations in place on it, as well as still recommend making sure its file storage is configured correctly and has proper permissions.

There are also improvements made to background task processing feedback in more recent versions of Community than you are using. Specifically, version 11.1.2.11315 made some improvements that should help to more clearly identify what error may be occurring in your case. But if you do upgrade, I'd recommend upgrading to the latest version of 11.