# Failed to initialize the bundle for encoder esapi **URL:** \ **Category:** Forum\ **Created:** [November 12, 2020, 2:53pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029 "2020-11-12T14:53:27Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 12, 2020, 2:53pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/1 "2020-11-12T14:53:27Z")
We are seeing this error massage continuously written on webMethods(9.8) IS server. Not sure about the error. Any help on this will be appreciated ---
**Author:** ![Holger\_von\_Thomsen](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/holger_von_thomsen/32/178_2.png) [@Holger\_von\_Thomsen](https://techcommunity.softwareag.com/u/Holger_von_Thomsen)\ **Post date:** [November 12, 2020, 4:45pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/2 "2020-11-12T16:45:22Z")
Hi Raghavendra, can you please provide the complete Error message as well as the Fix level you have applied to IS 9.8? Did you try to search the community forums for this error message? Hopefully, you will find some older posts here which are referring to this issue as well. Regards, Holger ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 13, 2020, 8:43am UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/3 "2020-11-13T08:43:28Z")
Hi Holger, we are on fix 22 IS\_9.8\_Core\_Fix22 Yes i did search community forms related to this error but didnt find anything similar and about the error message this is what we are seeing in logs piling up [1114]2020-11-13 08:42:24 GMT [ISC.0072.0023E] Failed to initialize the bundle for encoder “esapi” ---
**Author:** ![Holger\_von\_Thomsen](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/holger_von_thomsen/32/178_2.png) [@Holger\_von\_Thomsen](https://techcommunity.softwareag.com/u/Holger_von_Thomsen)\ **Post date:** [November 13, 2020, 1:29pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/4 "2020-11-13T13:29:43Z")
Hi Raghavendra, the latest Fix for 9.8 I am aware of is IS\_9.8\_Core\_Fix30. In the readme I could find the following entry: ```auto PIE-40027 (IS_9.8_Core_Fix7) Integration Server logs the wrong message when it cannot find the encoder "esapi". When Integration Server cannot find the encoder "esapi", it logs the following wrong error message: [ISC.0072.0023E] Couldnt initialize encoder "{0}". Whereas, Integration Server should log the following message: ISC.0072.0023E] Failed to initialize the bundle for encoder 'esapi'. This issue is resolved now. ``` As you are above of Fix7 by using Fix22 (as indicated by the error message), you should check why the IS is not able to find the encoder. Might be a Class-Loading issue. Is there any thing related to this in the wrapper.log of this instance? Was this working once in the past? If yes, were there any changes to this installation lately? Regards, Holger ---
**Author:** ![Kalpesh\_Shah1](https://avatars.discourse-cdn.com/v4/letter/k/aca169/32.png) [@Kalpesh\_Shah1](https://techcommunity.softwareag.com/u/Kalpesh_Shah1)\ **Post date:** [November 13, 2020, 2:42pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/5 "2020-11-13T14:42:42Z")
Does this problem occur on newly created IS instance or an existing one? Can you please make sure that you have installed latest OSGi platform fixes in your env? Thanks, -Kalpesh. ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 13, 2020, 3:09pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/6 "2020-11-13T15:09:46Z")
> [@Holger\_von\_Thomsen](#): > > Might be a Class-Loading issue. Yes correct occurs on new created IS instance Regards, Raghavendra ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 13, 2020, 3:10pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/7 "2020-11-13T15:10:23Z")
Yes correct occurs on newly created IS instance Regards, Raghavendra ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 13, 2020, 3:13pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/8 "2020-11-13T15:13:00Z")
to add more this new instance has been installed on same server where already has an existing IS Instance is working fine ---
**Author:** ![Holger\_von\_Thomsen](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/holger_von_thomsen/32/178_2.png) [@Holger\_von\_Thomsen](https://techcommunity.softwareag.com/u/Holger_von_Thomsen)\ **Post date:** [November 13, 2020, 3:48pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/9 "2020-11-13T15:48:00Z")
Hi Raghavendra, is this a complete new installation in a different wM Root directory or just a second instance to the existing installation? The first one (as long as you keep the instance name as “default”) should work while applying Fixes. The second one might have issues when the instance name is differing. See the Readmes for further informations on this. Regards, Holger ---
**Author:** ![wayne.leishman.20059](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/wayne.leishman.20059/32/33520_2.png) [@wayne.leishman.20059](https://techcommunity.softwareag.com/u/wayne.leishman.20059)\ **Post date:** [November 13, 2020, 3:52pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/10 "2020-11-13T15:52:09Z")
> [@raghavendra.madhurai](#): > > Failed to initialize the bundle for encoder “esapi” I found this issue in our archives for wM IS 9.8. It was reported April 2017. Here’s a summary explanation of the problem and solution: “If a new IS instance was created **after** fix installation, the OSGI patches from fixes are not copied. Therefore, the OSGI patches need to be re-installed in new instances. Please use Update Manager to over install the IS core fixes again, and OSGI patches will be updated in the new instance” Note: the file containing the bundle info for an instance is stored under: \profiles\IS\_\configuration\org.eclipse.equinox.simpleconfigurator\ bundles.info This is for your information. This file will be updated with the proper files after running SUM. Wayne Software AG wM Principal Instructor ---
**Author:** ![wayne.leishman.20059](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/wayne.leishman.20059/32/33520_2.png) [@wayne.leishman.20059](https://techcommunity.softwareag.com/u/wayne.leishman.20059)\ **Post date:** [November 13, 2020, 3:58pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/11 "2020-11-13T15:58:33Z")
Sorry, the path to bundles.info should be: \profiles\ **\** \configuration\org.eclipse.equinox.simpleconfigurator\ bundles.info ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 13, 2020, 5:03pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/12 "2020-11-13T17:03:39Z")
Hi Holger, yes its just a second instance added to the existing installation, As explained by you and Wayne below i will try to reinstall the corefix and let know the results really appreciate for your suggestions Thanks, Raghavendra ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 13, 2020, 5:05pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/13 "2020-11-13T17:05:52Z")
Hi Wayne, Yes i think this is something we didnt do after creating a new instance, as suggested will try to reinstall the corefix and let know the results Thanks Raghavendra ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 18, 2020, 7:44am UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/14 "2020-11-18T07:44:27Z")
Hi Wayne, Reinstallation of fix resolved the issue Thanks 🙂 Regards, Raghavendra ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 18, 2020, 4:22pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/15 "2020-11-18T16:22:08Z")
Hello, We have a new issue now the schedulers which are running on the existing instance are getting suspended with the below error WTEESB05.axa-uk-test.intraxa:6666)Unknown Service: ie.axai.esb.events.emailNotifications:process. Scheduled task will not run. The old instance is running on Port 5555 in the new instance we can see schedulers are created by themselves we tried to specify with server to use specific hostname watt.server.scheduler.logical.hostname=InstanceName but still some schedulers are failing because they run on server level logs ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 18, 2020, 4:33pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/16 "2020-11-18T16:33:31Z")
Hi Holger, We have a new issue now the schedulers which are running on the existing instance are getting suspended with the below error WTEESB05.axa-uk-test.intraxa:6666)Unknown Service: ie.axai.esb.events.emailNotifications:process. Scheduled task will not run. The old instance is running on Port 5555 in the new instance we can see schedulers are created by themselves we tried to specify with server to use specific hostname watt.server.scheduler.logical.hostname=InstanceName but still some schedulers are failing because they run on server level logs ---
**Author:** ![Holger\_von\_Thomsen](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/holger_von_thomsen/32/178_2.png) [@Holger\_von\_Thomsen](https://techcommunity.softwareag.com/u/Holger_von_Thomsen)\ **Post date:** [November 18, 2020, 5:31pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/17 "2020-11-18T17:31:10Z")
Hi Raghavendra, did you try to restart the “old” instance afterwards? Or you might have to reactivate the scheduled tasks in IS Admin UI. Regards, Holger ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 18, 2020, 5:34pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/18 "2020-11-18T17:34:38Z")
Hi Holger, yes i did restart the old instance I reactivated the tasks in IS Admin UI but it fails with same error one more observation what i am seeing is if i am creating any new task on new instance it gets created on old instance also ---
**Author:** ![Holger\_von\_Thomsen](https://sea1.discourse-cdn.com/techcommunity/user_avatar/techcommunity.softwareag.com/holger_von_thomsen/32/178_2.png) [@Holger\_von\_Thomsen](https://techcommunity.softwareag.com/u/Holger_von_Thomsen)\ **Post date:** [November 18, 2020, 5:37pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/19 "2020-11-18T17:37:31Z")
Hi Raghavendra, are the two instances sharing the same database schema? As long as the instances are not meant for being clustered, they should be using dedicated schemas (one for each instance). Regards, Holger ---
**Author:** ![raghavendra.madhurai](https://avatars.discourse-cdn.com/v4/letter/r/4491bb/32.png) [@raghavendra.madhurai](https://techcommunity.softwareag.com/u/raghavendra.madhurai)\ **Post date:** [November 18, 2020, 5:38pm UTC](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029/20 "2020-11-18T17:38:37Z")
yes both the instances share the same database schema [Next page](https://techcommunity.softwareag.com/t/failed-to-initialize-the-bundle-for-encoder-esapi/235029.md?page=2)