-608 error on NFAUUSER object in report synchronization status

  • 3304337
  • 24-Jan-2008
  • 26-Apr-2012

Environment

Novell eDirectory 8.7.3.9 for NetWare 6.5
Novell eDirectory 8.7 for All Platforms

Situation

1:Preparing for server migration, Report Synchronization Status in DSREPAIR shows -608, -663, and -625 errors. The -608 errors are regarding the NFAUUSER object. This object is created when Native File Access is installed and is used internally to manage eDirectory operations on behalf of NFS / NFAU.

2: Error -608 in Report Synchronization pointing to NFAUUser

Resolution

Option 1:
Delete the NFAUUSER object. In some cases, it is possible the object isn't created properly and can interfere with synchronization. If needed in the future, the object can be recreated with schinst -n -w.

Option 2:
Some times the -608 error in Report sync pointing to NFAUUser would be because of attribute corruption or attribute missing.
From iMonitor  select the NFAUUser and check for which attribute the -608 is pointing to and then add that particular attribute using iManager
For example:

"userPassword" attribute should probably be an optional attribute to the "User" class in tree schema. Use iManager and select the schema role and select "Class Information" task. List of class entries should appear ... scroll down and highlight "User" and then select the View button. This will show details of the "User" class object in schema. There will be a link in the middle of the screen titled "Update optional attribute" click on it. Now it will pop up new window with 'Available optional attributes:' and 'Optional attributes:' Scroll down the list of 'Available optional attributes' and locate the "userPassword" attribute and select it to add it to the list for Optional attributes. Click on OK  and now "userPasword" should be in list for 'Attributes' for the 'view' of the "User" class in schema. This should resolve the -608 error in report synchronization.


Feedback service temporarily unavailable. For content questions or problems, please contact Support.