You can upgrade to 5.6 and then to 6.2, no need to do 5.5

If the error says that there are open batches then there are open batches. I have done thousands of upgrades, double check your work. There may be open adjustment batches, that is usually the one everyone misses.

Thank you for your quick response Ettienne, i will coordinate with my accounting team to make sure all our batches are closed.

Do you have any insight into the first error I'm getting which says: "Error converting table APPJD", and what can be done to correct it?

Regards,

Mihai

What's the rest of the error message?

It could be dirty data or it could be something else. Run RVSpy/DBSpy and see if the SQL query is erroring out.

What's the rest of the error message?

It could be dirty data or it could be something else. Run RVSpy/DBSpy and see if the SQL query is erroring out.

Hello Ettienne,

The full error message says: "System error, could not modify table APPJD. Error Converting table APPJD"

I ran DBSpy during data conversion to 5.5 and i get the following errors in the log file:

13:00:58.26  GET-FIELD-INFO ( table=APPJD   , field=RATEDOC    )

    13:00:58.26   ==> 223 <DBS_FIELD_NOT_FOUND>

    13:00:58.26  GET ( handle=2, keyno=0 )

    13:00:58.26  

    13:00:58.28  TRANS-BEGIN ( )

    13:00:58.28  

    13:00:58.28  UPDATE ( handle=2 )

    13:00:58.28  

    13:00:58.28  TRANS-END ( )

    13:00:58.28  

    13:00:58.28  ALTER-TABLE ( table=APPJD   , fields=1, keys=0 )

    13:01:02.69   ==> (DBERROR=490730591)

    13:01:02.69  CLOSE-TABLE ( handle=1 )

I can attach the whole log if it will be more useful than this part where the errors occur.

Do an SQL trace, you will get the SQL query that errors out.

Try setting the SQL database compatibility down one or two levels, that sometimes helps with the older versions on newer versions of SQL server.