Novell Home

My Favorites

Close

Please to see your favorites.

Error: "-613 Syntax violation" in report sync status

(Last modified: 16Jul2004)

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

fact

Novell NetWare 5.1 Support Pack 1 (NW51SP1.EXE)

Novell NetWare 4.11 Support Pack 8A (NW4SP8A.EXE)

Novell NetWare 5.0 Support Pack 5 (NW5SP5.EXE)

Novell Directory Services 8

Novell Directory Services 7

Novell Directory Services 6

Novell eDirectory 8.7

Novell eDirectory 8.6

Novell eDirectory 8.5

DSREPAIR.NLM 4.68a through 4.70z

DSREPAIR.NLM 5.21c through 5.25z

symptom

Error: "-613 Syntax violation"  in report sync status

Schema attributes CreatorsName and ModifiersName define their syntax as Distinguished Name.

Unable to install the first NetWare 6 server into the tree

Directory Services upgrade to eDirectory 8.5, 8.6, or 8.7 fails.

Error occurs in SET DSTRACE=+S

CreatorsName and\or ModifiersName attributes on an object have truncated values (instead of cn=[user].o=[organization], the value would have garbage characters, ie  ****#$%, etc.).

Error occurs on a server receiving a replica of a partition of which an eDirectory 8.5 or 8.6 server holds (or did hold) a copy.

change

DSREPAIR | Advanced Options Menu | Global Schema Operations | Post NetWare 5 Schema Update has been run on a NDS 7.xx server using DSREPAIR versions 5.21a through 5.25z or NDS 6.xx server with DSREPAIR 4.68a through 4.70z.

cause

DSREPAIR versions 5.21a through 5.25z or DSREPAIR 4.68a through 4.70z create attributes CreatorsName and ModifiersName.  DSREPAIR will add the syntax Distinguished Name to SCHEMA. NDS 85.xx and NDS 86.xx require the schema definition syntax to be Case Ignore String.  This discrepancy causes  -613 and -722 errors.

fix

Novell recommends the following patches, or higher:
1.  All NetWare 6.0 servers have Support Pack 3 applied
2.  All NetWare 5.1 servers have Support Pack 6 applied.
3.  All NetWare 5.0 servers have Support Pack 6a applied
4.  All NetWare 4.2 servers have Support Pack 9 with DS617.EXE

Patching to the Support Packs listed above on all NetWare versions will have the necessary DSREPAIR versions for the steps listed below. 

To download the DSREPAIR versions individually, you can download and extract DSREPAIR from the following patches at  http://support.novell.com/filefinder/ 

NetWare 4.2 -                             DSREPAIR Version 4.72c from DS617.EXE
NetWare 5.x NDS 7.xx -             DSREPAIR Version 5.29 from DS760c.EXE  
Net Ware 5.x NDS 8.xx -            DSREPAIR Version 10250.35 from DS883c.EXE
Net Ware 5.x NDS /85.xx -        DSREPAIR Version 10250.37 from  edir8530.exe
NetWare 5.1/6 NDS 8.6.2 -        DSREPAIR Version 10250.34 from EDIR862SP3.EXE

Step 2.  Determine which Case applies to your Tree. Three Different Cases are below.  

NOTE: Make Backups. It is wise to Load DSREPAIR - RC on all servers. This will create a backup of the database.

Verify you have the problem.  Do this by using DSBROWSE (for NDS 7, NDS 8, eDir 8.5, eDir 8.6, and eDir 8.7) or DSVIEW for (NDS 6.xx).

Steps for DSBROWSE
Load DSBROWSE | Choose Schema Browse | [Schema Root] | [Attribute Definitions] | and search for the attributes CreatorsName and ModifiersName.  Press enter on CreatorsName | View Attributes | Press enter on [ID Schema Value] | View Value Details | Look for Attribute Syntax:
If Case Ignore String is present - schema is correct and you do not have the problem.
If Distinguished Name is present - the problem exists - go to Step 1.

Steps for DSVIEW.NLM
Load DSVIEW | Choose 4. <Attribute Definitions> | Then use 1. <Next> to search for CreatorsName and ModifiersName. (You must go through all attributes one by one.) Once each is found, Look for Syntax:
If Case Ignore String is present - schema is correct and you do not have the problem.
If Distinguished Name is present - the problem exists - go to Step 1.

NOTE:  Sometimes DSBROWSE will show the correct syntax for the attributes, but the underlying Flaim layer of the database still has the problem.  The only way to fix the Flaim layer and clear the -613 errors is to follow this TID exactly.

Case 1:  The tree has NEVER had eDirectory 8.5, 8.6, 8.7 (eDir 85.xx, eDir 103xx.xx, eDir 104xx.xx) or greater installed and ALL servers currently are NDS 6.xx or 7.xx.  (If eDirectory 8.5/8.6/8.7 was installed and removed, see Case 3)

Fix for Case 1:  

1.  If there is a 7.xx server that holds a copy of [Root], load DSREPAIR 5.29 or greater  | Advanced Options Menu | Global Schema Operations | Post NetWare 5 Schema Update
2.   If all copies of [Root] are on 6.xx servers, load DSREPAIR 4.72b or greater | Advanced Options Menu | Global Schema Operations | Post NetWare 5 Schema Update.    

This should correct the problem and timestamp the attributes to propagate them through the tree. After executing the above DSREPAIR options, toggle out to the console prompt and force a schema sync
    
     Set DSTRACE=+Schema
     Set DSTRACE=*SSD
     Set DSTRACE=*SSA

Case 2:  The tree has NEVER had eDirectory 8.5, 8.6, 8.7 (eDir 85.xx, eDir 103xx.xx, eDir 104xx.xx) or greater installed .  NDS 8 (DS 8.xx) exists in the tree.  
(If eDirectory 8.5/8.6/8.7 was installed and removed, see Case 3)

Fix for Case 2: 

1.  On all servers in the tree that are NDS 8.xx Load DSREPAIR -A0 -RD (**Note 0 is zero**)
2.  On all servers in the tree that are NDS 6.xx/7.xx Load DSREPAIR - A7 - RD
3.  Add a replica of ROOT to the NDS 8.xx server and load DSREPAIR | Advanced Options Menu | Global Schema Operations | Post NetWare 5 Schema Update
4.  Exit out to the console prompt and force a schema sync. 

        Set DSTRACE=+Schema
        Set DSTRACE=*SSD
        Set DSTRACE=*SSA 

If you have Solaris servers in the NDS tree running NDS 8.xx, Call Novell Technical Support.

note

WARNING!!!  PLEASE SEE TID #10068235 - Error: -602 after running DSREPAIR -A0 BEFORE PROCEEDING WITH THIS STEP

fix

Case 3: eDirectory 8.5, 8.6, 8.7 (eDir 85.xx, eDir 103xx.xx, eDir 104xx.xx) or greater installed has been introduced into the tree at any time
(If eDirectory 8.5/8.6/8.7 was installed and removed, Case 3 applies)

Fix for Case 3:

1.  On all servers in the tree which are NDS 8, eDir 8.5, eDir 8.6 or eDir 8.7), load DSREPAIR -A0 -RD (**Note 0 is zero**)  it will execute and exit automatically.
On NT/2000, start DSREPAIR with -AZ option and choose repair local database.
2.  On all servers in the tree which are NDS 6.xx/7.xx Load DSREPAIR - A7 - RD  This repair option will remove any invalid attribute values from objects in the tree.
3.  On the server that holds Master of ROOT,  LOAD DSREPAIR | Advanced Options Menu | Global Schema Operations | Post NetWare 5 Schema Update .  

The Post NetWare 5 Schema update will recreate the Schema Attributes for CreatersName and ModifiersName with the correct syntax.


Run DSREPAIR 85.18 or greater found in the PREEDIRF.EXE  file on our support site on all NDS 8.xx or NDS 85.xx
Run DSREPAIR 10 on the NetWare 6 servers.
***NOTE - If eDirectory 8.6.1 has been installed, DO NOT use DSREPAIR.NLM version 10210.15. *** You MAY use one of the repairs above.

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

For additional information on eDirectory 8.7, please see the following solution.  NOVL81742 - Novell edirectory 8.7.x Readme Addendum

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.

  • Document ID:
  • 10065372
  • Solution ID: NOVL60780
  • Creation Date: 15Oct2001
  • Modified Date: 16Jul2004
    • NovellBeta

      NetWare

      eDirectory

Did this document solve your problem? Provide Feedback