Prev: AD GPO to control Windows Firewall Settings
Next: Logon Failure: The target account name is incorrect.
From: Allen on 7 Sep 2006 01:25
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.
> > > > >
> > > > >
> > >
> > >
>
>
From: Allen on 7 Sep 2006 01:25
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.
> > > > >
> > > > >
> > >
> > >
>
>
From: Ada Pan [MSFT] on 12 Sep 2006 03:42
Hello Allen,

After reviewing the post log, I would appreciate it if you could help in
gathering the following information first:

Based on my experience, the issue could be related to several factors. To
troubleshoot the issue, we usually need to spend quite some time to perform
steps to find the problem causer due to complexity on technical side. I
appreciate your understanding and cooperation during the troubleshooting
process.

1. Run FRSDiag.exe on the DC1 and DC2.

File Replication Service Diagnostics Tool (FRSDiag.exe)
http://www.microsoft.com/downloads/details.aspx?FamilyId=43CB658E-8553-4DE7-
811A-562563EB5EBF&displaylang=en

2. Export the following registry key from the DC1 and DC2. NOTE: Before
sending the exported registry files to us, please change the file extension
from .reg to .txt.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs

3. Generate a Directory Services Edition (Mpsrpt_dirsvc.exe) of MPS report
on DC1 and DC2. For detailed instructions, please refer to the following MS
KB article:

818742.KB.EN-US Overview of the Microsoft Configuration Capture Utility
(MPS_REPORTS)
http://support.microsoft.com/default.aspx?scid=KB;EN-US;818742

My e-mail address is: < v-adapan(a)Microsoft.com >.

Hope this helps.

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.

From: Allen on 12 Sep 2006 07:28
Ada Pan,

Thanks for helping me out here. I thought of the FRSDiag but I ran into a
bind on it. Since it requires .Net Framework 1.1 I cant use it. We dont have
that installed and we cant install it because of our security requirements.
They wont bend on this even though it will really help me fix it. I am going
to run the MPS report tool and I will get that to you as soon as possible. Do
you know of any tools that run similar to FRSDiag that doesnt use .Net
Framework? I dont know of any but I will do some looking around. Thanks again.

"Ada Pan [MSFT]" wrote:

> Hello Allen,
>
> After reviewing the post log, I would appreciate it if you could help in
> gathering the following information first:
>
> Based on my experience, the issue could be related to several factors. To
> troubleshoot the issue, we usually need to spend quite some time to perform
> steps to find the problem causer due to complexity on technical side. I
> appreciate your understanding and cooperation during the troubleshooting
> process.
>
> 1. Run FRSDiag.exe on the DC1 and DC2.
>
> File Replication Service Diagnostics Tool (FRSDiag.exe)
> http://www.microsoft.com/downloads/details.aspx?FamilyId=43CB658E-8553-4DE7-
> 811A-562563EB5EBF&displaylang=en
>
> 2. Export the following registry key from the DC1 and DC2. NOTE: Before
> sending the exported registry files to us, please change the file extension
> from .reg to .txt.
>
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs
>
> 3. Generate a Directory Services Edition (Mpsrpt_dirsvc.exe) of MPS report
> on DC1 and DC2. For detailed instructions, please refer to the following MS
> KB article:
>
> 818742.KB.EN-US Overview of the Microsoft Configuration Capture Utility
> (MPS_REPORTS)
> http://support.microsoft.com/default.aspx?scid=KB;EN-US;818742
>
> My e-mail address is: < v-adapan(a)Microsoft.com >.
>
> Hope this helps.
>
> 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.
>
>
From: Ada Pan [MSFT] on 13 Sep 2006 04:58
Hello Allen,

To provide more accurate suggestions for you, please first send us the
reports so we can check the reports to see if other info is needed. Please
take your time to collect the reports and send me at your earliest
convenience. I look forward to hearing from you.

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.

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5
Prev: AD GPO to control Windows Firewall Settings
Next: Logon Failure: The target account name is incorrect.