Dynamics AX Common Errors

AX 2012 Help Server error: Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'\
Error No-3
HTTP Error 500.24 – Internal Server Error + HELP SERVER ERROR AFTER INSTALLING ON AX 2012 + ERROR – Unable to contact the server
Error No-4
"An occurred during setup of Reporting Services extensions. Reason: Unable to find appropriate service endpoint information in the configuration object"
Error No-1
AX 2012 Help Server error: Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
The SQL server reporting Service service is running -SSRS 2012
3. HTTP Error 500.24 – Internal Server Error + HELP SERVER ERROR AFTER INSTALLING ON AX 2012 + ERROR – Unable to contact the server

Module	ConfigurationValidationModule
Notification	BeginRequest
Handler	svc-Integrated
Error Code	0×80070032
Requested URL	http://testserver:8080/DynamicsAX6HelpServer/HelpService.svc
Physical Path	C:\inetpub\wwwroot\DynamicsAX6HelpServer\HelpService.svc
Logon Method	Not yet determined
Logon User	Not yet determined

1. Check that Directory browsing is enabled(IIS MANAGER>SITES>DIRECTORY BROWSING(DOUBLE CLICK AND ENABLE IT)

1. Go to Ax 2012>System administration > setup>system>Help system parameters

1. Also when you browse the site in IIS manager it will tell you ASP.NET 4.0 check for Integrated pipeline mode

1. Check the below criteria it should be the same

1. IIS>Application Pools>

1. ASP.NET4.0                                  V4.0       CLASSIC

1. ASP.NET4.0 CLASS                        V4.0       CLASSIC

1. CLASSIC .NET APPLICATION           V2.0       CLASSIC

1. DEFAULT APP POOL                       V2.0       INTEGRATED

1. 
   

1. 
   

Unable to find appropriate service endpoint information in the configuration object + An error occurred during setup of Reporting Services extensions.

1. CIL compile did not complete without errors

1. Firewall is blocking communication

1. BIServices is not activate

1. Account permission

1. Ensure the CIL compile is complete and error free.

1. Switch off firewalls on AOS server and Reporting server. This is just to validate if the firewall is causing the problem.

1. Check the BIServices is active. From AX menu System Administration->Services and Application Integration Framework->Inbound ports

4. Try and install Reporting extensions. If same problem persists process to step 5.

4. Re-deploy BIServices. This is completed from AX development environment: AOT->ServiceGroups->BIServices. Right click on the servicegroup and select deploy. This should result in a BIServices running as mentioned in step 3.

4. Try and install Reporting extensions. If same problem persists process to step 7.

4. Add the business connector account to the local admin group on the reporting server.

Error No-1

Error No-2

The SQL server reporting Service service is running-SSRS 2012

AX 2012 R2 SSRS Installation Service Endpoint Error

Run Command on CMD  

aspnet_regiis.exe /iru

The Aspnet_regiis.exe file can be found in one of the following locations:

%windir%\Microsoft.NET\Framework\v4.0.30319

%windir%\Microsoft.NET\Framework64\v4.0.30319 (on a 64-bit computer)

Error No-2

Solution for this error: 

The deployment was cancelled because of an error:

On the reporting server, |Verify that

The SQL server reporting Service service is running

Solution:

1. Check Local business connector is optimum/ correct.

2. Check Domain business connector is optimum/ correct.

3. Put increment CIL

Now deploy it will be deployed.

Error No-3

This error may arises at any of this name for same reason.

HTTP Error 500.24 – Internal Server Error,

The Location of the help server has not been specified.

ERROR – Unable to contact the server etc...

HTTP Error 500.24 – Internal Server Error

An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

Detailed Error Information

 Solution:

(check the location should be as)

http://ServerName/DynamicsAX6HelpServer/HelpService.svcthe

http://tcschennaiserver/DynamicsAX6HelpServer/HelpService.svc

1. DYNAMICS AX HELP SERVER          V4.0       INTEGRATED(Version will be 2.0 change to 4.0 and check)  pls keep in mind DynamicAX  HelpSVC >ASP.NET IMPERSONATION SHOULD BE DISABLE(DON’T ENABLE) 
   Error No:4  

   AX 2012 R2 SSRS Installation Service Endpoint Error

   "An occurred during setup of Reporting Services extensions. Reason: Unable to find appropriate service endpoint information in the configuration object"
   

   Reason: BIServices port is not deployed.

   Resolution:

   ü  Activate inbound ports BIServices (System Administration > Setup > Services and AIF > Inbound ports)

   ü  Delete the WCFCONFIG entry in registry under the Dynamics AX current user hive key (HKEY_CURRENT_USER\Software\Microsoft\Dynamics\6.0\Configuration\Orig)

   ü  Restart the box

   ü  Try installation again.  If fails then continue with

   ü  Make the BC proxy user a local admin on the SRS box.

   ü  Redeploy BIServices services: AOT > ServiceGroups > Right Click BIServices and deploy.

   Environment Details - Dynamics AX 2012 R2

   
   

   Explanation: Reporting services Extension is a service that occupies a port in Dynamics AX 2012. Whenever you use Reporting services extension you need to activate a port BIServices. 

   
   

   Steps for Registry:

   
   

   1.     Click Start, and then click Run.

   2.     In the Open box, type cmd and then press ENTER.

   3.     In the Open box, type regedit and then press ENTER.

   4.  Locate the following subkey in the registry: 

            HKEY_CURRENT_USER\Software\Microsoft\Dynamics\6.0\Configuration\Original

       5.  Delete the file "WCFCONFIG" file               

When installing SSRS server I have recently experienced a problem with the AX SSRS extensions not installing and resulting in an installation rolling back. The error message received was:

Unable to find appropriate service endpoint information in the configuration object.

The problem relates to the installation not being able to find the appropriate end point. There are a number of causes to this problem:

The process necessary to ensure you can get past this issue is as follows:

If the green tick is not present, then select the line and press the activate button.

If the BIServices is not present, or will not activate then proceed to step 5.

This should enable you to install the reporting extensions for AX 2012 R2, when experiencing problem with service endpoint errors.

An error (1332) occured while enumerating the group membership AX Report Deploy Error

When deploying AX 2012 reports, I got this following error message.

"The security group Administrators contains a member that is causing the following error : An error (1332) occurred while enumerating the group membership. The member's SID could not be resolved."

"The deployment was aborted. You do not have privilege to deploy to server: app server. For deployment, you must have

administrative rights to the SQL Server Reporting Services (SSRS) server. Contact your administrator to deploy."

When  tried deploying the reports using this command "Publish-AXReport - ReportName *", got this error message.

if you are a domain admin. This is the scenario; you have a user trying to deploy reports using the Microsoft Dynamics AX 2012 Management Utility, you get an error saying you need to be a member of the administrators group on SSRS machine, basically some variation of “you don’t have enough permissions” even though you have all the permissions required which does not include having to be a domain admin, you do not need to be a domain admin to deploy reports. Here is an example of the error message below:

Publish-AXReport -ReportName * -SkipReportServerAdminCheck

Solution:

Install KB2744300 which is Kernel build 6.0.1108.1870, or any other higher kernel build would be fine.

The fix is going to add an extra switch to the deploy command so that you can bypass the check if you want to.

The switch is: -SkipReportServerAdminCheck

So when you publish reports it will look like this for example:

Publish-axreport -reportname custtranslist -SkipReportServerAdminCheck

Please note this only works for deploying reports in the Microsoft Dynamics AX 2012 Management Utility.

Multipul AOS instance SSRS Reports

Installing three named instances of SSRS, running SQL Server Setup for each instance.

Furthermore I completed the initialization of each of them by making sure they all run under business connector proxy account and had the databases and sites ready.

Next Run AX2012 R3 Setup and installed the Reporting Extensions, which would make my first SSRS instance prepared for reporting. I opted for having the reports deployed as well.

However, the remaining instances remain without a complete configuration, so let us go ahead and prepare them as well.

Using the PowerShell command introduced after AX2012 makes this easy. Simply open the Dynamics AX 2012 Management Shell and run this command:

Install-AXReportInstanceExtensions –ReportServerInstanceName AX2012_DEV -Credential contoso\daxbc

Notice that after running this command, the configuration files will be modified and they will have the necessary changes to support Dynamics AX reporting.

Run the command for all the additional instances you're setting up.

So how will each instance know what AOS they bound to? We will drop an AX configuration file into the bin-folder for each Reporting Server. The guide tells us the file needs to have a specific name, Microsoft.Dynamics.AX.ReportConfiguration.axc, so all you need to do is to either create a configuration file or pick one you've already made earlier.

I always create configuration files for all environments, so I just copied the appropriate file for each environment to the bin-folder and renamed it according to the instructions. If you have to create new configuration files using the Dynamics AX Configuration from Administrative Tools, just make sure to leave it pointing at the first original configuration when you're done. If you remember, it was pointing to the same AOS as your first SSRS instance was, and you want to keep it that way. :-)

Notice the filesize. Typically if I see a configuration file that is less than 5kB, it tells me that file does not have an updated WCF-configuration. You know the huge chunk of XML that holds the WCF-configuration inside the AX-configuration file. You really want to make sure your configuration file has a proper WCF-configuration before you continue.

Finally restart the Report Server instances and they should be good to go.

Before deploying reports, you should prepare the settings inside AX. Open a client to each of the environments still missing reporting. Head over to System Administration, Setup, Business Intelligence, Report Services, Report servers. Either create a new configuration or change the one already there. My extra environments where copies from other environments, so I simply changed the existing one. Make sure it points to the right SSRS instance, has the right URLs and is associated with the right AOS (at the bottom of that dialog - so scroll down). If the settings are correct, you should be able to press the "Create report folder"-button and observe the folder be created successfully. That is a good sign! You're ready to deploy reports now.

Deploying reports is just a matter of running another PowerShell command. The whole process may take a while, so spend the time documenting your work and feel good about your achievement.

 Publish-AXReport -ServicesAOSName MYAOSSERVER -ServicesAOSWSDLPort 8103 -ReportName *

Publish-AXReport –Id SSRSConfigID –ReportName *

Notice the name of the server running the AOS is used, along with the WSDL-service port. You'll find the correct WSDL from the Dynamics AX Server Configuration under Administrative Tools on the AOS server.

Finally, you can test the reporting by opening a client, and try run any of the reports under System Administration, like the "Database Log". Don't worry about the report not having any data, as long as it loads.