Service Connection Failure Message in A2A DF
Hello everyone -
I have set up an A2A (Archer to Archer) data feed. However, when I run it, it faults and gives the following message: Service Connection Failure: No data has been processed.
Does anyone knows what causes this and how to fix this? I think it could be related to the Username that is defined in the Feed information of the DF General tab. That user is used to access the target application, but is not listed in the Access Control page.
- Community Thread
- Forum Thread
- RSA Archer
- RSA Archer Suite
I think it is something like that and thank you for posting the document.
- The data feed Security user credentials are set to Anonymous.
- In IIS, at the Archer level, I do have Anonymous disabled.
- But, also in IIS, I have the ws folder within the Archer site has Anonymous enabled.
This is the same configuration as in our development and staging environments, and the data feeds are able to connect in those environments. But they are not connecting in the production environment.
Looks like you have everything in IIS setup correctly so it is likely due to a problem logging into the instance that is running the report.
Here are some other things I can think to try (if you have not already done so )
1) Retype the password. Passwords always need to be retyped when a data feed configuration is imported into a different environment then it was exported. This is because the key used to encrypt passwords is different in each environment so it can't be decrypted in another environment. Retyping the password will cause it to be encrypted properly.
2) The credentials in the Transport Configuration section of the Transport tab is what is being used to log into the source instance. Try logging into the web application using these same credentials. You want to log into the instance in which the content is being retrieved, not the instance in which the target application is located (if pulling content from a different instance). If you are unable to log in but the account exists, check the status. I have seen (and I have done this myself) where the account gets locked because the data feed incorrectly tries to log in too many times.
3) If neither of these work I would suggest the next step be to contact customer support.
Thank you so much for all responses. Much appreciated. Does anyone know anything else that we can try? The issue is unfortunately still unresolved. Still actively looking for a solution to this.
Thanks again for all the input!!
It turns out that the issue we were having was related to an invalid certificate on the application server. Something had changed with the certificate authority. Once they installed a new certificate, the A2A data feed worked as expected.