Update 6 Errors

We are installing Update 6 on our development environment.
We get the following in jde.log.
Does anybody have any opinions on whether we should be concerned with any of these messages?
Are they safe to ignore?
We are on SP20C1 and have (we think) sucessfully applied the latest planner update JD14838.

317/269 Wed Sep 25 20:03:51 2002 B96701.c230
Unable to retrieve Registry value!
>> Note the above is repeated multiple times but
>> we checked on KG and believe is safe to ignore

317/212 Wed Sep 25 20:25:28 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:25:28 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F48S618T_CURRENCY@12

317/212 Wed Sep 25 20:26:13 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:26:13 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F20112_CURRENCY@12

317/212 Wed Sep 25 20:26:21 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:26:21 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F20111_CURRENCY@12

317/212 Wed Sep 25 20:27:56 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:27:56 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F09E108_CURRENCY@12

317/212 Wed Sep 25 20:31:44 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:31:44 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F76101B_DELETEBEFORE@12

317/212 Wed Sep 25 20:32:06 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:32:06 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F054115W_INSERTBEFORE@12

317/212 Wed Sep 25 20:32:06 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:32:06 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F054115W_UPDATEBEFORE@12

317/212 Wed Sep 25 20:33:05 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:33:05 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F063951T_CURRENCY@12

317/212 Wed Sep 25 20:33:12 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:33:12 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F0618T_CURRENCY@12

317/212 Wed Sep 25 20:33:19 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:33:19 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F06116TZ_CURRENCY@12

317/212 Wed Sep 25 20:33:27 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:33:27 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F06116T_CURRENCY@12

317/212 Wed Sep 25 20:34:04 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:34:04 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F054111W_INSERTBEFORE@12

317/212 Wed Sep 25 20:34:04 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:34:04 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F054111W_UPDATEBEFORE@12

317/212 Wed Sep 25 20:34:19 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:34:19 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F054101W_INSERTBEFORE@12

317/212 Wed Sep 25 20:34:19 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:34:19 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F054101W_UPDATEBEFORE@12

317/212 Wed Sep 25 20:35:10 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:35:10 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F05290T_CURRENCY@12

317/212 Wed Sep 25 20:41:40 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:41:40 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F99WFMSG_INSERTBEFORE@12

317/212 Wed Sep 25 20:41:54 2002 jdb_trig.c348
JDB3800023 - Fallback Trigger Library JDBTRIG not loaded.

317/212 Wed Sep 25 20:41:54 2002 jdb_trig.c436
JDB9900340 - Failed to Get Proc address for _F99WFSYS_INSERTBEFORE@12

317/212 Wed Sep 25 20:42:15 2002 JDBODBC.C2128
ODB0000183 - SQLExecute failed

317/212 Wed Sep 25 20:42:15 2002 JDBODBC.C2128
[Microsoft][ODBC Microsoft Access Driver] Invalid field definition 'DWDWNNM' in definition of index or relationship. - SQLSTATE: S1000

317/212 Wed Sep 25 20:42:15 2002 jdb_drvm.c920
JDB9900401 - Failed to execute db request

317/212 Wed Sep 25 20:42:15 2002 jdb_exem.c680
JDB2100018 - Failed to create index 2 for table F96402 in data source OneWorld Local

Hi,

Did you build a full package after applying Update 6?
Did you look at the special instruction?
Was there any errors during the Index/Table Creation step of the update?

We find this error when we apply update 6 through Planner.
We did not start build package yet.

Replies from JDE regarding the Registry Errors and the JDBTRIG errors are listed below; still not sure about the other errors though ie:

317/212 Wed Sep 25 20:42:15 2002 JDBODBC.C2128
ODB0000183 - SQLExecute failed
317/212 Wed Sep 25 20:42:15 2002 JDBODBC.C2128
[Microsoft][ODBC Microsoft Access Driver] Invalid field definition 'DWDWNNM' in definition of index or relationship. - SQLSTATE: S1000
317/212 Wed Sep 25 20:42:15 2002 jdb_drvm.c920
JDB9900401 - Failed to execute db request
317/212 Wed Sep 25 20:42:15 2002 jdb_exem.c680
JDB2100018 - Failed to create index 2 for table F96402 in data source OneWorld Local

Registry Error explanation

This entry is caused because the Service Pack or ASU have
entries in the Registry under HKEY_LOCAL_MACHINE\SOFTWARE\JD
Edwards\OneWorldWindowsInstaller and HKEY_LOCAL_MACHINE\SOFT
WARE\JDEdwards\OneWorldWindowsInstaller\ProductID.
On opening the ESU Application the system does some cross
checking between the Registry entries and the jdeplan
database. At this point it does not recognise something in
the ASU/SP entries in the Registry and therefore it creates
two error entries for each ASU/SP that it finds in the jde.log.

Trigger Error explanation
We do not Update the JDBTRIG dlls in the planner pathcode. So this information can be ignored on the deployment server. Since we only use PLANNER to Install, Upgrade and Install ESUs, there is no need to use these tables there. I believe it is safe to continue.