Error when running SSRS report-No connection could be made because the target machine actively refused it

(0) Share

Report

Posted on by Aragon

380

Hi guys,

Currently, I'm trying to install multiple instances of Reporting Services on one computer following to instruction from this link:

technet.microsoft.com/.../hh389760.aspx

The 1st SSRS instance for 1st AOS is running fine.

For the 2nd SSRS instance:

.Reporting Services configuration files are configured

.Reports are deployed successfully

.The settings for report server is validated

.Both Web Service URL and Report Manager URL are accessible

But , when I run a report from AX, the following error message is shown: "No connection could be made because the target machine actively refused it 192.168.xxx.xxx:8201". The error persists even after restarting SSRS / AOS.

After doing some research, it seems that the connection is refused by the computer. So, I went to my computer's firewall settings to check for ports config.

The strange thing is, the port 8201 is being set for the 1st AOS. And the NetTCP port number of 2nd AOS is 8202.

I think there is something wrong here.....

If you guys faced this problem before and know a workaround for it, please show me.

Thanks in advance.

*This post is locked for comments

I have the same question (0)

All responses (15)

Answers (3)

Alessandro Giannetta 710 on at

Like (0)

Report

We have the same problem...

Was this reply helpful? Yes No
Verified answer

Tommy Skaue Moderator on at

Like (0)

Report

Please confirm that you have successfully compiled the AOT without any errors, and that you have CIL compiled successfully. You could also restart the AOS and watch the Event Log for any errors. You want the necessary managed endpoints needed for SSRS to work to be operational (ie SRSFrameworkService and SSASFrameworkService).

After CIL is compiled, the infobox should list successful deployments of service endpoints

Was this reply helpful? Yes No
Verified answer

Ali Zaidi 4,657 on at

Like (0)

Report

You are using multiple AOS instances, sometime Dynamics Ax service crashes , you have to verify that AOS instance service is running on that machine. Then compile and generate full cil on that Instance. Hopefully Problem will solve.

Was this reply helpful? Yes No
Verified answer

Aragon 380 on at

Like (0)

Report

Err....Actually, the error made me think that sth went wrong when I installed / configured the 2nd reporting service. So I uninstalled ssrs + reporting service extension, and re-installed the whole thing again. Then I compiled and generated CIL like you guys suggested. And this time, it worked.

Thank you for your reply :)

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
manikumar 1,623 on at

Like (1)

Report

Im also facing same problem. at present we are having SSRS,DB,AOS in same server. I installed AOS in New server with db in present server. but I stuck at reports. reports are working in new server when old aos service is running, if I stop the service and run reports in new server getting following error.

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (0)

Report

Just make sure you have at least one default SSRS configuration defined inside AX for each AOS you've setup in that specific environment. So if PROD has 3 AOSes, you will need to define one SSRS Default configuration for each of the 3 AOSes, making sure each one of them point to each specific AOS.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

If you are installed multiple AOS, make sure in client configuration -> Business connector -> TCP IP is same as Current AOS TCP IP

Was this reply helpful? Yes No
manikumar 1,623 on at

Like (0)

Report

Both are same. running reports in new aos when other aos is running only. if i stop old one, new one is throwing error

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (0)

Report

If you have more than one (1) AOS for the same environment, you need to define SSRS settings for both, even if they both point to the same SSRS.

Just give each entry a unique name and make sure "default" is checked and the AOS-selection at the bottom points to correct AOS. First points to the first AOS, second points to second AOS, and so on.

Was this reply helpful? Yes No