We are experiencing problems retrieving data from a database, elements or attributes for one of our clients.
Our application authenticates using Kerberos (using a normal service account, with password) and the authentication process seems successful while looking at it using a debugger. For every failed call our implementation tries to reauthenticate. Which we’ve seen it always do successfully.
The problem occurs when the authenticated client is used to do a request. The first request results in a 502 error. The second attempt at the same database, after a restart of the application, results in a 404.
We’ve checked the path to the database multiple times, and it is correct.
We can, however, browse the database with it’s elements and attributes using the browser. Currently we’re using Edge. What’s worth noting is that after the browser is used to login and visit element’s, our application is able to find the database and the elements as well. Still then we cannot browse the attributes with our application. Only after we visit an attribute in the browser, I can see, what seems, all attributes.
After we stop our application, and wait for approximately an hour, we cannot see the database anymore and it results into the same 502 / 404 behavior mentioned above.
We did a Google search and it led me to this forum question:
The problem described in this question looks a lot like the problem we are experiencing. The answers to the question makes me believe that this is not a problem we can solve on our own. The selected answer only states that this is related to an error in the AF Link and the system status is ‘GenericBadState’. The answer concludes that it could be resolved by ‘TechSupport’.
If this is a known problem, how can we fix this?
We do not have access to the Web API configuration, and are unable to replicate this behavior on our own systems. We would like to help guide our customer come to the correct configuration.
Thank you in advance.
