Skip to main content
Solved

Network error when validating Supplier's doc tax ID via RMB


Manulak
Hero (Customer)
Forum|alt.badge.img+8

When the RMB “Validate Tax ID number” on Supplier>Address>Document Tax Information intermittently hits the below error.

Tax ID Number ******** cannot be validated due to network problem.

Further investigations:

  • The error mostly occurs when the action performed perpetually
  • The validation actually executes via the client (tbwSuppDocumentTaxInfo.cs)
  • Looks like a client limitation (threshold for MS_MAX_CONCURRENT_REQ)

Has this every happened to you?
Any clue will be highly appreciated.

Thank you.

 

Best answer by Manulak

@JGHSUSAN sorry to hear, but, as far as I understand, IFS cannot do anything about it. Because, my investigations confirmed that the particular error occurs when the web response contains the error code MS_MAX_CONCURRENT_REQ which makes the endpoint (EUROPA.eu web endpoint in this case) to be blamed.

What IFS could do is to implement a failover mechanism when it creates the client call, by catching this exception and perform a retry, as the second try works in most cases.

View original
Did this topic help you find an answer to your question?

Furkan Zengin
Superhero (Partner)
Forum|alt.badge.img+21

Hi @Manulak 

I believe this is due to limitation on server for accessing external websites. I have the same issue on one of my projects and they don't allow accessing external links from the server. Therefore we cannot validate.

The function uses below webpage to validate. 

Vies on-the-Web - European Commission (europa.eu)

 

Hope this helps


Manulak
Hero (Customer)
Forum|alt.badge.img+8
  • Hero (Customer)
  • May 8, 2023

Thanks a lot for the quick reply @gumabs. 👍

Yes, for me too it seems like the limitation pops out from the endpoint. 

It works most of the time (good news) but fails intermittently. 

Look what I found on Stack Overflow.

I’d assume that, if this is a known limitation, there should be a failover mechanism or a retry which should be imposed by IFS. This post is to find if this concern was ever triggered IFS support, etc.


Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • May 9, 2023

I have been experiencing the same issue and logged a case several months ago but no response yet.


Manulak
Hero (Customer)
Forum|alt.badge.img+8
  • Hero (Customer)
  • May 9, 2023

@JGHSUSAN sorry to hear, but, as far as I understand, IFS cannot do anything about it. Because, my investigations confirmed that the particular error occurs when the web response contains the error code MS_MAX_CONCURRENT_REQ which makes the endpoint (EUROPA.eu web endpoint in this case) to be blamed.

What IFS could do is to implement a failover mechanism when it creates the client call, by catching this exception and perform a retry, as the second try works in most cases.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings