Error while deploying SSRS report in Dynamics AX 2012 R3- An error occurred : The network path was not found. If User Account Control (UAC) is enabled on the machine, close the application, right-click the application, and then click Run as administrator.

Hi Folks,

Below are troubleshooting for Error while deploying SSRS report in Dynamics AX 2012 R3

Error 1:

The deployment was aborted. You do not have privileges to deploy to server: ######. For deployment, you must have administrative rights to the SQL Server Reporting Services (SSRS) server. Contact your administrator to deploy.

Error 2:

An error occurred: The network path was not found. If User Account Control (UAC) is enabled on the machine, close the application, right-click the application, and then click Run as administrator.

Solution:

Go to services-> Remote Registry and change the start type to automatic. And start the service.

Now deploy your report, it should deploy successfully.

Hope this will help you. Keep sharing your feedback under comment box. 

-Harry

Error While deplying SSRS report DAX 2012 R2/R3

 Hi Folks,

Here is one more troubleshoot for SSRS report. Please check my previous post for similar errors and solutions.

Error:

A call to the Microsoft Dynamics AX SRSFrameworkService service failed. There was no endpoint listening at net.tcp://####srv:8202/DynamicsAx/Services/BIServices that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details.

Possible Reason: 

Inbound port deactivated.

Solution:

Go System administration > Setup > Services & Application Integration Framework > Inbound ports.

Select BIServices port and activate it.

While activating you may one more error, and we will fix this as well :)

For that please follow below,

Goto AOT > Service Groups > BI Services, double check it has two services

Also check both services have the underline service operations:

 

If everything is correct then U can right click on BIServices service group and say Deploy Element.  

Enjoyyyyyyyy…. !!!

-Harry

Error: When opening AX client

“The Microsoft Dynamics AX client cannot be started because more users are connected to the system than are allowed by the license.” 

Error: While opening the AX client system showing below error message.
“The Microsoft Dynamics AX client cannot be started because more users are connected to the system than are allowed by the license.”
However there is clearly mention in error that its an license issue, 
But the actual issue is we are not able to open the AX and without opening we can not change the license. Upppsss:).



This error should not come While there is only one user login the server and RDP.

SO to resolve this issue Try this:

1. Open SQL management studio
Run below query on AX data base

select * from sysclientsessions where STATUS = 1
there must be some records in this table

2. Stop AOS services
3. Now delete are records from this table
4. Now restart the AOS service and open the AX client.
5. You may need to change the license as well (If expired).

-Harry

Error: “The CIL generator found errors and could not save the new assembly.”

Error: “The CIL generator found errors and could not save the new assembly.”

Updated: April 19, 2016.

Error: When run full or incremental CIL , system showing below error
“The CIL generator found errors and could not save the new assembly.”



Possible reason: This might be CIL generation issue.

Suggested Solution:

Step I: Stop AX services

Step II: Delete all isolated files from below path (Please Note: Delete only files which are not in any folder)

C:\Program Files\Microsoft Dynamics AX\60\Server\MicrosoftDynamicsAX\bin\XppIL directory



Step III: Start AX service

Step IV: Synch DataDictonary

Step V: Full Compile

Step VI: Full CIL Compile

Note: These all operation must be perform in the same sequence. (I also tried this only :P )

Now try to reopen you AX client. It should be work.

Update: April 19, 2016
You can rename the exist folder (e.g. XPPIL_BackUp12042016) and than start your AOS and do a full CIL. Its more effective than deleting only outer files.

- Harry