COA Hub Services Troubleshooting
Web Service Response Codes:
Error Response Formatting:
<COA> <Error>ERROR CODE GOES HERE</Error> <ErrorMessage>ERROR RESPONSE MESSAGE</ErrorMessage> </COA>
400 Series codes: (Responses from 400 codes still WIP)
- Layer7 setup to give 400 response
- Still working on standardizing layer7 based response codes
| Request Point of Failure | Code | Message | Example of Issue |
|---|---|---|---|
| XML Schema: Inactive | 4001 | Entered Invalid XML Request: (Pass detail of validation error) | Entered Invalid XML Request:Inactive parameter can only be yes, no or blank. |
| XML Schema: COAType | 4001 | Entered Invalid XML Request: (Pass detail of validation error) | Entered Invalid XML Request: COAType can only be segment or hierarchy. |
| XML Schema: Segment | 4001 | Entered Invalid XML Request: (Pass detail of validation error) | Entered Invalid XML Request: Segment parameter can only be one of the following values:assignee, costcenter, costcenterparentchild, company, debitline, fund, gift, grant, ledgeraccount, location, program, project, revenuecategory, spendcategory, yaledesignated. |
| OutputFormat | 4004 | Entered invalid output format: (Pass format sent), Valid Values: xml, json | sent "csv" as a format |
| Authentication Failure | 4005 | Invalid Credentials, please check your username and password. Username Sent: | Mistyped username or password. |
| Layer7 Gateway Issue | 4006 | An issue has occurred at the gateway. Please check your request, any parameters, and your authentication. If problem persists, contact the Data Services team. | You may be violating policy standards. |
500 Series Codes: (Some still WIP)
- All codes from Talend will give a status code of "500" and a detail code in the response message.
| Code | Message | Example of Issue |
|---|---|---|