In the 4.0 environment, go to the properties of that table and make sure that the createdDate parameter is set to NO. This will delete the createdDate field and then your upgrade will work without that error. I agree that the upgrade should be smarter than it is - but what I suggest is a workaround anyway.
On Fri, Mar 13, 2009 at 9:36 AM, Sumit Loya <loya.su...@gmail.com> wrote: > Hi All, > > I am working on upgrading a AX 4.0 SP2 application to AX 2009 SP1. > > While running Post synchronization in data upgrade I am encountering an > error in job updateHRMVirtualNetworkTable. > > Here is the error from event viewer. > > > Object Server 02: The database reported (session 6 (AnAg)): [Microsoft][SQL > Native Client][SQL Server]Invalid column name 'createddate'.. The SQL > statement was: "INSERT INTO SYSDATABASELOG > (DATA,USERNAME,DESCRIPTION,LOGTYPE,TABLE_,LOGRECID,CREATEDBY,CREATEDTRANSACTIONID,DATAAREAID,RECVERSION,RECID) > VALUES (?,?,?,?,?,?,?,?,?,?,?);SELECT CREATEDDATETIME FROM SYSDATABASELOG > WHERE RECID = ? AND DATAAREAID = ?" > > > > This error is thrown when HRMApplicantTable is getting updated from > HRMVirtualNetworkTable. > > > > I know MS has changed all the createdDates to createdDateTime in AX 2009. > But dont know why AX keeps throwing this error of Invalid column name. > > > > Has anybody else encountered this problem during upgrade? > > > > Regards, > > Sumit > >
