|
Home > Archive > Application Center Administration > July 2006 > Partial Synchronization
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Partial Synchronization
|
|
| Tom Goodman 2006-05-31, 7:14 pm |
| Every time synchronization occurs, I get an error in the event log as follows:
Event Type: Error
Event Source: Application Center
Event Category: Replication
Event ID: 5082
Date: 5/31/2006
Time: 1:15:49 PM
User: N/A
Computer: xxxxxxx
Description:
__CLASS:
MicrosoftAC_Replication_Session_DriverEv
ents_UpdateListApply_ObjectSetFailed_Eve
nt
__SERVER: xxxxxxxx
ServerGUID: {58D7478E-2253-471E-A6E2-D0BE8779C32A}
DriverID: NET
EventId: 5082
GUID: {848B85B3-CE5C-4BC6-8813-BF632392DF66}
Path: WINS
ReplicationID: Cluster Configuration Settings
ReplicationJobID: <servername>X1149095737X909981X1ae4da0
Status: 0x80070057
StatusMessage: The parameter is incorrect.
TimeGenerated: 5/31/2006 5:15:49 PM
Type: 1
DisplayName: Replication Session DriverEvents UpdateListApply ObjectSetFailed
The server OS is W2K SP4 with AC SP2. I only found 2 articles on Technet. I
also reviewed the event troubleshooting information for this event to no
avail.
How can I determine which object configuration can't be updated?
| |
| WenJun Zhang[msft] 2006-06-05, 1:19 pm |
| This may be a networking related error. You'd best open a support incident
to troubleshoot it in detail. Below is a former case with solution for your
reference:
"The Front End nic had netbios installed and it had the name of the server
registered. Backend nic did not have netbios enabled. We switched that and
did a
nbtstat -RR
and that resolved that but we are still getting 5082.
WE checked for differences on the NICs and found that on the member server,
the management NIC did not have "Register this connection's addresses in
DNS" checked. We checked the box and the error still happened. We also
removed the default gateway from the Front End and added it to the back
end. Same problem.
Finally, we move the NIC with the defaultgateway to the top of the binding
order. Remove the WINS servers from the front end nics since we removed
netbios from the frontend nics and thus wins would not be used. We did a
full synchronization and the 5082 went away for good."
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
| |
| WenJun Zhang[msft] 2006-07-03, 1:20 am |
| This may be a networking related error. You'd best open a support incident
to troubleshoot it in detail. Below is a former case with solution for your
reference:
"The Front End nic had netbios installed and it had the name of the server
registered. Backend nic did not have netbios enabled. We switched that and
did a
nbtstat -RR
and that resolved that but we are still getting 5082.
WE checked for differences on the NICs and found that on the member server,
the management NIC did not have "Register this connection's addresses in
DNS" checked. We checked the box and the error still happened. We also
removed the default gateway from the Front End and added it to the back
end. Same problem.
Finally, we move the NIC with the defaultgateway to the top of the binding
order. Remove the WINS servers from the front end nics since we removed
netbios from the frontend nics and thus wins would not be used. We did a
full synchronization and the 5082 went away for good."
Best regards,
WenJun Zhang
Microsoft Online Partner Support
This posting is provided "AS IS" with no warranties, and confers no rights.
|
|
|
|
|