A call to the Microsoft Dynamics AX SRSFramework Service service failed. An existing connection was forcibly closed by the remote host.

(0) Share

Report

Posted on by RM-22040759-0

2,014

I am receiving the above mentioned error while deploying the reports from AOT and Microsoft Administration Management shell.

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (1)

Verified answer

RM-22040759-0 2,014 on at

Like (1)

Report
Dear All ,

I have followed below mentioned steps to resolve the issue.

Open the development work space or you can press Ctrl+D

Register the SRSFrameworkService & SSASFrameworkService as mentioned in the below screen .
AOT-->Services-->SRSFRameworkService-->Add-Ins-->Click on Register service
AOT-->Services-->SSASFRameworkService-->Add-Ins-->Click on Register service

Deploy the BI services from AOT.
AOT-->Service Groups-->BIServices-->Deploy Service Groups

You can re-try to deploy the reports again.

Hope my solution will sort out your problem

Thanks & Regards.,

Ravi Theja Madisetty

"You can find the same post on my blog"

https://techguns.wordpress.com/

Was this reply helpful? Yes No

Vinai Varghese 150 on at

Like (0)

Report

I perform following steps to solve this problem.
1. Stop reporting services,
2. Stop AOS.
3. Goto: C:\Users\\AppData\Local\

Do step # for all the user profiles

4. Take the backup of all AUC files,
5. Remove them from there
6. Start reporting services
7. Start AOS.
8. Again run publish-AXReport -ReportName *. In powershell.

Reports are successfully deploy on my machine.

References:

http://dynamics-ax.blogspot.no/2013/03/ax-2012-fatal-axrdce-exception-error.html

https://community.dynamics.com/ax/f/33/t/115327.aspx

https://community.dynamics.com/ax/b/alirazatechblog/archive/2014/06/13/a-call-to-the-microsoft-dynamics-ax-srsframework-service-failed

Was this reply helpful? Yes No
Suggested answer

t-rex 5 on at

Like (0)

Report

So We have a setup where we have multiple environments i.e. DEV, UAT, PROD and for each env we have an AOS, Batch, RDS, and Report Server. We use AX 2012 and Remote apps are published via connection Broker. Until recently we was getting a similar error as described in the title and some timeout issues, we use powershell to deploy reports using:

Import-Module "C:\Program Files\Microsoft Dynamics AX\60\ManagementUtilities\Modules\AXUtilLib.Powershell\AXUtilLib.PowerShell.dll"

Import-Module "C:\Program Files\Microsoft Dynamics AX\60\ManagementUtilities\Modules\Microsoft.Dynamics.AX.Framework.Management\Microsoft.Dynamics.AX.Framework.Management.dll"

Publish-AXReport -Reportname *

After doing everything suggested in the forums I found the solution that worked for me was to have the AOS service installed on the report server and then point the AX configuration to the Report Server AOS service. You also will either need to go into SSMS and find dbo.srsservers or AX > Sys Admin > Business Intelligence > Reporting Services > Report Server and change the Configuration ID and Application Object Server Name to the report server, I find you can just use ssms to change these values as its easier.

Now when you run the reports using powershell you will see how quick it finds the AOS and deploys, you can even use

TEST-AXReportServerConfiguration which will output the config

Was this reply helpful? Yes No