ThumbnailGeneratorService - Unable to render

Questions
1

We’re getting a few of these errors daily and can’t figure out what’s causing them.

[ERROR] Litium.Web.Administration.WebApi.Common.ThumbnailGeneratorService - Unable to render ‘Litium.Web.Administration.WebApi.Common.ViewModels.Thumbnail.ThumbnailGenerateRequestModel’. Current user might not have permission.

We don’t have any references to ThumbnailGeneratorService or ThumbnailGenerateRequestModel in our code. Is this something running inside Litium?

Litium version: 7.7.8

2

Yes, the system generates thumbnails for pages and blocks when they are updated. Thumbnails are used in Blocks mode when editing a page, and to display images in lists.

3

OK, but is the System then the “Current user [that] might not have permission”? How can we fix so we don’t get these errors?

4

Please check this one Node services

5

The account that the Application Pool is running under has read and write permissions to the NodeServices folder, yes.

We’re still getting the errors.

6

So how do we fix it?

7

Hi,

I am also getting the same error.
Date: 2023-01-02 16:04:45
Level: ERROR

Event:

Unable to render ‘Litium.Web.Administration.WebApi.Common.ViewModels.Thumbnail.ThumbnailGenerateRequestModel’. Current user might not have permission.

Do we have any solution for this ?

8

We haven’t been able to solve this. Waiting for Litium to suggest a solution.

1 Like
9

The ThumbnailGeneratorService is the service that is creating thumbnails for blocks and pages and also the preview’s of the block in the block editing mode.

Some example that I can think of right now is:

  • The computer where the application is running is not configured to allow requests to the domain name that is used for back office.
  • The installation is using a multiserver setup that not using the same encryption keys on all applications, in IIS it’s usual the machine key from the web.config that need to be the same. Also that the installations are using the same folder for the shared storage.
  • The time between that the user made some change and that the background process executes is to long so the authentication ticket has expired.
  • Maybe some content that making the process to crash instead of returning the data or specific error-code.

With the information in this thread it’s impossible to say why it happen, only that it happen. We need more information about how we can reproduce this error to be able to investigate more.

10

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.