Skip to main content

Installing AX 2012 Reporting Services Extensions on SQL Server 2008 R2

 So what a day, spent about half my weekend trying to install AX 2012 reporting services extension installed on my machine which had SQL Server 2008 R2 with SP2.
The trouble started when I found out that AX 2012 Reporting Server Extensions (RSE) cannot be installed on SSRS in SharePoint Integrated Mode.
The solution was simple to use reporting services configuration manager and recreate reporting databases in native mode.
However I wasn't aware I had this option till I spoke to my colleague (after I had already uninstalled SSRS from my VM - argh). I then installed Reporting Services however it was not patched with SP1 and SP2.
So AX installer recommended me to install Sql Server 2008 R2 CU3. However this did not work for me as I got a message saying that no instances or shared components found upgradeable.
I ran the Sql Server 2008 R2 SP1 and got the same error. I was lost and confused how to patch this component only. After a lot of other attempts I finally ran Sql Server 2008 R2 SP2 setup which immediately notified me that some components have not been applied with the patch and it dawned that I simply had to run this installer instead of trying the others.
<Update> Well  even after this issue was resolved I hit upon another issue which roll backed the RSE installation. The AX setup log gave following message-
An error occurred  adding user to the SQL Server Reporting Services DynamicsAXBrowser role in the folder DynamicsAX
After some search on the web found out that you need to delete unused entries from sysserversessions (Note-did not find this table in AOT but went to SQL Server) to resolve this issue.
This is the link that helped me understand the issue: (translate it from Russian to English)http://axforum.info/forums/showthread.php?t=40312
</Update>

Hoping this will help someone in  similar situation
Labels:

Comments

Post a Comment

Popular posts from this blog

Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement.

I received the following error when trying to connect to a server's SQL Server. I was able to telnet the Server on the required TCP Port (1433) but SSMS could not connect to the SQL Server instance.  Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was – [Pre-Login] initialization=13472; handshake=14425; (Microsoft SQL Server, Error: -2) I eventually found that a Hyper-V Adapter was responsible for the issue, disabling which resolved the issue, have faced a similar issue with VirtualBox adapter too. Hope it helps.
Post a Comment
Read more

A simple customization in MPOS (Blank Operation) with AX7

Hi All, I recently had to add a Blank Operation to Modern POS (MPOS) to open a url from MPOS. Blank Operation as you may already be aware enable you to extend Microsoft Dynamics Retail for POS by adding custom logic that can be triggered from the Retail POS Register buttons. The way to implement Blank Operations in MPOS  is different from Enterprise POS as MPOS is a modern app as compared to EPOS which is a windows forms based app. So lets explore a very simple customization i.e. we want to open a URL on triggering a button from MPOS. 1. We would need to start with AX to add a button to the layout of MPOS. If you do not want to disturb the standard layouts its better to copy one of the existing layouts and then modify it using the designer. Please note the designer only opens in Internet Explorer so it will save you time by not trying to open it in other browsers e.g Chrome 2. Next we need to add this layout to the Store where we intend to use it...
Post a Comment
Read more