Dynamics AX 2012 RTM to AX2012 R3 Upgrade error

(0) Share

Report

Posted on by Community Member

Hello everyone

I've been trying to upgrade a Dynamics AX 2012 RTM applications to Dynamics AX 2012.

Before attempting to upgrade I fully compiled and sycnrhonized the application, removed the foundation ugrade models and change the status of batch jobs to WITHHOLD.

Then Uninstalled every RTM component and attempted to install de aapplication.

While configuring the database I selected to use a modelstore file to upgrade the code since the database has modification that want in the new environment.

This step runs just fine, however when trying to install the AOS the setup fails. When reading the log file I that ther was an error with the scripts:

Creating stored procedures post AOS install.
2015-09-22 16:24:35Z Creating stored procedure '[dbo].[getNumInternal]'.
2015-09-22 16:24:35Z An error occurred while Setup was creating the stored procedure [dbo].[getNumInternal] for access by login 'DOMAIN\user'.
2015-09-22 16:24:35Z Reason: Invalid column name 'PARTITION'.
2015-09-22 16:24:35Z Invalid column name 'PARTITION'.
2015-09-22 16:24:35Z Invalid column name 'PARTITION'.

There are 5 errors like this one including a ISSHAREPOINTINTEGRATED Invalid Column name.

Im thinking maybe I missed an important step while trying to upgrade so Im going to try again with a backup I made before upgrading.

Thanks in advance.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (1)

André Arnaud de Cal... 301,168 Super User 2025 Season 2 on at

Like (0)

Report

Hi Ivan,

Have you used the AX 2012 Upgrade guide step by step? www.microsoft.com/.../details.aspx (start at page 40)

Indeed you might missed one or more steps or the setup account does not have appropriate permissions on the SQL database.

Was this reply helpful? Yes No
Suggested answer

Douglas Noel 3,905 on at

Like (1)

Report

Hi Ivan,

did you read the following? (especially for inplace upgrades 2012->2012)

https://technet.microsoft.com/en-us/library/jj733502.aspx

There is a important difference in the setup phase between having a Ax2012R1(RTM/FP) or a Ax2012R2 as the System you want tu upgrade.

If you are upgrading from AX 2012 or AX 2012FP you should uninstall all componenets except the running R1(R0) AOS Server.

The instance is required to perform the database split during thge first part of AX 2012 R3 Setup.

Did you perform this step? (You have to do the database splitting)

This is not required on R2 systems. Here you should uninstall all components before the setup.

regards

Douglas

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for your response André

The user has the next roles assigned on the database:

db_owner

db_datareader

db_ddladmin

db_datawriter

db_securityadmin

And has the server roles:

dbcreator

sysadmin

public

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thank you for your response

I will try this again, yesterday I did this but the results were the same.

Should I configure the database and install AOS at the same time?

What I've been doing is configure the database first and then installing the AOS.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Yesterday I tried to do the upgrade with the steps you mentioned however sadly the result was the same.

One thing that I noticed is when doing the data synchronizaton for the RTM Application it starts synchronizing and when there are 6 minutes left the synchronization ends, no error is thrown.

I'm guessing this may be my issue since failing to synchronize the application causes errors at upgrade, I don't know if data base really did fully syncrhonize but my guess is it didn't.

This started happening when I removed the upgrade model before doing the R3 upgrade, of course I did compile, compiled CIL and Syncronized.

Also when I check my the database after R3 Database Configuration step is completed, none of the tables has the PARTITION field mentioned in the error.

Thanks in advance

Was this reply helpful? Yes No
Verified answer

Community Member on at

Like (1)

Report

After a lot of testing I found the solution.

The solution was actually written in the Dynamics AX R3 Upgrade Guidelands and was something I totally missed, more like didn't read.

Whenever you're doing the upgrade some of the tables may have the ChangeTracking property set to True(Enabled), you should disable this property or AOS will not run.

Thanks for your support André and Douglas.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Ivan you make my day! thanks for your investigation, I disabled the ChangeTracking in all tables first of MicrosoftDynamicsAX database with the script below, and the AOS started!

-- Mix of script modified

USE MicrosoftDynamicsAX

GO

declare db_cursor CURSOR FOR

SELECT t.name AS Table_name

FROM sys.change_tracking_tables tr

INNER JOIN sys.tables t on t.object_id = tr.object_id

INNER JOIN sys.schemas s on s.schema_id = t.schema_id;

DECLARE @tableName varchar(256);

OPEN db_cursor;

FETCH NEXT FROM db_cursor INTO @tableName;

WHILE @@FETCH_STATUS = 0

BEGIN

EXEC ('ALTER TABLE ' + @tableName + ' DISABLE CHANGE_TRACKING;');

FETCH NEXT FROM db_cursor INTO @tableName;

END;

CLOSE db_cursor;

DEALLOCATE db_cursor;

ALTER DATABASE MicrosoftDynamicsAX SET CHANGE_TRACKING= OFF ;

Was this reply helpful? Yes No