IdeaGen Technical Support

After your upgrade from 2006 SP2 to v2008 you will receive a message asking if you would like to look at your upgrade logs. It is ESSENTIAL that you check all logs for errors. Failure to do this could result in database issues occurring in the future and, potentially, the only resolution to this issue could be a reconversion of your 2006 SP2 data.

We have compiled a list of acceptable errors, if these errors show in your logs they can be safely ignored. If ANY OTHER ERRORS are shown you will need to send your upgrade logs to IdeaGen for investigation. 

To manually find the logs after the upgrade you will need to look in your \IdeaGen\WBPro\Atlas Server\Temp folder: 

 If thefiles size of a particular log is 0kb then you do not need to check this file. For all other logs:

• Open up in an editor such as Notepad.
• Select Edit | Find.
• Search for the word error
• If it finds errors matching those below you can safely ignore.
• If it finds any other error, please send the log(s) to This e-mail address is being protected from spam bots, you need JavaScript enabled to view it We will endeavour to investigate the issue as soon as we can to minimize any downtime.

Acceptable errors:

SET AUTODDL OFF;
**** Script Error ****
ISC ERROR CODE:335544569

ISC ERROR MESSAGE:
Dynamic SQL Error
SQL error code = -104
Token unknown - line 1, char 4
AUTODDL

Reason: This is a syntax error within the upgrade which does not cause the upgrade to fail and should therefore be ignored.

**** Script Error ****
ISC ERROR CODE:335544343

ISC ERROR MESSAGE:
invalid request BLR at offset 1073
procedure COPY_CHECKLIST is not defined

Reason: This usually only applies to the function COPY_CHECKLIST and can be ignored as it does not cause the rest of the upgrade to fail.

DROP TABLE <TABLENAME>;
**** Script Error ****
ISC ERROR CODE:335544351

ISC ERROR MESSAGE:
unsuccessful metadata update
Table not found

Reason: This error occurs when a table is no longer needed in Workbench as is required to be dropped. Some tables will not exist in a database as they have been (successfully) dropped in a previous upgrade, therefore this error can be ignored.

insert into <TABLE_NAME> (<IDFIELD_NAME>,<OTHER_FIELDS>) values (0, <OTHER_FIELD_VALUES>);
**** Script Error ****

ISC ERROR CODE:335544665

ISC ERROR MESSAGE:
violation of PRIMARY or UNIQUE KEY constraint "PK_AUDITANLFIELDS" on table "AUDITANLFIELDS"

Reason:  Workbench databases use a “zero” based record in most tables so that foreign keys can be used successfully between tables. These zero-based records are inserted by upgrade scripts, and sometimes on more than one occasion, and therefore subsequent attempts to insert this record fail. This error can be ignored ONLY WHEN IT APPLIES TO INSERTING THE ZERO-BASED RECORD. All other errors resulting from inserting records into tables must be investigated by IdeaGen.

Reason: This is trying to drop a procedure that does not exist in this database, therefore this error is fine.