Search This Blog

Wednesday 31 May 2017

Make sure that SQL Server Reporting Service in configured correctly

Make sure that SQL Server Reporting Service in configured correctly. Verify the Web Service URL and Report Manager URL configuration in the SQL Reporting Service Configuration Manager.

Your AX is working fine and you have installed the SSAS, SSRS and AX analysis and Reporting Extensions and configure the report manager also.

You can able to browse Report Manager URL and Web Service URL without any issue. And you have given the relevant rights for Report Server.

If you Validate Settings from the AX Report Server Configuration and getting the following error:

























Solution:

Close all AX related application.

Open Microsoft Dynamics AX with “Run as administrator” mode.

Try to Validate settings and got the DynamicsAX – success.






Wednesday 24 May 2017

Error while deploying SSRS reports in Microsoft Dynamics AX 2012 R3- An error occurred

Error while deploying SSRS reports in Microsoft 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.

Below are troubleshooting for error while deploying SSRS reports 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 Reporting Service (SSRS) Server. Contact to administrator to deploy.

Error 2:

An error occurred: The network path was not found. If User Account Control (UAC) is enable 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 services.


























Now deploy your report, it should deploy successfully.
















Solution: 2

You will try now second solution.

Go in Computer Management and then select Local Users and Groups.










































Now select in Groups.

Double click on Administrator group and Add your users as shown below.



























After doing these steps try deploying report again.



































The issue will be resolved.

Tuesday 16 May 2017

A call to the Microsoft Dynamics AX SRSFrameworkService service failed. There was no endpoint listening at



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



























Solution:

Go System administrationà Setupà Services & Application Integration Frameworkà Inbound Ports.

Select BlServices port, Activate same.



















Sometime you will get this below error for that.
















For that please follow below.

Go to AOTà Service Groupsà  Bl Services, double check it has two services.
Also check both services has the underline service operations:

If everything is correct then you can right click on BlServices group and say Deploy Element.

































Restart AOS Services and open Microsoft Dynamics AX again.

Saturday 13 May 2017

Object Server 01: Fatal SQL condition during login. Error message: “The internal time zone version number stored in the database is higher than the version supported by the kernel (8/7) User a newer Microsoft Dynamics AX kernel.”

Issue: Dynamics AX service failed to start due to below error:




























Event Log:


















AX: AX 2012 R3 with CU8 and without.
OS: Windows Server 2012 and 2012 R2.
SQL: SQL Server 2014.

Solution:
1. Open SQL Server (SSMS).
2. Select the Database (MicrosoftDynamicsAX).
3. Run the below script:

Select*from SQLSystemVariables
WHERE PARM = ‘SYSTIMEZONESVERSION’

UPDATE SQLSystemVariables
SET VALUE = 7
WHERE PARM = ‘SYSTIMEZONESVERSION’

And the return to window type CMD run as Admin





C:\Windows\system32>

Type: net start AOS60$01

Will look like: C:\Windows\system32>net start AOS60$01