Novell Error 659
Favorite Rating: error -659 while running PKIDIAGThis document (3623691) is provided subject to the disclaimer at the end of this document. Environment NetWare 5.1 NetWare 6.0 Netware 6.5 Novell http://www.novell.com/documentation/nwec/?page=/documentation/nwec/nwec/data/al39nmi.html Cetificate Server Situation Can not create SSL Certificate DNS and IP SSL CertificateIP does not exist Step 6 Failed -659 error -659 while running PKIDIAG Resolution Correct Time Synchronization and then run PKIDIAG with Options https://www.novell.com/support/kb/doc.php?id=3623691 4, 5, 0 Additional Information Time is not in SyncFormerly known as TID# 10099441 DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:3623691Creation Date:02-APR-07Modified Date:31-MAY-12NovellNetWareNetIQeDirectory Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
Favorite Rating: -9011 & -659 errors http://www.novell.com/support/kb/doc.php?id=3481710 starting eDirectory DriverThis document (3481710) is provided subject to the disclaimer at the end of this document. Environment Novell Identity Manager 3.0eDirectory Driver https://helpdesk.stone-ware.com/portal/helpcenter/articles/edir-nds-health-check Situation When starting the eDirectory Driver the following errors are encountered.DirXML Log Event ------------------- Driver: \IDVAULT\DirXML\Bsure\VaultEdir Channel: Publisher Object: \MIHOUSE\ADM\bvd (IDVAULT\ADM\bvd) Status: Retry novell error Message: Code(-9011) eDirectory returned an error indicating that the operation should be retried later: novell.jclient.JCException: modifyEntry -659 ERR_TIME_NOT_SYNCHRONIZED Resolution Found that time was reporting as synchronized in the vault and eDirectory trees. However, the console prompt was receiving synthetic time errors. Looked at the partition root novell error 659 object, and the modification timestamp was dated 4 months in the future.After making the server running the drivers the master replica server, and repairing timestamps and delcaring a new epoch, Identity Manager started synchronizing objects.See TID 10073685 - Implications of running"Repair Timestamps and Declare a new epoch" DisclaimerThis Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND. Document ID:3481710Creation Date:09-JAN-08Modified Date:30-APR-13NetIQIdentity Manager Did this document solve your problem? Provide Feedback © Micro Focus Careers Legal close Feedback Print Full Simple Request a Call Follow Us Facebook YouTube Twitter LinkedIn Newsletter Subscription RSS
issues and how to do a health check.This information comes from an old Novell article, some specific information may not be valid anymore but the general concepts are.Troubleshooting NDS ProblemsEditor’s Note: "Technically Speaking" answers your technical questions, focusing on network management issues. To submit a question for a future column, please send an e-mail message to nwc-editors@nwconnection.com, or send a fax to 1-801-228-4576.Novell Directory Services (NDS) problems can range from minor irritations that eventually resolve themselves to significant corruption of the NDS database that only Novell Technical Services (NTS) can fix. This article focuses on NDS problems that fall somewhere between these two extremes. The types of NDS problems discussed in this article require you to do some troubleshooting but do not require you to know the inner workings of NDS in particular or client-server databases in general.BACKING UP THE NDS DATABASEYou should be aware that troubleshooting and correcting problems in the NDS database could potentially lead to the loss of critical network resource information. To protect this information, you should make a verified backup of the NDS database before you attempt to troubleshoot NDS problems. (See "Technically Speaking: Backing Up NDS,"NetWare Connection, Aug. 1998, pp. 43-45. You can download this article from http://www.nwconnection.com/aug.98/techsp88 (no longer available))In addition, you should be familiar with Novell’s NDS management utilities, such as the NetWare Administrator (NWADMIN) utility, the NDS Manager utility, the Partition Manager utility, and the DSREPAIR utility. You should also be familiar with the DSTRACE function at the server console.DETERMINING THE NDS PROBLEMIn most cases, you must use the DSTRACE function at the server console to determine the type of NDS problem you are experiencing. The DSTRACE function returns an NDS error code, which indicates the type of NDS problem that exists on the network.In this article, I will assume that you have already used the DSTRACE function to isolate a specific NDS error code. To learn mor