Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 6 Current »

This page will be for adding issues that we identify that different organizations had in getting that first request to work in the lab.  Our experience has been that after the first web service action goes through, any of the subsequent requests with different web services are successful.

Network Issues

There are situations in which you may see an error message such as this:

Note the Support ID
":[{"code":"WebService.SystemError","message":"The requested operation was rejected. Please consult with your administrator. Your support ID is: 1309017649984718718 "}],"

These can be tricky because they can be a result of multiple issues.  Some things to try:

  • There have been a few occasions in the past where this type of error has been due to incorrect credentials.  Before submitting the Testing Troubleshooting request, try logging into the pilot website with your account and make sure your credentials work and reset the password, if necessary.)
  • Another situation that can cause these is when you are referring to the incorrect URL.  Make sure that the web service request is preceded by the URL, followed by /rest/ if you are using REST or /ws/ if you are using SOAP.  An example:  https://[Operational or Test Environment URL]/rest/FP/1111_2222_3333/retrieve?versionRequested=20140716 for the operational web service call to retrieve a flight plan via REST
  • Our network apparatus may also reject situations where the request should have been a POST and it was made as a GET or vice versa.  Be sure to follow the WSDL and follow the HTTP method to make use of the particular web service.

If you have exercised the above, and are getting these types of errors, it could also be a legitimate network error between your ISP and Leidos Flight Service as we have seen this in the past, as well.  Please send an email to R-FFSP-WebServicesSupport@leidos.com that includes the support id in the description and we will work with our networking team to find what caused the problem.



  • No labels