web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Microsoft Dynamics AX (Archived)

The SQL Server Reporting Services server name ***** does not exist or the Web service URL is not valid.

(0) ShareShare
ReportReport
Posted on by

Hi All,

We are trying to validate reporting servers , taken the URL's from "Reporting services configuration manager" from SQL machine, URLS are working fine in AX and SQL machine , but while validating it throwing the below error 

The SQL Server Reporting Services server name **** does not exist or the Web service URL is not valid.

Form Microsoft powershell cmd : test-AXReportserverconfiguration , below is the result

 

Importing AxUtilLib
Importing AxUtilLib.PowerShell
Importing Microsoft.Dynamics.Administration
Importing Microsoft.Dynamics.AX.Framework.Management
PS C:\Windows\system32> test-AXReportserverconfiguration
Testing the report server configurations.
WARNING: The default Report Server Configuration ID could not be found in the SRSServers table.
WARNING: Make sure that Microsoft Dynamics AX Business Intelligence Components are installed on the SQL Server
Reporting machine and verify that SQL Server Reporting Services is configured correctly matching the report server
configuration in the Microsoft Dynamics AX client.
Testing the report server configurations completed.
PS C:\Windows\system32>

Kindly advise how to proceed .

Regards,

Akbar

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    udaY-ch Profile Picture
    5,175 on at

    Hi Akbar,

    Have you tried checking the same by running AX client as Run as administrator.

    /Uday.

  • Suggested answer
    Vilmos Kintera Profile Picture
    46,149 on at

    The PowerShell tool is using the registry setting of the AX configuration, which is the currently selected config in your AX client configuration utility. Make sure you are pointing that to the correct AX AOS instance, port, and WSDL is refreshed in the AX config.

    Also verify that Windows Firewall is not blocking any communication by temporarily suspending in on both the transmitter and receiver ends (AOS, SQL, SSRS).

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics AX (Archived)

#1
Joris dG Profile Picture

Joris dG 5

#2
Andrew Jones a1x Profile Picture

Andrew Jones a1x 2

#3
Basit Profile Picture

Basit 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans