Error in logs for initservices/dnode & vbd is not present in PrConfigSettingsRegistry.
Hi Team,
Recently we upgraded our instance to pega 8.8.1v and we started observing below errors on our logs.
Could you share some solution to resolve these errors and if we need to set these Application settings !! then what was the default values !
Pega-Engine ==> prconfig/initservices/dnode/default
Pega-Engine ==> prconfig/initservices/vbd/default
Error in logs -
Hi Team,
Recently we upgraded our instance to pega 8.8.1v and we started observing below errors on our logs.
Could you share some solution to resolve these errors and if we need to set these Application settings !! then what was the default values !
Pega-Engine ==> prconfig/initservices/dnode/default
Pega-Engine ==> prconfig/initservices/vbd/default
Error in logs -
2023-03-29 05:20:17,269 [til LISTENER_STARTUP] [ STANDARD] [ ] [ ] ( basic.config.SettingsImpl) ERROR - The setting initservices/dnode is not present in PrConfigSettingsRegistry. API is depreciated. Please use new API to get the setting information. java.lang.Exception: Information : Setting does not exist in PrConfigSetting enum. at com.pega.pegarules.exec.internal.basic.config.SettingsImpl.logMessageForDepreciatedAPI(SettingsImpl.java:803) ~[prprivate-exec.jar:?] 2023-03-29 05:20:25,207 [til LISTENER_STARTUP] [ STANDARD] [ ] [ ] ( basic.config.SettingsImpl) ERROR - The setting initservices/vbd is not present in PrConfigSettingsRegistry. API is depreciated. Please use new API to get the setting information. java.lang.Exception: Information : Setting does not exist in PrConfigSetting enum. at com.pega.pegarules.exec.internal.basic.config.SettingsImpl.logMessageForDepreciatedAPI(SettingsImpl.java:803) ~[prprivate-exec.jar:?]
Accepted Solution
Updated: 13 Jun 2023 5:45 EDT
Pegasystems Inc.
PL
Hi, @HARIL043 ,
We have observed this error messages caused by custom instances of Data-Admin-ServiceType. In your case, you need to look for ones named VBD and DNODE. You can check by going to the Dev Studio -> App -> Find Data-Admin-ServiceType and click on the class name in the list. There you will see list of all ServiceType instances.
It should be safe to remove VBD and DNODE, as they are deprecated. Make sure to test the changes on lower environments before applying in production.
Regards,
Accepted Solution
Updated: 13 Jun 2023 5:45 EDT
Pegasystems Inc.
PL
Hi, @HARIL043 ,
We have observed this error messages caused by custom instances of Data-Admin-ServiceType. In your case, you need to look for ones named VBD and DNODE. You can check by going to the Dev Studio -> App -> Find Data-Admin-ServiceType and click on the class name in the list. There you will see list of all ServiceType instances.
It should be safe to remove VBD and DNODE, as they are deprecated. Make sure to test the changes on lower environments before applying in production.
Regards,