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

(0) Share

Report

Posted on by w.sallam

2,259

Hello All

there is an issue when trying to print any report.

an error message shows :

No connection could be made because the target machine actively refused it 192.168.1.98:8201

it didn't come before as everything was working fine,

is is a test environment so the report server is in the same machine.

there's no error comes to the event viewer, and the firewall is off.

one more thing, the server's IP address was changed. I don't know if this could cause any issue.

I have the same question (0)

All responses (4)

Answers (0)

kvnkk 800 on at

Like (1)

Report

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

we used to get this issue and below is the procedure we used follow to solve the issue :-

1. Full CIL

2. Registering the services SRSFrameworkService,SSASFrameworkService

3. Deploying BIServices

4. De-active and active the BIServices(Admin->>setup -->> Inbound ports)

Was this reply helpful? Yes No
w.sallam 2,259 on at

Like (0)

Report

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

thanks kvnkk for reply.

I tried everything you suggested but still have the same issue, '

Was this reply helpful? Yes No
ToddB on at

Like (0)

Report

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

Hi w.sallam,

Do you get any errors when you try and run the report from the SSRS reports site itself?

Was this reply helpful? Yes No
nickmanny 136 on at

Like (0)

Report

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

Often, connectivity issues arise when something is hindering access to a specific port or hostname. This obstruction can be due to a firewall blocking the connection or the service-hosting process not listening on the designated port. This could result from the service not running, or it might be listening on an alternative port. Consequently, establishing a connection becomes impossible.

To diagnose the problem, you can try running the netstat -anb command from the command line to check if anything is listening on the intended port. If it returns no results, consider changing the port number. In Windows operating systems, you can use the netstat command via the command line (cmd.exe), while on Linux, you may need to use netstat -anp.

Occasionally, when the target machine 'actively refuses' the connection, it could be because the server's 'backlog' is full. In such cases, you might consider increasing the server's backlog, but it's also essential to implement retry logic in your client code to handle this situation. This is necessary because even with an extended backlog, the server could be handling numerous other requests on the same port at that time.

Was this reply helpful? Yes No

Join the conversation

Community site session details

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

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Abhilash Warrier – Community Spotlight

Congratulations to the September Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

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

Helpful resources

News and Announcements

Quick Links

Responsible AI policies

Abhilash Warrier – Community Spotlight

Congratulations to the September Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates