Novell is now a part of Micro Focus

My Favorites


Please to see your favorites.

Issues Adding First NetWare 6 server to the Tree

(Last modified: 31Jan2003)

This document (10074186) is provided subject to the disclaimer at the end of this document.


Issues Adding First NetWare 6 server to the Tree


608 (FFFFFDA0 ILLEGAL ATTRIBUTE) during replica operations

603 (FFFFFDA5 NO SUCH ATTRIBUTE) during replica operations

Replica Sync Fails

Schema Sync Fails


Novell NetWare 6.0

Novell NetWare 5.1

Novell NetWare 4.2

Novell NetWare 4.11

Novell eDirectory 8.6 for All Platforms

Novell eDirectory 8.5 for All Platforms

Novell Directory Services 6


Added first NetWare 6 server to a pure NDS 6.x or 7.x tree


Time differences caused inconsistent schema definitions across servers

The following procedure was followed:

- Pure NetWare 4.11 tree running DS.NLM 6.16

- Server holding Master of [Root] was in-place upgraded to NetWare 6.0

- All appeared to go fine but subsequent replica operations failed with 603 and 608 errors

The problem is that in time zones east of Greenwich Mean Time (GMT) UTC is initially set incorrectly when booting from the install CD.  Suppose the installation was carried out at 3pm (15:00) British Summer Time (BST), which is one hour ahead of GMT (UTC=GMT and BST=GMT+1):

- Time for the whole tree is 15:00 BST which is 14:00 UTC (GMT)

- Server boots from install CD with no time zone, so UTC is set to whatever the servers' hardware clock is set to - i.e. 15:00.  This server now has UTC set one hour ahead of the rest of the tree

- During the install, the NDS 6.x RecMan database is migrated to eDirectory FLAIM format and the contents timestamped with that servers' time, i.e. 15:00

- Later on in the install, after the LAN Driver is loaded, the server can be seen on the wire - it will then figure out its own timezone (BST - i.e. UTC+1), correct its clock (i.e. put UTC BACKWARDS one hour) and synchronise its time with the rest of the tree

- Therefore this server has updated its DIB with 15:00 timestamps and has now set its clock to 14:00!

- At around the same timeframe, install will extend the schema with all the eDirectory enhancements, which will obviously be timestamped at 14:00

- While this is going on, schema has already started to synchronise out

- The local DIB now has OLD information (the original schema) stamped with a NEW date (15:00) and NEW information (the eDir schema extensions) stamped with an OLD date (14:00)

- Depending on network latency, how long time takes to synchronise etc, different servers end up with different versions of the schema

- When replica synchronisation starts, objects will fail to synchronise with 603 & 608 errors as the sending and receiving servers have different copies of the schema


As soon as the install routine has booted from the NW6 issue CD (the first screen is usually the "Select Language" one) switch to the console screen (ALT+ESC) and set the local time to equal UTC for the rest of the tree.


The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.

  • Document ID:
  • 10074186
  • Solution ID: NOVL81981
  • Creation Date: 04Sep2002
  • Modified Date: 31Jan2003
    • NovellNetWare


Did this document solve your problem? Provide Feedback