A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

DXP Deployment issue

Vote:
 

Hi

We deployed our build to the ADE1 DXP environment and everything was working correctly.
However, when we redeployed the same build again, the Language Manager stopped working in the ADE1 environment.

We are using CICD pipeline.

Language Manager version is 5.5.1
Episerver.CMS version is 12.29.1

This exception showing in  Azure log -- No service for type 'EPiServer.Labs.LanguageManager.Configuration.ILanguageManagerConfig' has been registered.


Thanks,

Deepmla Sharma

#341050
Edited, Nov 21, 2025 8:13
Vote:
 

Hi Deepmla Sharma

Can you share the snippets from your appsettings.json and Startup.cs relating to Language Manager please? 

If this problem is only occurring on DXP environment (and not locally on your development machine) then it may be worth looking at the app settings JSON files transforms (e.g. in appsettings.Integration.json).

Thanks,
Jon

 

#341053
Nov 21, 2025 9:28
Vote:
 

Hi Jon Williams,

We have the add-on of Language manager so don't have anything related to Language manager in Startup and Appsetting.json files.

In our local developer machine working fine.



Thanks,

Deepmala

#341054
Nov 21, 2025 10:10
Vote:
 

Have you verified that the addon is included in your modules folder when you deploy? 

#341139
Nov 28, 2025 21:11
Vote:
 

The issue appears to be related to dependency injection, as it indicates that ILanguageManagerConfig  is not registered. I suspect that a related dependency or AddOn registration may be missing. You can also try registering it explicitly in your local environment to validate.

#341193
Edited, Dec 02, 2025 8:45
Vote:
 

You may also want to double check that you have the 'EPiServer.Labs.LanguageManager.dll' published to the 'bin' folder on your Integration environment. 

#341213
Dec 03, 2025 11:27
Vote:
 

Hi Jon Williams, Pär Wissmark , Sanjay Kumar,

We were facing 2 issue - TinyMCE initialization failure and Language manager disapear.

Over the past few weeks, several Optimizely CMS projects began experiencing a puzzling failure: XHtmlString fields stopped initializing TinyMCE in the edit interface. The editor simply refused to load, leaving users unable to manage rich text content. This issue surfaced in multiple unrelated projects, so it was clear the root cause wasn’t project-specific code.


Now we follow the steps according to given in below link. Both issue resolved and deployment is happening properly from pipeline.
https://powerbuilder.home.blog/2025/12/08/fixing-tinymce-initialization-failures-in-optimizely-cms-a-hidden-pipeline-issue-with-net-sdk-versions/

 

Thanks,

Deepmala Sharma

#341242
Edited, Dec 09, 2025 9:09
Vote:
 

Hi Deepmla Sharma.

I'm glad that you manage to solve it. 

Thanks for coming back on this thread.

Warm regards,
Jon

#341243
Dec 09, 2025 10:06
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.