02-06-2008 12:50 AM
Event Type: Error
Event Source: Replication Exec RSA
Event Category: None
Event ID: 1030
Date: 2/6/2008
Time: 1:49:43 AM
User: N/A
Computer:
Description:
Replication Exec service initialization failed. : Initialization failed. : Internal error: Unable to resolve a name to an IP address.
10-07-2008 04:49 AM
I've run into the same issue with a system that was "rough cloned" from another and have yet to find a solution.
My next steps are to remove every trace of the application using something like Revo Uninstaller, reboot, reinstall and try it all over again.
10-07-2008 08:19 AM
Please post any additional info if you are able to resolve this. Thanks.
10-07-2008 08:33 AM
well that was a complete bust.
The uninstall seemed to go well until the clear up and then it list 45,000+ registry entries that had been left behind. Which upon reviewing a sample blatantly was not right.
Unfortunately it's back to the drawing board with this one. We may sysprep the machine or even rebuild it this weekend but unfortunately it is a production machine now so working on it is a bit tricky.
10-09-2008 11:25 PM
ok.. I had this issue today after cloneing a serverin esx. After much painfull kicking of things i finally worked out what was going on!!
The initial server and the new one have the same MachineID. This is defined in a key in the registry that is not removed during uninstall or reinstall.
HKEY_CLASSES_ROOT\CLSID\{blah blah blah}\MachineID\
This MachineID in the string is refered to in the RMS database and will only allow one instance connected at any time.
To fix ...
Find the MachineID of the original machine in the database by using the srtool provided with app.
run srtool
type:- list all servers
write down the id of the machine you cloned
or look in the C:\Program Files\VERITAS\Replication Exec\Logs\efc.log
You should see a entry like
"Machine name is MYVRE01 (05020104-e522e6f0-93f4-d811-b2f6-505054503030).
Platform is Windows NT 5.2 "
uninstall VRE from the new cloned machine
After restart go into regedit and search fot the string (as in above "05020104-e522e6f0-93f4-d811-b2f6-505054503030")
delete the key and then repush the client.
This worked for me and hope it sorts out your issues :)
10-14-2008 05:46 AM
Crabcam,
Thanks for this. After following your instructions, i was now able to see the machine in the Replication Exec Console now but the machine is showing Offline. All 3 services are started on the this machine and restarting them did not resolve it. Did you run into this?
07-13-2009 12:59 PM