Does the 'server1' computer account exist in AD?

If it is an old machine, it may be part of the Site List as ReplIStor was not gracefully removed from it.

Go to dsa.msc on a DC, then go to View -> Advanced Features.
Browse to the System -> EMC -> RepliStor folder.

Does the 'server1' site still exist? If so, proceed to delete it.

Start here and let me know about the 'server1' and if it still exists.

Duncan

I recommend you open a case with support. RepliStor installs a folder in the Domain container of Active Directory and uses it to determine some of the local settings. There is no danger to the AD from this message but it is possible that there is something corrupted from a RepliStor point of view. You can also disable the integration with AD.

The best thing would be to open a case with support just to confirm whether the object is there in AD. This will require installing a Microsoft tool called ADSIEDIT.msc from the Windows installation CD.

The "EMCCNF:7c44b651-5391-408d-8993-a748df62e24d" object got created due to an Active Directory conflict. This is how AD handles a duplicate name issue and it may have occurred because the 'server1' machine may have crashed or lost its connection with AD in some fashion.

Take a look at the following TechNet article that describes this issue:
http://technet.microsoft.com/en-us/library/bb727059.aspx

The CNF object can typically be deleted as long as the computer accounts you have in AD are intact and you know there are no issues with them. This will most likely be your quick fix.

After you delete the object, Restart the RepliStor Server service and the object should get created in the correct spot.

FYI, I was able to re-produce the error you recieved (There is no such object on the server) by deleting my site from AD and restarting the service. Moving forward, any subsequent restarts did not produce this error.

Duncan

John I have ADSI Edit installed on a admin machine.

The object exists but it is as I described above. An object exists for both the DR and Production servers. The production one looks odd with that funky character in the name.

We replistor setup so our imaging system in production sends over everything to our DR server. We need AD integration in case we need to fail over to the DR server. Should only one object exist even though it is installed on both systems?

The name of the server should exist as the actual name of the server, not the GUID. You might try renaming the entry to the correct name. Then, go into the Site list in the RepliStor GUI and change something in the site properties, such as the Description field. That should refresh the entry in AD.

Server1 is my source server so it has always existed in AD. The target server is called DR-server1.

What I see in dsa.msc on a DC in the sytem folder is odd. There are actually two entries for EMC -> Replistor

One shows as EMC and the other shows as
EMCCNF:7c44b651-5391-408d-8993-a748df62e24d with a square box after the EMC

The EMC -> Replistor folder on the 1st one has my DR server in there

The EMC with the funky numbers -> Replistor folder has my production server (server1) in there.

Is this odd or should it exist because replistor is installed on both machines?

It looks like this

CN=System
CN=EMC
CN=Replistor
CN=DR-SERVER-01


CN=EMC□CNF:7c44b651-5391-408d-899-a7a8df62e24d
CN=Replistor
CN=SERVER-01

Thanks Duncan!

So just delete this entry
CN=EMC□CNF:7c44b651-5391-408d-899-a7a8df62e24d

Then restart the replistor server service on my primary box or both? Should I stop forwarding first?

Again thanks for your help.

That is correct, delete the top part of that tree and restart the RepliStor Server service on the Source, server1.

There is no need to stop Forwarding.
If you have an Alias, it would be a good practice to Deactivate it first.

After you do the above work, go to AD and see if the server1 object is put in the correct spot. If it is, you may still get 1 more error. Any further service restarts will be fine.

If the object does get created, try a Repair of teh product via Add/Remove Programs.

Let me know if you ahve any issues.
Duncan

The good news is that this Site List and the AD integration has no bearing on replciation. It is simply to provide a common Site List in the environment.

I see that you have 2 options...

1. Delete the site and restart the service and see if the site gets re-created in the correct container.

2. Uninstall RepliStor.
If this removes the site, re-install and let it create the site again.
If this does not remove the site, delete it manually and the re-install. The Site should get put in to the correct location.

You can use the following commands to preserve your Spec's and Settings:
rep_srv cmd specexport/specimport
rep_srv cmd configexport/configimport


NOTE: RepliStor is coded to add objects to the EMC -> ReplIStor container. It is not coded to use the "CNF" object you happen to run in to.

This looks to have solved the problem.

I did get that last AD error but the server object was created correctly after delete and restart of the service.

Thank you very much for your help!