Hi there,
We are experiencing rest call failures from our OData services in ADF after the Linux Migration from last weekend. We’ve already placed a support case with Epicor but it they can’t seem to find a solution. Epicor already restarted the app server but this did not work. Are we the only ones with this problem? Also the documentation website is down (api/help/v2/index.html). Someone with a resolution for our problem? Al our reports outside Epicor are with old data (from last friday)
In order to help we are going to need examples of any errors/screenshots that you might be experiencing and if you are getting correlation errors, a copy of the system logs with that error in it.
The other thing is having Epicor understand what is unique to your site, surely everyone is not having the same problem sort there would be a public outcry.
Hi Simon,
Thanks for your reply.
Because this is an Epicor SaaS + Azure Data Factory setup, we only see the errors from the client side. The calls fail with “Unknown REST error”, but we don’t have access to Epicor system logs or correlation IDs ourselves.
What makes this puzzling is that this is pure OData/REST traffic (BAQSvc) and has been running stable for months. The failures started immediately after the Linux migration last weekend, with no changes on our side. UI access works fine; only the API usage is affected.
That’s why we suspect this is more a SaaS REST/API platform issue than something unique to our setup, and we’re mainly trying to determine whether others are seeing similar behavior.
Any insight is appreciated.
You can download your app server logs via Server file download. Takes a bit for them to populate in the tool but once they show you should be able to download.
You need to add a backslash at the end. At least, thats what solved it for me, one of the times. Have had issues with Epicor randomly changing things a couple times with no notice.
Ex: The end of your baq url was BaqSvc/baqName
It now needs to be BaqSvc/baqName/
If you have parameters: It now needs to be BaqSvc/baqName?parameter=value/
A good way to know for sure is to check your Swagger page for the api, do a test call from there, and itll spit out the exact url it used down below.
Hi Jonathan, the problem is that the Swagger Page isn’t available anymore as well. I tried accessing the Swagger Page.
try ../apps/resthelp/#/home instead - when my swagger was gone that still worked
