Re: event id:13552

Tech-Archive recommends: Fix windows errors by optimizing your registry

Well,

This was real fun. Yeah, I am being very sarcastic. Our update account
decided to log in on reboot going into Safe Mode w/ DS Restore Mode. It then
performed a DCPROMO and then applied EXCH2K SP3 for some reason. Afterwards,
the AD stopped on both servers and DC2 couldnt see DC1. Then DC1 couldnt see
the GC Server. Yeah!!. So I spent all day rebuilding my servers from scratch
because Backup Exec failed to start in Safe mode. Turns out that a pvl.mdb
file is required and wasnt there at all. It wasnt on any other server we had
nor on the disc that Veritas/Symantec claims it to be on. So restoring
SYSTATE was not going to happen via tape. So that left me manually rebuilding
the servers. Right now I am back at where I was before Journal_Wrap occured
again and the ADS stopped. Right now FRS runs for about 5-15 minutes then
stops. Event ID 13508 occurs and of course the lovely error for the service
stopping. This time though, DC2 cant replicate to DC1. If it wasnt for the
fun of what happened earlier, I would try that KCC idea again. But I been up
since 3am yesterday and it is now 1:22am. I am thinking of sleep. Anyway, I
could use some serious help here. I have been given full reign of my system
now. So any ideas are welcome. Thanks.

"Harj" wrote:

Hi,

It will not interfere with the end users as we are working on fixing
replication.
As long as the DC's and GC's are reachable, users will be ok.

Just make sure that the users are still pointed to a valid DNS server
is all I can think of.

Good luck

Harj Singh
Power Your Active Directory Investment
www.specopssoft.com


Allen wrote:
That was what I was refering to. I will give that a shot. Have you ever had
this interfere with users in a very noticable way? If not I will give this a
shot today. If it does interfere I will have to wait until Friday night to do
it. I havent done this part before so I want to make sure.



"Harj" wrote:

Hi,

Not sure what you mean by re-building the connectors but I would highly
recommend to let the KCC do it on its own and not for you to create
manual connection objects.

I would point both these DC's to the PDC emulator for primary DNS.
I would then run the following commands on both DC's
ipconfig /flushdns & ipconfig /registerdns & net stop netlogon & net
start netlogon.
Go to Sites/Services and delete the connection objects from both
machines.
Then stop and start the NTFRS service.
Trigger the KCC by right clicking the NTDS Settings under the Domain
controllers in Sites/Services, all tasks and click Check Replication
Topology.
Wait for the connection objects to be recreated and then look for any
errors in the event logs.

Good luck

Harj Singh
Power Your Active Directory Investment
www.specopssoft.com


Allen wrote:
Well, last night I transfered the 5 roles over to DC2. I also did a D2 on
DC1. Now the good news is that it rebuilt the SYSVOL with some help of
creating two directories. What I am concerned about right now is that DC2 is
not updating the profiles. I am starting to see events of 13508 on DC2
showing replication issues. It is failing to replicate from DC1 to DC2.

Would re-building the connectors be advised? Or would doing a Directory
Service restore on DC2 be recommended?

I am still trying to figure out why replication isnt completely working. I
am starting to think it has to do with RPC connections which is why I want to
rebuild the connection. But I would have to do this on a weekend at night.

Any suggestions are welcome. Thanks.

"Ada Pan [MSFT]" wrote:

Hello Allen,

How are you?

We have not heard from you regarding this issue. Please post back here at
your convenience if we can assist further.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.






.

Relevant Pages

  • Re: Netlogon not working when one DC is down..
    ... Verifying that the local machine dc2, ... Connecting to directory service on server dc2. ... Latency information for 6 entries in the vector were ignored. ... The File Replication Service SYSVOL ready test ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 Help
    ... Connecting to directory service on server tgcs001. ... The replication generated an error: ... Error Record 1, ProcessID is 1588 (DcDiag) ... established connection failed because connected host has failed to respond. ...
    (microsoft.public.windows.server.general)
  • Re: Cannot remove a lingering object with repadmin???
    ... configure loose replication for each DC, ... I'm having trouble removing a lingering object from a server that was ... So I performed repadmin /removelingeringobjects DC3 <DC2 GUID> ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication issue between domian controller server within same
    ... Earlier I have tried running dcdiag and below is some of the error that I ... From DC2 to DC1 ... The replication generated an error: ... If you don't have the support tools installed, install them from your server ...
    (microsoft.public.windows.server.active_directory)
  • Re: New Replication Project
    ... with 5 access clients connecting to an access db on server. ... Is the connection good enough to run Windows Terminal Server ... I would never use replication if there is an always-on WAN ... Client machines with an MS Access front end linked to MS Access ...
    (microsoft.public.access.replication)