Error: -608, Illegal Attribute since introducing NetWare 6

(Last modified: 15Jan2003)

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

fact

Novell eDirectory 8.6 for NetWare 6

Novell NetWare 6.0

symptom

Error: -608, Illegal Attribute since introducing NetWare 6

Non NetWare 6 servers are reporting "All Processed = YES"

Error occurs in SET DSTRACE=+s

change

Introduced the first NetWare 6 server into the tree.

cause

NetWare 6 schema has not been propagated to the rest of the servers in the tree.  This seems to only occur once in awhile when the first NetWare 6 server into the tree is migrated from either NDS 6.x or NDS 7.x and is the Master of Root.

fix

Use NDS iMonitor to compare schemas between the two NetWare 6 servers.

If the NetWare 6 server has unique Classes and/or Attributes, the differences will be listed in the SCHEMA.TXT file. There may be Definition differences. These will not cause the -608 errors.

***NOTE - If there are unique Classes and/or Attributes see the explanation below.  If there are NO differences, then there is not a problem in schema.

Definition differences:

There are 3 resolutions for this problem, some can be more destructive than others:  As always, it is wise to create backups of all server databases by running DSREPAIR -RC or loading DSREPAIR | Advanced options menu | NDS Archive Options on each server in the tree.  The three solutions below assume that the NetWare 6 server holds a copy of the ROOT partition.

1.  Call Novell Technical Support for a dial in to remedy this problem.

2.  On the NON NetWare 6 server,  Load DSREPAIR -a | Advanced Options Menu | Global schema operations | Authenticate as admin or one having rights to the ROOT of the tree | Reset Local Schema.  This will allow the NON NetWare 6 server to receive the correct schema from the NetWare 6 server. - This needs to be done on all servers in the tree.

3. Last Resort - Declare a schema epoch on the NetWare 6 server.
*** NOTE declaring a schema epoch CAN be very destructive if incorrect schema is sent.  See TID# 10066252 Declaring a schema epoch.


____________________________________________________

This sync was taken from the NetWare 6 server.   .SERVER2.PRV.TREE_NAME. in this trace is a Non NetWare 6 server

Multiple packet send of Schema...
Sending forward reference for class .domain.[Class Definitions].[Schema Root]
Sending class 2001/11/25 13:22:13, 6, 10786, <Server>.
Sending class 2001/11/25 13:22:13, 6, 10943, <Tree Root>.
Sending class 2001/11/25 13:22:13, 6, 10771, <NSCP:Nginfo3>.
Sending class 2001/11/25 13:22:13, 6, 10772, <NSCP:NetscapeMailServer5>.
Sending class 2001/11/25 13:22:13, 6, 10773, <NSCP:MailGroup1>.
Sending class 2001/11/25 13:22:13, 6, 10774, <ndsContainerLoginProperties>.
Multiple packet send of Schema...
Sending class 2001/11/25 13:22:13, 6, 10775, <ndsLoginProperties>.
Sending class 2001/11/25 13:22:13, 6, 10945, <domain>.
Setting .SERVER2.PRV.TREE_NAME. in SchemaSyncList, flags 0x1, apply 0xffffffff
Removing .SERVER2.PRV.TREE_NAME. from SchemaSyncList, type 0x2
Schema update end, success.
2001/11/28  8:40:57 * SchemaPurger processing deleted classes.
DCRequest failed, illegal attribute (-608).
Sending [0000807e] <.USER1.PRV.TREE_NAME.> from Sync Point 2 failed, illegal attribute (-608)
3C050589:62416752:d04a72c0:047 Sync - objects: 139, total changes: 262, sent to server < .SERVER2.PRV.TREE_NAME..>.
3C050589:62416752:d04a72c0:047 Sync - Process: Send updates to < .SERVER2.PRV.TREE_NAME..> failed, illegal attribute (-608).

For additional information on eDirectory 8.6, please see the following solution.   TID# 10066455 - eDirectory 8.6 Readme Addendum

document

Document Title: Error: -608, Illegal Attribute since introducing NetWare 6
Document ID: 10066686
Solution ID: NOVL65760
Creation Date: 10Dec2001
Modified Date: 15Jan2003
Novell Product Class:NetWare
Novell eDirectory

disclaimer

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.