Error in Publish-AXReport

(0) Share

Report

Posted on by Josh_Engelhart

Hello. I'm hopping you can help me. I have installed your module and I'm trying to use the Publish-AxReport command in a script I have built. For some strange reason after restoring a replacement Database to SQL for AX, then setting a report server and trying to deploy the reports I get the attached error and the script stops. However If I reboot all the AOS machines and run the command again it continues past the error and will keep deploying the reports. Any ideas? Restarting the SSRS service and AOS services don't help resolve the issue.

Thanks,

Josh

*This post is locked for comments

I have the same question (0)

All responses (3)

Answers (0)

Martin Dráb 237,884 Most Valuable Professional on at

Like (0)

Report

This question has been moved from DynamicsAxCommunity PowerShell module - Sync DB, because it's neither about DB synchronization nor the DynamicsAxCommunity module (Publish-AXReport is shipped by Microsoft).

Was this reply helpful? Yes No
Suggested answer

Tommy Skaue Moderator on at

Like (0)

Report

This may just be a hunch, but try open the report that fails to deploy in Visual Studio, build it there and try deploy. It might be the report itself has invalid dependencies.

Was this reply helpful? Yes No
Suggested answer

Vilmos Kintera 46,149 on at

Like (0)

Report

Make sure that you are not doing any code changes on your AOS and your CIL has been successfully compiled on a Staging/Build/Release environment that lands in your Production AX system. After a new code release once the AOS instances have been started, check that which AX AOS instance is being used by the AX Configuration on your SSRS instance. You should refresh the WCF configuration in your AX Client configuration tool, then save the refreshed AXC in the folder explained here, then restart the SSRS instance:

technet.microsoft.com/.../hh389774.aspx

After that log on to the AOS that your AXC is pointing at, and verify that the activated standard AX Application Integration Framework Inbound ports are green, and not showing any red crosses. Since the publish-report command uses AIF ports, a stopped or broken AIF port is the likely cause of failure.

Was this reply helpful? Yes No