Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Repeating MyCo REST error in PegaRULES logfile

SA-40583

Summary



Administrators observing the following errors repeating in the PegaRULES logfile throughout the day.


Error Messages



2017-06-28 00:00:35,912 [ PegaRULES-Batch-3] [ STANDARD] [ ] [MyCoCPMHCSuper:07.13] ( connect.rest.RESTConnector) ERROR Rule-Connect-REST.PegaFW-Int-Social-UserProjects-List.List - Rule-Connect-REST: null - The service URL ML Server URLzcore/api/project.json does not start with a protocol and hostname - The service URL ML Server URLzcore/api/project.json does not start with a protocol and hostname
com.pega.pegarules.pub.services.OutboundMappingException: The service URL ML Server URLzcore/api/project.json does not start with a protocol and hostname
at com.pega.pegarules.integration.engine.internal.ServiceMappingUtils.getURLPrefix(ServiceMappingUtils.java:4284)
at com.pega.pegarules.integration.engine.internal.ServiceMappingUtils.getURLParts(ServiceMappingUtils.java:4202)


Steps to Reproduce



Not Applicable


Root Cause



A software use or operation error.

Resolution



The URL in the error message is part of the URL for eZi Core Text Analytics.

The information on how to configure this feature is given on page 2-2 of the CPM Social Engagement Implementation Guide:

https://pdn.pega.com/documents/customer-process-manager-cpm-713-social-engagement-implementation-guide

While using this feature, one should configure the correct URL for the ML server as given to you by the ML server admin. If you are not using this, clear the ML_Server, ML_APIId and ML_APIKey values.

Suggest Edit

Published August 26, 2017 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us