Table of Contents

Error calling the ForNAV Report Service

When running a FORNAV report in Business Central, you may run into the following error:

Error calling the ForNAV Report Service
HTTP Status 0 NavHttpClient Request Failed
http://localhost:9030/ForNavReportService/

It means that it cannot reach the FORNAV Report Service on the local machine.

The report service is installed with the FORNAV Toolbox installer. Business Central uses it on-premises to render report output.

The report service must be installed on the same machine as your Business Central Service Tier (NST). If you have multiple service tiers, you must install the report service on all tiers.

You can check if the report service is running on your local machine. Run the following command line to check if it is running:

curl http://localhost:9030/ForNavReportService

* Host localhost:9030 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
*   Trying [::1]:9030...
* Established connection to localhost (::1 port 9030) from ::1 port 49362 
* using HTTP/1.x
> GET /ForNavReportService HTTP/1.1
> Host: localhost:9030
> User-Agent: curl/8.16.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Transfer-Encoding: chunked
< Server: Microsoft-HTTPAPI/2.0
< Date: Wed, 11 Feb 2026 13:15:49 GMT
<
<html>
<head>
<style>
...

If your report service is running but Business Central still has connection issues, it could be due to an NST service configuration introduced in BC 27.4.

The setting introduced in BC 27.4 is called NavHttpClientAntiSSRFEnabled. It blocks the HTTP call to the local report service because it is not HTTPS. You can change this setting to allow the HTTP call.

Using PowerShell, you load the administration module.

Import-Module -Name 'C:\Program Files\Microsoft Dynamics NAV\270\Service\NavAdminTool.ps1'

Check the current value of the setting.

Get-NAVServerConfiguration BC -KeyName NavHttpClientAntiSSRFEnabled

If it is true, set it to false to allow the HTTP call.

Set-NAVServerConfiguration BC -KeyName NavHttpClientAntiSSRFEnabled -KeyValue false

You must restart the NST to apply the changes.

Restart-NAVServerInstance BC