Microsoft Dynamics AX 2012 Error resolution

We will list a number of Errors that you can receive within Microsoft Dynamics AX 2012, and the solutions to get AX to work again:

1. “No connection could be made because the target machine actively refused it”

When printing a report, that is using SSRS to produce the report, you might receive the following error:

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

There can be a number of reasons why this is happening:
1. The quickest solution is to do a Full CIL Compile. See if that does not resolve the error. Please note, any service that is dependent on the CIL will no longer work, which includes SSRS, Workflow and AIF.

2. Check that the WCF confirmation is correct and you are able to refresh it. I have found the following sitsuation at one of our clients. They are using 2 IP addresses for each server. The IP address we RDP with works fine, but for some reason another machine on the network grabbed the IP address. When I tried to refresh the WCF configuration, the gave me any error.

3. Check that the Proxy settings within internet explorer is not set, or setup correctly – to bypass local addresses.

I hope this gives you a starting point.

About Johan Groenewald

I'm a Microsoft Dynamics AX Developer, working at Axnosis in Pretoria, South Africa, with over 15 years experience as a software developer and working for the past 5 years on Dynamics AX 2009 and 2012.
This entry was posted in Microsoft Dynamics AX 2012. Bookmark the permalink.

One Response to Microsoft Dynamics AX 2012 Error resolution

  1. Aditya says:

    Other cause can be lots of lingering client sessions in dbo.sysclientsessions table. That happens whenever AOS crashes or AOS service is not cleanly shutdown. To resolve, stop AOS (all AOSs), and delete all entries in said table from SQL Server Management Studio. Restart SSRS Service. This resolved said issue for us.

Leave a Reply

Your email address will not be published. Required fields are marked *