We have an Add-on package (a ZIP file) that contains a manifest file, configuration, and External Content Library (ECL) Provider-related DLL files as per guidelines from SDL docs. https://docs.rws.com/816112/782949/sdl-tridion-sites-9-5-main-documentation/add-ons-feature https://docs.rws.com/816112/750864/sdl-tridion-sites-9-5-main-documentation/basic-structure-of-the-add-on-manifest-file
We are uploading this package to CMS (Tridion 9.5) through Add On service but received the below error
One or more Extensions in the Add-on failed to run. Contact the developer(s) of the Extension(s) to have this issue resolved
Can not initialize add-on. (Environment: cmSites, Client Identity: IP-A***B, Process: TcmBatchProcessor)
Can not initialize add-on. (Environment: cmSites, Client Identity: IP-A***B, Process: TcmServiceHost)
Can not initialize add-on. (Environment: cmSites, Client Identity: IP-A***B, Process: Tridion.TranslationManager.Service)
Can not initialize add-on. (Environment: cmSites, Client Identity: IP-A***A, Process: TcmPublisher)
Can not initialize add-on. (Environment: cmSites, Client Identity: IP-***CB, Process: TcmWorkflowAgent)
Can not initialize add-on. (Environment: cmSites, Client Identity: IP-***9A, Process: TcmServiceHost)
Can not initialize add-on. (Environment: cmSites, Client Identity: IP-A***CB, Process: TcmSearchIndexer)
Can not initialize add-on. (Environment: cmSites, Client Identity: IP-A***B, Process: w3wp)
Has anyone experienced similar issues? Any help would be greatly appreciated.
Update1:
Manifest.json:
{
"manifestVersion": "1.0",
"version": "1.0.0.0-release",
"id": "CloudinaryProvider",
"author": "my company",
"description": "Cloudinary ECL Provider by company",
"name": "Cloudinary Provider"
}