Question
Lanit
RU
Last activity: 14 Jul 2017 3:57 EDT
Failed to retrieve Rule-Service-SOAP instance XXX using default rulesets
Hello everyone!
We have a SOAP integration - two services, two WSDL. Services, service packages and other rules are made in the same way. Both service packages have the same Service access group.
Service #1 works correct - returns correct WSDL, returns correct responses for requests.
Service #2 works strange - returns incorrect WSDL (almost empty), returns an error for requests.
Returned WSDL:
Service response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Failed to retrieve Rule-Service-SOAP instance SUDIRReferenceService.Services.getSupportingData using default rulesets (Data-Admin-ServicePackage SUDIRReferenceService doesn't exist)</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Of course Service package exists.
Hello everyone!
We have a SOAP integration - two services, two WSDL. Services, service packages and other rules are made in the same way. Both service packages have the same Service access group.
Service #1 works correct - returns correct WSDL, returns correct responses for requests.
Service #2 works strange - returns incorrect WSDL (almost empty), returns an error for requests.
Returned WSDL:
Service response:
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<soap:Body>
<soap:Fault>
<faultcode>soap:Server</faultcode>
<faultstring>Failed to retrieve Rule-Service-SOAP instance SUDIRReferenceService.Services.getSupportingData using default rulesets (Data-Admin-ServicePackage SUDIRReferenceService doesn't exist)</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
Of course Service package exists.
This problem occurs only on one environment - on the customer environment, does not reproduces on our dev and qa.
1. What is the reason of this error?
2. What is known as "default rulesets"? I thought that requestor gets standard access group PRPC:Unauthenticated and because of that he can't see Service Package from our application. But when I tried to set this AG if service package, I get another error: Failed to retrieve Rule-Service-SOAP instance SUDIRReferencesService.Services.getSupportingData using access group PRPC:Unauthenticated.
Environment was rebooted, service package was resaved, but no changes.
I've already created an SR SR-A100903 for this problem, but for now got no answer.
***Updated by moderator: Marissa to blur proprietary information in images, removed #helpme and Ask the Expert group tags. Apologies those should not have been available to users.***
Accepted Solution
Pegasystems Inc.
US
Your statement was "returns incorrect WSDL (almost empty), returns an error for requests".
Therefore, any client using that WSDL is going to get an error, correct? What the context of the error is would appear to be moot since the client has not even been told how to call the service.
The crux of your issue is "returns incorrect WSDL (almost empty)". If we correct that, we likely do not look at the error currently being sent back in a response.
How could the Service Package be suspect when it works fine for your working service?
10-6 update - Resolved through SR - "tester tried to get wsdl and call service method with incorrect url (one character was missing)"
Pegasystems Inc.
US
The service response from an invalid service should not concern you. What is your service supposed to do?
Lanit
RU
Hi Paul!
What do you mean by "The service response from an invalid service should not concern you"? This is our service, and for some reason it does not work.
Service has two methods, they return some data.
If we run service manually in Pega it works fine. The problem is in service package.
Accepted Solution
Pegasystems Inc.
US
Your statement was "returns incorrect WSDL (almost empty), returns an error for requests".
Therefore, any client using that WSDL is going to get an error, correct? What the context of the error is would appear to be moot since the client has not even been told how to call the service.
The crux of your issue is "returns incorrect WSDL (almost empty)". If we correct that, we likely do not look at the error currently being sent back in a response.
How could the Service Package be suspect when it works fine for your working service?
10-6 update - Resolved through SR - "tester tried to get wsdl and call service method with incorrect url (one character was missing)"