Our support engineers have assembled the top recommended solutions for you.
Microsoft Dynamics AX 2012CRM Connector in Microsoft Dynamics AX 2012Financials Management in Microsoft Dynamics AX 2012Upgrading to Microsoft Dynamics AX 2012
Microsoft Dynamics AX 2009
Application Object Server (AOS)
Enterprise Portal and Role Centers
Inventory Costing in Microsoft Dynamics AX 2009
Invoice Settlements/Discounts/Reversals
SSRS and SSAS Integration
Workflow
After preparing a restored database from RTM, and having it setup with an upgraded R2 compatible modelstore (using the installation wizard and the upgrade guide), I installed a new R2 AOS and pointed to the database. I want to test how this will work before I do it on production.
I noticed a few problems in the installation log, a couple of stored procedures that did not get created due to missing columns. Obviously, the AOS has not even started, so the data upgrade has not yet begun. I am wondering if anyone has any previous experience on whether or not I can safely ignore these errors, or will they create unforeseen problems later down the road. As everyone else, I don't want to waste time on something that eventually will not work.
Here is a transcript of the errors:
2013-01-03 10:19:37Z Creating stored procedures post AOS install.
2013-01-03 10:19:37Z Creating stored procedure '[dbo].[getNumInternal]'.
2013-01-03 10:19:37Z An error occurred while Setup was creating the stored procedure [dbo].[getNumInternal] for access by login 'DOMAIN\daxaos'.
2013-01-03 10:19:37Z Reason: Invalid column name 'PARTITION'.
2013-01-03 10:19:37Z Invalid column name 'PARTITION'.
2013-01-03 10:19:37Z Error occurred when executing stored procedure '[dbo].[getNumInternal]'. Error:
2013-01-03 10:19:37Z ******************************************************************************************************
2013-01-03 10:19:37Z Creating stored procedure '[dbo].[sp_GetNextRecId]'.
2013-01-03 10:19:37Z Creating stored procedure '[dbo].[sp_AddBIAnalysisServer]'.
2013-01-03 10:19:37Z An error occurred while Setup was creating the stored procedure [dbo].[sp_AddBIAnalysisServer] for access by login 'DOMAIN\daxaos'.
2013-01-03 10:19:37Z Reason: Invalid column name 'PARTITIONS'.
2013-01-03 10:19:37Z Invalid column name 'PARTITIONS'.
2013-01-03 10:19:37Z Error occurred when executing stored procedure '[dbo].[sp_AddBIAnalysisServer]'. Error:
2013-01-03 10:19:37Z Creating stored procedure '[dbo].[sp_AddReportServer]'.
2013-01-03 10:19:37Z An error occurred while Setup was creating the stored procedure [dbo].[sp_AddReportServer] for access by login 'DOMAIN\daxaos'.
2013-01-03 10:19:37Z Reason: Invalid column name 'ISSHAREPOINTINTEGRATED'.
2013-01-03 10:19:37Z Error occurred when executing stored procedure '[dbo].[sp_AddReportServer]'. Error:
2013-01-03 10:19:37Z Invalid column name 'ISSHAREPOINTINTEGRATED'.
Tommy Skaue | Dynamics AX Developer from Norway | http://yetanotherdynamicsaxblog.blogspot.no/ | www.axdata.no
Ok. I think I understand why these errors occurred.
If you install an R2 AOS and point it at a database coming from RTM, which has not been fully data upgraded, this will happen. This happened while I was trying to reestablish one of my R2 AOSes during an upgrade process.
Essentially, this created a catch-22 for me, so I had to revert back to a RTM AOS which I then could choose to "upgrade" instead. this makes the installer choose a different set of operations against the database and the errors I received earlier did not happen.
Lesson learned.
The problems that you will need to address are the access by login DOMAIN\daxacs errors - when you install the AOS separately from the database, we don't automatically assign the default permissions required for the SQL database to that AOS service account user. The Invalid column names will be taken care of as part of the data upgrade synchronization process.
Thank you, Kevin. I already have a support request somewhat related to this, so I will probably find some solution around this tomorrow, hopefully.
So I did grant the service account dbowner on the model database before installing the AOS-service, as I noticed the service account did not pop up as user on the model database. I would think dbowner should be enough.
I am right now curious to know if there are some special steps being taken care of in particular when you *upgrade the AOS*, that is from RTM to R2. When installing an R2 AOS you are asked if this is an upgrade or not, if I remember correctly. Will the upgrade path do some "magic" to the database in particular?
Hi Skaue,
I am getting exact same errors what you have mentioned in the forum. I have followed the steps which is mentioned here community.dynamics.com/.../102188.aspx. But in the setup log of AX2012 R2 AOS install connecting to the CU3 database(after running the DB install which splitted the DB into two), i am seeing the exact same errors.
Can you please tell me what was the problem and how you resolved the issue. It looks like a problem with the DB installation steps.
Regards,
Syed
Do you have found a workaround ? We encounter quite the same problemb but no solution found.
Greets,
Guillaume