No connection could be made because the target machine actively refused it ?

(0) Share

Report

Posted on by Madankumar Kasthuri

595

Hi,

I am getting the above error message when I am generating any AX2012 report. SSRS reports are deployed and default configuration id created. Also it's been configured. I am trying to fix this issue. If you guys anyone experience this issue, please do write and let me know how to resolve.

Thanks in advance.

Regards,

Shan

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

Vikas Mehta 21 1,163 on at

Like (0)

Report

any solution buddy.

Was this reply helpful? Yes No
Suggested answer

Volker Breitkopf on at

Like (0)

Report

Hi everyone!

Just ran into this error message.

And in this case it was kind of misleading because the error was simply caused by the SQL Server Reporting Services service not being started. So first of all check if it's running (and try a restart in case it got stuck).

Other causes could be:

- firewall is too restrictive

- possibly value of "SecureConnectionLevel" in rsreportserver.config

Regards.

Was this reply helpful? Yes No
Gert Raangs 265 on at

Like (0)

Report

Perhaps the SQL port for Reporting Services is firewalled ? Normally i leave the firewall started and have s script which opens the standard ports (SQL Server 2008 R2)

@echo ========= SQL Server Ports ===================

netsh firewall set portopening TCP 1433 "SQLServer"

netsh firewall set portopening TCP 1434 "SQL Admin Connection"

netsh firewall set portopening TCP 4022 "SQL Service Broker"

netsh firewall set portopening TCP 135 "SQL Debugger/RPC"

@echo ========= Analysis Services Ports ==============

netsh firewall set portopening TCP 2383 "Analysis Services"

netsh firewall set portopening TCP 2382 "SQL Browser"

@echo ========= Misc Applications ==============

netsh firewall set portopening TCP 80 "HTTP"

netsh firewall set portopening TCP 443 "SSL"

netsh firewall set portopening UDP 1434 "SQL Browser"

netsh firewall set multicastbroadcastresponse ENABLE

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

check whether full CIL is done without any errors.. Normally restarting AOS solves this issue.

Was this reply helpful? Yes No
Suggested answer

Tommy Skaue Moderator on at

Like (0)

Report

Also make sure the SSRS instance is running under the BCProxy account.

If you really want to make sure things are in ship shape, try running the powershell command for testing the setup:

technet.microsoft.com/.../jj720250.aspx

Was this reply helpful? Yes No
Suggested answer

rudra 6,534 on at

Like (0)

Report

Hi

In my case i just tried the following order in sequence, solved the issue.

Application compilation and all ssrs reports to be redeployed again are not needed in my case, as this task will require more time and patience.

To fix the issue as soon please follow the below:-

1. I have two AOS services in a same box, Disabled one AOS service and made another AOS service running state.

2. Restarted the running AOS service.

3. Restarted the SSRS and SSAS service.

4. Made Full CIL.

5. Got the Report without any connection issue.

Was this reply helpful? Yes No
Dick Wenning 8,705 Moderator on at

Like (0)

Report

first validate that the ssrs is connecting to the correct AOS by using an axc file.

validate the settings in AX

when it works try online user report.

sometimes, running the brouwser as administrator worksfine, otherwise not

Was this reply helpful? Yes No
Suggested answer

rudra 6,534 on at

Like (0)

Report

HI Dick,

I even tried validate the settings in Report server form got success message and it is pointing to the right AOS server. Then to got the same connection issue when i run any reports.

The steps i have mentioned above solved my issue.

Was this reply helpful? Yes No
Marco Vergaini 10 on at

Like (0)

Report

Hi,

I had the same problem on a multi instance Reporting Services environment, due to missing Microsoft.Dynamics.AX.ReportConfiguration.axc file in the ReportServer bin folder (usually C:\Program Files\Microsoft SQL Server\MSRS11.INSTANCENAME\Reporting Services\ReportServer\bin).

In my environment Reporting Service try to use de default value stored in the registry to connect to the AOS, while I need to connect to a specific AOS.

For me this resolve the issue.

Regards
Marco Vergaini

Was this reply helpful? Yes No
Bashir Ahmad 5,248 on at

Like (0)

Report

Restart the AOS and watch the Event Log for any errors.

Was this reply helpful? Yes No