Web Request error

(0) Share

Report

Posted on by BC questions

We have updated customer version from dynamics 2017 to dynamics bc and the servers are the same so the security permissions remains the same.

I' m having difficulties on a webrequest because on bc it took to long and gives timeout error, on dynamics 2017 that does not happen, its immediate.

Any idea why? I as looking ate codeunit 1299 Web Request Helper and the error occurs here HttpWebResponse := HttpWebRequest.GetResponse; on GetWebResponse function.

Thank you

I have the same question (0)

All responses (7)

Answers (1)

Verified answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

Is the request sent correctly? What about authentication? Causes could be a lot.

Was this reply helpful? Yes No
BC questions 5 on at

Like (0)

Report

Thank you for the answer...

The code is exactly the same on both version, the behavior should not be the same?

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

If code is the same yes, also response should be the same. It's quite difficult to know the reason without seeing the code of the call.

Was this reply helpful? Yes No
BC questions 5 on at

Like (0)

Report

Here it is...

HttpWebRequestMgt.Initialize(STRSUBSTNO('apiservices.gtglobal.eu/.../access_token'));

HttpWebRequestMgt.SetMethod('POST');

HttpWebRequestMgt.AddBodyAsText(

STRSUBSTNO('grant_type=password&username=*****&password=*****'));//hided on purpose to post the code here

ltempBlob.INIT;

ltempBlob.Blob.CREATEINSTREAM(lResponseInStrem);

HttpWebResponse := HttpWebResponse.HttpWebResponse;

StatusCode := HttpWebResponse.StatusCode;

lResponseHeaders := HttpWebResponse.Headers;

HttpWebRequestMgt.GetResponse(lResponseInStrem,StatusCode,lResponseHeaders);

lResponseInStrem.READTEXT(ltxt);

lTokenAccess := COPYSTR(ltxt,18);

lTokenAccess := COPYSTR(lTokenAccess, 1, STRPOS(lTokenAccess, '"')-1);

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

THis same code works in NAV 2017? Is this the same physical server? Can you reach the URL you're calling?

A timeout error is normally due to unreachable endpoint or firewall problems.

Was this reply helpful? Yes No
BC questions 5 on at

Like (0)

Report

The answer is yess to all your questions that's why I don't understand why its tooks too long on BC

Was this reply helpful? Yes No
Suggested answer

Stefano Demiliani 37,166 Most Valuable Professional on at

Like (0)

Report

You can also try to check NavHttpClientMaxTimeout parameter on the service tier.

docs.microsoft.com/.../configure-server-instance

If nothing change, I think you need a debug on both side (you and the final endpoint)

Was this reply helpful? Yes No

Join the conversation

Community site session details

Web Request error

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

Web Request error

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates