krusebr
asked on
Error -659
I have had IPrint working on my new 6.5 network for a couple of weeks now
and had been updating printers using IPrint RPM Configuration for NDPS
Printers. I have been turning this feature on and off as need when I want
to install printers to new clients. Works great but I just tried to turn
it off by checking the "do not update worstations" box as I have
previously. It gave me an error "NDS Error -659 Time synchronization
services has detected a problem with an operation attempting to modify
replica information."
What is the problem? I have run DSREPAIR without any errors and Timesync
on servers looks good.
and had been updating printers using IPrint RPM Configuration for NDPS
Printers. I have been turning this feature on and off as need when I want
to install printers to new clients. Works great but I just tried to turn
it off by checking the "do not update worstations" box as I have
previously. It gave me an error "NDS Error -659 Time synchronization
services has detected a problem with an operation attempting to modify
replica information."
What is the problem? I have run DSREPAIR without any errors and Timesync
on servers looks good.
Did you check replica synchronization in dsrepair?
ASKER
I ran a DSREPAIR Unattended and received NO ERRORS.
I ran the report sync status and timesync check and received the following...
NetWare 1602.00 Directory Services Repair 10550.86, DS 10551.78
Log file for server ".COUGAR-1.mnw" in tree "MNW"
Start: Monday, August 15, 2005 12:36:39 pm Local Time
Retrieve replica status
Partition: .[Root].
Replica: .COUGAR-1.mnw 8-15-2005 12:35:26
Replica: .IS2.mnw 8-15-2005 12:35:38
Replica: .IS1.mnw 8-15-2005 12:35:26
Replica: .ELEM.mnw 8-15-2005 12:35:30
All servers synchronized up to time: 8-15-2005 12:35:26
Finish: Monday, August 15, 2005 12:36:40 pm Local Time
*** END ***
/************************* ********** ********** ********** ********** ********** */
NetWare 1602.00 Directory Services Repair 10550.86, DS 10551.78
Log file for server ".COUGAR-1.mnw" in tree "MNW"
Time synchronization and server status information
Start: Monday, August 15, 2005 12:37:00 pm Local Time
-------------------------- -+-------- -+-------- -+-------- ---+------ --+-------
DS.NLM Replica Time Time is Time
Server name Version Depth Source in sync +/-
-------------------------- -+-------- -+-------- -+-------- ---+------ --+-------
.COUGAR-2.mnw 10551.78 -1 Secondary Yes 0
.IS2.mnw 8.85 0 Secondary No + 7
.IS1.mnw 10551.78 0 Secondary Yes 0
.ELEM.mnw 8.85 0 Secondary Yes 0
.COUGAR-1.mnw 10551.78 0 Single Yes 0
I ran the report sync status and timesync check and received the following...
NetWare 1602.00 Directory Services Repair 10550.86, DS 10551.78
Log file for server ".COUGAR-1.mnw" in tree "MNW"
Start: Monday, August 15, 2005 12:36:39 pm Local Time
Retrieve replica status
Partition: .[Root].
Replica: .COUGAR-1.mnw 8-15-2005 12:35:26
Replica: .IS2.mnw 8-15-2005 12:35:38
Replica: .IS1.mnw 8-15-2005 12:35:26
Replica: .ELEM.mnw 8-15-2005 12:35:30
All servers synchronized up to time: 8-15-2005 12:35:26
Finish: Monday, August 15, 2005 12:36:40 pm Local Time
*** END ***
/*************************
NetWare 1602.00 Directory Services Repair 10550.86, DS 10551.78
Log file for server ".COUGAR-1.mnw" in tree "MNW"
Time synchronization and server status information
Start: Monday, August 15, 2005 12:37:00 pm Local Time
--------------------------
DS.NLM Replica Time Time is Time
Server name Version Depth Source in sync +/-
--------------------------
.COUGAR-2.mnw 10551.78 -1 Secondary Yes 0
.IS2.mnw 8.85 0 Secondary No + 7
.IS1.mnw 10551.78 0 Secondary Yes 0
.ELEM.mnw 8.85 0 Secondary Yes 0
.COUGAR-1.mnw 10551.78 0 Single Yes 0
What server has Master of [ROOT]?
Are the 8.85's NetWare 5.1? Do they have Read/Write replicas?
What is on IS2? According to replica status, it has the most recent timestamp, meaning some kind of DS operation took place there, and it apparently has some difficulty keeping in timesync.
Are the 8.85's NetWare 5.1? Do they have Read/Write replicas?
What is on IS2? According to replica status, it has the most recent timestamp, meaning some kind of DS operation took place there, and it apparently has some difficulty keeping in timesync.
ASKER
Yes, they are Netware 5.1. I want to upgrade to the same NDS as the 6.5 servers have but I am not sure how.
Here are the timesync files from the server above that has +7 and NO. The COUGAR-1 file is listed below also.
I see the other servers have a line that reads "TIME SOURCE = 10.34.9.2".
The IS2 server does not have this line. Should it? The COUGAR-1 server
is the MASTER Replica and Time Source. Thanks again for the help.
IS2 SERVER
# TIMESYNC Configuration Parameters
Configured Sources = OFF
DEBUG = 7
Polling Count = 3
Polling Interval = 36000
Service Advertising = ON
Synchronization Radius = 2000
Type = SECONDARY
NTP Client Port = 0
# TIMESYNC Configured time source list
-------------------------- ---------- -
Cougar-1 SERVER
# TIMESYNC Configuration Parameters
Configured Sources = OFF
DEBUG = 7
Polling Count = 3
Polling Interval = 600
Service Advertising = ON
Synchronization Radius = 2000
Type = SINGLE
NTP Client Port = 0
-------------------------- ----------
Here are the timesync files from the server above that has +7 and NO. The COUGAR-1 file is listed below also.
I see the other servers have a line that reads "TIME SOURCE = 10.34.9.2".
The IS2 server does not have this line. Should it? The COUGAR-1 server
is the MASTER Replica and Time Source. Thanks again for the help.
IS2 SERVER
# TIMESYNC Configuration Parameters
Configured Sources = OFF
DEBUG = 7
Polling Count = 3
Polling Interval = 36000
Service Advertising = ON
Synchronization Radius = 2000
Type = SECONDARY
NTP Client Port = 0
# TIMESYNC Configured time source list
--------------------------
Cougar-1 SERVER
# TIMESYNC Configuration Parameters
Configured Sources = OFF
DEBUG = 7
Polling Count = 3
Polling Interval = 600
Service Advertising = ON
Synchronization Radius = 2000
Type = SINGLE
NTP Client Port = 0
--------------------------
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yes, it is
i will add it
i will add it
ASKER
Thanks again. Adding that line to the other two servers that did not have it worked great.
No more errors when performing RPM Config changes.
No more errors when performing RPM Config changes.