151 Posts

September 12th, 2007 11:00

1. Does the DC error persist?
2. Did you install RepliStor with AD support?

151 Posts

September 12th, 2007 11:00

The 1st error indicates that the site you have installed RepliStor on is having difficulty communicating with a Domain Controller in the environment, as the description indicates.

Is this box with the error in the domain?

For the 2nd error, go to the Functions menu on the Source, ensure both Mirroring and Forwarding are enabled.

September 12th, 2007 11:00

Yes, the source box is a DOMAIN controller, so it is in the domain. The target machine is a stand-alone server, but it is also in the domain.

September 12th, 2007 11:00

The DC error is no longer there, but I'm not sure if I installed Replistor with AD support...is there a way I can tell?

151 Posts

September 12th, 2007 11:00

Yes, you can go to the registry of the box you saw the error on. Go to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RepliStorControl\Parameters

There is a DWORD called DisableActiveDir.

If the value is set to 1, then you are not using AD.
If the value is set to 0, then you are.

September 13th, 2007 04:00

That reg key does not exist on the source machine.

151 Posts

September 13th, 2007 05:00

What is the exact version you are using?

Help -> About RepliStor

September 13th, 2007 06:00

6.2.1.3

151 Posts

September 13th, 2007 07:00

If you run a 'set l' command you will see which DC this particualr DC is using for logon. Most likely it will be itself.

Let me know if you see the site object via ADSIEDIT.msc and the results of your reboot.

151 Posts

September 13th, 2007 07:00

Another thing to check...

Was this error generated after a reboot?
It is possible ReplIStor tried to query AD for the site list before the service was started.

Therefore, it is as if the DC was unavailable.
Check the System logs to correlate the time stamp of the message to see if a reboot took place at that time.

September 13th, 2007 07:00

Well, we have more than one DC in this location, so unless I rebooted before AD replication took place...possible. I have to reboot this DC this weekend. I'll let you know.

151 Posts

September 13th, 2007 07:00

Use ADSIEDIT.msc (2003 Support Tools from the CD-ROM).
Go to the following location in the domain partition:
CN=RepliStor,CN=EMC,CN=System,DC=company,DC=com

This will show you a list of sites that have been added during the installation of RepliStor when using Active Directory support. Basically, it is the list of sites that you have registered as a result of installing RepliStor.

If you do not see the DC listed here as part of your install of RepliStor, then you are most likely maintaining your site list for this box in the local registry.

Keep me posted.

September 13th, 2007 09:00

I have not re-booted yet, but both servers-source and target, appear in the ADSIEDIT path listed above.
No Events found!

Top