Microsoft Dynamics AX (Archived)

Error in SSRS Query - wrong AOS info used for unknown reason

(0) Share

Report

Posted on by Community Member

Hello, everybody!

I have a problem with second RS instance.

Getting the error:

1) Opened my .axc file with Visual Studio;

2) Created SSRS report, and add Dataset;

3) Then i was trying to add query to this Dataset, push browse (...) button and get next error:

--------------------------

Microsoft Visual Studio
---------------------------
Exception occurred on the metadata service on client or server. See exception details below:
>Could not connect to net.tcp://ax2012R3_Server:8202/DynamicsAx/Services/MetadataService. The connection attempt lasted for a time span of 00:00:01.0100153. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.0.10:8202.
---------------------------

The problem is that my AOS work on 2720 (8120 and 8220) ports.

Problem RS instance named "AX2012R3_20". Microsoft.Dynamics.AX.ReportConfiguration.axc file pointing to correct AOS (WCF rebuilds fine). I can deploy and use native SSRS reports without problems. I can save my report from the Visual Studio, and find it in correct AX application.

Account of the AX2012R3_20 reporting service are the same with the AX buisness connector - DAXRS20.

Port 8202 used by original connector configuration. So, for some reason Reporting Service uses the original port (configuration) when opening Querys window.

It will be cool if someone can help me :)

Thanks in advance!

*This post is locked for comments

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Vilmos Kintera 46,149 on at

Like (1)

Report

The configuration is probably being read from the execution accounts' AX Configuration in the registry. The reporting instance will connect to the AOS which could be saved in an AXC file and stored in a specific folder of the SSRS instance, check the documentation. That might resolve the issue.

If you mean your account from Visual Studio is not going to the right instance, then you need to change both the Local client and Business Connector settings in your AX Configuration to have it point to the correct instance/port.

Was this reply helpful? Yes No
faiz7049 2,382 on at

Like (0)

Report

Open Visual Studio as administrator and try again.

Was this reply helpful? Yes No
Suggested answer

Tommy Skaue Moderator on at

Like (1)

Report

Hi

Vilmos is correct.

You need to make sure your local AX Client configuration is set to the right target environment.

Visual Studio will use your users AX Client Configuration, and Reporting Services will use the Business Connectors AX Client Configuration (unless SSRS Instance is explicitly configured for a different AOS using an AXC-file in the bin folder).

Just to add a bit more information here. Your users AX Client Configuration is typically stored for your user in the machine registry hive. I say typically, because it is possible to point the preferred configuration store to a specific file.

Open Administrative Tools, Microsoft Dynamics Ax Configuration Utility. Observe Active Configuration store. If it says "Registry" the configuration is stored in the registry. You can change configuration from the "Manage"-button and "Set Configuration Store" (empty value defaults to Registry).

Configuration Target allows you to switch between your local client configuration OR the "Business Connector" configuration.

Here's another tip; if you want your report modifications to end in the CUS-layer, you can create a local client configuration with the CUS developer code and now Visual Studio will ensure your changes are saved in the CUS layer. Otherwise it will end up in the USR-layer.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Hi,

I respect above suggestions, apart from that.

Please check your configuration file in configuration utility whether your working in correct configuration file?

Just restart SQL server reporting services.

Was this reply helpful? Yes No